EDIT: I downloaded the latest elogd.c from CVS, replaced the one from the
latest tar, and recompiled.  Worked great!

Thanks for the prompt response, Stefan!

> > I am using 2.3.4 and I am still having this problem.  If someone posts a
> > message with an attachment, and I then reply to that message, the attachment
> > gets 'deattached' from that message.  However, the file is still in the
> > logbook directory, so it is possible to recover it, but it did cause a 
> slight
> > panic the first time it happened :)
> 
> Uups, that is indeed a problem. I found that it was unrelated to the first 
> one, so it was there since quite some time now. I fixed it. It will come out 
> in 2.3.6 or can be obtained already now from CVS. It is trongly recommended 
> to upgrade all installations to avoid this problem.

I repeat ...
. Opera browser 7.03 simply crashes, when choosing the direct URL to our 
logbook, i.e. http://localhost:8080/logbook2. We have set a general 
password file and a different read password for each of our logbooks.
If we choose http://localhost:8080/logbook1 everything is fine. We get a 
window "Authentication required" and type in simply the read password, no 
user name.
If we choose http://localhost:8080/logbook2 the behaviour is different. We 
see the window "Authentication required" appear, then Opera crashes.
Change of the read passwords did not change this erroneous behaviour. This 
problem was not with version ELOG 2.3.4.

In Internet Explorer 6 all is okay.


 ... and add

The behaviour is different in those browsers even with the start page at 
http://localhost:8080/
Internet Explorer 6 demands a login. But as we have no password we cannot 
login.
Opera 7.03 demands no login and simply offers the list of logbooks to 
choose one.

It seems when I use "reply" with an attachments, the original attachments of
the message are removed.

I use elog-2.3.5

Alexander.

> It seems when I use "reply" with an attachments, the original attachments of
> the message are removed.
> 
> I use elog-2.3.5
> 
> Alexander.

Please see elog:280 . I will releae 2.3.6 with this bugfix somewhen during 
this week.

- Stefan

It seems that maximal number of attachments is about 20. When you try to add
more, a new entry _is_ added to the logbook but the refernce to it is not
added to the web page.

> > It seems when I use "reply" with an attachments, the original attachments of
> > the message are removed.
> > 
> > I use elog-2.3.5
> > 
> > Alexander.
> 
> Please see elog:280 . I will releae 2.3.6 with this bugfix somewhen during 
> this week.
> 
> - Stefan

Wow! Fast reply!!! Thanks a lot!

> It seems that maximal number of attachments is about 20. When you try to add
> more, a new entry _is_ added to the logbook but the refernce to it is not
> added to the web page.

Uhhh, Mr. "monster of number of attachments" gave it's stroke! Well, we never 
had such large number of attachments so I forgot to put a waring in. The 
limit comes from 

#define MAX_ATTACHMENTS  20

in elogd.c which you can easily increase (as long as you have RAM!) and 
recompile.

> > It seems that maximal number of attachments is about 20. When you try to add
> > more, a new entry _is_ added to the logbook but the refernce to it is not
> > added to the web page.
> 
> Uhhh, Mr. "monster of number of attachments" gave it's stroke!

:)  I wanted to post a message with ~200 attachments.

>Well, we never 
> had such large number of attachments so I forgot to put a waring in. The 
> limit comes from 
> 
> #define MAX_ATTACHMENTS  20
> 
> in elogd.c which you can easily increase (as long as you have RAM!) and 
> recompile.

Actually my report was NOT about this limitation. You have it - it is fine.
The problem is that I add some 'zombies' or dead files to my logbook.

BTW is there a tool to check the 'integrity' of a logbook? That all
attachments are in place,  there are no dead files, etc. I perfectly
understand that it is not _highly_ desired or needed, but with the two last
problems (auto-removing of attached files and silent adding a new ones with
20+ attachments) I have doubts that our logbook in a good state. And we just
started to use it. And I am still so excited about it!!