Nested entry revisions#17008
Merged
brandonkelly merged 2 commits into5.7from Apr 1, 2025
Merged
Conversation
[ci skip]
|
Nice! 🙂 I've been experimenting with using matrix fields as nested sections, but the lack of nested entry versioning was sometimes a deal breaker. |
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
2 participants
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
Adds an “Enable versioning for entries in this field” setting to Matrix fields. When enabled, nested entries will get new versions created for them each time they are saved, regardless of whether they were saved directly on their own edit page, or via a Matrix field’s input.
Related issues