Here are some things for your wish list:                                        
                                                                                
1) elogd should report quota or disk-full problem:  In case a logbook           
   entry cannot be saved (quota or disk full) then a message like               
   'Could not save last entry.  Please contact administrator.' should           
   be displayed.  Currently nothing happens.  Only the submitted                
   entries 'vanish'.                                                            
                                                                                
2) default page view per user, i.e. the 'Back' link goes to                     
   ?mode=Full,summary,... depending on the user that is logged in.              
   Some users complained that 'Back' is not really back.  Maybe                 
   consider renaming 'Back' to 'Default View' or something.                     
                                                                                
3) (related to 1) the 'Back' link should go back to the last used mode          
   (full, summary, threaded,...) and not to the default mode                    
                                                                                
4) mark messages as unread/read on a per user basis: The                        
   implementation of this might be quite involved but it would be               
   rather useful.  One way would be to add a default attribute 'Seen            
   by' to each entry, which lists the login names of the users.  Or 
   files LOGIN_NAME.has_seen can be created which contain the entry 
   IDs of the viewed entries for each user.   
                                                                                
5) alignment of attribute table (using <td colspan=2> for multi line            
   stuff): see elog:669 :)                                                      
                                                                                
You can count my vote for:                                                      
                                                                                
- Use "and" and "or" operands in queries                                        
                                                                                

> Somehow elogd 2.5.4 treat all users as normal user. When clicking on
> "config". All admin users has no "change elogd.cfg" button. Revert back to
> 2.5.2 OK.
> 
> Is there anything I need to change to upgrade other than replaceing elogd?
> Clearing the cookies didn't help.

The button name has been changed from "change elogd.cfg" to "change config file"
since the file name is now variable (can be changed during compile time). But I
guess this is not your problem.

Can you try with the demo logbook (contained in the distribution). Just add
"password file = ..." and "admin user = ..." to the sample elogd.cfg. If I do that
here, everything works fine. You also can send me your elogd.cfg so I can have a look.

I g

I am getting the following error message with version 2.5.4-4 when I try to
add a new entry to a log book.

Attachment file "" empty or not found

If I add the following line to me elogd.cfg I do not get the error, but will
not be able to use attachments.

Enable attachments = 0

I recently upgraded from version 2.2.5 which did not have the problem.  I
did not see anything in the changelog referencing this type of change to how
attachments are handled.

I there something I need to set in the config so that an attachment is not
expected every time a new entry is made?

That problem has been fixed in 2.5.4-5

We are trying to use ELog on Windows XP with Protection on individual log 
book and we unable to login after creating users even if we give correct 
user name and password login screen reappears. We are able to log in to the 
Elog when we use windows 98 Client we are running Elog on Windows XP and 
without password protection on logbook it is working fine with windows 98.

For win xp clients we are using winxp sp 1, ie 6.1 using a proxy server

> W

> We are trying to use ELog on Windows XP with Protection on individual log 
> book and we unable to login after creating users even if we give correct 
> user name and password login screen reappears. We are able to log in to the 
> Elog when we use windows 98 Client we are running Elog on Windows XP and 
> without password protection on logbook it is working fine with windows 98.
> 
> For win xp clients we are using winxp sp 1, ie 6.1 using a proxy server

First, upgrade to 2.5.4-5 (if you haven't done so). If the problem persists,
please start elogd on the server with the "-v" flag, capture the screen output
and send it to me by email so that I can have a look. Please send also your
elogd.cfg file.

- Stefan