Demo Discussion
Forum Config Examples Contributions Vulnerabilities
  Discussion forum about ELOG, Page 525 of 808  Not logged in ELOG logo
 Find |  Login |  Help 
 Full | Summary | Threaded | Hide attachments  Show only new entries    6457 Entries 
Goto page Previous  1, 2, 3 ... 524, 525, 526 ... 806, 807, 808   Next  
ID Date Icon Author Author Email Category OS ELOG Version Subjectdown
  69860   Mon Jan 6 14:59:06 2025 Reply Stefan Rittstefan.ritt@psi.chBug reportLinux | Windows | Mac OSXELOG V3.1.5Re: Equation Editor does not work

Apparently Codecogs have changed their URL. I tried the update from 

  https://editor.codecogs.com/depr/CK_Editor_v4x.php

but it did not help. The CK Editor v5 is quite different from v4 (like they require node.js to install it), so putting it into elog would be some major work. 

Stefan

Dominic wrote:

is there any update on this bug? Has anyone else observed the same problem?

Dominic wrote:

Hi!

I am not sure if this is a know issue: it seems that the equation editor does not work anymore. Is there any fix or alternative method to type latex formula in the log? 

Thank you!

 

 

  67914   Tue May 19 16:34:20 2015 Reply Andreas Luedekeandreas.luedeke@psi.chQuestionLinux2.9.2Re: Entry size too large for email notification
Hi Jacky,
if I read the source code correctly then the maximum size of a base64 encoded email is hard coded to be 10 MB in elogd.h (recompile after changing it):
#define MAX_CONTENT_LENGTH 10*1024*1024
But I think that an 2.2 MB image should easily fit into that.
Andreas
Jacky Li wrote:

Hi,

I am doing an inline image that is about 2.2 MB.  When I do a submit, I got the following message:

Error sending Email via <i>"<email server>"</i>: Entry size too large for email notification.

May I know what is the limit of the entry size and how do I change it?  Thank you.

Jacky
  67929   Fri May 22 13:43:14 2015 Reply Stefan Rittstefan.ritt@psi.chQuestionLinux2.9.2Re: Entry size too large for email notification

The size is defined by the variable MAX_CONTENT_LENGTH in elogd.c which is set to 10 MB. But email attachments are encoded in ASCII form, so they take useually 3-4 times the space of the binary format. If you have problems with large emails, you can use the option "Email Format = 111" which causes only the names of attachments to be included in email notifications. Users can then still click on the elog link inside the email notification and download the attachment from the elog page.

Jacky Li wrote:

Hi,

I am doing an inline image that is about 2.2 MB.  When I do a submit, I got the following message:

Error sending Email via <i>"<email server>"</i>: Entry size too large for email notification.

May I know what is the limit of the entry size and how do I change it?  Thank you.

Jacky

 

  68829   Fri Jul 13 19:14:21 2018 Reply Lars Martinlmartin@triumf.caQuestionLinux2.9.2Re: Entry size too large for email notification

Wouldn't it make sense for ELog (by default) to still notify, but not send the attachments by e-mail if the size limit is reached?

Andreas Luedeke wrote:
Hi Jacky,
if I read the source code correctly then the maximum size of a base64 encoded email is hard coded to be 10 MB in elogd.h (recompile after changing it):
#define MAX_CONTENT_LENGTH 10*1024*1024
But I think that an 2.2 MB image should easily fit into that.
Andreas
Jacky Li wrote:

Hi,

I am doing an inline image that is about 2.2 MB.  When I do a submit, I got the following message:

Error sending Email via <i>"<email server>"</i>: Entry size too large for email notification.

May I know what is the limit of the entry size and how do I change it?  Thank you.

Jacky

 

  68837   Mon Aug 27 13:07:28 2018 Reply Stefan Rittstefan.ritt@psi.chQuestionLinux2.9.2Re: Entry size too large for email notification

That's how it is implemented. If you use

Max email attachment size = 1000000

then attachments below 1 MB are sent as attachments, and if the attachment is above 1 MB, then only a link to the attachment in the elog is sent.

Stefan

Lars Martin wrote:

Wouldn't it make sense for ELog (by default) to still notify, but not send the attachments by e-mail if the size limit is reached?

Andreas Luedeke wrote:
Hi Jacky,
if I read the source code correctly then the maximum size of a base64 encoded email is hard coded to be 10 MB in elogd.h (recompile after changing it):
#define MAX_CONTENT_LENGTH 10*1024*1024
But I think that an 2.2 MB image should easily fit into that.
Andreas
Jacky Li wrote:

Hi,

I am doing an inline image that is about 2.2 MB.  When I do a submit, I got the following message:

Error sending Email via <i>"<email server>"</i>: Entry size too large for email notification.

May I know what is the limit of the entry size and how do I change it?  Thank you.

Jacky

 

 

  66818   Fri May 14 08:57:07 2010 Reply Stefan Rittstefan.ritt@psi.chQuestionWindows2.7.8-2294Re: Entry merging

Eric Krise wrote:

Is there a way to merge existing entries from several logbooks into a single logbook? 

Only manually: Add "Move to" to you set of commands via "Menu commands = ...", then select one or more entries, and move them to your target logbook.  

  66819   Fri May 14 16:50:53 2010 Reply Eric KriseEric.Krise@cmicompany.comQuestionWindows2.7.8-2294Re: Entry merging

Stefan Ritt wrote:

Eric Krise wrote:

Is there a way to merge existing entries from several logbooks into a single logbook? 

Only manually: Add "Move to" to you set of commands via "Menu commands = ...", then select one or more entries, and move them to your target logbook.  

 Got it! Thanks...

  1959   Mon Sep 25 21:09:58 2006 Reply Stefan Rittstefan.ritt@psi.chQuestionWindows2.6.2Re: Entry Submission Help

kcmin wrote:
1. When an entry is submitted is it possible to have it return to the submit page instead of a summary of the entry. In the ELog.cfg syntax on the site it mentions something about this. However It says something about a file being present in the resource directory. I am not sure what to do here.


You can hand-write a HTML file which gets displayed after submission, but that's probably not what you want. Unfortunately there is no option to go back to the submit page, so you have to click New again. If you want to enter a bulk of data, you can also do a CSV import. Maybe that's easier for you. Just write a comma-separated-value file, and import it via "CSV Import".


kcmin wrote:
2. When you submit an entry is it possible for the fields to stay set to the value that was selected on submission of the last entry. You would need to still be able to change them though.


The Duplicate command was made for that. Just select an entry which is close to your new one (might be the last one entered), and click Duplicate. This gets you to what you want.
Goto page Previous  1, 2, 3 ... 524, 525, 526 ... 806, 807, 808   Next  
ELOG V3.1.5-3fb85fa6