> > I've taken the approach of having a separate table mapping urls to > > page numbers and a file not found behaviour that performs > > redirects for old mappings (I also trawl through my server > logs for > > 404s and correct any repeated spelling mistakes / truncations) - > > I've left it as a separate table that I maintain by hand so as not > > to confuse the page tree. > > > > http://soxbox.no-ip.org/radiant/svn/extensions/x_groggy/app/models/ > > groggy_file_not_found_page.rb > > That rocks. It would be great if you could make that a separate > extension with an interface to manage the redirect table. (Hint, > hint. ~_^)
Well, you're free to take my code and clean it up (Hint, hint). The extension works great for regular pages but not so well for pages that can be referenced by multiple urls - ie, my gigs page is a single page that filters gigs based on the last part of the url - since my mapping is from url to page id and not url to url, that means I can't redirect to those individual state filters. My comics page (AlphabetPage) is a similar beast. The reasoning behind this is that these old urls are likely to be referenced well into the future and I wanted it to be robust in the face of reparenting. I had a brief discussion a week or two ago about having a page url table that would map urls to pages for fast lookup and would also remain persistant so that if a page moves, there would still be a reference in the lookup table for that page so that it's old url would also work. There's a few problems with that approach, but it's something that I'd like to try fleshing out to see if those problems are surmountable - I think that might be the way to go for providing page aliases. Dan. _______________________________________________ Radiant mailing list Post: [email protected] Search: http://radiantcms.org/mailing-list/search/ Site: http://lists.radiantcms.org/mailman/listinfo/radiant
