Hmmm Think there is an issue with this release... Please take a look
to the ticket generated after a user tried to login using a fake
password:


####################################################################################

Traceback (most recent call last):
  File "/Users/OnemeWs/App Server/web2py/gluon/restricted.py", line
173, in restricted
    exec ccode in environment
  File "/Users/OnemeWs/App Server/web2py/applications/BeUnickDemo/
controllers/default.py", line 171, in <module>

  File "/Users/OnemeWs/App Server/web2py/gluon/globals.py", line 96,
in <lambda>
    self._caller = lambda f: f()
  File "/Users/OnemeWs/App Server/web2py/applications/BeUnickDemo/
controllers/default.py", line 134, in login
    return dict(loginform = auth.login())
  File "/Users/OnemeWs/App Server/web2py/gluon/tools.py", line 980, in
login
    onvalidation=onvalidation):
  File "/Users/OnemeWs/App Server/web2py/gluon/sqlhtml.py", line 771,
in accepts
    onvalidation,
  File "/Users/OnemeWs/App Server/web2py/gluon/html.py", line 1267, in
accepts
    status = self._traverse(status)
  File "/Users/OnemeWs/App Server/web2py/gluon/html.py", line 449, in
_traverse
    newstatus = c._traverse(status) and newstatus
  File "/Users/OnemeWs/App Server/web2py/gluon/html.py", line 449, in
_traverse
    newstatus = c._traverse(status) and newstatus
  File "/Users/OnemeWs/App Server/web2py/gluon/html.py", line 449, in
_traverse
    newstatus = c._traverse(status) and newstatus
  File "/Users/OnemeWs/App Server/web2py/gluon/html.py", line 449, in
_traverse
    newstatus = c._traverse(status) and newstatus
  File "/Users/OnemeWs/App Server/web2py/gluon/html.py", line 456, in
_traverse
    newstatus = self._validate()
  File "/Users/OnemeWs/App Server/web2py/gluon/html.py", line 1074, in
_validate
    (value, errors) = validator(value)
  File "/Users/OnemeWs/App Server/web2py/gluon/validators.py", line
728, in __call__
    if (not self.banned or not self.banned.match(domain)) \
AttributeError: 'lazyT' object has no attribute 'match'


####################################################################################


Anyway idea ?

Yannick P.


On Dec 14, 11:30 pm, mdipierro <mdipie...@cs.depaul.edu> wrote:
> I do not know. Glad it is fixed anyway.
>
> On Dec 14, 9:19 pm, Yannick <ytchatch...@gmail.com> wrote:
>
> > Hello Massimo,
> > Thanks I just test the new release and realized that the double
> > redirect seem to be fixed on the Auth - Login.... I just wonder what
> > was the root of the issue I got in the previous release...
>
> > Thanks
>
> > On Dec 12, 12:31 pm, Yannick <ytchatch...@gmail.com> wrote:
>
> > > Hello Massimo, thanks for the note...
> > > i did follow your instructions which was :
> > > 1) I put this in the view {{=loginform}}
> > > 2) I print request.function and request.vars from the model
> > > And here is what i see:
> > > login
> > > <Storage {'email': 'sdfsdf...@efsdf.cfd', '_formkey':
> > > '440a019c-1479-4b0d-8e86-b27c0496dd7a', 'password': '12w12123',
> > > '_formname': 'login', '_next': ''}>
> > > login
> > > <Storage {}>
>
> > > It looks like there is a double redirect...
>
> > > I did create a small brand new application just to test the login with
> > > Auth using the web2py admin console ( Just to double check that is not
> > > my code which cause this) and I have the same result...
>
> > > I'll send you the code that I used to test it... I really don't know
> > > why that happen, I think it use to work in the pass...
>
> > > Thanks for your help...
>
> > > Cheers,
> > > Yannick P.
>
> > > On Dec 11, 9:59 am, mdipierro <mdipie...@cs.depaul.edu> wrote:
>
> > > > For debugging purposes....
>
> > > > 1) try replace everything in the view with {{=loginform}}
>
> > > > 2) try print request.function, request.vars
>
> > > > what do you see?
>
> > > > Feel free to send me your code and I will take a look.
>
> > > > massimo
>
> > > > On Dec 11, 8:47 am, Yannick <ytchatch...@gmail.com> wrote:
>
> > > > > Yes I did comment this out "auth.settings.login_next=URL(r=request,
> > > > > f='profile') "
> > > > > but still same old, the double redirect is still there... I really
> > > > > wonder what trigger that double redirection... there is nothing extra
> > > > > I'm doing here, I fulling using Auth API... Hmmm...
>
> > > > > On Dec 11, 9:33 am, Wes James <compte...@gmail.com> wrote:
>
> > > > > > On Thu, Dec 10, 2009 at 8:09 PM, Yannick <ytchatch...@gmail.com> 
> > > > > > wrote:
> > > > > > > Hello thanks for the note...
>
> > > > > > > I did add "print request.function"
> > > > > > > and Yes there is a double redirection because the output print the
> > > > > > > function login twice :
> > > > > > > login
> > > > > > > login
>
> > > > > > > I wonder how to fix this double redirection here is one of the 
> > > > > > > setting
> > > > > > > I have in my controller:
> > > > > > > auth.settings.login_next=URL(r=request, f='profile')
>
> > > > > > comment this out just to see what happens...
>
> > > > > > or use wingide and see where it goes.
>
> > > > > > > Do you have any idea... I'll keep debugging...
>
> > > > > > > On Dec 9, 11:20 pm, mdipierro <mdipie...@cs.depaul.edu> wrote:
> > > > > > >> Add a
>
> > > > > > >> print request.function
>
> > > > > > >> to your model and check if there is a double redirect.
> > > > > > >> The other possibility is that sessions are not working.
>
> > > > > > >> On Dec 9, 9:12 pm, Yannick <ytchatch...@gmail.com> wrote:
>
> > > > > > >> > Is anyone already has this issue and where able to solve it... 
> > > > > > >> > I don't
> > > > > > >> > see any double redirect in my code...
>
> > > > > > >> > Thanks for your help...
>
> > > > > > >> > On Dec 9, 11:36 am, Wes James <compte...@gmail.com> wrote:
>
> > > > > > >> > > Sorry,  I'm not sure exactly when/where I made this change 
> > > > > > >> > > in the last
> > > > > > >> > > week.  You can use wingide and check what the 
> > > > > > >> > > repsponse.flash is
> > > > > > >> > > between function calls.
>
> > > > > > >> > > -wes
>
> > > > > > >> > > On Wed, Dec 9, 2009 at 8:49 AM, Yannick 
> > > > > > >> > > <ytchatch...@gmail.com> wrote:
> > > > > > >> > > > Hmm interesting, thanks for the note... I don't think I'm 
> > > > > > >> > > > doing a
> > > > > > >> > > > double redirection in my code though... can you please let 
> > > > > > >> > > > me know how
> > > > > > >> > > > you resolved that issue when you had it >
>
> > > > > > >> > > > Thanks,
> > > > > > >> > > > Yannick P.
>
> > > > > > >> > > > On Dec 9, 9:30 am, Wes James <compte...@gmail.com> wrote:
> > > > > > >> > > >> On Tue, Dec 8, 2009 at 9:35 PM, Yannick 
> > > > > > >> > > >> <ytchatch...@gmail.com> wrote:
> > > > > > >> > > >> > hello mate,
> > > > > > >> > > >> > I wonder  because I noticed that in auth, when the user 
> > > > > > >> > > >> > fails to login
> > > > > > >> > > >> > (enter a fake username and password) there is no error 
> > > > > > >> > > >> > message
> > > > > > >> > > >> > returned...
>
> > > > > > >> > > >> Yannick,
>
> > > > > > >> > > >> I just tried it on one of my sites and I got "Invalid 
> > > > > > >> > > >> Login" flash message.
>
> > > > > > >> > > >> I had the same issue on one of my forms not showing  
> > > > > > >> > > >> field validation
> > > > > > >> > > >> errors.  It was as mr.freeze indicated, a double redirect 
> > > > > > >> > > >> that was
> > > > > > >> > > >> causing this .
>
> > > > > > >> > > >> -wes
>
> > > > > > >> > > > --
>
> > > > > > >> > > > You received this message because you are subscribed to 
> > > > > > >> > > > the Google Groups "web2py-users" group.
> > > > > > >> > > > To post to this group, send email to 
> > > > > > >> > > > web...@googlegroups.com.
> > > > > > >> > > > To unsubscribe from this group, send email to 
> > > > > > >> > > > web2py+unsubscr...@googlegroups.com.
> > > > > > >> > > > For more options, visit this group 
> > > > > > >> > > > athttp://groups.google.com/group/web2py?hl=en.
>
> > > > > > > --
>
> > > > > > > You received this message because you are subscribed to the 
> > > > > > > Google Groups "web2py-users" group.
> > > > > > > To post to this group, send email to web...@googlegroups.com.
> > > > > > > To unsubscribe from this group, send email to 
> > > > > > > web2py+unsubscr...@googlegroups.com.
> > > > > > > For more options, visit this group 
> > > > > > > athttp://groups.google.com/group/web2py?hl=en.

--

You received this message because you are subscribed to the Google Groups 
"web2py-users" group.
To post to this group, send email to web...@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.


Reply via email to