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 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?

Hello!

First of all, thank you for this great piece of software! For now it seems to perfectly cover our need to log very basic events, there was a setting for everything we wanted to set.

However we have one problem and that is the saving of the letter "č" (Slovenian) into the log files. That is unicode character U+010C and U+010CD https://unicode-table.com/en/010C/. When writing to the log file it is replaced with "Č" and "č". Is there a known fix for this?

Thank you and best regards,

Matej

Hi,

I recently upgraded elog from 2.7 to 3.1 and have a hard time to insert images inline. The attachements work just fine. I am certain it is something silly, but I cannot figure it out.

1. In edit mode, I click the image icon
2. A pop-up "Image Propertied" shows with two tabs "Image Info" and "Upload" (selected)
3. Click on Browse button and select an image
4. Now
   • if I click OK, I get an error "Image source URL is missing".
   • if I go to "Image Info" tab - what URL am I supposed to enter, 68757/<1> ?

I found an old thread elog:68410 (from 2016) but could not find a solution that would work for me. Where does "Preview attachments" option should be inserted? In the global section?

Hopefully there's a simple explanation for this

Piotr

I did just that. The image was properly send to the server (it appears in the attachement list). However clicking OK still produces "Image source URL is missing".

What is the URL that refers to an attachment? I've tried 68759/<1> and 68759/1 and even elog:1234/<1> (where 1234).

Hello, Sorry if this has been addressed elsewhere, but I could not find info.

I am wanting to submit a new elog entry (that should have been) for a past date, to predate log entrys currently in my system.

I assume I must manually create a new .log file. What ID# should I assign to this entry? Should I sub-increment (i.e 33.1)? I presume the correct thing to to would be to automate ID# increments in all sucessive logs with a script (python).

Please advise.

Thank you,

-Michael Hibbard

Hi All,
I just installed elog latest version. I can see that my chkeditor (HTML encoding) is pretty simplified with respect to the version i can see there. Why this ? For example, it does not offer the possibility to upload images.

Could you please help me ?

Thank you
Andrea

Hello, the "drop attachments here..." feature is very useful, especially when I have multiple files. I can drag them all over in one operation, however I have noticed that this feature only works well in the IE browser.

It does not work reliably in Safari/Chrome/Firefox. I have tired in both 3.1.3 and 3.1.2. I also have the same symptom on the Demo log book of this site.

Please advise. Thank you for the continued development of Elog.

-Michael Hibbard