I found the problem and it is a major bug. If one does
form=SQLFORM(...)
FORM.accepts(form,...)
form.custom.end will not contain the hidden fields (_formkey and
_formname) and custom form will not work. This is used in tools hence
you cannot custom forms with current Auth.
In my opinion this cannot be fixed. Hence I suggest the solution
already posted in trunk lp1181/gc1086:
1) deprecate FORM.accepts(form,...)
2) introduce a new syntax form.accepts(...dbio=False) instead.
Notice that this is backward compatible since the existing code will
work as it did or didn't. If you want to process a SQLFORM with
dbio=False you will be suggested to use the new syntax and if you do,
there will be no problem with custom forms.
The new way is also more powerful because it will deal with file
renaming and uploads even without database IO (SQLFORM.factory for
example).
Any objection?
Thanks to Yannick for discovering this problem.
Massimo
On Aug 23, 12:25 pm, Yannick <ytchatch...@gmail.com> wrote:
> I just sent the both Html page by email....
>
>
>
> > > and what do you mean by "does not work" do you get a ticket? If so,
> > > can you send me the ticket?
>
> No ticket is generate, it just don't generate any feedback. When I
> fill up the form and click on "Submit" nothing happen from the user
> point of view and from the back-end I put a break point on the
> register in Tools.py and the form validation is not going through.
>
> Thanks for your help.
>
> Cheers,
> Yannick P.
>
> On Aug 23, 11:08 am, mdipierro <mdipie...@cs.depaul.edu> wrote:
>
> > same for login..
>
> > On Aug 23, 10:08 am, mdipierro <mdipie...@cs.depaul.edu> wrote:
>
> > > Please email me personally. Can you show me the generated html when
> > > you do:
>
> > > {{=regform.custom.begin}}
> > > {{=regform.custom.widget.first_name}}
> > > {{=regform.custom.widget.last_name}}
> > > {{=regform.custom.widget.email}}
> > > {{=regform.custom.widget.password}}
> > > {{=regform.custom.widget.password_two}}
> > > {{=regform.custom.end}}
>
> > > and what do you mean by "does not work" do you get a ticket? If so,
> > > can you send me the ticket?
>
> > > On Aug 23, 8:04 am, Yannick <ytchatch...@gmail.com> wrote:
>
> > > > Even the customization of the Login Form doesn't work using this :
>
> > > > {{=loginform.custom.begin}}
> > > > <table>
> > > > <tr>
> > > > <td>Email:</td>
> > > > <td>{{=loginform.custom.widget.email}}</td>
> > > > </tr>
> > > > <tr>
> > > > <td>Password:</td>
> > > > <td>{{=loginform.custom.widget.password}}</td>
> > > > </tr>
> > > > <tr>
> > > > <td>{{=loginform.custom.submit}}</td>
> > > > <td></td>
> > > > </tr>
> > > > </table>
> > > > {{=loginform.custom.end}}
>
> > > > So basically this is how i customize the login page:
>
> > > > <form action="" enctype="multipart/form-data" method="post">
> > > > <table>
> > > > <tr>
> > > > <td>Email Address:</td>
> > > > <td><input name="email" type="text"
> > > > value="{{=loginform.latest.email}}"</td>
> > > > </tr>
> > > > <tr>
> > > > <td>Password:</td>
> > > > <td><input name="password" type="password" value="" /></td>
> > > > </tr>
> > > > <tr>
> > > > <td><input type="submit" value="Submit" /></td>
> > > > <td></td>
> > > > </tr>
> > > > </table>
> > > > {{=loginform.hidden_fields()}}
> > > > </form>
>
> > > > Thanks for your help!
>
> > > > Yannick P.
>
> > > > On Aug 23, 8:44 am, Yannick <ytchatch...@gmail.com> wrote:
>
> > > > > Thanks for the note Massimo,
> > > > > I tried it but no the validation is not going through... It's not
> > > > > working.
>
> > > > > Thanks for your help and please let us know if you have any other
> > > > > idea.
>
> > > > > Cheers,
> > > > > Yannick P.
>
> > > > > On Aug 23, 6:54 am, mdipierro <mdipie...@cs.depaul.edu> wrote:
>
> > > > > > auch! I just realized password_two is implamented without a widget
> > > > > > therefore this syntax does not work.
> > > > > > Until this gets firxed this you can do:
>
> > > > > > > {{=regform.custom.begin}}
>
> > > > > > {{=regform.custom.widget.first_name}}
> > > > > > {{=regform.custom.widget.last_name}}
> > > > > > {{=regform.custom.widget.email}}
> > > > > > {{=regform.custom.widget.password}}
> > > > > > <input type="password" name="password_two" />
> > > > > > {{if regform.errors.password_two:}}<div class="error">
> > > > > > {{=regform.errors.password_two}}</div>{{pass}}
> > > > > > {{=regform.custom.end}}
>
> > > > > > Let us know if it works or not.
>
> > > > > > Massimo
>
> > > > > > On Aug 22, 10:31 pm, Yannick <ytchatch...@gmail.com> wrote:
>
> > > > > > > Hello mate,
> > > > > > > quick question... I'm trying to customize the Registration form
> > > > > > > using
> > > > > > > Auth.
> > > > > > > I was wondering about the Password_two field ???
> > > > > > > here is what I'm doing but not working:
>
> > > > > > > ####################################
>
> > > > > > > {{=regform.custom.begin}}
> > > > > > > {{=regform.custom.widget.first_name}}
> > > > > > > {{=regform.custom.widget.last_name}}
> > > > > > > {{=regform.custom.widget.email}}
> > > > > > > {{=regform.custom.widget.password}}
> > > > > > > {{=regform.custom.widget.password_two}} ### <--- here is my
> > > > > > > problem ??? what to i have to put here?
> > > > > > > {{=regform.custom.submit}}
> > > > > > > {{=regform.custom.end}}
>
> > > > > > > ##################################
>
> > > > > > > with this " {{=regform.custom.widget.password_two}}" the
> > > > > > > textfield
> > > > > > > doesn't show... What do I have to put there ?
>
> > > > > > > Can anyone already had the same issue ?
>
> > > > > > > Thanks for your help
--~--~---------~--~----~------------~-------~--~----~
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
-~----------~----~----~----~------~----~------~--~---
