"Entity untranslatable fields" prevents flagging translations as outdated

I have been able to trigger this same error by:
* Enabling translation on content
* Creating a node and a translation of that node.
* Editing the original node and resaving with "Flag other translations as outdated" checked by default.

So, basically, we are unable to resave the default translation once a translation exists.

I am seeing this on Drupal 9.5.11.

I have created an MR using the recommendation from the original post. The MR updates the getFieldsToSkipFromTranslationChangesCheck method to skip fields from the content_moderation module.

A more flexible approach would be to make this feature configurable so other can define fields that they would like to ensure are skipped when performing a diff of untranslated fields on save.

Thank you for this patch. It fixes this issue, as well as another issue I was having over in https://www.drupal.org/project/drupal/issues/3025039#comment-16046212 🐛 New non translatable field on translatable content throws error Needs work with content_translation_uid field changing for programmatically created taxonomy terms which are then edited via the UI.

This issue can also occur when you programmatically create taxonomy terms and then translate them programmatically too, because the content_translation_uid field is NULL in the database by default. When you go to re-save the previously created translation in the UI you get the above error message because it defaults to the anonymous user (0) when assigning a value via the form.