I have a use case where a previously published Resource still needs to exist in the system, but no longer be published. In this case, a Redirect rule should be configured to reroute traffic to a more appropriate location than 404 page.
However, Redirector will not let you create the redirect:
(!) Pattern URI already exists for Resource ID 123 in "web" context... Redirect will not work!
Technically speaking this statement is not true. Yes, if you are logged into mgr context as an Administrator the redirect will not occur. (Not a bad thing!) However, for a normal web user (anonymous), the Redirect works exactly as configured.
It would be nice if Redirector still warned against this potential concern, but at least allowed you to Save. Even better, provide a system setting to allow overriding this behavior entirely, and remove the warning along with it. Or, perhaps it only warned / prevented for Published & non-deleted Resources?
pixelchutes
commented
9 years ago
I have a use case where a previously published Resource still needs to exist in the system, but no longer be published. In this case, a Redirect rule should be configured to reroute traffic to a more appropriate location than
404page.However, Redirector will not let you create the redirect:
Technically speaking this statement is not true. Yes, if you are logged into
mgrcontext as an Administrator the redirect will not occur. (Not a bad thing!) However, for a normal web user (anonymous), the Redirect works exactly as configured.It would be nice if Redirector still warned against this potential concern, but at least allowed you to Save. Even better, provide a system setting to allow overriding this behavior entirely, and remove the warning along with it. Or, perhaps it only warned / prevented for Published & non-deleted Resources?