>>> [!note] Migrated issue <!-- Drupal.org comment --> <!-- Migrated from issue #2799479. --> Reported by: [jmuzz](https://www.drupal.org/user/2607886) Related to !5 !91 >>> <h2>Steps to reproduce:</h2> <p>There's many ways to reveal this bug. For example a view of nodes related to paragraphs, <em>or</em> a view of paragraphs related to the parent entity like so:</p> <ul> <li>Set up a node with a paragraph field (field_x) and a paragraph in it with some content.</li> <li>Create a view page that displays paragraphs.</li> <li>Add a relationship on "Content using field_x", set it to required.</li> <li>View the page for the view, observe that it has no entries.</li> </ul> <p>The paragraph should appear on the view page since it is referenced by "Content using field_x". You can set up something similar with 2 different node types and a regular entity reference field and see that it does display the referenced entity.</p> <p>There's probably many other combinations of view of X related to Y that will reveal this bug. </p> <h2>Remaining tasks</h2> <ul> <li>Write a hook_update_N() to migrate views' relationships (and fields/filters/sorts/arguments that use those relationships) to the new format. see <a href="https://www.drupal.org#comment-13520041">#124 for details</a></li> <li>There's some reports of broken filters due to this patch. <a href="https://www.drupal.org#comment-13957721">#151</a></li> <li>There's some reports of old revisions showing in views due to this patch.</li> <li>There's some reports of missing paragraphs in views for a multi-value ERR Paragraphs field due to this patch.</li> <li>There's some reports of duplicate rows when having a delta field due to this patch. <a href="https://www.drupal.org#comment-13654135">#134</a> and others</li> <li>This patch causes some UX confusion because there's now multiple ways to connect a paragraph to its parent entity in Views. <a href="https://www.drupal.org#comment-13957721">#151</a></li> <li>...Could be more bugs, I only read back the last year's worth of comments on this issue...</li> </ul> <h2>How to apply patches</h2> <p>If you need to know how to use a patch, please take a look at<br> <a href="https://www.drupal.org/docs/develop/git/using-git-to-contribute-to-drupal/applying-a-patch-in-a-feature-branch#s-obtain-and-apply-a-patch-file">https://www.drupal.org/docs/develop/git/using-git-to-contribute-to-drupal/applying-a-patch-in-a-feature-branch#s-obtain-and-apply-a-patch-file</a><br> and<br> <a href="https://www.drupal.org/docs/develop/git/using-git-to-contribute-to-drupal/applying-a-patch-in-a-feature-branch#s-composer">https://www.drupal.org/docs/develop/git/using-git-to-contribute-to-drupal/applying-a-patch-in-a-feature-branch#s-composer</a><br> please don't muddy this issue with questions about how to apply a patch.<br> <img src="https://www.drupal.org/files/issues/2024-05-14/patch-from-merge-request.png" alt=""></p> > Related issue: [Issue #2896381](https://www.drupal.org/node/2896381) > Related issue: [Issue #2831233](https://www.drupal.org/node/2831233) > Related issue: [Issue #2819603](https://www.drupal.org/node/2819603) > Related issue: [Issue #2795455](https://www.drupal.org/node/2795455) > Related issue: [Issue #2895578](https://www.drupal.org/node/2895578) > Related issue: [Issue #2932880](https://www.drupal.org/node/2932880) > Related issue: [Issue #2706431](https://www.drupal.org/node/2706431) > Related issue: [Issue #1699378](https://www.drupal.org/node/1699378)