- Issue created by @svendecabooter
- 🇧🇪Belgium svendecabooter Gent
Added a WIP MR to fix the issues I already encountered.
I will need to dig a bit deeper to see what else is breaking for my project, when I find some more time.
I have an entity type that uses form modes, and is translatable.
In version 3.0.0 I was able to translate these entities, by loading them in the appropriate language, and clicking the right form mode manager tab.
E.g. when my original entity has a form mode "Advice", I could go to `/en/{entity_type}/123/edit/advice` and configure the original entity. When I want to set up a translation in Dutch, I'd go to `/nl/{entity_type}/123/edit/advice` and edit the translation of that entity.
In version 3.1.0 that no longer seems to work.
Upon inspecting the changes between 3.0.0 and 3.1.0, I saw a commit related to content translation, which seems to break this functionality. Upon inspection of the code, I noticed the following:
- It seems node-specific in some parts of the code, so wouldn't work with my custom entity
- It only adds a "content translation add" route, not an edit route. I'm not sure if that is by design, because the edit path should keep working as I mentioned above (it doesn't for me at least), or if that's been forgotten.
Active
3.1
Code
Added a WIP MR to fix the issues I already encountered.
I will need to dig a bit deeper to see what else is breaking for my project, when I find some more time.