To obtain the newest source code of ELOG, go to the CVS repository at

http://midas.psi.ch/cgi-bin/cvsweb/elog/src

It contains usually the newest bug fixes, which will show up in the next 
realease. On the other hand it can also contain some new features, which 
are not yet fully tested, so care should be taken when using it. The 
revision comments usually explain what is new in that revision.

We use ELOG 2.3.5 for Windows with a German language file and have found 


some new problems:




. Certain strings are not translated.


Language error: string "Plese log on by clicking on following link and 


change your password" not found for language "de"


Language error: string "A new password for user <i>"%s"</i> has been sent 


to %s" not found for language "de"




While the first string is obviously written wrong, the second one misses a 


quotation mark.






. If a user uses the new "password forgotten" function, he receives an 


email, but after having clicked the URL in the mail, he gets the following 


error message as simple text, i.e. not formatted by use of the CSS file:




Invalid URL: Notizen/?redir=%3Fcmd%3DChange%20password%26old_pwd%


3DE3ARcjI/&uname=sal&upassword=E3ARcjI/ 


Bitte benutzen Sie die Zurück-Taste Ihres Browsers ...  




Nevertheless the new password was written into the specified password file. 


(This behaviour as far as we know was also with earlier versions of ELOG.)






. If one could not log in through the button "Login", one does not receive 


an error message, but will be pushed simply back to the main page, 


status "Not logged in". (This was as far as we know was also with earlier 


versions of ELOG.)








. If you want to change as an admin the passwords of several users, it 


would be convenient, to get always back to the page, where you may choose 


the next user ... but you will be pushed back to the main page with the 


messages. (This was as far as we know was also with earlier versions of 


ELOG.)








. But the simple change of passwords for users does not always succeed: I 


have changed the password for a user A to "anuvis", the next user B should 


have gotten the same new password, but this time it was not accepted. 


Message "Wrong password". Might it be, that this goes only once because of 


an initialisation problem ? I had to edit the password file manually.








. Opera browser 7.03 simply crashes, when choosing the direct URL to our 


logbook, i.e. http://localhost:8080/logbook2. We have set a general 


password file and a different read password for each of our logbooks.


If we choose http://localhost:8080/logbook1 everything is fine. We get a 


window "Authentication required" and type in simply the read password, no 


user name.


If we choose http://localhost:8080/logbook2 the behaviour is different. We 


see the window "Authentication required" appear, then Opera crashes.


Change of the read passwords did not change this erroneous behaviour. This 


problem was not with version ELOG 2.3.4.




In Internet Explorer 6 all is okay.






. NOWRAP tag in Date column


The date column takes quite a lot of space in the logs overview. As the 
information is only of secondary importance I would prefer date and time 
being wrapped like e.g. the contributors name. Of course, I could help 
myself with a 
 in my language file, but this would force a break also 
on 
the single message view.

> We use ELOG 2.3.5 for Windows with a German language file and have found 
> some new problems:
>
> . Certain strings are not translated.

That has been fixed in meantime.

> . If a user uses the new "password forgotten" function, he receives an 
> email, but after having clicked the URL in the mail, he gets the following 
> error message as simple text, i.e. not formatted by use of the CSS file:
> 
> Invalid URL: Notizen/?redir=%3Fcmd%3DChange%20password%26old_pwd%
> 3DE3ARcjI/&uname=sal&upassword=E3ARcjI/ 

Have you tried the elogd.cfg setting:

[global]
URL = http://your.host/

it might help there.

> . If one could not log in through the button "Login", one does not receive 
> an error message, but will be pushed simply back to the main page, 
> status "Not logged in". (This was as far as we know was also with earlier 
> versions of ELOG.)

You should at least receive a login page. So does this push back occur on a 
wrong username there or how does it happen?

> . If you want to change as an admin the passwords of several users, it 
> would be convenient, to get always back to the page, where you may choose 
> the next user ... but you will be pushed back to the main page with the 
> messages. (This was as far as we know was also with earlier versions of 
> ELOG.)

Agree. Will work on that.

> . But the simple change of passwords for users does not always succeed: I 
> have changed the password for a user A to "anuvis", the next user B should 
> have gotten the same new password, but this time it was not accepted. 
> Message "Wrong password". Might it be, that this goes only once because of 
> an initialisation problem ? I had to edit the password file manually.

Can you reproduce the problem? If so, tell me the exact sequence of thing 
you do and I can try to reproduce it as well, then fix it.

> . Opera browser 7.03 simply crashes, when choosing the direct URL to our 
> logbook, i.e. http://localhost:8080/logbook2. We have set a general 
> password file and a different read password for each of our logbooks.
> If we choose http://localhost:8080/logbook1 everything is fine. We get a 
> window "Authentication required" and type in simply the read password, no 
> user name.

Wow, your browser crashes? Funny, I never had that. So what does the browser 
say?

> If we choose http://localhost:8080/logbook2 the behaviour is different. We 
> see the window "Authentication required" appear, then Opera crashes.
> Change of the read passwords did not change this erroneous behaviour. This 
> problem was not with version ELOG 2.3.4.

I will try to install 7.03 and reproduce this, might take some while...

> . NOWRAP tag in Date column
> The date column takes quite a lot of space in the logs overview. As the 
> information is only of secondary importance I would prefer date and time 
> being wrapped like e.g. the contributors name. Of course, I could help 
> myself with a 
 in my language file, but this would force a break also 
on 
> the single message view.

Something like

Date format = %B %d, %Y

in your configuration file reduces the date string length considerably.

Today I found out that Apache 1.3.23 (and probably 1.3.24) has a problem 
with ELOG if used as a proxy server. Due to a bug in Apache, only one 
cookie is transmitted through the proxy at a time. This makes it impossible 
to log in into ELOG with user name and password (requires two cookies). 
Apache 1.3.23 comes with RedHat 7.3 for example.

To solve the problem, update Apache to 1.3.27.

See also http://bugs.apache.org/index.cgi/full/9655

elog -h 192.168.0.25 -p 80 -l Database -a Type=test1 -a OS=W2K -a Loc=room1
-a Status=operational

doing anything wrong here?

Note: When I hit ctrl-break, it exits to cmd prompt, and the entry appears 
in the logbook.... ?

> elog -h 192.168.0.25 -p 80 -l Database -a Type=test1 -a OS=W2K -a Loc=room1
> -a Status=operational
> 
> doing anything wrong here?

opps nevermind, i didn't realize I had to put something in for the ending 
body text.  Anyway to skip that part?

> elog -h 192.168.0.25 -p 80 -l Database -a Type=test1 -a OS=W2K -a Loc=room1
> -a Status=operational
> 
> doing anything wrong here?

> opps nevermind, i didn't realize I had to put something in for the ending 
> body text.  Anyway to skip that part?
> 
> > elog -h 192.168.0.25 -p 80 -l Database -a Type=test1 -a OS=W2K -a Loc=room1
> > -a Status=operational
> > 
> > doing anything wrong here?

Due to frequent requests, the elog utility reads the message body text from the 
console (stdin), if it's missing on the command line (like in your case). Under 
Linux, you can then pipe some text into elog

cat message.txt | elog -h ...

or under Windows

type message.txt | elog -h ...

If you enter the text directly, you have to finish it with Ctrl-Z / Return
(Windows) or Ctrl-D (Linux). If you do not want any text, you can write

elog -h .... -a Status=operational " "

to submit an empty text (well, almost empty, contains single blank).