1.

I do not know if this is a problen of the 2.5.5 (11/03/04) version or of
other versions as well:

I'm using the $message id parameter in a substitution:
Subst KlientIn/KundIn = $Vorname $Name; P: $Telefon Privat; G: $Telefon
Geschäft; N: $Telefon Mobil; $Landeskennung-$PLZ $Ortschaft [<a
href="http://localhost:8080/$logbook/$message id">$logbook:$mesage id</a>]

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?


2.

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?  ;-)

2.5.4-6 was corretly translated.

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

1. thats now clear with the £message id and the work-around is ok for my 
needs

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

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

installed elog 2.5.5 agin, same effekt with "back" / "zurück". checked the 
language file eloglang.german witch seem ok for me and the translations are 
well done. removed then in eloglang.germen the traslation for back and checked 
this: still back was viewed. reinserted the translation "Zurück" (just this 
word!)and checked again: everithing looks fine, no longer back, correctly 
Zurück on the button.
absolutly no idea why and whats the difference was! bus it works...
thank's stefan!  :-)

> > 2. the "back" 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?

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

The <pubDate> item doesn't appear to be a valid RFC-822 date.  Causes some
aggregators to fail when parsing.

The error is shown by Feedvalidator:
http://www.feedvalidator.org/check.cgi?url=http%3A%2F%2Fmidas.psi.ch%2Felogs%2FForum%2Felog.rdf

> I implemented experimentally RSS feeds into Elog. Before releasing this new
> addition, I would like to collect some experience with it. This forum now
> supports RSS feeds, for which you can subscribe with a RSS feed reader like
> Mozilla Firefox. Please give it a try and send me any feedback.
> 
> For an introduction to RSS feeds, please see 
> 
> http://www.webreference.com/authoring/languages/xml/rss/intro/
> 
> To subscribe to a logbook, enter following URL into your RSS reader:
> 
> http://<your-elog-host.domain>/<logbook>/elog.rdf
> 
> From the newest Mozilla Firefox browser, you can also click on the RSS box at
> the lower right corner of the browser (see attachment).

> The <pubDate> item doesn't appear to be a valid RFC-822 date.  Causes some
> aggregators to fail when parsing.

I fixed that, now it passes the Feedvalidator. New version is under CVS.