Re: Possible Bug: 2.3.7 : Welcome Title = < img src=, posted by Stefan Ritt on Tue May 20 14:23:56 2003
|
> 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. |
Re: Possible Bug: 2.3.7 : Welcome Title = < img src=, posted by Fred Hooper on Tue May 20 19:09:26 2003
|
> > 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! |
Re: Possible Bug: 2.3.7 : Welcome Title = < img src=, posted by Stefan Ritt on Tue May 20 22:16:47 2003
|
> 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... |
bug in cfg file, posted by Roberto Morelli on Thu May 22 21:36:54 2003
|
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 |
Re: bug in cfg file, posted by Etienne Van Caillie on Fri May 23 09:12:16 2003
|
> 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 |
Re: bug in cfg file, posted by Stefan Ritt on Tue Jun 3 20:49:27 2003
|
> 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...) |
Re: bug in cfg file, posted by Stefan Ritt on Wed Jun 4 15:26:15 2003
|
> 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. |
Bug Found, posted by nickc1 on Mon Jun 16 17:44:49 2003
|
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 |