- Issue created by @Remco Hoeneveld
- 🇳🇱Netherlands Remco Hoeneveld
Nvm closing this i see that the code we where using is not drupal standard.
The current implementation of the DynamicPathProcessor class always uses the current language from the language manager to determine which translation of an entity to load. This approach causes issues when the processor is triggered from a backend admin route, where the default language is used. As a result, the view_mode processing may not resolve correctly for multilingual content when accessed through the admin interface.
Set up a multilingual Drupal site with content in multiple languages.
Create a view mode that uses the DynamicPathProcessor.
Log in as an administrator and navigate to a backend route that triggers the DynamicPathProcessor for content in a non-default language.
Observe that the entity is always loaded in the default admin interface language, regardless of the content's actual language.
Modify the DynamicPathProcessor to prioritize the language code from the request attributes (specifically 'path_langcode') if available. This allows the processor to use the correct language context even when triggered from backend admin routes. If no specific language is set in the request, it will fall back to the current language from the language manager.
Implement the proposed change in the DynamicPathProcessor class as shown in the provided diff.
Update unit tests to cover the new language determination logic, including scenarios for both frontend and backend routes.
Test the change thoroughly in a multilingual environment, especially focusing on admin interface interactions.
Update relevant documentation to reflect the new behavior and its impact on multilingual content management through the admin interface.
No direct UI changes. The modification affects the backend processing of paths and entity loading, particularly improving the behavior when managing multilingual content through the admin interface.
No public API changes. The modification is internal to the DynamicPathProcessor class.
No data model changes. This modification only affects how existing data is processed and doesn't alter the structure of stored data.
Active
4.0
Code
Nvm closing this i see that the code we where using is not drupal standard.