I recently upgraded elog from 2.7.8 to 2.8.0 (and moved servers, removed unused logbooks, etc.). I'm now having a problem where elog consistently crashes when attempting to edit multiple entries. This is a very common use case, as we use a "status" field, set to "open" or "closed" to track problems. When a problem is resolved, we will go to the "list" display, set it to "threaded", "select" the thread, and then edit it, to change the status field for all posts in the thread to "closed".

Now, as soon as the "edit" button is clicked, elog crashes. This happens on every thread and logbook that I've tried. The elog logfile itself doesn't show anything useful.

However, if eLog is run with "-v" in place of "-D", it does not crash.

Environment:

        CentOS 5.4

        eLog 2.8.0 built Aug  5 2010, 12:24:11

I tried to reproduce your problem with following simple configuration file:

[Bergman]
Attributes = Author, Status
Options Status = open, closed
Preset Author = $long_name

The result was that it worked fine (see attachments). Maybe there is another setting in your configuration file which causes the problem. Can you try the simple configuration and see if it still crashes?

I could not reproduce your problem. I tried the very simple config file:

[Demo]
Attributes = Author, Subject

and the problem did not occur (see attachment). Can you try the most recent version (elog280-4.exe) with this simple configuration. Maybe you have a more complicated configuration which causes the problem. In that case please send it to me, so that I can reproduce the problem.

[Demo]
Attributes = Author, Subject

 Thank you Stefan for your help on this. I am using version 2.8.0 built Aug 2, 2010 rev 2312. I tried your configuration file and the problem did not occur. Using my config file the elogd crashes using the % sign in the subject when replying to the entry. So the problem is something in my config file. After checking through my config file and remming out individual lines and testing, I found that the following statement is causing the problem:

Preset on reply subject = Re: $Subject

I was using this to put the "Re:" on the replies.

The only problem now is I don't get the "Re:" in the subject on replies. Am I doing something wrong to cause this? My config file is attached.

Thanks,
Mike

[Demo]
Attributes = Author, Subject

Thanks for your detailed report. Actually the problem only happens if you have Re: $Subject and a '%' in the subject line. So you were the first one encountering this situation. I fixed it in release elog280-5 which you can download now.

corrected file is attached

Hi,

I have two logbooks based on the same data directory through "Subdir" option and when I add new entry in one logbook, then that entry is not visible in other logbook.

I suppose it is a bug in el_submit function, where I think the new message should be added to message index of every logbook based on the same data directory as the one, where the message was physically created. 

There is a piece of code, which I think should do this automatically

/* if other logbook has same index, update pointers */

but it seems the other logbooks does not have the same index. 

I'm new to elog and the sources are also new to me, so my guess to the ground of the problem may be wrong.

Let me know is this bug possible to fix in near future.

Best regards,

Jacek

If I create an entry via the web-interface, the defined encoding of the browser is used.
If I create an entry via "elog", it is always stored in UTF-8 encoding.
For the text I can overcome that with HTML encoding, but for attribute values the encoding does not show properly.
The only solution I found was to convert the whole logbook to UTF-8 encoding:

 define "charset=UTF-8" in elogd.cfg
 iconv --from-code=ISO-8859-1 --to-code=UTF-8 elogd.cfg >tmp;mv tmp elogd.cfg
 iconv --from-code=ISO-8859-1 --to-code=UTF-8 resources/eloglang.german >tmp;mv tmp resources/eloglang.german

Has anyone any idea why ISO8859-1 does not work for me?

Or can anyone advice me of an editor similar to NEdit that is capable to display UTF-8? :-)