Updating CKeditor did work, thanks for the tip.

In the emails generated by anyone making an entry in this log book, every apostrophe is followed by a semi-colon.  So the text "I don't think..."  appears in the email as "I don';t think...", and possibly that comment will appear in the email as "I don';;t think...." - not sure on the last bit.  It has been around in the past few versions of elog, but don't recall precisely when this started occurring.  It was fine back in February, with v2.9.2 (presumably) running.

Apostrophes are encoded as "'" inside the CKEditor used by elog, which sents the raw HTML text as email notification. You can test this by pressing the "Source" button at the top left menu in the CKEditor, then you see it. In my mail program (both Apple Mail and Thunderbird) this HTML enocding is correctly shown as the original apostroph, so I suspect that your mail program has an issue interpreting HTML encodings.

For the time being, I am deeming ELOG 3.1.2 unusable with https (SSL = 1) functionality on my "Debian GNU/Linux 7 (wheezy)" server with "OpenSSL 1.0.1t", due to the described apparent issues with SSL.  Reverting to http (SSL = 0) brings back my ability to upload attachments and synchronize with a remote elogd running on a MacOS laptop.

Interestingly, my records indicate that I suffered a problem with very similar symptoms back in 2011, with version 2.8.0.  The problem at that time, which is acknowledged in the Changelog as "Fixed bug with SSL connection shutdown", got fixed in version 2.9.0.  Perhaps, when the "Replaced insecure SSLv23 with TLSv1 method" change was implemented for version 3.0.0, a similar issue was (re-)introduced?

It would of course be best if this issue were resolvable soon, due to the security vulnerabilities of http versus https.  Thank you in advance for any efforts!

Best regards,

Andreas Warburton

Further to my comment in https://midas.psi.ch/elogs/Forum/68549, if the described synchronization requires attachment(s) to be transferred from my Mac laptop to the Debian linux server (with SSL = 0 set), it fails in all the tests that I tried.

To check whether these problems are linked to the OpenSSL version on the linux server, we also tried building an elogd executable using 1.0.2j instead of 1.0.1t.  This did not appear to change/improve the behaviour.

I'd like to keep using ELOG into the foreseeable future.  Don't hesitate to contact me if you'd like me to beta test any upcoming releases.  I'd appreciate having the earlier mirroring and attachment-handling functionality back again.

Best regards,

Andreas W.

I would like to know, if the command "Admin restrict edit time = " does really work as intended.

In my case I have the following global configuration:

Admin user = <me>
Restrict edit = 1
Restrict edit time = 1
Admin restrict edit time = 10000

And every time, when I want to edit an entry (as admin), that is older than 1 hour, i get the following error message:

"Entry can only be edited 1 hours after creation"

Dear elog community,

We have a problem with elog V3.1.2-bd75964.
Sometimes entries disappear from the list after editing.
I found them in the .log files with attributes

Locked by:
Draft:

But they are not in the list anymore!
The only solution by now is manually remove these two attributes from the file,
but this is terrible.

How can I fix this?

Thanks,
Peter.

Drafts are message which somebody started to edit, but did not complete, like leaving the page without saving. If you don't like this, you can set "save drafts = 0".

The locking has a similar background. If you have locking on (vis "Use lock = 1"), then one person can "lock" a message, and other then cannot edit the same message. If you don't want that, switch locking off.

Best,
Stefan