Ok, I removed the code from the official code now. 

A bit background: The "autosave" mechanism in elog saves regularly the current content in a "draft" message, so that the data does not get lost if the browser for example crashes. The saving is done asynchronously via some AJAX call. This call takes some time, since it's a round-trip to the elogd server. If the user hist "submit" during such a save, the second save might be issue before the first one has been finsihed. That's why I had a "while (in_asend)" in the code, where in_asend gets set to true when the AJAX call is started and false when it completes. Now JavaScript is not really multi-threading, so having a loop "while (in_asend)" can actually prevent the AJAX request to complete. This might have been different when I implemented that feature, which is the reason that it worked before. Without that code, it can now happen that a second HTTTP POST is sent before the first request finishes, but I guess this should not be a problem, since both requests come sequentially to the elogd server and are executed one after the other. So in worst case the elog entry text is just saved twice.

Sure it will be stuck on a date/time, until you show "inactivity". So wait for >1h, and then check again. You will see the time updated.

/Stefan 

 Hi Stefan,

well I just logged on tonight after being "inactive"  (away from work) for two days and the "Show only new entries" button is still stuck at "Tue Oct 22 10:56:27 2013". 

Could it be that I am have left myself logged in on another machine somewhere?

How does ELog determine "activity"?

Regards

Mark.

 I just had a look in the password file and found ...

 <full_name>Mark Campbell</full_name>

    <last_logout>Tue Oct 22 10:56:27 2013</last_logout>

    <last_activity>Wed Nov  6 01:17:08 2013</last_activity>

    <inactive>0</inactive>

 Yah! It's working again ...

I found out I was still logged on to one workstation, I logged off from there, waited a few hours and tried again. All good.

Regards Mark

In elog I simplu use the function gethostbyaddr() to resolve the host name. If this does not work, the underlying OS does not know the hostname either. Probably you can test this with "nslookup a.b.c.d", to see any further error message.

I'm sorry... it was my mistake. I put Resolve host names in logbook config instead global.

Regards Daniel.

> Hi Stefan,
> 
> This has happened twice on this forum now, starting from Mon 23rd November.
> 
> Someone submits an entry (Me, 66625, Bertram Metz 66628)
> I assume you post a reply (66626, 66629), but it shows up as if I or Bertram are the author of the reply, not
> yourself.  My reply to you (66627) was really authored by me, and I expressed puzzlement then at this point.
> 
> Is this a bug, or some wierd affect of us forgetting to log out?
> 
> Regards,
> 
> David.

Thanks for pointing out this issue. This bug was introduced recently, when I tried to avoid the

Re: Re: Re: ...

in the subject line. I changed this now completely so that we can have

Preset on reply Author = $full_name
Preset on first reply Subject = Re: $Subject

which fixes both things. The modification is in revision 2271.