> When you do a find in elog, records per page (some crazy large number - for 
> your forum logbook, display 57 entries seem to cause the problem, then 
> select last year (1 years worth of logs),(don't select printable)
> 
> the results appear way off the screen (the message body looks fine, but the 
> title, etc extend way off the screen).
> 
> Printable doesn't have this problem.

I could not reproduce this problem. Can you send me the exact URL (the 
address with all the parameters from your browser's address bar like 
http://midas.psi.ch/elogdemo/Forum/?npp=57...) and tell me exactly under 
which browser this happens?

Stefan,

When will you have 2.3.1 out? I just upgraded to 2.3.0 and would like to see
the links in my summary view. If it is going to be out soon I will wait
instead of compiling from source.

Thanks for great software,
k.

> > Would be nice if you can specify which columns data has links as a flag or 
> > setting of some sorts, as opposed to either the first or all, but given a 
> > choice I would want the first column to be the linkable one 
> 
> Well, I decided to make all entries in a table a link, to be consistent with 
> the threaded display. But I changed the style such that they look like 
> before, but are actually links. This way it cannot hurt (like having too 
> much underlined text). The style can be changed via classes ".list1" 
> and ".list2" in the style sheet.
> 
> The modification will come in 2.3.1, or you can get the source code from CVS 
> under 
> 
> http://midas.psi.ch/cgi-bin/cvsweb/elog/src/elogd.c
> 
> and
> 
> http://midas.psi.ch/cgi-bin/cvsweb/elog/themes/default/default.css
> 
> > > > Problem 2 - no matter what i try in the config file i cannot get elogd 
> to 
> > > > use stylesheets ive tried specifying and even editing and removing the 
> > > > default.css style sheet i downloaded but it just seems to ignore its 
> > there.
> > 
> > I resolved this problem, many thanks for your help
> 
> What happened. If you tell your initial problems, I can maybe put something 
> into the docs so that others won't have it...
> 
> - Stefan

> When will you have 2.3.1 out? I just upgraded to 2.3.0 and would like to 
see
> the links in my summary view. If it is going to be out soon I will wait
> instead of compiling from source.

2.3.1 will come out next week, since this week I'm at home. But you always 
can get the sources from CVS (see below).

> > The modification will come in 2.3.1, or you can get the source code from 
CVS 
> > under 
> > 
> > http://midas.psi.ch/cgi-bin/cvsweb/elog/src/elogd.c
> > 
> > and
> > 
> > http://midas.psi.ch/cgi-bin/cvsweb/elog/themes/default/default.css

I noticed the site has been updated as far as the documentation for 2.3.1, 
however the latest version in the downloads section is 2.3.0, any other 
places where I can get 2.3.1

Cheers

> I noticed the site has been updated as far as the documentation for 2.3.1, 
> however the latest version in the downloads section is 2.3.0, any other 
> places where I can get 2.3.1
> 
> Cheers

Patience, patience! 2.3.1 is currently kind of in "beta" version, but will be 
released this week. Not that you can always get the latest snapshot from the 
CVS tree at

http://midas.psi.ch/cgi-bin/cvsweb/elog/src/elogd.c

- Stefan

Is is possible to postdate the Entry Date for an entry?

The documentation lists the ability to forward date an entry, but I don't 
see any ability to backdate an entry (edit the date to a date in the past).

Given that the entry date is part of the logbook entry file structure, it 
wasn't obvious how to make this change.

thanks

fred

Stefan, 
We are interested in using your ELOG (which we consider to be a wonderful 
application) even more. We would like to make a few adaptations in your 
source code, above all to add some functionality that we are missing.

I was wondering if there is a way we could coordinate the development 
together. For instance, would it be of your interest to receive the code 
adaptations we do and implement it in your future releases? 

To be more specific, for the moment we are really interested in 
implementing the SHELL script execution on the server (I noticed it is in 
your wishlist).

Best regards,

Tomas Rudolf
Micro Belgium Application

> We are interested in using your ELOG (which we consider to be a wonderful 
> application) even more. We would like to make a few adaptations in your 
> source code, above all to add some functionality that we are missing.
> 
> I was wondering if there is a way we could coordinate the development 
> together. For instance, would it be of your interest to receive the code 
> adaptations we do and implement it in your future releases? 

Sure, I'm very interested in those and ready to merge it into the main 
development tree.

- Stefan