I tried to reproduce the problem but could not. The config file uses "emtpy.html", "filtermenutext.html" and so on which I don't have. Same with eventlocation.

Rather than sending me all the files, can you strip down your elogd.cfg to a minimal version where you still see the problem. Then give me all information to reproduce it. You also have to tell me when the error occurs, like when you submit a new entry, scan through entries etc.

Stefan

Thanks for the fix, I merged it into the current development branch.

Stefan

Hi,
  I'm using elog 3.1.3 and I have an elogbook with an attribute with name 
Attributes = Author, CO2 Temp [deg], ...

If I add this attributes to quick list, 
Quick filter = Author, CO2 Temp [deg]

it does display on web page, but the search fails with "ERR_TOO_MANY_REDIRECTS" if I leave the default value in the corresponding quick filter box.

My understanding is that the presence of a "[]" in the default search value is the reason for failure and if I remove them the search works fine.

Is there a workaround?

I don't want to change the attribute name, since I do have quite a large number of entries in the elogbook, and I'd like to keep the attribute in the quick search if possible.

Thanks,
  Stefano

No, there is no quick workaround. The only way is to go through your logbook files manually (or with a script), and replace all occurrences of that attribute.

Stefan

Hello,

I am using Elog v3.1.1. When entries contain embedded images, these images are attached to the email notifications but are not properly displayed in the body of the email.
Is it expected?
For example, with an image file myimage.png the email source code contains <img alt="" height="150" src="190208_143305/myimage.png.png" width="200">
Maybe the email should make use of the Content-ID of the attached image?

Your observation is correct. The mailer inside elog should scan all email bodies and replace all <img> tags correctly. I put that on my todo list.

Stefan

Hello,

Somehow when replying to a log entry, a log entry was created that was referring to itself. How this happened, I have no idea. The effect was that each time this enty was loaded, the elogd started to hang, going to 100% load and not responding to any http requests anymore. This problem can be reproduced by manually creating such a self-referencing log entry (see attachment). The problem entry that leads to the crash can be made by editing any elog entry and adding a line "Reply to: X" and a line "In reply to: X" where X is the MID of this entry.

1) Maybe it is possible to add a check when writing files that ensure, that is a log entry does not reference itself.
2) Maybe when loading files are preparing the thread view, elogd can detect cycles and abort.

Hi,

sorry for bugging you with this, but I could not find any information for making migration of elog system from one server to another.
The migration should be done from one server version (CentOS 6.10 to CentOS 7.6). Also we are talking about migration from one subdomain to another. Example subdomain1.example.com to subdomain2.example.com. Old elog application version is 3.1.2 and I would like to migrate to the latest version 3.1.4 

Is the migration from one system to another possible?  What are the prerequisites for migration?
Are there any instructions how to do it?

Thank you in advance and have yourself a lovely day,
Warmest regards