Demo Discussion
Forum Config Examples Contributions Vulnerabilities
  Discussion forum about ELOG, Page 590 of 808  Not logged in ELOG logo
ID Date Icon Author Author Email Categorydown OS ELOG Version Subject
  348   Tue May 20 19:09:26 2003 Reply Fred Hooperfhooper@sushisoft.comBug report  Re: Possible Bug: 2.3.7 : Welcome Title = < img src=
> > I noticed that my custom start page did not display the Welcome title icon.
> > It worked fine in prior elogs.
> > 
> > any hints?
> 
> Indeed there is a bug, it has to do that some icons wnt into the themes 
> directory and are served now from there. So the bug will fixed in the next 
> version (the fix is already avaliable from CVS). As a temporary workaround 
> you just move your image to the themese/default/ directory and it should 
> work.
> 
> An absolute path like /usr/local/... does not work, because this would open 
> a security hole (someone could access any picture on your computer just by 
> requesting an absolute path in the URL), so I removed that option from the 
> software and the documentation.

I did the work-around (moving icon to theme/default) and it worked. Thanks.

Now if you just port elog over to an apache and mysql enviroment, it would be
perfect! 
  349   Tue May 20 22:16:47 2003 Reply Stefan Rittstefan.ritt@psi.chBug report  Re: Possible Bug: 2.3.7 : Welcome Title = < img src=
> Now if you just port elog over to an apache and mysql enviroment, it would 
> be perfect! 

ELOG runs under apache, as described in the installation documentation, so 
half-perfect...
  351   Thu May 22 21:36:54 2003 Warning Roberto Morellimorelli@es.netBug report  bug in cfg file
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
  354   Fri May 23 09:12:16 2003 Reply Etienne Van Caillieetienne.vancaillie@mba.beBug report  Re: bug in cfg file
> 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
  361   Tue Jun 3 20:49:27 2003 Reply Stefan Rittstefan.ritt@psi.chBug report  Re: bug in cfg file
> 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...)
  368   Wed Jun 4 15:26:15 2003 Reply Stefan Rittstefan.ritt@psi.chBug report 2.3.8Re: bug in cfg file
> 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.
  372   Mon Jun 16 17:44:49 2003 Entry nickc1nick@nick.comBug reportLinux2.3.8Bug Found
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
  373   Tue Jun 17 12:52:34 2003 Reply Stefan Rittstefan.ritt@psi.chBug reportLinux2.3.8Re: Bug Found
> 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.
ELOG V3.1.5-3fb85fa6