Personally, I like the way the widget renders the error by default -
it's pretty tidy and does what you want most of the time. If you want
to remove the error from the widget you could look at the section
called "Switch off errors" on page 220 of the manual.
On Oct 8, 5:03 am, Thadeus Burgess <thade...@thadeusb.com> wrote:
> Massimo, how hard would it be to implement
>
> form.custom.errors.field
>
> instead of having the widget render the error?
>
> -Thadeus
>
> On Wed, Oct 7, 2009 at 10:46 AM, Thadeus Burgess <thade...@thadeusb.com>wrote:
>
> > I have to perform a nasty hack to get around the form.errors displaying on
> > each radio button!
>
> > Make sure to set error_message="". Now it won't display a divs for the
> > error.
>
> > Manually in my view,
>
> > {{if form.errors.has_key('field'):}}
> > <div id="field_error__div">You must enter a value into this field!</div>
> > }}
> > {{=form.custom.widget.field}}
>
> > There has got to be an easier way?
>
> > -Thadeus
>
> > On Wed, Oct 7, 2009 at 7:22 AM, leone <handja...@gmail.com> wrote:
>
> >> I notice that if you don't match defined Field in SQLFORM.factory and
> >> {{=form...}} in html form.results is False but form.errors is empty.
> >> The length attribute of Field-string doesn't produce a desired width
> >> of input. There is a different way to obtain the apprioate layout?
>
> >> On 6 Ott, 21:53, mdipierro <mdipie...@cs.depaul.edu> wrote:
> >> > Let us know when you find out.
>
> >> > Massimo
>
> >> > On Oct 6, 2:43 pm, leone <handja...@gmail.com> wrote:
>
> >> > > Acc.!!
> >> > > It works fine, but form.accets(request.vars) returns always False.
> >> > > I have a button type=submit with an image before {{=form.custom.end}}.
> >> > > I suppose this could be an error and Ihave substitute it with
> >> > > {{=form.custom.submit}} with no result.
> >> > > I have difficult to find solutions using your manual, but it is my
> >> > > problem.
>
> >> > > On 6 Ott, 19:58, mdipierro <mdipie...@cs.depaul.edu> wrote:
>
> >> > > > It is automatic. You just need
>
> >> > > > Field('name',requires=IS_IN_SET(('a','b','c')))
>
> >> > > > or requires IS_IN_DB
>
> >> > > > On Oct 6, 11:32 am, leone <handja...@gmail.com> wrote:
>
> >> > > > > How can I render a <select> <option> sequence by Field in
> >> > > > > SQLFORM.factory?
> >> > > > > Thanks!
>
> >> > > > > On 6 Ott, 17:14, mdipierro <mdipie...@cs.depaul.edu> wrote:
>
> >> > > > > > yes
>
> >> > > > > > form=SQLFORM.factory(Field('x'),Field('y'))
>
> >> > > > > > <HTML>
> >> > > > > > ......
> >> > > > > > {{=form.custom.begin}}
> >> > > > > > {{=form.custom.widget.x}}
> >> > > > > > {{=form.custom.widget.y}}
> >> > > > > > {{=form.custom.submit}}
> >> > > > > > {{=form.custom.end}}
> >> > > > > > ......
> >> > > > > > </HTML>
>
> >> > > > > > On Oct 6, 9:51 am, leone <handja...@gmail.com> wrote:
>
> >> > > > > > > I want use FORM object and helpers objects, but I need
> >> complete
> >> > > > > > > control over html code.
> >> > > > > > > Exists a factory method as in SQLFORM, so I can code
> >> > > > > > > <HTML>
> >> > > > > > > ......
> >> > > > > > > {{=form.begin}}
> >> > > > > > > {{=form.widget.x}}
> >> > > > > > > {{=form.widget.y}}
> >> > > > > > > {{=form.submit}}
> >> > > > > > > {{=form.end}}
> >> > > > > > > ......
> >> > > > > > > </HTML>
> >> > > > > > > ???
> >> > > > > > > If not, exist an alternative way to obtain the advantages of
> >> web2py
> >> > > > > > > and html flexibility?
--~--~---------~--~----~------------~-------~--~----~
You received this message because you are subscribed to the Google Groups
"web2py-users" group.
To post to this group, send email to web2py@googlegroups.com
To unsubscribe from this group, send email to
web2py+unsubscr...@googlegroups.com
For more options, visit this group at
http://groups.google.com/group/web2py?hl=en
-~----------~----~----~----~------~----~------~--~---
