Hi, we are using ELOG for keeping track of a server maintainance.  I've
translated some of ELOG's strings.  The file is attached.  There will be
more translations, when I get inspired again ;-)

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

> 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? as it is
now, you can either leave it blank or enter anything you want, so long as you
use the correct password it still works. however, to keep users from getting
confused, i think it would be better to only have a box asking you for the
password and not both the password and username.

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

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

> 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? as it is
now, you can either leave it blank or enter anything you want, so long as you
use the correct password it still works. however, to keep users from getting
confused, i think it would be better to only have a box asking you for the
password and not both the password and username.

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

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?

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


okay. that's good to know. i'll try using the apache method instead. but, there is
something wrong with the "secure" link to an example on the elog administrator's
guide.

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'm running a Debian package of elog with verision number 2.5.4+r1480-1. 
The revision of the elog client in this package is 1.21. 

I'm using the elog client to send entries generated by a script to my
logbook.  I want to format the body text of the entry using HTML, to include
links and images.  When I submit the entry with the elog client it is
submited as text and not HTML.  

The man page for the elog client does not mention any commandline options to
specify the formating of the entry and I have not found any info in this
forum on the issue.

Is it possible to submit an entry with a html body using the elog client?

> Is it possible to submit an entry with a html body using the elog client?

I added a "-H" flag for that. New version of elog.c under CVS and in the next
release.

> > Is it possible to submit an entry with a html body using the elog client?
> 
> I added a "-H" flag for that. New version of elog.c under CVS and in the next
> release.

Great!  Thanks.

Kristinn

Here are some things for your wish list:                                        
                                                                                
1) elogd should report quota or disk-full problem:  In case a logbook           
   entry cannot be saved (quota or disk full) then a message like               
   'Could not save last entry.  Please contact administrator.' should           
   be displayed.  Currently nothing happens.  Only the submitted                
   entries 'vanish'.                                                            
                                                                                
2) default page view per user, i.e. the 'Back' link goes to                     
   ?mode=Full,summary,... depending on the user that is logged in.              
   Some users complained that 'Back' is not really back.  Maybe                 
   consider renaming 'Back' to 'Default View' or something.                     
                                                                                
3) (related to 1) the 'Back' link should go back to the last used mode          
   (full, summary, threaded,...) and not to the default mode                    
                                                                                
4) mark messages as unread/read on a per user basis: The                        
   implementation of this might be quite involved but it would be               
   rather useful.  One way would be to add a default attribute 'Seen            
   by' to each entry, which lists the login names of the users.  Or 
   files LOGIN_NAME.has_seen can be created which contain the entry 
   IDs of the viewed entries for each user.   
                                                                                
5) alignment of attribute table (using <td colspan=2> for multi line            
   stuff): see elog:669 :)                                                      
                                                                                
You can count my vote for:                                                      
                                                                                
- Use "and" and "or" operands in queries                                        
                                                                                

> 1) elogd should report quota or disk-full problem:  In case a logbook           
>    entry cannot be saved (quota or disk full) then a message like               
>    'Could not save last entry.  Please contact administrator.' should           
>    be displayed.  Currently nothing happens.  Only the submitted                
>    entries 'vanish'.                                                            

That has been fixed in meantime.

> 4) mark messages as unread/read on a per user basis: The                        
>    implementation of this might be quite involved but it would be               
>    rather useful.  One way would be to add a default attribute 'Seen            
>    by' to each entry, which lists the login names of the users.  Or 
>    files LOGIN_NAME.has_seen can be created which contain the entry 
>    IDs of the viewed entries for each user.

There is an elegant way to achieve this already now: Use an RSS reader (like
SharpReader for Windows or Straw from Linux) and subscribe to a logbook. Then don't
read the entries directly in the logbook, but read them in your RSS reader. Once you
read them, they become automatically marked read.   

> 5) alignment of attribute table (using <td colspan=2> for multi line            
>    stuff): see elog:669 :)                                                      

Has been fixed as well.

> - Use "and" and "or" operands in queries                                        

Elog supports now regular expressions. So for a "<str1> OR <str2>" one can write

<str1>|<str2>

and for a "<str1> AND <str2>" one can write

<str1>.*<str2>|<str2>.*<str1>

Looks a bit complicated, but maybe some day we will get some code which rewrites
"AND" and "OR" as regular expressions.

> > - Use "and" and "or" operands in queries                                        
> 
> Elog supports now regular expressions. So for a "<str1> OR <str2>" one can write
> 
> <str1>|<str2>
> 
> and for a "<str1> AND <str2>" one can write
> 
> <str1>.*<str2>|<str2>.*<str1>
> 
> Looks a bit complicated, but maybe some day we will get some code which rewrites
> "AND" and "OR" as regular expressions.

It seems that the quick filter searches are now (2.5.4-6) case sensitive.
Could you add an option to specify this in the config file?  Or does it
exist already?

> 2) default page view per user, i.e. the 'Back' link goes to                     
>    ?mode=Full,summary,... depending on the user that is logged in.              
>    Some users complained that 'Back' is not really back.  Maybe                 
>    consider renaming 'Back' to 'Default View' or something.                     

I replaced the "back" link with a "list" link, hope that this makes now more sense.

If I make changes to the elog source, How do I re-compile it and not 
distrupt the program??????

> If I make changes to the elog source, How do I re-compile it and not 
> distrupt the program??????

You first have to stop the running elogd server, then replace the executable,
then restart the server.