- Issue created by @AlfTheCat
- 🇩🇪Germany jurgenhaas Gottmadingen
Nice use case, and interesting question. I don't know the answer from the top of my head, but will do some research and let you know. If it's bot yet possible, I'm sure we will build a new action to make it work.
- Assigned to jurgenhaas
- Issue was unassigned.
- 🇩🇪Germany jurgenhaas Gottmadingen
I've looked into this, and it appears, that ECA can't create a translation for an existing entity yet. The
Entity: create new
action creates a new entity, not a translation of an existing entity. TheEntity: load
action loads an existing translation of an entity, but doesn't create a new one.Several choices to be decided:
- Should that be a new action plugin or could this be added to the
Entity: load
action to create a translation if it doesn't yet exist? - If it's going to be a new action, should that be part of
eca_content
oreca_language
?
My preference is to create a new action in
eca_content
.Thoughts?
- Should that be a new action plugin or could this be added to the
- 🇹🇭Thailand AlfTheCat
I think it should indeed be a new action as part of eca_content. Entity load would be confusing for some users, for it may not be obvious that a translation can be created by loading a non-existent one. I think it fits in the eca_content part because it is a content operation and not yet a specific language operation until the translation for a language is created.