> No, but I will put it on the wishlist. Anyhow it is hard to implement 
> something like this. Assume that I would lock a page whenever it's edited 
by 
> someone. This person can edit it and forget to submit the changes, just 
close 
> the browser. Since the elogd server does not know when a remote browser 
is 
> closed, it cannot determine if the editing is just taking long or if the 
> person closed the browser. In the latter case, the message would be 
locked 
> forever and nobody could change it any more. If I put a timeout, like 
keep 
> locked for N minutes, it's again not 100% safe. I saw people doing shift 
work 
> with elog, opening a page, keeping it open for 8 hours and then submit 
it. 
So 
> if I set the timeout to 8h, and someone abandons editing a message, this 
> message would be blocked for 8h, which is probably also not what you 
want. 
> 
> Alternatively, I just can display a messge: Warning: this message is 
> currently edited by user xxx on host xxx. But if the warning is ignored 
by 
> the user, then again we have the same problem.
> 
> Do you see a clever solution to that?


I was thinking of having an icon on the page that administrator can click 
to 
unlock a record that has been left locked by someone, perhaps using 
something 
like 

Allow Unlock = admin (or even just have the option on the top like 
(Admin/Config) for administrators

Just like the delete function works, in addition to the Warning message as 
you suggested

> Is there a way to simulate an ELOG SUBMIT?

Have a look at the elog utility which comes in the package. It does exactly 
this. It "simulates" a browser and does a submit directly to elogd. So you 
can either redo the elog code somewhere, or call elog with the proper 
command line parameters to insert logbook entries.

> > Is there a way to simulate an ELOG SUBMIT?
> 
> Have a look at the elog utility which comes in the package. It does exactly 
> this. It "simulates" a browser and does a submit directly to elogd. So you 
> can either redo the elog code somewhere, or call elog with the proper 
> command line parameters to insert logbook entries.

Thank you, Stefan!

> Can anyone tell me the URL for the CVS download section
> 
> the link has gone from one of the main screens
> 
> Cheers

The message stating the URL is still in this forum: elog:233

> 
> missing '.' in emails
> -----------------------
> 
> A dot '.' at the beginning of a line is not transmitted via email.
> It is stored in the entry properly though.
> 
> Test:
> ./There is a dot just before '/There...'
> 
> Greetings, Heiko

Here is what I got as email:

Test:
./There is a dot just before '/There...'

So I guess you mean ONLY a dot at the beginning of the line. In the email 
SMTP protocol, at lonely dot at the beginning of the line means "end of 
message" and the mail server stops by that. I checked my mail program and 
found out that it converts a single dot into two dots at the beginning of the 
line. I have to implement this in elgod.c. Thanks for pointing out this 
problem.

> I have upgraded elog from version 2.2.4 to 2.3.6 and then entry "Number
> Attachments =" is not being read.  Looking at the changelog, I found that
> "Number Attachments" has been removed in favor of "enable attachments".  I
> tried looking in the documentation but I can't find a discription of the way
>  in which multiple attachments are handled.  Can someone give me a pointer?

Just upload one attachment at a time by hitting the "Upload" button, your 
message text stays there. Once you are finished, hit "Submit". Sorry, I 
thought this would be obvious, since most providers use this for their mail 
web interface.

> > I have upgraded elog from version 2.2.4 to 2.3.6 and then entry "Number
> > Attachments =" is not being read.  Looking at the changelog, I found that
> > "Number Attachments" has been removed in favor of "enable attachments".  I
> > tried looking in the documentation but I can't find a discription of the way
> >  in which multiple attachments are handled.  Can someone give me a pointer?
> 
> Just upload one attachment at a time by hitting the "Upload" button, your 
> message text stays there. Once you are finished, hit "Submit". Sorry, I 
> thought this would be obvious, since most providers use this for their mail 
> web interface.

No need to say sorry.  It is probably obvious to pretty much everyone.  -- It
the story of my life.

Thanks
Kevin

> it would be useful, if the web server automatically produced tags <A NAME=
> [AttachNo3]>Anhang 3</A> around the entry of the attachment. With this one 
> could easily reference in the HTML text an attachement at the end of the 
> page.

I added a name tag <A NAME=attx> where x is 1,2,3,... to the attachments 
(->CVS). So you reference them by "/<logbook>/<id>#attx" where x is the 
attachment number, <id> the message ID (the one displayed in the URL if you 
display a single message) and <logbook> is the logbook name.

> I had a problem, when I just put a HTML text with <IMG> tags into the 
> formular box and I could not reference them although they were available 
> (and displayed pictures) as attachments.

That won't work, since attachments are preceeded by the date/time, to avoid 
name collisions if two identical file names are submitted several times. You 
see that if you click on an attachment to display only that picture. The URL 
in the browser gives you the full URL including the date/time, which you 
have to use to reference that image. This is of course not possible if you 
are just submitting an entry, since you don't know which exact time the URL 
will get. So you first have to submit the message with the attachment, the 
lookup the attachment URL, then edit the message again and enter the full 
URL. Not very handy, I know, but right now the only way.