> > There are too many <table> tags when displaying a singel entry.  E.g.
> > in http://midas.psi.ch/elogs/Config+Examples/1 the row 'Configuration Name'
> > is not aligned with the others (see attachment).
> 
> The <table> tags are there on purpose. As you can combine several attributes
> into one line (see this forum for example), it's necessary to make an
> independent <table> for each line. 

Couldn't one include the extra <table> tag only when there is really more than
one attribute per line.  All other lines could then be aligned properly.

To increase the width is not really a solution, since this depends on the
text size used.  See attachment with really big text.

> Couldn't one include the extra <table> tag only when there is really more than
> one attribute per line.  All other lines could then be aligned properly.

Sure one can do a lot of things if one has enough time and not tens of other
requests on the wishlist which really concern some functionality and not just
cosmetics.

The elogd.cfg is attached in the previous message as attachement 3. Sorry it is a
little bit buried between pictures.
The reason I put the picture of the global elogd.cfg is to show that the not logged
user has access to elogd.cfg which is some kind of trouble...

> I just see your [global] part of elogd.cfg, could you send me the complete file?
> 

Hi I tried to remove the cookies and it still did not ask for password under 2.5.4.
Has the password file format changed between 2.5.2 and 2.5.3 ?

> What you also could try is to delete all cookies stored in your browser. The way
> cookies are formed changed between 2.5.2 and 2.5.3, so the system could be
> confused by old cookies.
> 
> - Stefan

Everything after curly parenthesis is ignored in attribute entry boxes 
like 'Subject' above

What I typed in the subject line was exatcly this:

  'curly parenthesis problem {abc}'

> Everything after curly parenthesis is ignored in attribute entry boxes 
> like 'Subject' above
> 
> What I typed in the subject line was exatcly this:
> 
>   'curly parenthesis problem {abc}'

Just don't use curly brackets (;-)

Nevertheless I fixed it in the current version (see subject)

Ok, now I see your problem. You defined a "Guest menu commands" which explicitly allows
not-authorized access (that's what it's for). If you only want to allow authorized
access, remove the "guest menu commands" from the logbook sections and also from the
[global] section.

Please note that if an option is not preent in a logbook section, it is looked for in
the [global] section. I see that most of your logbooks have similar settings. Just put
them into the [global] section, and override it in the logbook section if they are
different.

Thank you, I misunderstood how the "Guest menu commands" worked I thought I had to specify
a limited set of commands to actually limit guest users.

Thanks again for your wonderful work on this program too.

Regards,

Alexandre

> Ok, now I see your problem. You defined a "Guest menu commands" which explicitly allows
> not-authorized access (that's what it's for). If you only want to allow authorized
> access, remove the "guest menu commands" from the logbook sections and also from the
> [global] section.
> 
> Please note that if an option is not preent in a logbook section, it is looked for in
> the [global] section. I see that most of your logbooks have similar settings. Just put
> them into the [global] section, and override it in the logbook section if they are
> different.

> > Couldn't one include the extra <table> tag only when there is really more than
> > one attribute per line.  All other lines could then be aligned properly.
> 
> Sure one can do a lot of things if one has enough time and not tens of other
> requests on the wishlist which really concern some functionality and not just
> cosmetics.

Ouch!
And just to add insult to injury, the same <table> structure doesn't even look the
same between, say, IE6.0 and FireFox 0.9!!

Stefan, keep up the good work!