That's very strange. I just assumed that we were using the Rails routing system to build our paths. In many places we are, but the <a> tag and its helpers build them up as strings, and of course they don't support the host or protocol options. I'm really surprised that nobody has complained about that before.
Now I just have to decide whether to refactor object_url to base it on url_for or whether I should just take the easy route and add host & protocol options. Opinions? Is the app you're working on using 1.4? Whatever I do should backport fairly easily, but... Bryan On Thu, Aug 9, 2012 at 8:15 PM, kevinpfromnm <[email protected]> wrote: > Trying a subdomain enabled site but because most (all?) of the links aren't > using url_for, the standard rails way of changing how the subdomain is used > no longer works. Really have a simple case where I want urls to redirect > back to the main url when viewing a page through the subdomain, but either > I'm too tired to be doing this or it's obfuscated in the source. Either > way, was hoping there'd be a simple one place handles all change to be made. > > -- > You received this message because you are subscribed to the Google Groups > "Hobo Users" group. > To view this discussion on the web visit > https://groups.google.com/d/msg/hobousers/-/RH1hpKLC-SwJ. > 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/hobousers?hl=en. -- You received this message because you are subscribed to the Google Groups "Hobo Users" 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/hobousers?hl=en.
