umpf. the behaviour is reproducible. The thing is, handling component redirects with ajax as normal redirects is bad because ajax just follow the same convention as browsers and it's impossible to intercept a get wich follows a redirect from a normal get in any way.
For now the proposed fix/workaround is to pass an explicit _action to the FORM, which will prevail if explicitely found. Its quite easy because _action=URL() gets things done pretty quickly and painless. Now, for the "real fix", we'd have either to add an header to every ajax or we won't be able to distinguish a 200 from a 302+200. I'm open to possible solutions not involving add an header to every ajax request. -- Resources: - http://web2py.com - http://web2py.com/book (Documentation) - http://github.com/web2py/web2py (Source code) - https://code.google.com/p/web2py/issues/list (Report Issues) --- 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 web2py+unsubscr...@googlegroups.com. For more options, visit https://groups.google.com/d/optout.
