> Hello,
> 
>    Thank you for such a great piece of software!
> 
>    When displaying the entries in a log book with Summary view, ELCode is not processed in 'Text'. I know 
there
> is an option called 'Allow HTML", but is there something similar for decoding ELCode in the Summary 'Text' 
field?
> 
> Thank you again,
>    - Dan

Decoding HTML (or ELCode which translates to HTML) in the summary field is difficult, since the text is 
truncated. 
Assume you have some code like

Text
<b>Text
  <i>Text
----- cut here
</i>
</b>

Sot he bold <b> and italics <i> tags are opened, but closed after the cutting line. In that case the whole page 
might render wrongly, because everything after the summary text will be displayed in bold and italics. To fix this I 
would have to scan the HTML code and close all open tags "by hand". But since there are very many possibilities, 
especially if one used multi-column tables, this is almost impossible without writing my own HTML parser which is 
beyond the scope of elog. So the only clean solution I have found so far is to strip off all HTML formatting and 
just showing plain text there.

When Chrome came out, I vaguely remember that there were some initial problems, but they have been fixed since about a year. But I see you are using a pretty old version of ELOG, so please consider upgrading. 

You shoudl start elogd interactively in a DOS box to see if there is any error. Maybe disk full or a network problem... 

No, but you can remove the "Department" with

Remove on reply = Department

this way the attribute vanishes, but that should be ok since you always have the link to the original entry which contains the department. 

I see the same problem with IE. The knowledge base says that one should remove the "no-cache" statement from the header, but that has strange side effects: Assume you export a logbook to a CSV file, and a few days later you export it again, since many things changed. But you browser will in that case not retrieve the new logbook, but read the old CSV file from the cache. But the browser does not tell you this, so you see an old version of the logbok without knowing this, which can be dangerous. So I better leave the "no-cache" in the header. The workaroung is not to click on "Save" on the file download dialog, but on "Open". You see then the CSV data inside the browser and can copy/paste it into a notepad document, then save it. 

> When locks are enabled, users should see a pop-up window asking them to submit an entry if they edit an entry but then go away from that page or 
> close the browser without submitting the changes.  However, it only appears as though this works when using the plain or ELCode editors.  When 
> using the HTML editor, no such pop-up appears.
> 
> If possible, a fix for this would be greatly appreciated.
> 
> Many thanks,
> Devin

Thanks for reporting this problem, I fixed it in SVN revision 2256.

Allow HTML = 1

I can easily remove the "no-cache" from the header, but as I wrote you, people can then shoot themselves into the foot by getting an old document, and I guess they become even less happy then. So you tell me which way you prefer.