according to the users guide,

http://midas.psi.ch/elogs/Database/?cmd=New&pType=PC

should create an entry with the type value set to PC, but this doesn't work

> according to the users guide,
> 
> http://midas.psi.ch/elogs/Database/?cmd=New&pType=PC
> 
> should create an entry with the type value set to PC, but this doesn't work

Now it works. Updated elog version under CVS and as a snapshot (see Download Page)

> according to the users guide,
> 
> http://midas.psi.ch/elogs/Database/?cmd=New&pType=PC
> 
> should create an entry with the type value set to PC, but this doesn't work

Thanks!

Hi everybody,

several people have reported of strange problems concering the login/logout
behaviour of elog. After editing elogd.cfg, they could not logout any more
from a logbook, or they were not able to log in. Here comes some
explanation. If you are not interested in the details, skip to the last section.

The login parameters (user name and password) are sored in cookies, which of
course have to be enabled for the elog site in your browser. Each cookie can
contain an optionsl "path=..." statement, which defines for which subtree in
the URL the cookie is valid. If you use a "global" password file (one where
the "password file = ..." statement is in the [global] section of
elogd.cfg), the elogd server stores a cookie with path "/", so it will apply
to the whole site and therefore to all underlying lobooks. If your password
file is defined in an individual logbook section, the elogd server stores a
cookie with path "/<logbook>", so that it applies only to the specific logbook.

The problem arises now if one moves the password file statement from the
global section to the logbook section or back. The browser might still have
old cookies, whic can override any newly set cookie.

Long story short conclusion: If you observe this behaviour, just delete all
cookies in your browser and you should be fine. I added some additional code
to version 2.5.4 which catches a few cases but unfortunately not all.

The upgrade was done by just replacing elogd from 2.5.2 to 2.5.4 from the rpm.

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.

Thanks,
.nait.

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                                        
                                                                                

At some point, in the last week or so, I upgraded the debian-unstable
version (r1459-1) of elog.  Now, PostScript files (as attachments) are
displayed (shown in ascii text, instead of just showing the link).  

Is there an option in the elog.cfg to only display certain files (like .gif
or .jpg).

At some point, in the last week or so, I upgraded the debian-unstable
version (r1459-1) of elog.  Now, PostScript files (as attachments) are
displayed (shown in ascii text, instead of just showing the link).  

Is there an option in the elog.cfg to only display certain files (like .gif
or .jpg).