> 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'.                                                            

That has been fixed in meantime.

> 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.

There is an elegant way to achieve this already now: Use an RSS reader (like
SharpReader for Windows or Straw from Linux) and subscribe to a logbook. Then don't
read the entries directly in the logbook, but read them in your RSS reader. Once you
read them, they become automatically marked read.   

> 5) alignment of attribute table (using <td colspan=2> for multi line            
>    stuff): see elog:669 :)                                                      

Has been fixed as well.

> - Use "and" and "or" operands in queries                                        

Elog supports now regular expressions. So for a "<str1> OR <str2>" one can write

<str1>|<str2>

and for a "<str1> AND <str2>" one can write

<str1>.*<str2>|<str2>.*<str1>

Looks a bit complicated, but maybe some day we will get some code which rewrites
"AND" and "OR" as regular expressions.

> > - Use "and" and "or" operands in queries                                        
> 
> Elog supports now regular expressions. So for a "<str1> OR <str2>" one can write
> 
> <str1>|<str2>
> 
> and for a "<str1> AND <str2>" one can write
> 
> <str1>.*<str2>|<str2>.*<str1>
> 
> Looks a bit complicated, but maybe some day we will get some code which rewrites
> "AND" and "OR" as regular expressions.

It seems that the quick filter searches are now (2.5.4-6) case sensitive.
Could you add an option to specify this in the config file?  Or does it
exist already?

> On many of my logbooks when I specify the menu commands to appear i will get one, usually 'List', which has a
> link not back to the logbook itself but to the root of the elog web server i.e. http:/hostname.domain:8080 
> But nothing will respond without the logbook name after the port number.  This also seems to be happening to the
> "back" submit button.  I can't seem to figure out how to address it.  Suggestions?

Can you show us your config? I had this issue when i was initially trying to integrate elog with apache.

Here's the global section and the logbook section for one of the logbooks affected.  Of note, the 'demo' logbook works
fine and does not have this issue.

[global]
port = 8080
SMTP host = localhost
Welcome title = Welcome
Top group 2012 =  2011, 2010, 2009, 2008, 2007, WINTER

[WINTER]

;*****Look and Feel*****
Page title = Winter Weather
List page title =  Winter Weather
Edit page title = Winter Weather
Theme = default
CSS = default.css
Comment = Winter Weather
Title image =

;*****Email*****
Use Email From = me@me.com
Suppress Email to users = 1
Display Email recipients = 0
Email Encoding = 4
Suppress Email on edit = 1

;*****Settings*****
Entries per page = 30
;Reverse sort = 1
Expand default = 2
Display mode = SUMMARY
Mode command = 0
Time format = %d%B%Y-%H:%M
Summary lines = 15
Show top groups = 0
Message height = 8
Message width = 38
Default encoding = 1
Mode commands = 0
Suppress default = 2
Resubmit default = 2
Back to main = 1
RSS Title = $entry time - $Event

;*****MENU*****
List Menu commands = New, Find
Menu commands = List, New, Edit, Find, Reply, Delete

> Top group 2012 =  2011, 2010, 2009, 2008, 2007, WINTER

Your usage of "Top group" is strange. Top groups should only be used for independent groups of logbooks, more like you were running one dedicated sever fore 
a group of logbooks. Further, you defined logbooks (2008, 2009, ...) which do not exist in your config. Why don't you just remove the "Top group" line from your 
config? If you want to group different logbooks, just use the "group" command as written in the docs.

/Stefan

I answer myself... Modify the value of width=100% in the class .listtitle2 in the .css file.