[6.x] Fix page: 0 corrupting the collection tree in ReorderEntriesController - #15429
Merged
Conversation
page: 0 (or perPage: 0) produces a negative array offset, slicing from the end of the tree, passing the out-of-date guard, and writing negative keys back onto it — corrupting the collection's tree permanently on disk.
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.
page: 0(orperPage: 0) produces a negative array offset, which slices from the end of the tree, passes the out-of-date guard (the submitted ids genuinely match that slice), and then writes negative keys back onto the tree — appending duplicates instead of overwriting. The corrupt tree reaches disk before a 500 is thrown, permanently breaking the collection's entries listing until someone hand-edits the tree YAML.Not reachable by clicking — the CP always posts the page it fetched — but a forged/malformed request can hit it via devtools, curl, or a buggy addon, so it's worth hardening.
Adds
min:1to thepage/perPagevalidation rules, matching what already ships for taxonomy reordering.