garyrgi touched base on what I was talking about. I had to do
this on our main www.shift4.com when we updated it. The problem was
that we didn't want to loose all the search engine links when
various template names changed or were consolidated.
I wrote a 404.cfm template. In it I created a big list
template names specifying the old name and the new name (actually I
use an xml document to define this and I also have a parameter of
whether to use cflocate vs. dish it out directly using cfinclude or
cfcontent -- this way even pdf's or other documents can be found as
well).
If I find the template called in the old list, I do whatever
action I need to do to send the user to the new location or present
the information to the user from the new location. If I don't find
a match, then I take the user to our site map with a message that
the file requested was not found.
The only tricky part is that in IIS or whatever server you
use, somewhere there is a 404 template setting -- you'll need to
point this to your 404.cfm template.
It works. Try any of the following links -- both do exactly
what I just described (I also pasted my corresponding xml
definition just to give you an idea of what I am doing):