I have just upgraded elog from 2.9.2 -> 3.1.3.

3.1.3 runs fine with new logbooks. However, when trying to run 3.1.3 with my logbooks created with 2.9.2 things stop working.

Here is the command I run for testing [attachment 1]: first of all it takes a very long time (~ 10 minutes) for it to index the logbooks. When finished indexing I try it out in a web browser - it takes infinite time to load: no error message appears but also no logbook. After an hour or so elogd crashes without an error message.

When running 2.9.2 on the same machine, all runs wel (attachment 2)

cfd file: (I only left in one logbook - they are all configured the same)

[global]
port = 18080
Logging level = 3
Max content length = 500000000
Date format = %A, %d %B %Y

[Logrun - Amptek]
Theme = default
Comment = Logrun Amptec
Reverse sort = 0
Quick filter = Date, Type

Any ideas on how to solve this?

I found a sequence which hides the message from the list.
In addition this sequence corrupts UTF encoding of the text.

1. create new message
2. submit it
3. Edit this message again
4. click SAVE and then exit the editor (click Logbook name in the header or BACK in the browser)
5. message disappeared from the list!
6. by clicking NEW message I found my lost one in the drafts, but all text was corrupted.

I've made small GIF presentation on this issue (attached, open in new window), may be this helps.

I also experienced various sproradic issues with locking, so I usually keep it off.

Stefan

Thanks for fast response!

I LIKE locking and saving drafts.
The only problem is that the locked message disappeared from the list.
This does not happen every time one left the editor, but sometimes.
I can send you the problematic message as it was disappeared, before I deleted Locked by and Draft attributes.
I can't imagine why it is not shown in the list.

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

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.

Thanks Andreas!
This is more or less exactly what I was looking for...

Regards
Markus