>>> [!note] Migrated issue <!-- Drupal.org comment --> <!-- Migrated from issue #3050027. --> Reported by: [josephdpurcell](https://www.drupal.org/user/2944035) Related to !88 !89 !67 !42 >>> <h3 id="summary-problem-motivation">Problem/Motivation</h3> <p>If someone clones any Layout Builder-enabled entity that has inline block content, and then subsequently deletes the original entity, the inline blocks on the cloned entity will be deleted on the next cron run. Content editors will see a "This content is missing or broken" message while in "Layout editing" mode. In "View" mode, the node will omit the content altogether. The missing content cannot be recovered.</p> <h4 id="summary-steps-reproduce">Steps to reproduce</h4> <p>1. From a clean site installation, enabled "Layout Builder" and "Entity Clone" and configure a node type to use Layout Builder.<br> 2. Create a page and add a single inline block of any type to the the layout.<br> 3. Clone the page. The content will look fine.<br> 4. Delete the original node. The content on the cloned node will still appear.<br> 5. Run cron.<br> 6. View the cloned page. The content on the cloned node will be missing.</p> <h3>Root cause</h3> <p>The entity_clone module clones Layout Builder-style entities by copying verbatim the data in <code>[entity]__layout_builder__layout</code> from one entity to the next. This data copies the block ID of inline blocks as-is. This works just fine for allowing content changes between the nodes to differ, since changes are stored as new block **revision** IDs. </p> <p>Example of why things work fine *before* deletion:<br> - Start with a site empty of content. Create a Layout Builder node with a single inline block.<br> - Node 1 will now have an inline block with ID 1. That block's revision number is also 1.<br> - Change the content of that inline block. Node 1 now references block 1, revision 2.<br> - Clone node 1. A New node, 2, is created. It references block 1, revision 2 (i.e., copied verbatim).<br> - Change node 1's block. It now references block 1, revision 3, while node 2 still references revision 2.<br> - Change node 2's block content. It now references block 1, revision 4, while Node 1 still references block 1, revision 3.</p> <p>The problem arises when the original node is deleted. This marks the inline block with ID 1 as ready for deletion. When <code>layout_builder_cron()</code> executes during the next cron run, it deletes block ID 1, along with all of its revisions, and the content on Node 50 is lost.</p> <h3 id="summary-proposed-resolution">Proposed resolution</h3> <p>First, adjust the behavior of the <code>entity_clone</code> module so that when Layout Builder-style entities are cloned, inline blocks are resaved as new blocks with distinct block IDs. This is the correct solution from the standpoint of Layout Builder's architecture: an inline block is expected only to be referenced in one place. </p> <p>However, this alone will not fix entities cloned prior to the proposed change. </p> <p>So, second, add an update hook to examine each row in <code>[entity]_revision__layout_builder__layout</code> and count the instances of block references and then re-save ones that have more than one count and update the data in <code>[entity]__layout_builder__layout</code> and <code>[entity]_revision__layout_builder__layout</code> with the new block ids. Special care should be taken to preserve revisions of these newly created blocks (and thus preserve the ability to revert to a previous revision of the node).</p> <p>Finally, since there are likely some sites with already-missing and unrecoverable blocks, create an audit tool that can identify these for site owners.</p> <h3 id="summary-ui-changes">User interface changes</h3> <p>None.</p> <h3 id="summary-api-changes">API changes</h3> <p>Inline blocks should always be duplicated during clone.</p> <h3 id="summary-data-model-changes">Data model changes</h3> <p>None.</p> > Related issue: [Issue #3190915](https://www.drupal.org/node/3190915) > Related issue: [Issue #3062819](https://www.drupal.org/node/3062819)