Demo Discussion
Forum Config Examples Contributions Vulnerabilities
  Discussion forum about ELOG  Not logged in ELOG logo
icon4.gif   Odd bug with conditional and required attributes, posted by T. Ribbrock on Fri Feb 4 23:48:54 2011 
    icon2.gif   Re: Odd bug with conditional and required attributes, posted by Stefan Ritt on Mon Feb 7 15:14:36 2011 
       icon2.gif   Re: Odd bug with conditional and required attributes, posted by T. Ribbrock on Mon Feb 7 17:26:26 2011 
Message ID: 67013     Entry time: Mon Feb 7 17:26:26 2011     In reply to: 67011
Icon: Reply  Author: T. Ribbrock  Author Email: emgaron+elog@ribbrock.org 
Category: Bug report  OS: Other  ELOG Version: 2.9.0-2384 
Subject: Re: Odd bug with conditional and required attributes 

Stefan Ritt wrote:

 

Your problem is the "?" in the attribute Public?.  Attributes may only contain ordinary characters. Unfortunately I did not document this so far. Therefore I put some fix in SVN revision 2387 which allows your attribute Public?, but I'm not 100% sure if this works in all places. The safest is just to remove the question mark.

 Thanks Stefan, I'll try that. It's strange, though: At work, we're running 2.7.6 (and have used older versions in the past) and we have several logbooks with each at least one or two attributes with '?' and never had a problem with conditionals. Hence my surprise when this suddenly hit me with 2.8.1+ at home. Removing the '?' would be quite some work, as I'd have to change all logbooks and the associated data (the latter could probably be done with "rpl", I hope). I'll think about it.

ELOG V3.1.5-fe60aaf