Schedule Moderation State Updates for Translations

Good chance this will have to be fixed in Scheduled Updates or that it's related to known issues with forward revisions and translations. I put this in our current sprint so we can figure that out.

We dug into this a little bit.

Scheduled Updates

1. Would need a new update runner plugin, or probably better, an update to the existing UpdateRunnerBase that took into consideration the language of the update and loaded the appropriate translation of the given entity.
2. Allow update entities to be translatable. Right now, translation is specifically set to false.

And the from the configuration (Lightning) side:

Configuration (Lightning)

There are two types of Updates:

1. Updates that are created within the context of an entity where the entity contains a reference to the update
2. Updates that are created independently which have references to entities to update

For the former, the update field would need to be translatable. Lightning couldn't ship with a translatable field since it doesn't have Content Translation enabled out of the box. But it should be (?) fairly intuitive to the user once the translation->false is removed from Scheduled Updates (would be just like any other field)

For the latter, the update itself would either need to be translated (likely) or the reference to the entity would need to reference a specific language (which I don't think is currently possible).

Entity Reference

It looks like Entity Reference doesn't currently support referencing a specific language. That should be fine, but it causes some weirdness when trying to reference something that is translated. E.g. autocomplete works when typing reference in Language A, but Language B shows up as option.

Considerations

What about users who want to schedule a transition to all languages at once? The update runner would likely need to take that into account (that is, if an untranslated update references a translated entity that == update all languages)

Summary

This is a fair amount of work. There is no current workaround for users who need this functionality and I'm honestly a little surprised that it hasn't come up before. But that fact that it hasn't makes me wonder how much of our limited resources we should throw at it.

This looks like a duplicate of #2647094: Handle Content translation: How should be it be handled? to me. For the time being I've just referenced each one to the other. Is there a reason we need both of them open? This one has more detail, but the other issue is older. The parent issue of this one has been closed. Should we just copy the information from comment #5 to the other one and close this one as a duplicate?

Hi. Yeah, it's a duplicate. I think it's here because Lightning has a vested interest in getting it fixed and ships with default config that makes it easy to test against (at least for Lightning's use case). But if it's going to get fixed properly, it should be done in the Scheduled Updates module either way.

Let's close this so we don't confuse anyone else.

Hi All,

I see that this issue is closed because mirrors an issue on the shceduled_updates which doesn't even have support anymore? Is this accurate? And, that issue hasn't had any traction for 2 years?

Any updates of any kind or any work-arounds would be very appreciated as this is a big deal for our project.

Thank you!