[4.x] Ensure changes to "Parent" get saved when using revisions #9079
Conversation
This file contains 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
We can't change the tree when saving a revision because it's not published yet. However, we *do* need to save it, which we're doing with the whole supplements thing. I've adjusted the code in `EntriesController@extractFromFields` since we need to push the new parent back up to the frontend, without it actually being the parent.
This reverts commit 9690e9f.
Sign up for free
to join this conversation on GitHub.
Already have an account?
Sign in to comment
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.
This pull request fixes an issue when using Revisions where changes to the "Parent" wouldn't be saved & the entry wouldn't be moved in the collection's tree.
This PR fixes that by persisting the
parentas part of the revision data, then handling the "move in tree" part when the revision is published.Fixes #8547.