Okay, I was starting to feel stupid because I couldn't get nuttin' to work. However, I did get a custom 404.cfm page to come up on my dev Workstation. But I still can't get it to go on my dev Server. The main difference between my workstation and server is the IIS Default Web Site directory. My workstation uses the default C:\inetpub\wwwroot. I put my 404.cfm file there. The server uses D:\WebRoot\DomainName.
So then I have a '/' mapping on the server that points to just D:\WebRoot. Maybe this is screwing things up. I have tried various possibilities and mappings and am not having any luck. I created a mapping named '/404' pointing to 'D:\WebRoot\DomainName\404'. Then in the Missing Template Handler I put /404/404.cfm. After submitting the CF Admin says it cannot find the file and will use the default instead (I have CF 7 on my Dev Server, which gives this feedback whereas I don't think CF 6.1 does). So to fix this I change the Missing Template Handler field to /DomainName/404/404.cfm (essentially eliminating the need for the /404 mapping). Server updates okay, but when browsing to a non-existant .cfm file, I still get the default 404 error. Aaargh! This isn't even that big of a deal, but has become frustrating and seems like it shouldn't be so confusing. -- Matt Williams "It's the question that drive us." ~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~| Message: http://www.houseoffusion.com/lists.cfm/link=i:4:244541 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=11502.10531.4 Donations & Support: http://www.houseoffusion.com/tiny.cfm/54
