>>> [!note] Migrated issue <!-- Drupal.org comment --> <!-- Migrated from issue #3626950. --> Reported by: [anruether](https://www.drupal.org/user/894458) Related to !577 >>> <h3 id="summary-problem-motivation">Problem/Motivation</h3> <p>On a node page, a prop bound to a field of a referenced node resolves against the route's node. The source chain is "[Entity] &#10140; Referenced [Entity]" on an entity reference field, then "[Entity] &#10140; [Field]" and a field property.</p> <p>Display Builder's entity view passes <code>view_mode</code>, <code>entity</code> and <code>display</code> plus every global runtime context, including <code>@node.node_route_context:node</code> (<code>EntityViewDisplayTrait::getContextsForEntity()</code>). <code>EntityReferencedDerivableContext::getDerivedContexts()</code> removes <code>entity</code> from these contexts and appends the referenced entity as <code>entity</code> with <code>array_merge()</code>. The route's node now comes before it. The next step takes the first context that matches each definition, in <code>DerivableContextPluginBase::setDefinedContextValues()</code>:</p> <pre>$matching_context = \reset($matches);</pre><p>Both nodes match the <code>entity:node</code> definition, so <code>reset()</code> returns the route's node. That node has no such field, the value is NULL, and a required prop throws on render:</p> <pre>Drupal\Core\Render\Component\Exception\InvalidComponentException: [hda_theme:progress_bar/current] The property current is required.</pre><p>The same page renders a video through a Media reference correctly, because the global contexts hold no Media entity. A reference to a user entity would meet <code>@user.current_user_context:current_user</code> first by the same order; we have not tested that.</p> <p>In drush, without a route, the same source configuration returns the referenced node's value.</p> <h4 id="summary-steps-reproduce">Steps to reproduce</h4> <ol> <li>Install Drupal 11.4.7, UI Patterns 2.0.21 and Display Builder 1.0.0-beta7 with <code>display_builder_entity_view</code>.</li> <li>Create a content type Campaign with an integer field <code>field_anteile_current</code>, and a content type Page with an entity reference field <code>field_campaign</code> that targets Campaign.</li> <li>Add a component with a required integer prop <code>current</code>.</li> <li>Enable Display Builder with overrides on the Page view display. On a Page node, place the component and bind <code>current</code> to "[Entity] &#10140; Referenced [Entity]" on <code>field_campaign</code>, then "[Entity] &#10140; [Field]" <code>field_anteile_current</code>, property value.</li> <li>Publish and open the Page node. The request fails with the exception above.</li> </ol> <h3 id="summary-proposed-resolution">Proposed resolution</h3> <p>Prefer the context whose key equals the definition name, and fall back to the first match:</p> <pre>-&nbsp;&nbsp;&nbsp;&nbsp;&nbsp; $matching_context = \reset($matches);<br>+&nbsp;&nbsp;&nbsp;&nbsp;&nbsp; // Prefer the context with the definition's own name, so a derived<br>+&nbsp;&nbsp;&nbsp;&nbsp;&nbsp; // 'entity' wins over another context of the same entity type, such as<br>+&nbsp;&nbsp;&nbsp;&nbsp;&nbsp; // the route's node.<br>+&nbsp;&nbsp;&nbsp;&nbsp;&nbsp; $matching_context = $matches[$name] ?? \reset($matches);</pre><p><code>EntityReferencedDerivableContext</code> keys the referenced entity as <code>entity</code>, the same name as the entity context definition of the next step, so the referenced node wins.</p> <p>We run this as a local patch on 2.0.21. The prop renders the Campaign's value (520000 of 800000), and the other bindings on the page render as before: the title, the video through the Media reference, and field formatters.</p> <p><code>SourcePluginBase::setDefinedContextValues()</code> selects only through <code>context_mapping</code>, so the order of contexts does not affect it.</p> <h3 id="summary-remaining-tasks">Remaining tasks</h3> <ul> <li>Add a kernel test with a node that references another node, rendered with a node route context.</li> <li>Open a merge request against 2.0.x.</li> </ul> <h3 id="summary-ui-changes">User interface changes</h3> <p>None.</p> <h3 id="summary-api-changes">API changes</h3> <p>None.</p> <h3 id="summary-data-model-changes">Data model changes</h3> <p>None.</p> > Related issue: [Issue #3574380](https://www.drupal.org/node/3574380)