Hello,
I like the ELcode feature that lets you easily make an internal link to an attachment in the same post. However, I wasn't able to get this to work in the html editor, even though it's possible to use the ELcode format to link to another post in the logbook. When I type in elog :/1 in the html editor (without the space) and submit (even with an attachment present), it weirdly gets changed and shows up as 61/1 in the submitted elog, without any hyperlink. As far as I know we're using the standard elog code and only modified css parameters. Is there another syntax to link to attachments in html?
Testing it out here: 69699/1  (elog :/1 without the space turned into 69699/1)

I'm trying to run elog behind haproxy, but get the error "Invalid Content-Length in header" on posting.

As stated in the manual, haproxy rewrites all headers to lower case.

elogd parses the content-length header case sensitive which is against the HTTP RFC. This might also apply to other headers that get parsed.

For now I'm using the workaround from the manual:

global
  h1-case-adjust content-length Content-Length
  h1-case-adjust content-type Content-Type

backend elog
  option h1-case-adjust-bogus-server
  server elog 127.0.0.1:8080

But as the manual states, this should not be  used as a permanent solution.

Hello,

I noticed the wikipedia article of the ELOG got deleted in November 2021.
With the reason: "Poorly sourced article, and I was not able to find good sources myself."

I could access the old article through web.archive.org, but for the project it would be good, if the article got revived.

Hi all,

I'm experiencing an issue on Kubuntu 24.04 where the WYSIWYG editor (in HTML mode) doesn't appear at all. This happens across multiple browsers (tested with Firefox and Chromium). The editor area is simply blank, without any visible toolbar or editable content area.

Has anyone encountered this on Kubuntu or found a workaround? Any tips would be appreciated!

Thanks in advance,
Pawel

Sometimes we change the attributes in a config file for a given tab as time goes on, which naturally can get out of sync with the older data in that tab.

I can imagine some other Elog users have encounterd this too at some point so I'm wondering if there's a utilty or some way anyone knows of that I can use to parse a log file DIRECTLY to view the older data, without using the Elog GUI?

Hi Illam,

You can find it in src/elogd.h, #define TEXT_SIZE  250000, the original value 250000, you can change it to a larger one like #define TEXT_SIZE    1000000. Then recompile it again, just need typing "make". Elog Version is 3.1.3 in my site. HTH.

Cheers,

Xuan Wu