Re: Error: Entry text too big. Please increase TEXT_SIZE and recompile elogd, posted by Stefan Ritt on Mon Nov 28 11:56:06 2016 
|
I guee you tried to paste an image into the text area, and your browser somehow converted this into a text entry, which then of course can become very
long. Elog since vesion 3 supports drag-and-drop. You can drop an image from your local disk into the "Drop attachemnts here..." box at the bottom
of this page. You can also drag an image directly to the text box like this one: |
Re: Error: Entry text too big. Please increase TEXT_SIZE and recompile elogd, posted by Xuan Wu on Wed Nov 30 02:29:36 2016
|
Thanks for your advice! I've test that dropping an image from my local disk into the text box with Elog-3.1.2. It did work. However, I
still have a question want to ask that When I paste a small image into the text area, I can submit it successfully. But when I paste a bigger one, it will
say "Entry text too big. Please increase TEXT_SIZE and recompile elogd". And There's the same result in https://midas.psi.ch/elogs/Linux+Demo/. |
|
Re: Error: Entry text too big. Please increase TEXT_SIZE and recompile elogd, posted by Stefan Ritt on Wed Nov 30 08:51:55 2016
|
How big is your image? I just tried a 5000 x 3600 pixel image (8 MB in size), and it worked fine on the demo logbook.
Stefan
Xuan |
|
Re: Error: Entry text too big. Please increase TEXT_SIZE and recompile elogd, posted by Xuan Wu on Thu Dec 1 01:40:14 2016
|
I just test on your Demo logbook. I use a screen-capture tool to create an image which doesn't been saved as a file, the size is 1920*1080(1.8M),
then copy it in clipboard, and then paste in text area. Then the web page become very slow, so that I can't submit it sometime. Sometime, I can submit
it but it say "Entry text too big. Please increase TEXT_SIZE and recompile elogd". If I drop an image file into the text area, it works. I used |
|
Re: Error: Entry text too big. Please increase TEXT_SIZE and recompile elogd, posted by Stefan Ritt on Thu Dec 1 08:13:41 2016
|
Ah, that's the difference! I always drop an image on the text area, never paste it. So please refrain from pasting.
Xuan
Wu wrote:
I just test on your Demo logbook. I use a screen-capture tool to |
Possible misuse of email headers Message-Id and In-Reply-To, posted by fbretel on Wed Feb 8 16:38:15 2017
|
Hi,
As mentionned before, we happen to fail to receive email messages related to updates on
elog entries at our site. My understanding is that the SMTP header Message-Id MUST be unique for each email message. Whereas all elogd email |
|
Re: Possible misuse of email headers Message-Id and In-Reply-To, posted by Stefan Ritt on Wed Feb 8 18:16:30 2017
|
A pull request would be highy appreciated, because you can then test it thoroughly on your side. Adding a random number to the message id is simple.
"Reply-to" indeed does not make sense since elog cannot receive emails. Most sites use a generic "noreply@<domain>" to indicate
to the user that a reply does not make sense. I guess the "Reply-to" does not have to be unique, right? |
|
Re: Possible misuse of email headers Message-Id and In-Reply-To, posted by fbretel on Wed Mar 15 16:04:13 2017
|
| Pull-request posted. Cheers. |