Re: Max Logbooks for Email notify, posted by Oliver Kleinau on Fri Apr 10 09:59:42 2015
|
It was str variable in function process_http_request in elogd.c.
This should have the size of received buffer.
PROBLEM SOLVED!!! |
Odd behaviour when attaching a file to an entry, posted by David Pilgram on Sun Apr 12 21:12:29 2015
|
Having installed v3.1.0 on a test logbook, I find that I can browse and select a file, but when I click on the "Upload" button, I get a pop-up
message from the browser asking me:
"This page is asking you to confirm that you want to leave - data you have entered may not be saved." |
|
Re: Max Logbooks for Email notify, posted by Stefan Ritt on Wed Apr 22 13:40:19 2015
|
Ok, I fixed this in the current GIT version. You might check if that works for you.
Oliver
Kleinau wrote:
It was str variable in function process_http_request in elogd.c. |
|
Re: Odd behaviour when attaching a file to an entry, posted by Stefan Ritt on Thu Apr 23 15:13:06 2015
|
This problem has been fixed in Version 3.1.0-2. Please upgrade.
David
Pilgram wrote:
Having installed v3.1.0 on a test logbook, I find that I can browse |
|
Re: Odd behaviour when attaching a file to an entry, posted by David Pilgram on Thu Apr 23 15:37:37 2015
|
Thanks Stefan, that did the trick.
Had a bit of an effort with the git repository, though, kept getting 403 errors when tried the
git clone https://bitbucket.org/ritt/elog as per the "download" page. |
|
elogd lost entry database without restart during file system trouble, posted by Andreas Luedeke on Thu Apr 30 09:54:17 2015
|
I'm running ELOG since several years with rather heavy usage.
Last week I've upgrades from 3.0.0 to 3.1.0 and this week I had twice the same problem:
elogd lost the index for old entries and showed empty logbooks, without having restarted.
|
|
Re: elogd lost entry database without restart during file system trouble, posted by Stefan Ritt on Thu Apr 30 13:01:29 2015
|
First, I can only fix problems which are reproducible. Can we do another power outage at PSI again?
But seriously, I guess what happened is that elog sees an empty directory when the AFS server
|
Problem with autosave functionality when combined with no 'edit' button, posted by Thomas Lindner on Tue May 5 07:33:50 2015
|
We recently tried upgrading the ND280 elog instance to elog 3.1.0. [1] We seem to have some problems with this 'auto-save' functionality.
Specifically, it doesn't seem to play nice with the fact that we prefer to disable user's ability to edit old messages. So we have (up to
now), had the following set of commands specified in elogd.ccfg |