This problem has been fixed in revision 1.462

> This problem has been fixed in revision 1.462

Thank you!

Hi,

We just recently upgraded from an older version of Elog to the latest and
greatest, 2.5.4-2.  Everything is workinly nicely, except the "Use Email
From" option does not seem to work as before.  We have the option set so
that all e-mail that is sent should be from a single address, but instead it
just ignores that address and uses the e-mail address of the user currently
logged in.   

I have this set in the global section of the elogd.cfg:

Use Email From = elog@****.com

Please let me know if this is the intended function or if it may possible be
a bug.

Thanks,
Chris

I gave the user email address priority over the "Use email from" option, that
means only if the user does not have an email address, then the "Use email from"
value is used. Now I realize that the priority is maybe wrong, so I should give
the "use email from" switch the highest priority. Only if this flag is not
present, then the system uses the user's email address. If that one is not
present, too, then the system uses "elog@<host>".

I applied this change to the CVS version, so let me know if it is ok with you.

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

Looking at the HTML one sees that there are <table> tags for each row
which should not be there:

<tr><td><table width="100%" cellpadding=0 cellspacing=0><tr><td nowrap
class="attribname">Author:</td><td class="attribvalue">
Stefan Ritt&nbsp</td>
</tr></table></td></tr>

> 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. This causes the shifting as you noted
correctly. To avoid this, simple increase the width of the attribute name field
in the CSS file. Edit <elo>/themes/default/default.css, find the section with
".attibname" and change the width from 150px to 200px, such as

.attribname {
  width:200px;
  background-color:#CCCCFF;
  border:1px solid #0000FF;
  border-top:1px solid white;
  border-left:1px solid white;
  padding:3px;
}

I tried this with http://midas.psi.ch/elogs/Config+Examples/1, and it wroked
fine (see attachment). [I had to increase the text size a bit in my browser to
reproduce the initial problem]

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