Re: Formbuilder ¿bugs?

From: Date: Thu, 09 Dec 2004 06:12:16 +0000
Subject: Re: Formbuilder ¿bugs?
References: 1 2 3  Groups: php.pear.general 
Request: Send a blank email to pear-general+get-16134@lists.php.net to get a copy of this message
On Thu, 9 Dec 2004 07:05:54 +0100, Rodrigo Alvarez Fernández <papipo@gmail.com> wrote: > On Wed, 8 Dec 2004 21:52:58 -0800, Justin Patrin <papercrane@gmail.com> wrote: > > > > On Thu, 09 Dec 2004 05:18:12 +0100, Rodrigo Alvarez <papipo@gmail.com> wrote: > > > Hi PEARs, > > > > > > If I use $fb_textFields, then specified fields become textarea, but if > > > they are defined as NULL, this option overrides their 'required' rule.. > > > > > > > Nice catch. This was indeed a bug. If the field was in any of the > > *type*Fields arrays it would lose its NOT_NULL-ness. Fixed in CVS. > > > > > Is there a way to add an empty option (like $fb_selectAddEmpty), to an > > > enum field (i'm using $fb_selectAddEmpty with $fb_enumFields, but this > > > simply don't work). > > > > Good point. I've added selectAddEmpty support to enums. I've also > > added support for an auto-empty option when the field is allowed to be > > null (link fields also do this now). > > That auto-empty option is exactly what I need ;] > > > > > All of this is in CVS. Thanks much for reporting these. (Bug > > report/feature request would have been acceptable too). > > Which method of reporting this issues do you prefer? (For next time, if any). > Bug reports are best as they are persistent and more likely to be noticed and handled. -- Justin Patrin

« previous php.pear.general (#16134) next »