- Issue created by @arwillame
- 🇧🇪Belgium arwillame
Handle the "allowed_languages" module as well in the last commit of the MR.
I would prefer to use a more global method to fiw this but i dont for now.
If anyone has a better approach?
I am encountering an issue where the "Translate with AI" button provided by the ai_translate module is not appearing on the content translation overview page. After investigating the issue, it seems to be caused by a route alteration conflict with other contrib modules that are also altering the content translation overview route (e.g., language_access).
Both modules are trying to alter the same route (entity.{entity_type}.content_translation_overview), and since ai_translate relies on altering the controller to inject the AI translation button, the changes from other contrib modules (like language_access) may override or prevent the AI functionality from being displayed.
- Enable the ai_translate module and another contrib module that alters the same route (e.g., language_access).
- Go to the content translation overview page of any translatable entity.
- Observe that the "Translate with AI" button does not appear.
Active
1.0
Other Submodules
Handle the "allowed_languages" module as well in the last commit of the MR.
I would prefer to use a more global method to fiw this but i dont for now.
If anyone has a better approach?