On Aug 27, 2:09 pm, Mike Orr <[email protected]> wrote: > I don't know, it could be a bug in named route generation. Cc'ing Ben. > The examples in the manual show only the controller-action syntax. > Named routes should work, but perhaps they don't.
Thanks for helping me look into this. > I'm also surprised that you're getting the host prefix when you didn't > specify 'qualified=True'. If you're not spanning domains (going from > one subdomain to another), eliminating the host prefix would also > solve your problem, right? Yeah, if all it returned was /verify, that would be fine. When the user is on a subdomain, I want them to stay on that subdomain. I had a named route in my template and when I tried to use the form from a subdomain, I noticed the problem. -- You received this message because you are subscribed to the Google Groups "pylons-discuss" group. To post to this group, send email to [email protected]. To unsubscribe from this group, send email to [email protected]. For more options, visit this group at http://groups.google.com/group/pylons-discuss?hl=en.
