nested element draft site sync#19293
Open
i-just wants to merge 2 commits into
Open
Conversation
i-just
marked this pull request as ready for review
July 23, 2026 10:58
This file contains hidden or bidirectional Unicode text that may be interpreted or compiled differently than what appears below. To review, open the file in an editor that reveals hidden Unicode characters.
Learn more about bidirectional Unicode characters
Sign up for free
to join this conversation on GitHub.
Already have an account?
Sign in to comment
1 participant
Add this suggestion to a batch that can be applied as a single commit.This suggestion is invalid because no changes were made to the code.Suggestions cannot be applied while the pull request is closed.Suggestions cannot be applied while viewing a subset of changes.Only one suggestion per line can be applied in a batch.Add this suggestion to a batch that can be applied as a single commit.Applying suggestions on deleted lines is not supported.You must change the existing code in this line in order to create a valid suggestion.Outdated suggestions cannot be applied.This suggestion has been applied or marked resolved.Suggestions cannot be applied from pending reviews.Suggestions cannot be applied on multi-line comments.Suggestions cannot be applied while the pull request is queued to merge.Suggestion cannot be applied right now. Please check back later.
Description
Follow up to #17650.
When duplicating an element, check if it’s a derivative, not just a draft.
This should prevent the reported integrity constraint violation error.
I also added a unit test that Claude wrote for this particular issue.
Note: I was not able to reproduce this manually, as I was not able to get it to a state where the content block’s derivative was not propagated to the new site along with the owner’s draft.
Related issues
#19277