Conditions won't work for IOption attributes. You need an additional attribute like:

The display mode is taken from the configuration option "Display mode = ..." only the very first time a users accesses a logbook. When the user switches to any other mode (summary, full) by clicking on the according menu option, the new mode is stored in a cookie in the browser and overrides the "Display mode = ..." setting. Maybe that is what you see.

> Hi, Stefan.  When someone using a satellite connection tries to upload an attachment *or* edit a long entry, it fails and they are presented
> with an "Internal Server Error."  This is a huge improvement over the previous behavior of crashing elogd, but we were wondering if there is any
> hope of improving this further so that one can edit large entries or upload attachments over a slow (in this case, satellite) connection.  Do
> you have any ideas or plans on working on this further?  Apparently ELOG is the "only" service this user has trouble with from  home.

There was a timeout of 1 sec. in the elogd daemon, which probably is too short for a satellite connection. Unfortunately I have no satellite here 
around to test it, so I "blindly" increased it to 6 seconds in the current SVN version. Please give it a try. You can increase this yourself, its here 
in the code at (Rev. 2291) line 28270:

   FD_ZERO(&readfds);
   FD_SET(_sock, &readfds);
   timeout.tv_sec = 6;            <----
   timeout.tv_usec = 0;
   status = select(FD_SETSIZE, (void *) &readfds, NULL, NULL, (void *) &timeout);

so you can change the 6 to 10 or so. The disadvantage of a large value is the following: Suppose you submit an entry, and in the middle of the 
submission your browser dies (or the user closes it). If you have a timeout of n seconds, the elogd server will wait that time until it closes the 
connection. During this waiting time is cannot respond to other request, so it might look dead. That's why we should not make it too long.

- Stefan

The option

Show Attributes =

has been changed to

Show Attributes Edit =

to distinguish between normal entry display an edit mask. So please adjust your configuration file and everything will be fine again.

Unfortunately I cannot reproduce your error. In my test set-up it works fine, so it might be related to your configuration. Can you send me your config file, a zip with the needed logbook entries (xxxxxxa.log files), and a recipe what to click exactly in what order.

> David send me his modification and I put it into the main source code, so it will be contained in the next Windows 
> version.

I made an interim 2.7.8-3 version which contains the fix and can be downloaded from the web site.

 I have tried setting up a VM (VMWare) with W2K  and testing it out on both a W2K and WXP host. In both cases the Elog successfully sends emails. I don't know if this helps, or not.

 Thanks for the reply. I found problem with existing version. I opened log book group  without  opening log book details in configuration, that is why at submitting or opening elog was not able to find log book for that group and was getting lost.

Regarding moving to 2.7.8, I want to know that in this new version file location for pwd and log books will remain same or are changed. If changed then I have to change location manually. Also how I can perform password recovery.