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

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

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

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

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

> 1. shellonsubmit command : give the possibility to execute external 
> program from elog by sending specific parameter (user/logbook/message ID)
> 
> 2. elog log file in xml format : give a better view on what happens with 
> users see attachments easy to push the files to excel or sql database.

I'm happy to include these functions in the source code, please send them 
to me.

> 3. synchronisation to mySql or SQL server through perl routine and the 
> shellonsubmit command
> this will push any new/edit/delete command in sql server so we keep a 
> full historic off all transaction in ELOG

Can you please put this perl routine into the "Contributions" section

> 4. sms gateway : from elog entry we send sms message throught internet 
> gateway (perl routine)

Same as above.

> other projet : 
> we use a logbook from our external phone call
> 
> from our telephone connected to RS232 and/or TAPI interface we keep the 
> phone number and try to find the name from sql server : if found 
> we want to push an automatic entry in elog and fill specific field like 
> name/contact/last phone call....
> 
> I will ask to Stephan Ritt what's the best way to include our routine in 
> his standard source ?

As I said, put the perl programs into the "Contributions" logbook, send the 
C source code modifications to me.

> could we create a specific logbook for the wishlist
> in elog/contribution may be some parameters for the actual status of the 
> project ? 

Good idea, will do so.

Tomas send you by mail the source files and documentation in English



> > 1. shellonsubmit command : give the possibility to execute external 
> > program from elog by sending specific parameter (user/logbook/message ID)
> > 
> > 2. elog log file in xml format : give a better view on what happens with 
> > users see attachments easy to push the files to excel or sql database.
> 
> I'm happy to include these functions in the source code, please send them 
> to me.
> 
> > 3. synchronisation to mySql or SQL server through perl routine and the 
> > shellonsubmit command
> > this will push any new/edit/delete command in sql server so we keep a 
> > full historic off all transaction in ELOG
> 
> Can you please put this perl routine into the "Contributions" section
> 
> > 4. sms gateway : from elog entry we send sms message throught internet 
> > gateway (perl routine)
> 
> Same as above.
> 
> > other projet : 
> > we use a logbook from our external phone call
> > 
> > from our telephone connected to RS232 and/or TAPI interface we keep the 
> > phone number and try to find the name from sql server : if found 
> > we want to push an automatic entry in elog and fill specific field like 
> > name/contact/last phone call....
> > 
> > I will ask to Stephan Ritt what's the best way to include our routine in 
> > his standard source ?
> 
> As I said, put the perl programs into the "Contributions" logbook, send 
the 
> C source code modifications to me.
> 
> > could we create a specific logbook for the wishlist
> > in elog/contribution may be some parameters for the actual status of the 
> > project ? 
> 
> Good idea, will do so.