To get around that issue, I had my 404 page dump all the cgi variables into a db table, and then cflocate itself over to a "missing.cfm".
I'm gonna try to compile a list of missing pages and their matching re-directs (via a yet to be built UI) and use that list to send a 303 and then redirect to the correct location, if there is one. A 404 manager for the webmaster, so to speak. We'll see how it pans out. :D On 6/23/06, Matt Williams <[EMAIL PROTECTED]> wrote: > > We have a winner! Yes, the .cfm template I was trying to call for my > custom > 404 was too fancy. Basically it included the same header file as the > normal > site. This header has lots of javascript for DHTML drop down menus and > such. > Thanks Denny. And thanks to everyone patiently trying to help. > -- > Matt Williams > "It's the question that drives us." > > On 6/22/06, Denny Valliant <[EMAIL PROTECTED]> wrote: > > > > Also, it's worth noting, that if you have functions (for navigation, > say) > > on the 404 page, they themselves will throw 404s and include the > > default 404 handler instead of the custom one. > > > > Try a plain html 404.cfm file first, before doing anything fancy. > > > > :d > > > > > > > > > ~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~| Message: http://www.houseoffusion.com/lists.cfm/link=i:4:244743 Archives: http://www.houseoffusion.com/cf_lists/threads.cfm/4 Subscription: http://www.houseoffusion.com/lists.cfm/link=s:4 Unsubscribe: http://www.houseoffusion.com/cf_lists/unsubscribe.cfm?user=89.70.4 Donations & Support: http://www.houseoffusion.com/tiny.cfm/54
