They're not unworkable, you just have to be very careful about how you use them. In general, I found that you had to prepend the current level of nesting in order to get children of the current page; i.e. if I'm in a page with the "links" slug, I would do href="links/rails" to get the "rails" child page. So I guess if you're not using virtual pages, you might be able to get away with <r:slug/>. YMMV. I just did <r:url/> because I was lazy and didn't want to figure out which way it would go.
Sean Chris Parrish wrote: > Sean Cribbs wrote: > >> When I worked on kckcc.edu, we had a pretty deep structure in some >> places. If I wanted quasi-relative URLs I took to using <r:url/> or >> <r:parent:url/> where necessary to cut down the typing errors. >> >> Sean >> > > So all your URLs wound up as absolute (href="/path/to/the/new/page") but > you only had to input them in a relative-ish fashion > (href="<r:url>/new/page"). Interesting. > > It's beginning to look like true relative links are unworkable (or > untrustworthy). > > _______________________________________________ Radiant mailing list Post: [email protected] Search: http://radiantcms.org/mailing-list/search/ Site: http://lists.radiantcms.org/mailman/listinfo/radiant
