Problem/Motivation
When duplicating a page, all blocks with their texts are also copied. However, the text of the duplicated page appears as a preview (in the layoutbuilder) on the original content if you have modified it.
Steps to reproduce
- Duplicate a Page.
- Change text from druplicated textblock.
- Go to the original page and look in the preview.
- you can now see the modified text from the duplicated page.
Proposed resolution
When duplicating a page, the content must be independently customizable.
Original page should not be the same as copied page.
Release notes snippet
- Drupal-Version: 9.5.3
- PHP Version: 7.4.33
- DB: MySQL 8.0.32
| Comment | File | Size | Author |
|---|---|---|---|
| #8 | Bildschirmfoto 2023-07-12 um 12.47.29.png | 44.35 KB | sandro_pagliara |
| Bildschirmfoto 2023-03-21 um 11.41.28.png | 451.35 KB | sandro_pagliara |
Comments
Comment #2
cilefen commentedCan you please explain step one: "duplicate a page"? Is that by using a module like entity clone or by some other method?
Comment #3
larowlanThis is most definitely a bug in whatever you're using to duplicate
Comment #4
larowlanComment #5
sandro_pagliara commentedWe use the "Quick node Clone" module for duplicating.
Steps to reproduce:
- I duplicated a page with the "Quick node Clone"-Module.
- On the new "Clone" page, I changed and saved the text in the text element.
- On the original page, my initial text is still displayed. However, If I open the text element in Layout Builder, the text content from the duplicated page is shown, leading to the divergent content display as shown in my screenshot.
Comment #6
cilefen commentedComment #7
cilefen commentedIs this a duplicate of #3100117: Inline blocks from layout builder not cloned properly?
Comment #8
sandro_pagliara commentedUnfortunately the patch from the other issue didn't help.
As a result of the patch, all elements from the duplicated page have disappeared (see image).
The problem in the patch is different. In our case, you can edit the blocks.
Comment #9
remoschneider commentedAre there any new developments on this? We still have this problem with Drupal 10.3.1