> Correct Way prior to 2.3.8
> 
> http://192.168.0.1:99/Provisioning%20Request/35
> 
> Broken way with new version
> 
> http://192.168.0.1:99/Provisioning Request/35

Exactly this problem has been fixed between 2.3.7 and 2.3.8, so can it be 
that you mixed up these two versions? To be precise, the fix happend in 
Revision 1.113 from 2003/06/04 08:17:35. So are you sure that you use a 
version of elogd after that modification? I tried to reproduce your problem 
with the official 2.3.8 version, but I got the correct result.

Ive just been alerted to a bug with email notifications in Elog.

Basically if your log book contains a space then the URL that is sent in 
emails when creating tickets or updating old entries doesnt put %20 (IEs 
space) inthe URL it leaves a space hense breaking the link.

for example

Correct Way prior to 2.3.8

http://192.168.0.1:99/Provisioning%20Request/35

Broken way with new version

http://192.168.0.1:99/Provisioning Request/35
                                 ^
Link is broken at this point

My config looks like this

Email Status Assigned = $Owner@abc.co.uk
Email Status Re-Assigned = $Owner@abc.co.uk
Email Status Completed = $Requester@abc.co.uk
Email "Send Update Email" Yes = $Requester@abc.co.uk
Use Email Subject = A Provisioning Ticket has been assigned to you or 
completed
Use Email From = NetworkTeam@abc.co.uk

> > i put the last version on this link
> > http://public.mba.be/demo/elog/u-edit-elog-syntax.txt
> 
> If you don't mind I added the file to this message.

surely not but as I put some new command each time you update elog :)
it's easy for us to put on on webserver
but for each update I ll send the new version

Thank you very much for your request, well motivated and described. I hope I 
will soon find time to impelment this.

> I was wondering if there is a way to have a more detailed log of users' 
> activities?
> Current Logfile = <file> gives a good base for information about 
> logins/access to 'protected' logbooks. 
> 
> What we would like to have is information about when a user reads an ELOG 
> entry (to be able to determine the reaction/response time). 
> 
> For instance the LOG could look sg like this: 
> %%user %%datetime %%logbook %%record read/edit/new/delete 

Very nice idea, I put it on the wishlist.

> When you take the elogd.cfg file and the menu commands = <list> and guest 
> menu commands = <list>, the config menu for edit the elogd.cfg stops 
> working, yet if I change the URL manually, I can still get to the file and 
> the menus do not change.  If I delete all menu commands, then all works 
> without errors, yet the menus do not match default.

Has just been fixed. Available under CVS and soon in 2.3.8.

> i put the last version on this link
> http://public.mba.be/download/u-edit-elog-syntax.txt

If you don't mind I added the file to this message.

> could you add command for main menu guest user
> Selection Page guest = ....

I added "Guest Selection Page" coming in version 2.3.8