I am trying to get the custom redirect gadget in the BVN.404Handler, but I can't get it to work. It simply wont do the redirects I add.
I have installed the latest version (11.2.3).
The 404 redirect is working.
The redirects are set up like this: <oldurl> - <newurl>
If the old url is valid, it will stay there. If the old url doesn't exist anymore, it will show the 404 page.
Can you post an image of your redirects? Ive created some redirects today although in an older version with now problem.
If you export your redirects do they show up in the XML file?
I would post an image if I could, but the image upload doesn't seem to be working?
I exported the redirects to an xml file, and the result is this:
<?xml version="1.0" encoding="UTF-8"?>
Verify that your web.config settings are correct. See: https://github.com/Geta/404handler. Especially the handlermode="On".
Other troubleshooting things:
Thanks for your replies!
So, it seems that it works for urls that don't exist. But it doesn't work for pages that either exist or are expired.
Is this the intended functionality?
I would use IIS Url Rewrite module for redirects instead.
Yes, but we wanted the editors to be able to configure this, so we needed a way to do this in episerver.
For pages that exist you may want to use the built-in shortcut feature
Did you follow the migration steps as instructed in the release notes:If you are upgrading this package from a version previous to 11.2.0 (or 10.4.0 for CMS 10), you should run a migration of data. Open administration view on the gadget and under "Migrate redirects from DDS to SQL." click "Migrate." It will take some time depending on how many redirects you have. After the migration, the message will be displayed with information about how many redirects were moved to the SQL store. The message looks like - "Migrated 1000 redirects from DDS to SQL".
I have a similar problem. Most of the redirects work fine (there are 37) but one in particular insists on redirecting to another page. I have tried removing the offending redirect yet the redirect to the wrong page persists, even after touching the web.config and also restarting iis. What could be going on? The redirect is no longer in the 404handler.redirects table, yet the redirect (to the wrong page) still persists? Is there some cache that is not apparent for this list, that can survive an IIS restart? It defies all logic
If you have triggered a redirect for a page it might be so that the browser has the redirect chached and it could be quite troublesome to make it correct the cached redirect, see https://stackoverflow.com/a/21396547/1381710 So even if you update the redirect your browser keeps redirecting to the old address.
To see if a redirect is cached and is indeed working correctly try add some cache clearing data to the address, like ?cc=123