>>> [!note] Migrated issue <!-- Drupal.org comment --> <!-- Migrated from issue #3627204. --> Reported by: [jmcerda](https://www.drupal.org/user/205148) Related to !111 >>> <h3>Problem/Motivation</h3> <p>On Drupal 10.6.18/PHP 8.2 with Entity Reference Revisions 1.14.0 and Paragraphs 1.23.0, creating a translated node draft can fail validation when an unchanged referenced paragraph revision is older than that paragraph&rsquo;s default revision.</p> <p>The response is HTTP 422: <code>Entity is not valid: Non-translatable fields can only be changed when updating the original language.</code> The request changes only the node&rsquo;s translated title; it does not change the paragraph reference or its pinned revision.</p> <h3>Reproduction</h3> <ol> <li>Use a translatable, moderated page with a shared Entity Reference Revisions field referencing a translatable text paragraph.</li> <li>Publish an English page that pins a paragraph whose text is <code>Hero</code>.</li> <li>Create a newer default revision of that paragraph with text <code>Default later</code>, leaving the published page pinned to the earlier revision.</li> <li>Create a Spanish draft of the page, changing its title only and retaining the original paragraph pin.</li> </ol> <p>The existing <code>McpDraftParagraphTranslationTest::testNonDefaultPinnedRevisionTranslation</code> in released MCP Sentinel 2.25.5 provides an executable reproduction. On an unchanged release checkout against the dependency versions above, it fails at line 207: expected HTTP 200, received 422 (1 test, 18 assertions). A separate candidate produces the same response before its changed save path. The same existing test passes on Drupal 11.3.18.</p> <h3>Investigation</h3> <p>Source review points to <code>EntityReferenceRevisionsFieldItemList::hasAffectingChanges()</code>: the loaded-revision original is set only on Drupal 11.3+. On Drupal 10.6, <code>ContentEntityBase::hasTranslationChanges()</code> can instead compare the pinned paragraph against its newer default revision. This appears related to the loaded-versus-default comparison discussed in #3388540, but the supported Drupal 10 path remains affected. This is the working diagnosis; a focused ERR regression and fix are still needed.</p> <h3>Proposed resolution</h3> <p>Compare against the referenced loaded revision on supported older core as well, using the appropriate revision-loading API. Preserve validation of actual shared-field changes, paragraph IDs, revision pins and the published English content. Do not bypass the non-translatable-field constraint.</p> <h3>Remaining tasks</h3> <p>Add an ERR-level regression, implement and review the compatible original-revision read, and qualify supported core versions.</p>