Let me look into this. I am sure there is a way to do it. I just never use custom forms myself. Is the problem with your own widgets? Do you assign widgets explicitely? Can you post an example?
Massimo On Jul 27, 6:00 am, Thadeus Burgess <thade...@thadeusb.com> wrote: > This has been a problem for quite some time, I just did not get around > to complaining about it again until now =) > > If I am to use a custom form (which I almost always do). Then I can't > have my form elements going off and rendering their own errors now can > I? Not very enterprisey of SQLFORM to just assume I want to always > display errors automatically. > > -- > Thadeus > > On Tue, Jul 27, 2010 at 5:04 AM, mdipierro <mdipie...@cs.depaul.edu> wrote: > > It is the INPUT widget that upon serialization displays the errors. I > > can see it may be a problem with custom widgets. > > > On Jul 27, 4:42 am, Thadeus Burgess <thade...@thadeusb.com> wrote: > >> There is no possible way it can. Looking through the source code, it > >> never passes along the extra attributes to anything. The current way > >> the widgets are implemented never use attributes passed to them. > > >> -- > >> Thadeus > > >> On Tue, Jul 27, 2010 at 4:13 AM, mdipierro <mdipie...@cs.depaul.edu> wrote: > >> > I am surprised it does not. can you help debug. > > >> > Try form.errors.clear() > > >> > On Jul 27, 2:29 am, Thadeus Burgess <thade...@thadeusb.com> wrote: > >> >> I don't get it.... > > >> >> SQLFORM.factory(Field....., hideerror=True). > > >> >> It doesn't do what its supposed to. > > >> >> How can I make sure that none of my widgets render errors alongside > >> >> their own INPUT elements without rewriting everything in sqlhtml? > > >> >> -- > >> >> Thadeus
