Thanks for the fix. I tried out 2197 and when I click the "Forgot Password" link it causes elog to crash. I've attached my cfg file.

The problem was the password recovery in conjunction with "Bottom text", thanks for supplying your configuration file. I fixed that in revision 2198.

 That did the trick, thanks for the fix!

Hello

Was playing with elog. I send mail to the persons involved with a elog entrie. This mail produces something like this ( rather default) .

 Logbook: Accelerator  Message ID: 4    Entry time: 05/10/09 21:48:25     In reply to: 3

When I am logged in into elog , clicking on the Message ID 4 or 3 from the mail client , elog is started with the logged in user at that time and it's permissions.  So instead of starting a new elog session ( and getting the guest permission ) I get the permission of the currently logged in user.( Could be the administrator / root) . The process will function correctly i no one is logged in into elog. I've tested this on a local machine, so I cannot say if the same happens when multiple  machines are used. So, maybe it's a bug, maybe it's my testing  configuration. 

Do not know if i explained  the problem clear enough, but is seems something that could be examined.

By the way : thanks for this great and free program.

This is not a bug, this is a feature! Once you log in to ELOG, your credentials are stored in cookies of your local browser. If you access a logbook entry, like via the link you in your email, you still use that credentials. If you clear all cookies of your browser, or log out explicitly from ELOG, then of course you will only get guest access. 

 Thanks Stefan

This was probably a buggy bug report. Was just testing things out on a local machine and cookies were send to the local machine. so the mail was using these cookies also.

In Practice this could never happen. 

Hi Stefan,

Any possibility on this one?

David Pilgram.
> Hi Stefan,
> 
> When Moving entry (and replies) from one log book to another, is it possible to prevent elog from renumbering
> the entries' ID number(s) ($@MID@$).  While it may not be good practice, we've referred to these numbers in
> cross-referencing, and it all goes wrong when an entry is moved from an "Open" thread to a "Closed" thread (cf
> your FAQ about marking of whole threads).
> 
> In the cases I'm thinking about, i.e. from main logbook to archive logbook(s), there would never be a clash of
> ID number.
> 
> Thanks,
> 
> David Pilgram.

> Hi Stefan,
> 
> When Moving entry (and replies) from one log book to another, is it possible to prevent elog from renumbering
> the entries' ID number(s) ($@MID@$).  While it may not be good practice, we've referred to these numbers in
> cross-referencing, and it all goes wrong when an entry is moved from an "Open" thread to a "Closed" thread (cf
> your FAQ about marking of whole threads).
> 
> In the cases I'm thinking about, i.e. from main logbook to archive logbook(s), there would never be a clash of
> ID number.
> 
> Thanks,
> 
> David Pilgram.

I have implemented this feature in revision 2205. You need to set the new flag "Preserve IDs = 1" in the 
configuration. I have not tested this extensively, but I'm sure you will do it ;-)