Last modified: 2010-03-09 15:41:18 UTC
In the example above, using the mobile site brings up a search page for the article, rather than the article itself. Clicking on the article merely appears to refresh the page.
I have done some initial investigation on this bug and it seems that it is related to the way that URLs in the Merb framework are interpreted. It just assumes that a double slash is a mistake. Which, isn't always a bad assumption. However, in this case it bites us in the ass.
It likely changes the // internally to /./
#merb <+merboutpost> thedj: AH :-) <+merboutpost> thedj: hm... <+merboutpost> thedj: interesting, that's the router behaviour, feel free to file the Ticket in the lighthouse. It will take me some time to change that. I remember I've seen some similar ticket or conversation. <+merboutpost> thedj: I remember that the result was: Not easy to fix :-) No time to figure out how their OpenID works, and don't feel like signing up for Yet Another Bugreporting system. https://merb.lighthouseapp.com/
Related: https://merb.lighthouseapp.com/projects/7433/tickets/398-merb-router-doesn-t-match-with-url-in-regex
Fixed this with some custom code in the show action. Only fixed for double slashes at the beginning of articles. Any double slash in the middle will break, but I can't think of any examples of that, so we will consider this closed for the moment. PS: please don't just arbitrarily create an article with two slashes. ;)
