I could, but I don't see the point in creating a manual redirect while there is no node with the target url (/frontpage.aspx)...

Could you elaborate a bit more on this?

It might just be me not understanding the purpose/features of the package as it is right now :)

My question is:

Is it possible to make 301 URL Tracker redirect from an old URL on a old CMS to a new existing one on Umbraco.

Yes, that's the whole purpose of the 301 URL Tracker ;-) I'll explain:

- Say you have this old site (somesite.com)
- You have a page calles '/cars.aspx'
- You're now using umbraco with directoryUrls on
- The new url is '/cars'
- If you visit '/cars.aspx' you will get a 404 page from umbraco
- Now you should create a URL Mapping with the 301 URL Tracker on the node 'Cars' and say the old url is 'cars.aspx'
- From now on '/cars.aspx' will redirect to '/cars'

Hope that makes things a bit more clear :-)
If you have any questions left, don't hesitate to ask!

Perfect, thats how i hoped it would work :)

How about other extentions than .aspx, is that supported? And parameters eg. index.asp?id=1234 ?

Every extension (or extension-less; a.k.a. directory urls) is supported, as long as you configure IIS the right way to map requests with the specific extension to .NET...
QueryString parameters are not supported yet, but I'll look into it next week :-)

Sounds great :)

As far as i know a lot of the older sites on Content management systems are using parameters, so it would be a great thing to have on your package.

Perfect! Thank you

is working on a reply...