> the "$message id" will not be replaced by the msg id, the string "$message
> id"  will be dispalyed and used. Other substitutions as $logbook etc. are
> working.
> 
> Is this a bug or did i missunderstood the manual?

Well, the manual does not state that "$message id" should work for "Subst
<attribute>" option (;-)

The reason is that the message ID is available only *after* a new entry has been
written to the database, and the "Subst" command is evaluated *before* an entry
is submitted. "$message id" only works for "Thread display", "RSS Title", "Subst
on reply", "Subst on edit" and "Display". You should use

Display KlientIn/KundIn = $Vorname $Name; P: $Telefon Privat; G: $Telefon
Geschaft; N: $Telefon Mobil; $Landeskennung-$PLZ $Ortschaft [<a
href="http://localhost:8080/$logbook/$message id">$logbook:$message id</a>]

Please note that you wrote "mesage id", correct is however "message id" (two
"s"), so there is also a typo.

> Since Version 2.5.5: If ELOG is running under German, the "Zurück" Bottom is
> named "Back". Any Idee where I can change this back?  ;-)

The link "Back" has been replaced upon request by "List" which is more
appropriate. So if you changed your menu with "Menu commands = ...", please
replace "Back" by "List" there.

> 2. the "bacl" link is clear and tranlated to "Liste". But I mean the back 
> button 
> in the entry and the edit mode (see picture)...  ;-)

Well, if you try with the demo logbook, the "Back" button is translated
correctly, so I don't know whats wong in your case. Can you check that your
eloglang.german file is intact?

The problems came from the French accents and the German umlauts. I changed the XML
charset, so this should be fine now. New version is under CVS.

> I included the HTML result so you can "visualize" what's going on (this may 
> also be on the avant browser side !).

I believe it is on the avant browser side. Below is the same shown in the
SharpReader browser, where everything is displayed correctly.

> i am trying to implement ssl features on our logbooks. however, it seems
> that stunnel has drastically changed their program and the usual startup
> procedures listed on the elog page don't work.
> so, what is the new method for getting elog set up with stunnel?

stunnel is kind of a deprecated feature. Better use the SSL proxy of Apache,
as written in the elog admin guide. If someone else figures out how to use the
more revent stunnel, I'm willing to update the documentation.

> i

> is there a way to set up a logbook so that a password is required to get
> into it, but no username?

Have a look under "Access control" in the manual. What you need is "Read
Password".

> thanks. that seems to get me the functionality i needed. is there any way to
> get rid of the username line when using the "Read Password" feature?

No, this is an HTTP standard. The dialog box is generated by your browser, and I
do not know any way to prevent it.