Ah, that's the fact I feared :) I perhaps can pass in parameters as 'args' as a work around and create the _next hyperlink by converting args to anchor text.
I'm using browser history management so anchors have to be used 'eventually'. On 18 Jun 2011, at 13:08, Anthony <[email protected]> wrote: > As I understand it, browsers do not send anchors (i.e., "fragment > identifiers") to the server, so if a user clicks on > http://127.0.0.1:8000/init/default/account#Invite, the http request sent to > web2py will not include the "#Invite" part of the URL, and web2py will > therefore not be able to include it in the redirect. Fragment identifiers are > only meant for client-side purposes (i.e., to identify fragments within > returned resources). You might be able to get it to work using Javascript -- > that's how sites with hash-bang URLs work. > > Anthony > > On Friday, June 17, 2011 4:46:52 PM UTC-4, Carl wrote: > The anchor text of URLs is lost when I'm redirected to login and then > on to "next. > > I think it's down to gluon.py requires_login() > this code: > > next = URL(r=request,args=request.args, > vars=request.get_vars) > ... > self.settings.login_url + '?_next='+urllib.quote(next) > /// > > I think URL() creates an url but doesn't added any existing anchor > text. > > thoughts, any one?
