Hi,

  We have been using Elog successfully as a shiftlog book for over a month 
now, but I recently ran into an annoying bug, I think.
  We had a thread that was created and was being replied to over several 
days.  We first replied to the original thread and then each subsequent 
reply was a reply of the previous reply.  When the thread reached above 13 
of these, the elogd.exe would crash everytime a user attempted to select 
the logbook that contained the enormous thread.  
  I found the only workaround was to manually delete the offending entry 
from the log file and to instruct my users to not reply to replies unless 
absolutely necessary.  I have been able to replicate this error across the 
rest of my logbooks as well.  If there is any more information you may 
need, please feel free to contact me.

Thanks,
Chris Jones

> I found a stack overflow if there are too many replies. This has been fixed in 
> the current CVS verson of elogd.c and will be incorporated into the next release.

Many thanks for your quick reply to this issue.  I have also noticed that when 
moving a log entry that contains as few as 4 replies to replies with the "Move to" 
command that the elog server will crash.  I ran into this issue many times when I 
created a new logbook and was trying to move some of the longer threads into it.  
Please let me know if you would like me to send some sample entries from our 
logbook that illustrate this.

Thanks,
Chris    

Hi,

We just recently upgraded from an older version of Elog to the latest and
greatest, 2.5.4-2.  Everything is workinly nicely, except the "Use Email
From" option does not seem to work as before.  We have the option set so
that all e-mail that is sent should be from a single address, but instead it
just ignores that address and uses the e-mail address of the user currently
logged in.   

I have this set in the global section of the elogd.cfg:

Use Email From = elog@****.com

Please let me know if this is the intended function or if it may possible be
a bug.

Thanks,
Chris

Nasty nasty. I prepared a longish post and only because I forgot to click an Icon of choice, all my message is lost.

Thus in short:

openssl/ssl.h isn't there.

I assume I got to get it from openssl.org.

But where do I put it in the compilation tree?

--

Christoph

 Replying to my own post: libdev-ssl wasn't installed.

--

Christoph

Hi,

I'm trying to configure Elog such that users can self-register. But no luck so far.
I cannot get the login screen. I'm connecting to a logbook (and I can do this without logging in).
Shouldn't I get a screen to login/register?

Here is my elogd.cfg:
[global]
Port=8880
Password file = /usr/local/elog/logbooks/passwd
SMTP host = smtp.mydomain.de
SMTP user = kuku
Logfile = /usr/local/elog/logs/elog.log
Admin user = kuku other
Login user = abc def ghi
SSL=1
URL=https://www.mydomain.de:8880/
Self register = 1
Menu commands = List, New, Edit, Reply, Duplicate, Find, Config, Logout, Help
Guest menu commands = List, Find, Login, Help

Admin user = me@mydomain.de
[Demo]
Admin Password = 9lVlUsigs4neBt9xnX44YYQay15Yu9PyLC9hK6sifI9
Attributes = Author, Status
[Linux]
Admin Password = 9lVlUsigs4next9PnXShhQQa515Yu9PyLC9hK6sifI9
Attributes = Author, Status
[Windows]
Admin Password = 9lVlUsigs4neBt9PnXShhQQay15YuxPyLC9hK6sifI9
Attributes = Author, Status

I just got a Proxy error from your site: When I clicked on the change password link that was sent to my email, I entered my new password (which was the same that I believed to have used before) and after submitting this form, I got the Proxy error. Also I find that I can never login with my once set password. Is it the Email or username on gives in the login field? Other quirk: I never can preview my post. When I click preview, nothing happens. Submitting worked today but yesterday I was unable to submit a post. I clicked several times on the submit button and nothing happened. -- Christoph

 It seems that the submit/preview problem is solved. Submit/Preview buttons at the bottom of the page seem to work on the attachments only.

Sorry for the oversight on my side.

--

Christoph