I implemented a "datetime" option which does exactly what you want. All you
need is a

Type Record Date = datetime

in your config file. The new option is present in version 2.5.8-2 and ready to
download.

> Is there an option that elog creates one logfile for one entry in the
> database? It seems that there elog is creating one logfile for one day.

No. One file per day was chosen in order to keep the number of files small.
For which purpose would you need such an option?

Is there an option that elog creates one logfile for one entry in the
database? It seems that there elog is creating one logfile for one day.

> > - Irestarted the daemon
> > - attached strace to it
> > - requested the list for a testin logbook, few entries some quite big images 
> >   (two thumbnails, the other are old images get resized my the browser)
> > - repeted previous point a couple of times
> > - press F5 (mozilla-firefox)  the browser hangs 4ever
> > - stop the load
> > - repeat point 3, all right
> > - F5 => hangs
> > - F5 => hangs
> 
> I tried to reproduce this problem, but everything was fine. This problem was never
> reported by anyone else as well.

running ethereal I found a bug, hope this is the problem hanging my firefox (I think
we have a good chance it is :-P)

when I have thuimbs enabled, elog returns for the ".thumb" (or ".whatever".. thumb's
extension should be transparent to elog .. uhm... it can't be .. this is a problem)

anyway, having attached a pdf (a big one) and aving attachment display enabled (with
my thumbnails generated by my script)  elog returns for the displayed thumb a
Content-Type for application/x-pdf, instead of the correct image/jpeg. I think this is
the problem.

The only way for elog to know what is the correc\t content type for thumbnails is to
get it from a configuration parameter, becouse it is a chioce of the external script
used to generate them to choose the type of thumbs (jpeg, png, gif ... )
One conf parameter defaulting to jpeg may be the solution

> Here is my elogd.cfg.
> I hope this will help you :)

Yes it did. You were the first one using an attribute containing a dot inside a
required attribute ("Maint."). This crashed JavaScript. I found a workaround and
implemented it.

> when we be released the next elog version who correct the crash of Protect 
> Selection page = 1 ?

I just release 2.5.8-2 which contains both fixes.

> > I'am using Elog V2.5.8-1 and the "Preset Text" option don't work more 
since 
> > I've updated Elog. could you fix it?
> 
> I tried with the example elogd.cfg and it worked there, so it must have 
to do
> with your special configuration. Can you send me your elogd.cfg so that I 
could
> reproduce your problem?
> 
> - Stefan

Hello Stefan,
Here is my elogd.cfg.
I hope this will help you :)

when we be released the next elog version who correct the crash of Protect 
Selection page = 1 ?
thanks for all

> > - Irestarted the daemon
> > - attached strace to it
> > - requested the list for a testin logbook, few entries some quite big images 
> >   (two thumbnails, the other are old images get resized my the browser)
> > - repeted previous point a couple of times
> > - press F5 (mozilla-firefox)  the browser hangs 4ever
> > - stop the load
> > - repeat point 3, all right
> > - F5 => hangs
> > - F5 => hangs
> 
> I tried to reproduce this problem, but everything was fine. This problem was never
> reported by anyone else as well.

I tried to rise the problem with konqueror, and all works nice... running
mozilla-firefox gives the problem instead (also running the test at the same time), so
there should be something in firefox or in the interaction between firefox and elog.
I'll send you one of the elog giving the problems so you can test by yourself as you
asked.

btw:
http://midas.psi.ch/elogs/Forum/?mode=full&attach=1  does not gives any problem to me
even running firefox. so the problem may be in some my elog.cong parameter ...

> I'am using Elog V2.5.8-1 and the "Preset Text" option don't work more since 
> I've updated Elog. could you fix it?

I tried with the example elogd.cfg and it worked there, so it must have to do
with your special configuration. Can you send me your elogd.cfg so that I could
reproduce your problem?

- Stefan