We installed the 301 tracker in a site which already had the uComponents multi site not found handler installed. We found that the 301 tracker entry in the 404handlers.config was placed after the uComponents entry, therefore the 301s were not getting reached. Here is our corrected 404handlers.config:
Play nicely with uComponents not found handler
We installed the 301 tracker in a site which already had the uComponents multi site not found handler installed. We found that the 301 tracker entry in the 404handlers.config was placed after the uComponents entry, therefore the 301s were not getting reached. Here is our corrected 404handlers.config:
<?xml version="1.0" encoding="utf-8"?>
<NotFoundHandlers>
<notFound assembly="umbraco" type="SearchForAlias" />
<notFound assembly="umbraco" type="SearchForTemplate" />
<notFound assembly="umbraco" type="SearchForProfile" />
<notFound assembly="InfoCaster.Umbraco._301UrlTracker" type="Handler301URLTracker" />
<notFound assembly="uComponents.NotFoundHandlers" type="MultiSitePageNotFoundHandler" />
<notFound assembly="umbraco" type="handle404" />
</NotFoundHandlers>
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.