This was a bug which only occurs under certain conditions, that's why nobody 
has seen it yet. I fixed it, the new version is available under CVS:

http://midas.psi.ch/cgi-bin/cvsweb/elog/src/elogd.c?rev=1.275

> This was a bug which only occurs under certain conditions, that's why nobody 
> has seen it yet. I fixed it, the new version is available under CVS:
> 
> http://midas.psi.ch/cgi-bin/cvsweb/elog/src/elogd.c?rev=1.275

Great! 

I'm inclined to wait until you release a new rpm with the changes, as I'm 
likely to mucky things up by trying to upgrade from the cvs archive rather than 
using the rpm mechanics. 

But glad to hear it's fixed.  

By the way, ELOG is a fantastic tool. I'm very thankful for all the effort gone 
into it. I do wish there were standard sql hooks, as I'm a bit fearful of how 
it will scale. But the front-end, which is often most neglected, is well 
thought out.  Thanks so much, Val

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

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

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

I added that code in revision 1.471.

This is a nice idea, but currently no text substations in templates are implemented. It only works in attributes right now.

Stefan

> Hello,
>   I am using template for some elogbook entries.
> 
> Is is possible to automatically change the template using the actual date in some filed. 
> 
> Something like: the template has a place-holder <start date> and this is replaced with today's date when a new entry is created.
> 
> I already have a "date" filed which is automatically filled, but I've been asked to have the date also in the template.
> 
> Thanks in advance
> Stefano