How do I set up Redirects in 12.x ?

Hi Zak,

There's currently no UI for managing Url Redirects, although we do have it logged as an improvement to make. There is an In-Process UrlRedirects API where you can create this redirect, though it does require custom development, perhaps through an IInstallablePlugin to create this redirect one time.

Redirects are created automatically when content is moved. However, this does not extend to items moved before the system was in place.

What's been your upgrade path/timeline?

What is an IInstallablePlugin? I would prefer a method that does not require custom development.

 IInstallablePlugin Plugin Type  - further info is in our  Plugins Developer Training, but this would definitely fall under the category of custom development.

Another option is to set up an IIS redirect for that specific path.

(Side note: The format of the old url has been a legacy format in Community for a number of versions - particularly the use of the .aspx extension.  If you try going to community.idera.com/.../filter-powershell-results-fast-and-text-based without the .aspx extension, it does actually preserve the route in your community, though it is a Page Not Found. The route parser is reading the non-.aspx route as a valid legacy route and using the route to attempt to parse the correct blog post out of it, but it's unable to find it, since the blog it's in has changed.)

 IInstallablePlugin Plugin Type  - further info is in our  Plugins Developer Training, but this would definitely fall under the category of custom development.

Another option is to set up an IIS redirect for that specific path.

(Side note: The format of the old url has been a legacy format in Community for a number of versions - particularly the use of the .aspx extension.  If you try going to community.idera.com/.../filter-powershell-results-fast-and-text-based without the .aspx extension, it does actually preserve the route in your community, though it is a Page Not Found. The route parser is reading the non-.aspx route as a valid legacy route and using the route to attempt to parse the correct blog post out of it, but it's unable to find it, since the blog it's in has changed.)