[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

 Sorry so long getting back to you, Stefan. Just wanted to say "thank you". This new function works great!

When creating new logbooks, I will create a single entry to test the  
configuration. After revising the configuration I want to delete that  
single entry and create a new one based on the revised config.  
  
elogd will crash every time upon deleting that single entry with an  
xrealloc error. Here are the syslog entries leading up to the crash:  
  
Oct  9 08:09:41 obstin8 elogd[20614]:  
GET /Support/1?cmd=Delete&nextmsg=0&confirm=Yes HTTP/1.1^M Connection:  
Keep-Alive^M User-Agent: Mozilla/5.0 (compatible; Konqueror/3.3; Linux)  
(KHTML, like Gecko)^M Referer: http://localhost:8080/Support/1?cmd=Delete^M  
Accept: text/html, image/jpeg, image/png, text/*, image/*, */*^M  
Accept-Encoding: x-gzip, x-deflate, gzip, deflate^M Accept-Charset:  
iso-8859-1, utf-8;q=0.5, *;q=0.5^M Accept-Language: en^M Host:  
localhost:8080^M Cookie: urem=0; upwd=dDRubjNyBDI=; unm=mstolove  
Oct  9 08:09:41 obstin8 elogd[20614]: xrealloc: not enough memory  
  
This is on a Slackware 10 box using kernel 2.6.7. Elogd is accessed  
directly, not through an Apache proxy.  

I have the following in a local logbook config: 
 
  append on edit = "\n\n[$date: $short_name]\n" 
 
When I upload an attachment to an entry, it appears like the page is 
getting refreshed in the browser and the 'append on edit' action is called 
again. This results in two appended strings in the text entry, one for the 
initial edit and one for the upload. 
 
Is this by design or an inadvertent result of uploading an attachment? 
 
My preferred handling of this - and perhaps a more intuitive behavior - 
would be to have the append/prepend actions happen once and only once for 
each edit or reply. 
 
BTW Stephan, many thanks for the great program. 

I have the following in a local logbook config: 
 
  append on edit = "\n\n[$date: $short_name]\n" 
 
When I upload an attachment to an entry, it appears like the page is 
getting refreshed in the browser and the 'append on edit' action is called 
again. This results in two appended strings in the text entry, one for the 
initial edit and one for the upload. 
 
Is this by design or an inadvertent result of uploading an attachment? 
 
My preferred handling of this - and perhaps a more intuitive behavior - 
would be to have the append/prepend actions happen once and only once for 
each edit or reply. 
 
BTW Stephan, many thanks for the great program. 

Hi,

I'm having an issue with Elog 3.1.1 on windows 10 not displaying all log entries (after a certain date) in a logbook directory.

The logbook is saved in a Dropbox folder and the entries were created on a windows 8.1 PC with 3.1.1 also.

I created an entry in windows 10, this created a new log file (new day) with a duplicate ID, deleted the log file and then the windows 10 pc displayed all entries.

Is there any way to ensure Elogd picks up all log files ?

Thanks & Regards,

Mike

Thanks very much for your comments. I will take a look at the mirror server functionality.

I have only been running one elogd at a time, restarting elogd (on Windows 10) doesn't seem to pick up the changes made on Windows 8.1 PC (stopped elogd after changes made and log file updated)

Mike