Demo Discussion
Forum Config Examples Contributions Vulnerabilities
  Discussion forum about ELOG  Not logged in ELOG logo
icon4.gif   elog crashes when admin tries to register new users, posted by Heiko Scheit on Wed May 18 14:18:07 2005 
    icon4.gif   Re: elog crashes when admin tries to register new users, posted by Stefan Ritt on Sat Jun 4 12:25:57 2005 
       icon4.gif   Re: elog crashes when admin tries to register new users, posted by Heiko Scheit on Thu Jun 9 15:20:04 2005 
          icon2.gif   Re: elog crashes when admin tries to register new users, posted by Stefan Ritt on Fri Jun 17 22:33:29 2005 
             icon2.gif   Re: elog crashes when admin tries to register new users, posted by Heiko Scheit on Tue Jun 21 19:24:58 2005 
                icon2.gif   email flagged as spam, posted by Heiko Scheit on Tue Jun 21 19:38:06 2005 
                   icon2.gif   email flagged as spam, posted by Stefan Ritt on Fri Jun 24 21:15:14 2005 
                icon2.gif   Re: elog crashes when admin tries to register new users, posted by Stefan Ritt on Fri Jun 24 21:02:05 2005 
Message ID: 1206     Entry time: Tue Jun 21 19:24:58 2005     In reply to: 1198     Reply to this: 1207   1212
Icon: Reply  Author: Heiko Scheit  Author Email: h.scheit@mpi-hd.mpg.de 
Category: Bug report  OS: Linux  ELOG Version: 2.5.9 
Subject: Re: elog crashes when admin tries to register new users 

Quote:

Thanks for that info. It helped me debugging things. The problem is that the "activation" URL does not contain a logbook if there is a global password file. I have never tried that so of course it crashes Crying

I tried to fix this and committed the changes to CVS. Can you try with that version?


Not really, unless you have a fixed 2.5.9 version. Version 2.6 has
way too many new features, which I don't want at the moment. Or is
there a config option to get the old behavior?

I also saw that the format of the email notification has changed. As
I have scripts (bash, akw, procmail) that depend on this format I
would need much more time than I currently have to actually test
everything.

Maybe you should consider supporting two branches, say 'stable' (2.5.9
currently) and 'experimental' (2.6 currently)? For 'stable' only
severe bugs and security issues are fixed and in 'experimental' new
features are introduced. What do you say?

For me the risk of upgrading to 2.6 now seems to high, as many people
depend on the logbook.
ELOG V3.1.5-fe60aaf