No. What the thread says is first try this forum, see if you can drag and drop here. If not, you have a problem on your browser. If yes, you have somewhere some old JavaScript file around. Might be in the cache of your browser.

You guys know that there is the possibility to execute an arbitrary script on each submission of a new messge? Just use "Execute new = <script>". In the script you have access to all parameters of the message. That's maybe simple than to watch the file set.

In the documentation of course :-)

You look here: http://midas.psi.ch/elog/config.html and scroll down to "Execute New". I wonder how you ever could run elog without looking at that page.

When you install elog under windows, an example config file gets installed which lets you do already what you want. Then you can extend the config file according to the documentation https://midas.psi.ch/elog/config.html

I have a question here. You say "previsous releases didn't have this problems". Well, they did not have the auto-save feature. You can turn this off if you like with "autosave = 0". This also removes the "Save" button so elog behaves exactly as before.

I decided NOT to show draft entries in the list, because these are entries currently under editing, and maybe the editor does not want others to see a half finished entry. Actually I had this feature initially and people complained about seing half finished messages in the list. Previously, when there was no "Save" button, new entries where not visible on the list because nothing was submitted at all, and I guess that was ok with you. So would reverting to the old functionality via "autosave = 0" make you happy? Of course you then loose the autosave functionality. So if people enter a long entry, and surf away from the page or the browser crashes, the entry is lost.

Devin Bougie wrote:

Thanks, Andreas.  I was aware of the "pending draft" menu, and I am aware that you can manually browse to an entry even if it doesn't appear in the list.  However, for our operations group it is a requirement that any saved entry appears in the list, even if it's in the process of being edited.  We won't be able to upgrade until this is possible.   Previous releases didn't have this problem, so hopefully it won't be too difficult to address with a new configuration option.  Please let me know if there's something I should do to submit an official feature request / bug report. Thanks again, Devin Andreas Luedeke wrote: Hi Devin, this is the intended bevaviour, there is nothing wrong with that. Only a submitted entry should be visible to the world. If you would have played a little bit longer, you would have found out yourself how you'll get access again to this so-called "draft" entry after closing the browser window: as soon as you attempt to create - as the same user - an new entry, you'll be asked if you want to continue editing your old draft entry instead. I've attached a screenshot of this "pending draft" menu, as it has been shown for this entry before I've submitted it. Kind Regards, Andreas PS: You gave a very clear "failure" description: what you did, what you expected to happen and what you've observed what happened instead. Well done: that deserves a swift answer! Devin Bougie wrote: When an entry is being edited, it does not appear in the list once it's been autosaved or the editor manually clicks on "Save."  This has been reproduced in the "Linux Demo" forum on this site, as well as on a clean installation of the 3.1.1 binary on EL6. It would be great if there was a configuraiton option to control this, but I haven't found it yet.  To reproduce: - edit an existing entry - click on "Save" - view the list for that logbook, and the entry will be hidden until you click "Submit" Obviously this becomes a problem when a user edits an entry, but navigates away from the browser window before submitting the changes. Any suggestions would be greatly appreciated.   Many thanks, Devin

> Good day,
> 
> I have an attribute that is 25 chars. it can be empty until someone edit it to fill the information.
> The default view for that logbook is List. 
> 
> Is it possible to display that attribute in list view but not the entire 25 chars ?
> What I mean is that if the field is empty, show it as empty but if it has some information, show something like "X" in List view.
> 
> I tried playing with Styles and Cell Styles but I couldn't figure it out...
> Cell Style seams to require specific values "" to apply the style properties. I can't figure how to apply cell style "if field is not empty" :)
> 
> Thanks for your help :)

Unfortunately something like this is not implemented in elog.

Stefan

Use

usr = <user anme>

in elogd.cfg as written in the documentation.

Stefan