You signed in with another tab or window. Reload to refresh your session.You signed out in another tab or window. Reload to refresh your session.You switched accounts on another tab or window. Reload to refresh your session.Dismiss alert
{{ message }}
This repository has been archived by the owner on Jun 16, 2022. It is now read-only.
We have some additional routes added to our RouteTable that go to a custom controller. It appears that adding redirects that would be otherwise handled by those custom routes don't work.
For instance, we have a route that looks kind of like
It seems like this route is preventing UrlTracker from having any knowledge of a redirect that we added for an old page that uses this controller but that we now want to redirect somewhere else.
Does anyone know if this is this a limitation of UrlTracker, or is it possible to set up custom routes to controllers that can still be intercepted by UrlTracker if it recognizes a configured redirect?
The text was updated successfully, but these errors were encountered:
We have some additional routes added to our RouteTable that go to a custom controller. It appears that adding redirects that would be otherwise handled by those custom routes don't work.
For instance, we have a route that looks kind of like
RouteTable.Routes.MapUmbracoRoute(
"CustomSearch",
"{parameter1}/{parameter2}/{parameter3}-{parameter4}",
new
{
controller = "CustomController",
action = "CustomAction",
parameter1= UrlParameter.Optional,
parameter2= UrlParameter.Optional,
parameter3= UrlParameter.Optional,
parameter4 = UrlParameter.Optional
},
new UmbracoVirtualNodeByIdRouteHandler(Helpers.getPageId("CustomPageId"))
);
It seems like this route is preventing UrlTracker from having any knowledge of a redirect that we added for an old page that uses this controller but that we now want to redirect somewhere else.
Does anyone know if this is this a limitation of UrlTracker, or is it possible to set up custom routes to controllers that can still be intercepted by UrlTracker if it recognizes a configured redirect?
The text was updated successfully, but these errors were encountered: