I just typed a long text into this elog, clicked "submit" and it bombed with "you must select an Icon", returned me to the editor with all my text gone gone gone. I do not want to select icons, I just want to report a problem with elog. Well, 2 problems, now.

K.O.

Well, first RTFM: "Fields marked with a * are required" on top of the elog entry page. Then, use a reasonable browser on a reasonable OS  

On Google Chrome the text is still there (actually I just tried it with this entry). No idea what Safari under OSX does. Under Windows, Safari keeps the text. Actually this is controlled by the FCKEditor inside elog which is written by someone else. So complain there! Funny: We have about 1000+ entries in this forum, and you are the first one complaining about this.

My logbook kept crashing whenever I tried to reply to an existing entry. I found that the percent sign "%", when used in the subject line, will crash the elogd service when you try to reply to the entry. This appears to only happen with windows installations. I tested this on your Linux logbook and it didn't crash.

Here is the message taken from the Windows event viewer after the crash:
An unhandled win32 exception occurred in elogd.exe [5224].

Thank you for Elog, you have done a good job with it.  It is a great logbook.

Mike

 Since we updated to 2.7.8 we've found a problem.

Previously, when we used 

Subst on reply subject = Re: $subject

We have been experiencing corruption of logbook entries by elogd mirror synchronization. Has anyone else encountered this? Is there a known cause and/or workaround for it?

Details

We have two elog servers set up with identical elogd.cfg and password files, except that one server has "Mirror server" pointing to the other host. There are three logbooks defined.  (Their names are DoubleChooz, BigBrotherTable, and FlushingTable.)  When the mirror synchronization happens, whether by "Mirror cron" or by an administrator hitting the "Synchronize all logbooks" link, it often happens that entries requiring synchronization are corrupted on both servers (not just the one to which the entry was copied). This is particularly likely to happen if entries have been made on both servers since the previous sync.

Looking at the logbook files themselves, we see that the corrupted entries will have attributes from the wrong logbooks. E.g., we'll see an empty "Barometer: " line in a DoubleChooz logbook file, where "Barometer" is an attribute that is only in the FlushingTable logbook, or we will see there are unexpected DoubleChooz logbook attributes in the FlushingTable files.

Strangely, the entries will not be identical on the two machines after syncing, and they stay non-identical on further syncs.

Most disturbingly, data is lost from entries that were perfectly valid before the sync, on both servers.

This was happening with elogd 2.7.8, and continued to happen after upgrading to 2.8.0. Both servers are running Linux. One is a 32-bit machine and another 64-bit, in case that might matter (but read on).

I made copies of both servers' files and ran two elogd servers on my Mac on different ports, compiled from a fresh checkout of 2.8.0, and the same behavior was observed as I repeatedly made test entries and synchronized.  This suggests it isn't specific to Linux architecture, 64-bit or otherwise.

Sorry, that appears to be an undocumented bug fix :-)

The desired behaviour should be created by

Preset on reply subject = Re: $subject

The command "Subst" is supposed to overwrite the field after it is submitted.

From the documentation you will even find a nicer possibility:

Preset on first reply Subject = Re: $Subject

The prevent replies to build a long chain of "Re: Re: Re: ...."

Cheers Andreas

Hello

Using windows7 and the elogd 2.7.7 built Jul 31 2009, 13:01:20 revision 2246.  I noticed a bug in the tables created with fckeditor. When on winxp there is no problem. So it seems windows7 related. 
Don't know if I should post here or somewhere else. When i Click the table icon i get : 
When I want to continue ( Pressing Yes) i get

So the OK button is removed, and i can only cancel. So it's impossible to create a new table in elog. ( yes , create it by hand, but that is not so nice )
Download the latest version of elog : elogd 2.8.0 built Aug  2 2010, 12:16:05 revision 2312 . Just to see if this helps. The result is the same.
Is there some solution/workaround for this ?

Thanks for elog : it's great.

Answer : Problem solved. It is not window7 related. When I did a fresh install ( not installing over the old directory ) everything is working as expected. So I did something wrong with installing over the old elog directory.

Thanks for you're time and the inconvenience.