I don't know if this will help solve your problem but maybe it will help someone out there. If you are using IIS 7.0 (integrated pipeline), you need to manually add the http module to the modules section of system.webServer in the web.config. The package automatically adds the module to the system.web/httpmodules node, but it does not add it to the system.webServer node used by IIS 7.0.
I've just installed this but I'm getting a 404 instead. The config line mentioned above (<add name="terabytePermanentRedirect" type="Terabyte.Umbraco.Modules.PermanentRedirect.Redirect" />) is in both system.web/httpmodules and system.webServer/modules in the web.config.
Annelie, I have this running under 4.7.0 as well, so that shouldn't be a problem. If you have added the module to both web.config locations and you are using a content picker property with alias umbracoPermanentRedirect then it should work. You might try bumping your app domain (editing web.config should do it, but iisreset is a sure thing). If you're using IIS 7.0, make sure you're using integrated mode. You can also try using ?umbDebugShowTrace=true in you query string to see if any errors are being thrown and also check for .Net Runtime warnings or errors in your system's application event logs. It sounds to me like you may have an error not allowing the DLL to load properly (as Matt pointed out as well).
If none of that works, please post what version IIS you are using and the system.web/httpmodules and system.webServer/modules sections of your web.config.
Matt and Jeremy, thank you so much for your help. It turns out that the reason it didn't work was that I didn't have a template selected for the page I was trying to redirect from. Sorry about this, I'm new to Umbraco so didn't spot this until now.
Is there any known issues for using this in a load balanced environment? This worked fine on dev when I tested it last week, but when we uploaded to live any items were just published to the staging server and not to the three load balanced production servers. This was the only change that was made, and when we rolled back publishing worked fine again. Any ideas why this happened? Also, the live config didn't have a httpModules node, so I added the whole node.
I've just moved an old .asp site to Umbraco so need to issue 301 redirects for any requests for the old .asp pages. Does http://our.umbraco.org/projects/backoffice-extensions/permanent-redirect allow you to set this up within Umbraco? I don't want to install the package unless I understand what it does as some packages don't uninstall well. There doesn't seem to be any documentation with it.
I have installed the module, but it still does not do any redirects.
Can you please let me know if there is any other configuration require after installing the module?
Same problem - did you find a solution?
I don't know if this will help solve your problem but maybe it will help someone out there. If you are using IIS 7.0 (integrated pipeline), you need to manually add the http module to the modules section of system.webServer in the web.config. The package automatically adds the module to the system.web/httpmodules node, but it does not add it to the system.webServer node used by IIS 7.0.
Add the following to system.webServer/modules:
<add name="terabytePermanentRedirect" type="Terabyte.Umbraco.Modules.PermanentRedirect.Redirect" />
Thanks, after installing this on Umbraco 4.7.2 with IIS7 I was just being shown my configured 404 page.
Adding the above to the web.config fixed it.
I've just installed this but I'm getting a 404 instead. The config line mentioned above (<add name="terabytePermanentRedirect" type="Terabyte.Umbraco.Modules.PermanentRedirect.Redirect" />) is in both system.web/httpmodules and system.webServer/modules in the web.config.
Is there anything else I need to do?
Sorry, forgot to mention, I'm using Umbraco 4.7.0.
In mine the declaration is in <system.webServer><modules> and <httpModules>
You may want to check the DLL got installed correctly.
Annelie, I have this running under 4.7.0 as well, so that shouldn't be a problem. If you have added the module to both web.config locations and you are using a content picker property with alias umbracoPermanentRedirect then it should work. You might try bumping your app domain (editing web.config should do it, but iisreset is a sure thing). If you're using IIS 7.0, make sure you're using integrated mode. You can also try using ?umbDebugShowTrace=true in you query string to see if any errors are being thrown and also check for .Net Runtime warnings or errors in your system's application event logs. It sounds to me like you may have an error not allowing the DLL to load properly (as Matt pointed out as well).
If none of that works, please post what version IIS you are using and the system.web/httpmodules and system.webServer/modules sections of your web.config.
Matt and Jeremy, thank you so much for your help. It turns out that the reason it didn't work was that I didn't have a template selected for the page I was trying to redirect from. Sorry about this, I'm new to Umbraco so didn't spot this until now.
Is there any known issues for using this in a load balanced environment? This worked fine on dev when I tested it last week, but when we uploaded to live any items were just published to the staging server and not to the three load balanced production servers. This was the only change that was made, and when we rolled back publishing worked fine again. Any ideas why this happened? Also, the live config didn't have a httpModules node, so I added the whole node.
Does anyone know if this should work in a load balanced environment?
I've just moved an old .asp site to Umbraco so need to issue 301 redirects for any requests for the old .asp pages. Does http://our.umbraco.org/projects/backoffice-extensions/permanent-redirect allow you to set this up within Umbraco? I don't want to install the package unless I understand what it does as some packages don't uninstall well. There doesn't seem to be any documentation with it.
Craig
Craig,
If you're looking to map old ULs to new pages I think there are more suitable packages available. This is not the package to do that.
Thanks Matt, I'll continue looking.
Craig
Perfect! I worked adding it to the web.config. Maybe you should write it in the project description?
Has anyone had any luck with this package in v6.0.3?
I upgraded my site to 4.11.3 and it stopped working for me although someone else reported on my thread that it worked for them.
is working on a reply...