ELOG Version 3.1.0 announcement, posted by Stefan Ritt on Thu Apr 2 15:44:33 2015
|
This is an announcement for the ELOG version 3.1.0 being released just now. Among several bug fixes and an improved Drag & Drop interface for attachments,
it contains a long awaited "autosave" feature.
Let's assume that you write an ELOG entry, and keep the window open for a longer time (like to write some shift notes over several hours). |
Re: ELOG Version 3.1.0 announcement, posted by Banata Wachid Ridwan on Wed Apr 15 04:02:41 2015
|
congrats, any detail changelog? I assume in software packages?
is it save just install and overwrite the old version?
Stefan |
|
Re: ELOG Version 3.1.0 announcement, posted by Stefan Ritt on Wed Apr 15 09:01:04 2015
|
The changelog is here: http://midas.psi.ch/elog/download/ChangeLog
It is save to install the new version over the old one.
|
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 |
|
Re: Problem with autosave functionality when combined with no 'edit' button, posted by Andreas Luedeke on Tue May 5 11:01:36 2015
|
Hi Thomas,
just my two cent: as a quick workaround (for now) you could restrict editing messages to a short time range, like 30 minutes. That would cover
most cases of draft messages.
Restrict edit time = 0.5
But I agree that |
|
Re: Problem with autosave functionality when combined with no 'edit' button, posted by Stefan Ritt on Tue May 5 12:05:47 2015
|
I changed the code such that editing of draft messages is always possible, even if the "edit" command is not allowed otherwise. Update is in
GIT. Please check if that works at ND280.
Thomas |