This is not a serious bug...but when the global settings are as follows

[global]
Display mode = threaded
Reverse sort = 1

all logbooks with only a single entry produce the wrong URL on 
clicking "last 10"

The URL produced is http://localhost:8080/LogbookName/0
instead of http://localhost:8080/LogbookName/1

Ravi

> The last x link TEXT now shows up like this
> 
>    'Last 20 entries?mode=threaded'
> 
> I can not reproduce this with the elogdemo logbook, however.

...because it has been fixed in meantime (revision 2.41). I have not made a 
new release since I want to fix the elog password submission first. In 
meantime, you can get the actual version from 

http://midas.psi.ch/cgi-bin/cvsweb/elog/elogd.c

The last x link TEXT now shows up like this

   'Last 20 entries?mode=threaded'

I can not reproduce this with the elogdemo logbook, however.

> Hello,
>     If you delete a message from the middle of a logbook that contains a 
> bunch of messages, the message numbers do not get updated properly.  For 
> instance, if you have 20 messages in the logbook, and delete number 15, 
> entry numbers 16 through 20 all do not get subtracted by one; their numbers 
> stay the same with #15 just missing in the middle.  
> 
> Mo

That's how it's supposed to be. Once a unique message ID is attached to a 
message, it stays there forever. Think of links to message like

http://midas.psi.ch/elogdemo/Forum/68

If you have such a link in a message or as a bookmark in your browser, and 
the ID gets changed from 68 to 67, then your link would be off.

Hello,
    If you delete a message from the middle of a logbook that contains a 
bunch of messages, the message numbers do not get updated properly.  For 
instance, if you have 20 messages in the logbook, and delete number 15, 
entry numbers 16 through 20 all do not get subtracted by one; their numbers 
stay the same with #15 just missing in the middle.  

Mo

>    If you have only one entry in the logbook and have it set up in threaded 
> mode like: ?cmd=Search&mode=threaded&reverse=1, when you click on the icon 
> of the entry or the number of the entry to see it, it does not allow you 
> to.  If there is more than one entry, it works fine.  

Ok, has been fixed. Will come in 2.0.5

>    Also I wanted to make a submit page from where you could either go back 
> to the logbook which you just entered a message for or type a new entry for 
> that logbook.  First of all, is there a way to have only one file called 
> submitpage.html in which I can define this for all logbooks or do i need it 
> for ever logbook.  And also, is there a way I can even set a link that will 
> allow to create a new entry.  I tried: 
>     <a href="demo/?cmd=new">Enter</a> another message<p>
> 
> but for some reason it does not work.  Is there a way to implement this?

The documentation was wrong about that which has been corrected. The proper 
file contents should be

<h1>You successfully submitted a message</h1>
<a href="?cmd=Back">Back</a> to the logbook<p>
<a href="?cmd=New">Enter</a> another message

This way one only needs one file for all logbooks.

   If you have only one entry in the logbook and have it set up in threaded 
mode like: ?cmd=Search&mode=threaded&reverse=1, when you click on the icon 
of the entry or the number of the entry to see it, it does not allow you 
to.  If there is more than one entry, it works fine.  
   Also I wanted to make a submit page from where you could either go back 
to the logbook which you just entered a message for or type a new entry for 
that logbook.  First of all, is there a way to have only one file called 
submitpage.html in which I can define this for all logbooks or do i need it 
for ever logbook.  And also, is there a way I can even set a link that will 
allow to create a new entry.  I tried: 
    <a href="demo/?cmd=new">Enter</a> another message<p>

but for some reason it does not work.  Is there a way to implement this?

Thanks,
Mo

> I guess it cannot and doesn't have to be 100% save.  Maybe if the web
> interface is used for a new message a long random number (let's call
> it newID) can be included, which elog remembers for some time (say 1
> day).  Now elogd accepts a new message only if 
> 
>   1) the cookies is there and valid or
>   2) if the cookies are NOT THERE, but the newID matches one of the
>        stored ones.     
> 
> The new message is rejected if the cookies are there, but are wrong.

Ok that sounds a good idea to me, I will work on that.

> Can one delete or edit messages with elog?  If yes then this should not be
> possible.

No this is not possible.