Maybe it is a wrong configuration, because in this forum it works well.
If I change the encoding in the logbook entry I get "Submit modified ELOG entry?",
and after clicking OK the entry is closed. Because this behavior is on all loggbooks
it must be a global config entry, but I dont know, which.
Here is the GLOBAL section:

Expand Selection page = 1
URL = http://sapelogs/
Date Format = %d.%m.%Y
Time Format = %d.%m.%Y %H:%M
Reverse Sort = 1
Menu commands = New, Edit, Delete, Reply, Download, Find, Last day, Last 10, Select, Copy to, Config, Admin, 
Login, Logout, Help
Find Menu commands = New, Edit, Delete, Reply, Download, Find, Last day, Last 10, Select, Config, Admin, Login, 
Logout
Password file = passwords.txt
Login expiration = 2
Admin user = ME
Suppress Email to users = 1
Self register = 0
Logout to main = 1
admin textarea = 150,45
Entries per page = 100
Mode commands = 1
Use Lock = 1
Supress Email on edit = 1
Supress default = 1
Summary lines = 1

Icon comment log.gif = Allg. Log
.....
Group SAP = .....

> > Maybe it is a wrong configuration, because in this forum it works well.
> > If I change the encoding in the logbook entry I get "Submit modified ELOG entry?",
> > and after clicking OK the entry is closed. Because this behavior is on all loggbooks
> > it must be a global config entry, but I dont know, which.
> >
> > ...
> > Use Lock = 1
> > ...
> 
> I comes from using the lock. If you remove that, you won't get this dialog box any more.
OK, it seems, that the last part of the Use Lock documentation is the explanation:
----
If someone edits an entry, but then goes away from that page or closes the browser without submitting the 
changes, a pop-up window appears asking the user to submit the changed entry. Although this works for most 
browsers in most cases, it could be that Javascript has been turned off in a browser, in which case the stale 
locks still might appear.
---
So if I switch the encoding the whole entry is reloaded, and the JS take it as leaving.
Is it possible to change this behavior? Changing encoding should be handled different as
"regular" leaving.

Additional information:
If you have set Use Lock = 1 you can't switch the encoding on a NEW entry.
The new entry is closed w/o saving. To prevent this you must input any data,
after them you can save the NEW entry with the PopUp-OK. But there can't be 
anyone else on a new entry?

Hello.

I installed the latest elog (3.1.4-2) in CentOS 7, and it is working well without SSL.
When I enalbled SSL option (SSL = 1) in the "elogd.cfg", and tried to start the elogd, the message below was shown and failed to run.

SSL support not compiled into elogd

If I switched the elog to older one (3.1.4-1), I could successeed to run the elogd with SSL option.
Is there any other option required in the latest elog to run with SSL? Or is this bug in the latest version?

Thank you,
Hisataka YOSHIDA

Dear Stefan,

Thank you for your comment. I successfuly compiled the latest elog from source code, and now elogd could work with SSL.

In fact, I reported the case of installation with rpm file. Maybe, the latest elog rpm doesn't support SSL, I guess.
The installtion with rpm file is easier to build the common environment, so I hope the next rpm will support the SSL.

best regards,
Hisataka YOSHIDA

Dear experts,

I am trying to use ELOG for my projects which we want to record every daily activities.
I have successful installed the ELOG to the computer (Windows10 -64 bit).
However, I don't know how to make it public or online, that people can access it from their computers.
I am a very newer to the ELOG.
Could you help me on it, please?

Best regards,
Hien.

We are using elog to allow users to enter their time spent on a project and we would like them to be able to see the entries that they themselves have

created but not the entries that other users have created.

Thanks,

Herman