From reading other posts, it seems this should be possible but it's not working for me. I am trying to map from my old .CFM pages to the new pages in Umbraco.
It should work, as long as you map the extension 'cfm' to the correct .NET handler. Just like .jpg, it will be handled by the StaticFileHandler, which is obvious, and it looks like IIS doesn't know what to do with the .cfm extension.
The
link posted in this thread didn't really help. I can't figure out what
I'm supposed to do with the handler mappings to stop .cfm extentions
giving me problems...
I've just realised (I'm an idiot) that this is in the 301 url tracker forum.
This was the only topic that seemed relevant to my search. I'm not actually using 301 url tracker. All I really need is for .cfm pages to get handled the same way as everything else so that I can rewrite them to a normal page! :(
So just to double check: rewrite to a page that doesn't exist, and use 301 Url Tracker to map that non-existant page (since 301 tracker catches stuff on umbracos 404) to the correct page?
And to confirm, there no way to do this without 301 URL Tracker?
I was doing something stupid. It was because I needed to do domain redirects at the same time. Turns out the solution was to do the domain redirects, and then after that, redirect the .cfm pages without domains in front (it really didn't work trying to do both at the same time).
That probably made no sense but either way what you said helped, so thanks :D
Ability to map from old URLs, non-ASPX
From reading other posts, it seems this should be possible but it's not working for me. I am trying to map from my old .CFM pages to the new pages in Umbraco.
This works: from /googoo to /default
This does not work: from /googoo.cfm to /default
Ignore, wrong forum.
It should work, as long as you map the extension 'cfm' to the correct .NET handler.
Just like .jpg, it will be handled by the StaticFileHandler, which is obvious, and it looks like IIS doesn't know what to do with the .cfm extension.
I think this will help you: http://www.eggheadcafe.com/software/aspnet/28403752/cfm-to-aspx-mapping-no-longer-works-after-upg-to-net20.aspx
Ignore me, thought this was a general post, not one specific to 301 URL Tracker
I'm having problems with this too.
I am setting up a new site, and need to redirect old URLS to new ones. The old URLS are something like
http://www.lorem-ipsum.com/dolor/sedit.cfm
Which I want to redirect to
http://www.lorem-ipsum.com/ipsum
The link posted in this thread didn't really help. I can't figure out what I'm supposed to do with the handler mappings to stop .cfm extentions giving me problems...
Try this: http://our.umbraco.org/projects/developer-tools/301-url-tracker/bug-reports/19029-Getting-InfoCasters-301-URL-Tracker-to-handle-starhtml-extensions-#comment72080
Hi kipusoep, thanks for the link.
I've just realised (I'm an idiot) that this is in the 301 url tracker forum.
This was the only topic that seemed relevant to my search. I'm not actually using 301 url tracker. All I really need is for .cfm pages to get handled the same way as everything else so that I can rewrite them to a normal page! :(
Well, you can do this the same way as mentioned in the link...
Thanks for that quick reply.
So just to double check: rewrite to a page that doesn't exist, and use 301 Url Tracker to map that non-existant page (since 301 tracker catches stuff on umbracos 404) to the correct page?
And to confirm, there no way to do this without 301 URL Tracker?
Yes there is; just don't use it if you don't want to...
If you rewrite your *.cfm requests to *.aspx, you can do anything you'd like to do with them.
Ugh, what's wrong with my brain.
I was doing something stupid. It was because I needed to do domain redirects at the same time. Turns out the solution was to do the domain redirects, and then after that, redirect the .cfm pages without domains in front (it really didn't work trying to do both at the same time).
That probably made no sense but either way what you said helped, so thanks :D
is working on a reply...
This forum is in read-only mode while we transition to the new forum.
You can continue this topic on the new forum by tapping the "Continue discussion" link below.