Hi,

my ELOG sometimes dies with "deadc0de", do I have too large ELOG config or logbook? Or is it simply a bug?

What can I do to solve this problem? "ulimit"? Or some trace output from elog?

BR, Niklas

 Probably you did not install the FCKeditor. Just try a reply to this message, and you will see the many formatting icons on top of the page coming from that HTML editor. Without the editor, you will only see the plain HTML. You can switch back however to the old behavior by selecting the ELCode encoding. You can make this permanent with the "Default encoding =0" option.

Hello,

Recently upgraded to 2.7.3 and I'm seeing html code filling up the reply window. Before I would just see [quote] and [/quote] around the original entry. Did I miss something in the upgrade? Thanks!

 What configuration do you use? I tried to reproduce your problem with a "minimal" configuration like

[demo]
Attributes = Author, Subject
Preset Author = $long_name
Locked Attributes = Author

When I log out from the second browser tab and click on "New" on the first browser tab, I am shown the login page, not the new entry page. I guess your "menu commands" and "guest menu commands" allow non-logged in users to issue a "New" command. Try removing that.

Stefan

One of my shifters just managed to make an anonymous logbook entry even though the Author attribute is required.

It turns out that he had two tabs in his browser opened/logged into the Elog.  He logged out in one tab only.   Then he

did some other work on the desktop.  Then he returned to the browser to make a new logbook entry, finding the tab which

still showed the logged in menu, including the link for "New".  The Shifer is on day two, so he did not give any special

notice to seeing Anonymous in the Author field instead of his name.  He did point it out when I came in, and noted that

no warning was given about making an anonymous entry.

I tested the same scenario myself.  One cannot preview an anonymous entry (when Author field is a required attribute).

A warning is given.  However, one can submit the anonymous entry, and no warning is given.

Alan

 I would give it a try!

My Elog running on windows 2003 sp1 is crashing with this error "  Faulting application elogd.exe, version 0.0.0.0, faulting module elogd.exe, version 0.0.0.0, fault address 0x00061330."  the version of elogd.exe is  has a built date of 2/22/2008.  Will upgrading to the latest windows binary resolve this issue?    Thanks!!

 

 Whenever you ask for it 

I made you an elog274-1.exe containing revision 2118.