Have fixed this by removing the last added user from the Passwd file.

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

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. 

The way I have ELOG configured it sends an email to supervisors based on which "Department " (attribute) was selected. Problem is that when the supervisor replies the department

is still selected and it sends a second email to the supervisor. Is there any way to supress the emails (automatically) on "Reply"?

That would be a lot of effort for very little gain. I appreciate your detailed response. 

Thank you,
   - Dan

> > 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.

 It is running on a linux box, we have started in it in a telnet session, and no errors appear, as I am new to e-log is there an error log anywhere.

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

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.