well, I need to reproduce your problem in order to fix it. The failed assertation you get is due to some internal writing beyond array boundaries, but I have no clue which part of the code makes this. It might be related to the fact that you use the same index (via Subdir=...) for two logbooks. In this scenario, you are only allowed to modify/add entries to one logbook, not the other. The other one may only be used for reading. And even then it's not guaranteed that new entries show up in the second logbook immediately, you might have to restart the server in order to re-index the logbooks. Internally, the daemon does not know that two logbooks are "the same" and one instance will not realize if the other instance modifies the data "below its feet". Can you try to give up the double logbooks and see if the problem goes away?

Nonetheless, given that this set-up has been a great help for us - if you ever get the chance to make this work (even) better, I'd be most grateful.

Well, for that I have to reproduce the problem. So best would be if you strip it down to the bare minimum in order to reproduce this reliably. Then you zip everything and send it to me. Then tell me what I have to edit and submit in order to stimulate the crash. Once this is successful, I can fix it.

Hi,

I am new to eLog, trying to make a logbook tool.  This is probably a question with a simple answer, but here it is...  I need to be able to edit the entry time for an entry as it is being made and also in Edit mode later.  We have field staff who use a paper log in the field and then come back to the computer later and create the log entries, and they need to be time stamped to reflect when an event happened, not when the entry is put into the log.

I'm guessing I'm missing something easy in my Config file, I've looked through the config examples and searched the forum but I couldn't come up with an example of how to make this work.

Thanks in advance!

Jay

Hi Jay,

the entry time cannot be changed, because it should reflect the real time when the entry was made. What you can do in your case is to define a "datetime" attribute, which contains then the time stamp. You need something like this:

Attributes = Author, Field time, Subject

Type Field time = datetime

... 

I just ran into this little bug: I had defined a new logbook in my config file and suddenly got the message Attribute "Date" not allowed. While I did have several attributes starting with the word "Date" (e.g. "Date In Service", "Date Retired") I had no attribute "Date" in there. After some pondering and wildly commenting out lines, it finally dawned on me: I had used an attribute "ID" - which is also not allowed. However, it would be very helpful if the error message actually reflected that...

I'm not sure if this is the expected behavior, but it appears as though an attachment is not displayed in the list of attachments if you manually add a link to the attachment into the body of the entry.  I would greatly appreciate any advice on how to fix or change this behavior.

I will try to demonstrate with the two attachments on this entry.  There are two attachments in this entry, but only one appears in the standard view of the entry.

Picture_1.png.png 

Many thanks,

Devin

Hi all,

I have set my PC in Time Zone GMT+10:00 but I get GMT time in Entry time/Last edit field.

I have installed in another PC. Which has Time Zone GMT+10:00 but I still get GMT time in Entry time/Last edit field.

Please help. Thank you very much.