Entry size too large for email notification, posted by Jacky Li on Tue May 19 12:27:01 2015
|
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. |
Re: Entry size too large for email notification, posted by Andreas Luedeke on Tue May 19 16:34:20 2015
|
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
|
|
Re: Entry size too large for email notification, posted by Lars Martin on Fri Jul 13 19:14:21 2018
|
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 |
|
Re: Entry size too large for email notification, posted by Stefan Ritt on Mon Aug 27 13:07:28 2018
|
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. |
|
Changing of entries after expired time restriction by synchronisation, posted by Gino Guenzburger on Thu Aug 16 13:33:39 2018
|
I'm working on setting up an elog as lab-journal in our group with the following set-up:
The elog is running on a server, with no back-end access for the users.
Multiple people will use it, all loging in with the
same user-name and password.
The entries submitted to the log-book can only be edited for 24hours, as defined by the "Restrict edit time= |
Problem with eloglang.german_UTF8, posted by Andreas Luedeke on Tue Aug 7 10:53:45 2018
|
I had a problem with restarting ELOG since about a year, and finally I found the culprit. I just want to share it here, to prevent anyone else to make
the same mistake,
Apparently the files resources/eloglang.* are rather sensitive to the syntax. But it doesn't tell you: no warning or error message comes |
|
edit templates from config page, posted by Stefano Lacaprara on Thu Jun 14 13:12:02 2018
|
Dear all,
I have some logbook which uses preset text depending on some option values, and uses text files for this.
|
|
Re: edit templates from config page, posted by Stefan Ritt on Thu Jun 14 13:20:26 2018
|
> Dear all,
> I have some logbook which uses preset text depending on some option values, and uses text files for this.
>
|
|
Re: edit templates from config page, posted by Andreas Luedeke on Thu Jun 14 18:17:07 2018
|
> Dear all,
> I have some logbook which uses preset text depending on some option values, and uses text files for this.
>
|
|
Re: edit templates from config page, posted by Stefan Ritt on Thu Jun 14 19:17:41 2018
|
As always, Andreas has clever ideas. Never thought about this possibility.
Stefan |
number of entries in Login user list, posted by Janusz Szuba on Wed Jun 13 18:08:06 2018
|
Hi,
could it be possible to increase the limit of entries in Login user list from 100 to somewhat reasonably higher? Like twice or 3 times as
much. Similar limit exist also on Admin user list, which is afair 10, could this also be increased? |
|
Re: number of entries in Login user list, posted by Andreas Luedeke on Thu Jun 14 12:37:22 2018
|
Hi Janusz,
You can change the following line in elogd.h and recompile:
#define MAX_N_LIST 100 |
|
Re: number of entries in Login user list, posted by Janusz Szuba on Thu Jun 14 13:07:32 2018
|
Thanks, good point, I was not sure that in case of other lists which will be changed as well, there will not be any problems, like overflow, etc.
Regarding admin list, now I remember, that was the limit to send email notification in case of registration requests. But actually it is not
important right now. |
|
Re: number of entries in Login user list, posted by Stefan Ritt on Thu Jun 14 13:17:33 2018
|
Well, many arrays based on MAX_N_LIST are created on the heap memory, and if you exceed that, elogd simply crashes. There are compile options to increase
the stack and heap size, but that depends on the operating system and the compiler. The value of 100 has been proven to work everywhere. If you increase
it, you're on your own. |
|
html mode with preset text template cannot be read by newly updated MS-Edge browser, posted by utomoadji wisnubroto on Wed Jun 6 18:25:32 2018
|
i have elog tab configuration with preset text as follow :
=====================================================================
[Shift Entry] |
|
shiftcheck restrict edit, posted by Xuan Wu on Thu May 24 08:53:50 2018
|
Hi all,
There are options "Restrict edit" and "Restrict edit time" for general logbooks, but it seems not work for shiftcheck logbook.
I think the function only author can change their own entry is necessary for shiftcheck too. Any suggestion would be hightly appreciated. |
|
Re: shiftcheck restrict edit, posted by Xuan Wu on Wed Jun 6 02:41:32 2018
|
Is there a way to restrict other author to edit the custom input form submitted?
Xuan
Wu wrote:
Hi all, |
|
text area height, posted by Giuseppe Cucinotta on Fri Jun 1 17:08:48 2018
|
Hi,
I wonder if it is possible to set a minimum default value for the height of the text box when submitting new entries. If I understood well, by
default the text box height automatically resizes in order that all the elements of the page are visible. Actually for our needs having a minimum |
|
Re: text area height, posted by Stefan Ritt on Tue Jun 5 10:12:06 2018
|
Have you tried
Message height = ...
unit is number of text lines. |
Re: text area height, posted by Giuseppe Cucinotta on Tue Jun 5 15:06:18 2018 
|
I tried with Message Height = 100 inside the conifguration of my logbook, but nothing changed as you can see in the first picture...
What I'm looking for is a way, if possible, to start by default with a wider message box, someting like fig2. For our purpose, using wide
tables, it would be very useful to have a wider message box in order to have a full look to the message content, and also having it by default without |
|
Re: text area height, posted by Stefan Ritt on Tue Jun 5 21:37:26 2018
|
The message height option only works if you select either "ELCode" or "plain" for encoding (this can also be made as default in the
config file). For the HTML editor, the size is set internally and I don't have any influenc on it.
Stefan |