Thank you Stefan!

1. Will help in the real hard cases!

2. Great! Specially editing adresses or some stutus overviews will be easier with a compleate
overview!

> > 1. Is there a possiblity to fix the position of the attribut fields if they are in
> > the same line? As. ex. if one attribute is empty or contain a very short value it may
> > be possible that the position of the following atrributes in the line are moving to
> > the left, if the value is very long, they move to the right side. This make it
> > sometime not easy to read the informations, specially if the user browses trough some
> > entries, the picture the eyes are scanning is changing.
> 
> Yes there is a possibility. In the format option, you can specify two CSS names, one for the
> attribute and one for it's value. The default ones are "attribname" and "attribvalue". Just
> make new ones by copying these two, renaming it to something like xxxname and xxxvalue where
> "xxxx" is the name of the attribute. You find that in the file themes/default/default.css.
> They contain a field called "width:" which can be changed:
> 
> .typename {
>   width:150px;             <-- must be changed
>   background-color:#CCCCFF;
>   border:1px solid #0000FF;
>   border-top:1px solid white;
>   border-left:1px solid white;
>   padding:3px;
> }
> 
> By having separate classes for all attributed, you can change their width separately,
> accomplishing hopefully what you need.
> 
> > 2. Did I understand you right, that tis will not work while editing? I would like to
> > put this to the wish list for a uppcoming version (not very importand, but VERY nice
> > to have), that it may be possible to use Format in the new and edit mode too, because
> > it is somtimes more comfortable to have some attributes grouped locically in one line
> > or to have a overview over all attributes on one screen without scrolling while editing.
> 
> I will put this on the wishlist.
> 
> Stefan

I did not have the following problem in any snapshot before 23.7.04 .
Actually I do not have a possibility to test the snapshot under an other
system than win xp pro sp 1 (fully pached). 

Using my logbooks as well as the demo logbook works well under older
snapsgots of 2.5.3 as well as long as the "List Display = <attributes>" is
not used!

Using "List Display = <attributes>" produces an ususal output with the text
field content in the first row and a row title of the first 3 letters.

Ex.:
Attributes = Customername, Customeraddres
List Display = Customername, Customeraddres

Output:
¦Cus¦Customeraddres¦

If no record is in the logbook, only the "Cus" is dispalyed! Removing "List
Display = <attributes>" produces a normal output with same logbook!

By the way: Thnak's for the Format in the entry/edit view!!!

Thank you very much Stefan!!!

Also the horizontal alignement with "Format = 1" looks much better   as before
with standard css files! Really great work!

> > Using "List Display = <attributes>" produces an ususal output with the text
> > field content in the first row and a row title of the first 3 letters.
> 
> I fixed that problem. Please get the snapshot from July 28th 14:16.

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.

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.

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?

God really STRANGE and problematic effect on 2.5.5-1 (can't remember it this
was with 2.5.5 or 2.5.4-X but i'm nearly sure it worked well):

Entering a date (Formate Bithday = date) may crash down the server:
Value is 22.2.2004: Everything is well
Value is 22.2.1962: Server crashes emmediatly (menas restarzing several
times, always the same problem)

I do not have time to check true all the years for finding out where the
problem may beginn, sorry. Also I was not able to check on other systems
right now. My system: Win XP Pro SP 1, IE 6 as well as Mozilla Calssic 1.7.3. 

Didn't check it under Linux right know in case of a lot work.

Clould you this fix please Stefan???  THANK'X!!!

know that illness...  :-(  but was the last of the family of 4 people

i'd like to ask for an other usefull change togehter with this and how url's are 
handled by elog:

since there may be spaces in the name of a logbook (ex. "1stWordOfLogbook 
2ndWordOfLogbook") it is very userfriendly to name logbooks. also it's easy th 
make a reference for a other entry by copy and paste:

Display ThisURL = http://localhost:8080/$logbook/$message id

however, using spaces in the logbook name may give a wrong result, because the 
url would be http://localhost:8080/1stWordOfLogbook

and the space as well as the 2ndWordOfLogbook//$message id is only normal text.

may it be possible stefan, to replace the space in an url (starting 
with "http://") with a "+" or "%20"? this would allow to automate some things. 
actual the logbook name has to be hardcoded.


> > I think you should be using tcp_hostname instead of gethostname if it is 
> > specified.
> 
> Sorry my late reply, I was ill for some time. I implemented your suggestion in
> revision 1.522 which is available from CVS.
> 
> Note that there is also the "URL = xxx" option in the configuration file which
> lets you specify the whole URL including the host name.