- Issue created by @jasonawant
- Merge request !144Draft: 3529665: Add route to redirect checker to enable access checking. → (Open) created by jasonawant
- 🇺🇸United States jasonawant New Orleans, USA
Looking for feedback on this drafted MR and inquiry
When the RouteNormalizerRequestSubscriber uses the RedirectChecker here, there is no route name provided as the second parameter.
As such, how can the RedirectChecker properly check access to the route?
In a scenario where logic similar to content_translation_language_fallback_candidates_entity_view_alter() has been implemented for the entity_upcast operation (see patch from #2978048-6: Unpublished translations should fallback to the original language → , 🐛 Sort out and fix language fallback inconsistencies Needs work ), I think the Redirect module will redirect to a translated url alias of an unpublished translation.
If providing the route name to the RedirectChecker::canRedirect() method, the redirect to an unpublished translation alias does not occur.
Active
1.11
Code
Looking for feedback on this drafted MR and inquiry