> Hi Stefan 
> YOu have been a great help on the Elog problem solving .
> I have another sort of bug , when i have a attribute type as date.
> And i have fixed the attribute on reply , i actually get a string of 
> number when i reply , and the date becomes not the orginal date in the 
> first message.
> 
> So the way i work ard is that i did not place the date field in the fixed  
> attribute reply which i will run the risk of pple modifying that entry .
> Can this be fix?

Yes, I fixed this. Revision 1.412 under CVS, new snapshot for Windows at the
download page.

Just compiled 1.410 and have run into an issue that *may* have been
introduced in 1.393.

Config file directives such as "Welcome title" could be very long strings. 
After compiling 1.410, our "Welcome title" is truncated and, while I haven't
counted the actual chars, I suspect that the truncation happens at 1024
characters.  The procedure 'getcfg' has a declared passed paramater "int
vsize". 

I haven't looked to see if this effects any other large configuration
strings that are managed by "getcfg" but this procedure is perhaps the most
popular one by far in elog.

Thank you very much Stefan!!!

Also the horizontal alignement with "Format = 1" looks much better   as before
with standard css files! Really great work!

> > Using "List Display = <attributes>" produces an ususal output with the text
> > field content in the first row and a row title of the first 3 letters.
> 
> I fixed that problem. Please get the snapshot from July 28th 14:16.

> I noticed that the gcc compiler options in the tarball Makefile were not
> conducive to speed.  There, I tried changing the gcc options to:
> 
> CFLAGS = -O3 -funroll-loops -fomit-frame-pointer -W -Wall

Thank your for this hint, I changed my Makefile for the production code. However, I
could not feel any difference between the two options. The real problem is the
function getcfg(), which gets called many thousand times internally and has to parse
elogd.cfg each time. Once I implement a hash table for that function, elogd should
become faster by at least a factor of two.

> Using "List Display = <attributes>" produces an ususal output with the text
> field content in the first row and a row title of the first 3 letters.

I fixed that problem. Please get the snapshot from July 28th 14:16.

> I followed copied the example config provide to run on my server .
> Apparently , the author field was blank when i do a reply .
> I was hoping to get it to be the actual reply author.
> Just like the way the forum is done up.
> Please help ..

This (new) behaviour came from the request that some people id *NOT* want to
have the new author on the reply, but the *ORIGINAL* (they used an attribute
"Origial author" which should not be replaced on a reply). Therefor I added a
new option to resolve that. So please use

Preset Author = $long_name
Preset on reply Author = $long_name

if you want to have the attribut "Author" replaced by the current one both on
new entries and on replies.

Elog is a great program, but it can be slow.

I noticed that the gcc compiler options in the tarball Makefile were not
conducive to speed.  There, I tried changing the gcc options to:

CFLAGS = -O3 -funroll-loops -fomit-frame-pointer -W -Wall

for version 2.5.3, the compile worked, and the program appears to work as
normal, but a bit faster.   I have not benchmarked it, but I think it should
offer a nominal increase in speed.

In particular, I removed the "-g" profiling option, which is not needed for
production code, and can be safely removed. In addition, I put in slightly
aggressive optimization settings, so if this doesn't work for you, you can
first try removing the -f setting, and then backing off the optimization to -O2.

Other may want to post other settings that work for them.

I did not have the following problem in any snapshot before 23.7.04 .
Actually I do not have a possibility to test the snapshot under an other
system than win xp pro sp 1 (fully pached). 

Using my logbooks as well as the demo logbook works well under older
snapsgots of 2.5.3 as well as long as the "List Display = <attributes>" is
not used!

Using "List Display = <attributes>" produces an ususal output with the text
field content in the first row and a row title of the first 3 letters.

Ex.:
Attributes = Customername, Customeraddres
List Display = Customername, Customeraddres

Output:
¦Cus¦Customeraddres¦

If no record is in the logbook, only the "Cus" is dispalyed! Removing "List
Display = <attributes>" produces a normal output with same logbook!

By the way: Thnak's for the Format in the entry/edit view!!!