I have requested an undeletion of the article. The article was deleted  "PROD", which means that someone tagged it. And if noone removes the tag, it could be deleted.

I could revive the article. So in the future, One should have an eye on it and maybe update the current version of the software.

If there iy an paper on the elog, maybe it could be cited for more creditability.

It looks to me like only an author of an article can contradict a deletion. I did not find a single method to even comment on the deletion.
I am not an Wikipedia expert, can anyone suggest on how to push for the article to be restored? Or do we just write it again, until people stop deleting it?

I agree. I ahead ;-) I think it is not a good idea if the ELOG author pushes on that, but better someone else.

Best,
Stefan

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,

I currently testing last ELOG version from git in a docker with LDAP activated (https://hub.docker.com/r/usinagaz/elog-ldap). The goal is to use it on Synology NAS server, associated with local LDAP server.

The reverse proxy is done by embedded DSM nginx, according to FDQN associated to ELOG service (elog.corp.com). In Docker, URL is set to elog.corp.com.

All is good, but when I post any enclosure in any elog post, the elogd exits and docker is automatically restarted. The browser shows an error 405 generated by nginx server.

Do you have any idea of the cause of this problem  ?

Thanks for help.

Laurent

> I guess we want "white-space: pre-wrap" which keeps the old line breaks.

Yep. You're right. Thanks!

> Sorry, I forgot to mention that I also added some styles to the <pre> tag:
> style="white-space: normal"
> (see the screenshot on my previous post)

Actually the

style="white-space: normal"

makes the difference, the <div> is not necessary at all!

But I'm not sure that "white-space: normal" is what we want. All manual line breaks in an entry are collapsed and you get just one text block without any new line. See here

https://developer.mozilla.org/en-US/docs/Web/CSS/white-space

I guess we want "white-space: pre-wrap" which keeps the old line breaks.

You can try that out by changing elog.css:

--- a/themes/default/elog.css
+++ b/themes/default/elog.css
@@ -475,6 +475,7 @@ td {

 .messagepre {
   font-family:'lucida console',courier,monospace;
+  white-space:pre-wrap;
 }

and see the effect. If you like it, just keep it. No need to recompile elogd.cxx.

Stefan

Sorry, I forgot to mention that I also added some styles to the <pre> tag:
style="white-space: normal"
(see the screenshot on my previous post)