[4.x] Entries Fieldtype: Tree View #8899
Merged
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
…ents. accept a more generic "tree" object
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 introduces a new "Tree View" to the entries fieldtype stack selector.
The Tree View displays pages (or any kind of entry for that matter) in a hierarchical tree structure, providing better context and visibility into the entry's parents and overall entry structure.
This is particularly useful when dealing with page structures that have multiple pages with the same name, making it difficult to differentiate them using the traditional list view.
Example:
The Tree View is only available for Entries fields that have a single collection configured.
To Do
Related: #4187.
Closes statamic/ideas#666.