My elog is named "Whatever Elog" so the URL generated is /Whatever+Elog . This works fine but when in the interface certain buttons generate this URL : /Whatever%20Elog  ...this URL fails.  It seems that elog does not recognize these ( + and %20 ) as the same which I believe they should be as part of HTTP request.

Hi ,

currently I am running Elog 2.1.1; when using a konqueror browser (ver. 
2.2.1, kde 2.2.1) the admin user cannot access in the Config menu the Login 
infos for other users except himself. The pulldown menu "Select user" is 
shown, but when the admin selects another user the info fields (Login name, 
full name, email) are not updated. They still show the attribute values for 
the admin user himself.

Is there a solution available?
Thanks (also for this very useful tool) and regards,

Stefan

We've upgraded our ELOG installation to v3, and we really like the new CKeditor. However, one of my users has noticed a problem when using Iframe HTML elements with CKeditor; namely that the HTML is not present when trying to edit the post, and saving the post erases the HTML. 
I was able to reproduce this fairly simply, by trying to embed a youtube video. I would create a new post, click the "Source" view in CKeditor, and paste something like the following:
<iframe width="420" height="315" src="//www.youtube.com/embed/RzZgFKoIfQI" frameborder="0" allowfullscreen></iframe>
Upon submission, this produces a totally normal .log file in the logbook directory, and the video is viewable on the ELOG page:

Date: Mon, 22 Dec 2014 15:52:20 -0800
Author: test
Type: General
Category: General
Subject: test
Attachment:
Encoding: HTML
========================================
<iframe width="420" height="315" src="//www.youtube.com/embed/RzZgFKoIfQI" frameborder="0" allowfullscreen></iframe>

Then, upon hitting "Edit," I am greeted by a totally empty CKeditor window, and hitting "Source" does not display the original HTML. 
Any help is greatly appreciated!

PS: Including the first line of the logfile in this very post would cause the submitted post to be truncated for some reason, although the preview looked fine. Pasting it here also caused the log to end abruptly. The string is "(dollar sign)(at symbol)MID(at symbol)(dollar sign): 9"

I had a problem with restarting ELOG since about a year, and finally I found the culprit. I just want to share it here, to prevent anyone else to make the same mistake,

Hi all,

first off all let me say, that I realy like this great tool. That is a lot of help for keeping our server documentation up-to-date. Thanks to all contributors for that.

I right here, because I actually have an issue with saving entries working with IE11 (but also in IE9). When ever I enter an entry, and click the save button, the page open a page with the text: "OK 1"   or the second attemp: "OK 2"   3rd  "OK 3" and so on (see screenshot). To get back to my Item list, I have to click the back button in the internet explorer. I also opens a lot of draft entries in my databases.  When I submit my entry, I don't have an issue, and the entry is saved correctly.

This issue doesn't happen when using Google Chrome.

Had anyone an simlar issue using elog with IE?  It would be great to have some help with that issue.

Thanks

Torsten

We recently tried upgrading the ND280 elog instance to elog 3.1.0. [1] We seem to have some problems with this 'auto-save' functionality.  Specifically, it doesn't seem to play nice with the fact that we prefer to disable user's ability to edit old messages.  So we have (up to now), had the following set of commands specified in elogd.ccfg

Menu commands = List, New, Reply, Delete, Duplicate, Copy to, Move to, Find, Help

The problem is that we now get auto-saved messages, but no ability for the user to actually go back and finish the draft message.  You can see an example of this state in this test elog

http://neut17.triumf.ca:8080/demo/

Clicking on the draft message you can see that it can't be editted.  If you try to click 'new' then edit the draft, you get the message 'Error: Command "Edit" not allowed'.  So we had zombie draft messages, until we added the edit command back; but that defeats our preference that users not mess up old messages.

In general this auto-saving seems like a useful feature.  So the ideal solution for me would be to have some mode where users could edit/finish draft messages, but where we could still disable users from editting completed/finished messages.  Ie, where we can omit 'Edit' from the menu command, but still get auto-save.

A less ideal, but perhaps simpler solution would be that if an elog has omitted 'Edit' from the menu commands, then this auto-save/save functionality is disabled so that we don't get uneditable draft messages.

[1] https://midas.psi.ch/elogs/Forum/67855