With elog it is possible to submit messages to a password protected
logbook without specifying the -u option.  I.e. NO PASSWORD is
necessary to submit a message.  I assume it is related to the problem
of expiring password-cookies while entering the message using a web
browser.

   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

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

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.

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

Hello,

I noticed a strange behaviour with Elog 2.0.4 (i386 RPM) in Linux (RH 7.2). 
I started Elog out-of-the-box with portnumber 888 ('sbin/elogd -p 888').

It runs just fine, but appears to listen to port 8080, the default! It 
looks like the -p option on the command-line is ignored.

Anyone seen similar problems? 

Joeri

Hello,
    In the newest version of eLog, I was having trouble saving the 
configurations once I change them through the web interface.  I can change 
them and save them fine if I do it in notepad; but that way you have to 
restart the elogd server.  I think this is a bug on the new version unless 
I am doing something wrong.  Also I was wondering if you were going to add 
any of the wish list items on version 2.0.6 (Conditional attributes seems 
to have the most votes and would be an extremely helpful feature!! :-).  
Thank You.

Mo.

When logging in with a username and password; then trying to logout or 
change password one gets the following message:

Error: Parameter value too big. Please increase VALUE_SIZE and recompile 
elogd ; Please use your browser's back button to go back 

(up to now I have not yet tried to recompile - may be it works then)

Regards,

Stefan