That change originated from this discussion:
https://groups.google.com/d/msg/web2py-developers/6J6U6f_VL00/q0GMWvwsl8gJ
For now you can do FORM(...,_action="")
but I would like to get to the bottom of this. Why does it not work? That
is supposed to be the way to do it according to the discussion thread? Can
you explain to us what behavor you see?
On Thursday, 7 March 2013 06:18:06 UTC-6, Eric wrote:
>
> I've just upgraded to version 2.4.2. Now the custom login page doesn't
> work anymore in Firefox and Chrome, on the previous version everything
> worked nicely on both browsers.
>
> What I discovered it that since version 2.4.2 a little "#" was popping up
> into the action attribute of our custom login form... When I remove the
> hashtag with Firefox the login form works as expected again... So, with
> versie 2.4.2 I end up with this form tag (that doesn't work in FF and
> Chrome):
> <form method="post" enctype="multipart/form-data" action="#"
> autocomplete="off">
>
> When I change it into:
> <form method="post" enctype="multipart/form-data" action=""
> autocomplete="off">
>
> Everything works again :)
>
> Did something change in this version that's causing this behavior?
>
> The view isn't more than this when you strip out all the HTML:
>
> {{=form.custom.begin}}
> <div class="row form">
> <label>{{=T('E-mail address')}}</label>
> {{=form.custom.widget.email}}
> </div>
> <div class="row form">
> <label>{{=T('Password')}}</label>
> {{=form.custom.widget.password}}
> </div>
> {{=form.custom.submit}}
> {{=form.custom.end}}
>
--
---
You received this message because you are subscribed to the Google Groups
"web2py-users" group.
To unsubscribe from this group and stop receiving emails from it, send an email
to [email protected].
For more options, visit https://groups.google.com/groups/opt_out.
