Hi,
I wasn’t sure what to call this post - here goes…
I’m migrating from an existing site catalog to Radiant based site. The
site is
indexed in various search engines already, so after deploying the new
Radiant
based site, it is very likely a search engine result will produce a link
to an
old site URL. I’d like to devise a way to accommodate the old URL in
the new
site.
This is what I’m thinking: reviewing the site logs I’ve created a table
of old
url and new Radiant url. Now, I need to write some code that checks the
url
for a reference in the aforementioned table before returning a 404.
My
assumption is that the old url will not be found in Radiant based site,
so the
FileNotFoundPage will be called. (I want to check the URL before
processing
FileNotFoundPage and if found in the table, redirect to the new URL, of
course).
So, where is the best place to integrate this code into Mental?
app/models/FileNotFoundPage and override render method?
I see in Page:
children.find(:first, :conditions => “class_name = ‘FileNotFoundPage’”)
So, I guess the FileNotFoundPage is hardcoded.
Could I write an extension to drop in a custom FileNotFoundPage?
Your thoughts appreciated,
Todd