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

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

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

Im using the plain RPM from 2.3.8, i uninstalled the 2.3.7 RPM before this 
upgrade, the only thing I kept was my own stylesheets and the config file.

One thing I just noticed is that if you dont have the URL statement set 
under global properties, some machines quote the hostname of the machine at 
which point this breaks the link. if you define the URL to the IP address 
the problem goes away.

However even without the URL setting undefined, it works for some people 
but not for others, I tried from 2 seperate machines and got 2 lots of 
results, so I suspect it might be DNS related somewhere along the lines.

> Im using the plain RPM from 2.3.8, i uninstalled the 2.3.7 RPM before this 
> upgrade, the only thing I kept was my own stylesheets and the config file.
> 
> One thing I just noticed is that if you dont have the URL statement set 
> under global properties, some machines quote the hostname of the machine at 
> which point this breaks the link. if you define the URL to the IP address 
> the problem goes away.
> 
> However even without the URL setting undefined, it works for some people 
> but not for others, I tried from 2 seperate machines and got 2 lots of 
> results, so I suspect it might be DNS related somewhere along the lines.

The only place I can see this problem could arise from is the "Referer:" 
statement in the HTTP header. This is sent by the browser to elogd, so if the 
included URL contains a blank, this could cause the problem in case no "URL" 
statement is present in elogd.cfg. Can you please run "elogd -v" to see the 
communication betwen elogd and your browser and check this? Maybe it depends 
from the browser, or even from the history of previous accesses. If you 
confirm that the "Referer:" statement contains blanks, I can put in a fix.

we develop some improvement to elog and modify the C source
to adapt some internal improvement.

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.

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

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

If somebody has good experience in C and Perl I suggest to contact me to 
improve this wonderfull product
Thank Stephan

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 ?

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

SQL : 
for our sql link we have a probleme as elog re use id when deleted
we must generate an unique ID for each elog CREATE 
and a version# field automaticly incremented after each update.
This must be implemented in ELOG source.

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

UltraEdit Syntax coloring
=========================
add this file in ultraedit
UltraEdit --> ADVANCED --> CONFIGURATION --> SYNTAX HIGHLIGHTING
I hope this will help you...

it gives different color according to elog commands
some attributes are use internaly like

ShellOnSubmit
ShellParam

if somebody has other suggestion to improve the display ask me

> add this file in ultraedit
> UltraEdit --> ADVANCED --> CONFIGURATION --> SYNTAX HIGHLIGHTING
> I hope this will help you...

Have you maybe forgotten the attachment to this message?

> > add this file in ultraedit
> > UltraEdit --> ADVANCED --> CONFIGURATION --> SYNTAX HIGHLIGHTING
> > I hope this will help you...
> 
> Have you maybe forgotten the attachment to this message?

yes :s

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

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

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

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 

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

Hello Folks,

Found an interesting problem with 2.3.7 under redhat 9.0 linux.

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.

Also, the self registration function equal to 3 does not always send email.

Cheers,
Roberto

> Hello Folks,
> 
> Found an interesting problem with 2.3.7 under redhat 9.0 linux.
> 
> 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 

are you logged
if you have a guest menu there is no access in the admin
access is restricted with 
Admin user = 'your login name' 
in Global section



> 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.
> 
> Also, the self registration function equal to 3 does not always send 
email.

it is send to the admin user list
be sure that smtp parameter is ok

> 
> Cheers,
> Roberto

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

There was a recent bug which made "Edit elog.cfg" stop working if the 
language is not English. This has been fixed and the update is in CVS. If 
you use English, this might be another problem. Can you send me your 
complete elogd.cfg so I can try to reproduce your problem?

> Also, the self registration function equal to 3 does not always send email.

"Not always" is hard to understand. Either it works or it does not for a 
certain configuration. What you can do is start elogd with the "-v" flag, 
which outputs all communication to the console window. Among this 
information, you have the communication with the SMTP server when sending an 
email. Maybe you see some problem there which only sometimes occurs (like 
wrong email addresses or so...)

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

Can you tell me what the following change in CVS offers

Revision 1.99 / (download) - annotate - [select for diffs] , Fri May 2 
10:00:31 2003 UTC (6 days, 2 hours ago) by midas 
Changes since 1.98: +10 -1 lines
Diff to previous 1.98 
Added lock icon for protected logbooks


Does this relate to the request in article 309

and if so is there any flags set to enable it.

Cheers

> Can you tell me what the following change in CVS offers
> 
> Added lock icon for protected logbooks
> 
> Does this relate to the request in article 309

No, unfortunately not (yet). I'm still working on the problem described in 
elog:309. This "lock" icon only shows you in the logbook selection page which 
logbooks are public and which are protected by passwords (was another 
request).

> > Can you tell me what the following change in CVS offers
> > 
> > Added lock icon for protected logbooks
> > 
> > Does this relate to the request in article 309
> 
> No, unfortunately not (yet). I'm still working on the problem described 
in 
> elog:309. This "lock" icon only shows you in the logbook selection page 
which 
> logbooks are public and which are protected by passwords (was another 
> request).

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

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

I added "Guest Selection Page" coming in version 2.3.8

I suggest to add an attributes  like  OS

MOptions OS = linux, windows2000, windowsXP¨, windows2003

to indicate on which version we are speaking

> I suggest to add an attributes  like  OS
> 
> MOptions OS = linux, windows2000, windowsXP¨, windows2003
> 
> to indicate on which version we are speaking

Good idea, I added a "ELOG Version" as well.

> > I suggest to add an attributes  like  OS
> > 
> > MOptions OS = linux, windows2000, windowsXP¨, windows2003
> > 
> > to indicate on which version we are speaking
> 
> Good idea, I added a "ELOG Version" as well.

I suggest MOptions - people are lazy .... :)
by the way any possibilities to have 'multiple icons' ?

> I suggest MOptions - people are lazy .... :)

Not for the Version! I don't want to update this list on every release (:-(
Plus the list would get too long over time!

> by the way any possibilities to have 'multiple icons' ?

No, you have to use MOptions instead.

Used to deny a certain command to a list of users. This can be used to 
deny a guest user to enter new messages or modify a message. 


Hosts allow = <list> 
Hosts deny = <list> 

could you deny guest user like this 

guest is not loggeg ?
hubert is logged

Hosts deny = guest,hubert
does anybody has experience with deny based on IP adresse ?

> Used to deny a certain command to a list of users. This can be used to 
> deny a guest user to enter new messages or modify a message. 
> 
> 
> Hosts allow = <list> 
> Hosts deny = <list> 
> 
> could you deny guest user like this 
> 
> guest is not loggeg ?
> hubert is logged
> 
> Hosts deny = guest,hubert
> does anybody has experience with deny based on IP adresse ?

You probably mixed up deny of a command to a certain user and deny of hosts 
based on their IP. This has nothing to do with each other except the 
word "deny". Please read the documentation about how to set up IP 
based "hosts deny". This works only for certain IPs, but not for certain 
users. 

If you want guests not to be able to enter messages, but allow this to 
registered users, you should set up a password file, and a guest menu. 
Please refer to the elogd.cfg file for this forum which is done in this way. 
Have a look at elog:Config%20Examples/4 .