Any known issues running in Win Server 2008 R2, 64 bit environment? We sometimes lose connection with the Elog app (ssl) and wonder if due to 64bit or other factor in this set up. A forum search does not explicitly reveal any clues however I did find an entry from someone posting a similar question without a response yet (#67061).

Ok, I fixed that in revision 2442. 

 Does this occur if you are adding an attachment?  As I am blessed with forever using ancient systems, I've seen fields and indeed text  being cleared  because they were entered between clicking on 'Upload' for an attachment and the .png files being generated and displayed.  Answer here is patience - I use all too much of mine up in this exercise, sadly.

 Well, this is a choice. But if the encoding of the entry is 'plain', you could just avoid checking for embeded HTML. We use the summary view constantly for our main experiment logbook. Thanks anyway.

I have not heard of that problem before.

The key to fix is to reproduce it, then teach me how to reproduce it. Only errors I can reproduce on my computer I am able to fix.

Best regards,

Stefan

That's a feature

In the summary view, I cannot use any HTML code, since it will screw up the table layout. Therefore elog searches for any "<" and ">" pairs and removes the text in between. In principle one could do a better job, but I do not want to write a complete HTML interpreter just for that purpose. 

In the summary view, it seems that the text is truncated at the first "<" character. See https://lblogbook.cern.ch/Shift/48812 for a simple entry, then use the 'list' command to see that only a very small part is displayed.

Saving, using Submit sees recently updated fields cleared after hitting SUBMIT.

MOre significantly this then leads to a proliferation of instances of the same record being generated in the logfile and consequently on the logbook.

Has anybody a fix or advice on this?