Hi Andreas,

Yes, the empty string does exactly that, in the drop down menu, but before my changes, I could not set it to be the default setting in the configuration file.  In an archived logbook, it's perfectly possible for "all time" to be the only sensible value.  I tried "Show last default =  " and various other variants, with no success in getting what I actually required.  Also, in the documentation, there was no mention of a way to set the default as "all time", just a list of number of days (week (7), month (31), year (364) etc), which also led me to believe that it was not possible with the existing code.

I've sent an email to Stefan giving my coding changes for information.

Show last default = 0

always worked, even in my original code. It was just not documented. I added that.

Andreas Luedeke wrote:

Hi David, I was confused because one normally does not need to include a line in the configuration to set a default value. A default is exactly what you get if you don't specify anything in the configuration But I think I've figured it out: you were overriding the default in the global section for all logbooks and wanted to get back to the default for a particular logbook. Then another simple solution would have been to remove the line in the global section and add it just in those logbook configurations, where you actually need it. Anyway, it is good that one can now set the default in the configuration; I agree that this should always be possible. Cheers Andreas David Pilgram wrote: Hi Andreas, Yes, the empty string does exactly that, in the drop down menu, but before my changes, I could not set it to be the default setting in the configuration file.  In an archived logbook, it's perfectly possible for "all time" to be the only sensible value.  I tried "Show last default =  " and various other variants, with no success in getting what I actually required.  Also, in the documentation, there was no mention of a way to set the default as "all time", just a list of number of days (week (7), month (31), year (364) etc), which also led me to believe that it was not possible with the existing code. I've sent an email to Stefan giving my coding changes for information.

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). If your browser crashes or closes for some reason, you will loose your entered text. To avoid that, ELOG starting from version 3.1.0 has an autosave feature. Whenever you enter some text, it is saved in the background as a draft message to the server. If your browser is closed by accident, you always can go back to the logbook, click "New" and ELOG will tell you that there is a draft message and asks you if you want to edit it. When you edit and regularly submit this message, it becomes a "normal" entry and the draft flas is removed. In addition to the background saving, there is now also a "Save" button so you can manually save your text to the draft entry.

I have tested this to some extent, but I might not have seen all browser/OS combinations, so in case there is a problem, please report it here.

Happy Easter,
Stefan

congrats, any detail changelog? I assume in software packages?

is it save just install and overwrite the old version?

The changelog is here: http://midas.psi.ch/elog/download/ChangeLog

It is save to install the new version over the old one.

Hi Stefan,

I am happy to see that you include the webserver authentication.
So I can now login at some other page and then access elog.
However, I would also need some means of logging out some where else.

For this I propose a new Configuration option "Logout to page" which redirects to another page if set and "Logout to main" is 0.

See the attached patch (against git HEAD)

Does this make sense to you ?

Christof

PS: Many thanks for the autosave mode,  I already used it ;-)
 

Hi Stefan,

here is a draft of how you could describe the webserver authentication in your docs.

T/Christof