Sean Cribbs wrote: > They're not unworkable, you just have to be very careful about how > you use them.
> I'm in a page with the "links" slug, I would do href="links/rails" > to get the "rails" child page. Actually, the example above, it only works if your browser is pointed to: 'example.com/links' (i.e. the browser 'thinks' its opening the links file in the root directory). If, instead, your browser is pointed to: 'example.com/links/' (i.e. the browser 'thinks' its opening the default file in the links directory), the link sends the browser looking for 'example.com/links/links/rails' My point about 'unworkable' is that, there is no way to guarantee that user's browser is always at the address with (or without) trailing slash. And so, if your href's don't give the full address from the root, your links may not work. The problem is that Radiant gives feedback that the user's at the "right" page even when, in fact, they may have the slash wrong for the relative links to work. As for the ability to limit this issue by forcing a trailing slash on every page (or preventing it everywhere), I never considered using the server. I like that. I also agree with Oliver that it fits well in Radiant (I would certainly configure it within Radiant if given that option). But it's also not something you'd change regularly, so I could make do with Apache. -- Posted via http://www.ruby-forum.com/. _______________________________________________ Radiant mailing list Post: [email protected] Search: http://radiantcms.org/mailing-list/search/ Site: http://lists.radiantcms.org/mailman/listinfo/radiant
