#content translation

@berdir thanks a lot for your thoughts, but, please, allow me to disagree
We have in core:
- Add/Create Translation API - but no Action for it
- There is hook for this - updated the MR with testing on it.

This "proposal" is using mostly Core API, except the translation source thing, which seems that needs Content Translation module

My question
Do we want "CTools/Entity API" approaches, not to mention things like CCK/Views/i18n and related "era"
So, imho, the core should provide CORE solutions for its API, not to have, again, extra modules to "complete" a basic Drupal project.

I can follow the remarks from @berdir, just one fact to add some clarification: core comes with a few other action plugins that have no specific interaction with anything else around. Examples are the send mail action plugin or the display message action plugin. Because of them being still around I'd argue that another one with a specific purpose wouldn't hurt and provide a foundation for others to build upon, even if that happens in contrib space. That could either be the AI ecosystem or even translation management that was mentioned before in #8.

However, if there is going to be a conclusion that this is not for core, it could easily go into contrib space, like e.g. ECA.

I'm not convinced that this needs to be in core. I understand the use cases, but this is not extensible. There is no hook here that something could use to intercept the process and actually do something with the translation. You still need to write a custom AI integration to actually do something.

This also doesn't tie into the content translation permissions and settings, it just checks regular entity update access. Content translation has per-bundle settings to enable/disable translation UI, and it has multiple permissions and its own API to check if a user is allowed to translate into a specific language. It also doesn't tie into the revision API's that were created to deal with content moderation and stuff like this, doesn't check for things like existing drafts and what not.

The configuration approach means you need to configure this before you can use it and then it's fixed for those specific, and core removed the action UI module from core. So one more reason why you can't use this without additional modules.

The reference handling is also very opinionated and non-configurable.

Content Translation has had no official maintainer for 5 years, plenty of issues and adding more features isn't really helping with that. Sorry, but -1 from me. This can live in a contrib module for those that consider it useful.

This is looking good to me.

When it comes to the discussion of whether something like this is even required, I would add the whole AI context. With such an action plugin, one could prepare a translation of an entity and then pass the untranslated content entity to AI to let it do the translation.

Hey All,

Is there any patch available to fix this, because we are facing the same problem here as well?