Repository navigation
[6.x] Hide Assets fieldtype's "Restrict to Folder" toggle when using a dynamic folder - #15635
Merged
Merged
Conversation
The `dynamic` option is a select (id, slug, author), so the `not true` condition always passed and the toggle stayed visible, even though a dynamic folder always restricts navigation regardless of its value. Co-Authored-By: Claude Opus 5.5 <noreply@anthropic.com>
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.
Someone reached out via support because their Assets field wouldn't let them navigate outside its dynamic folder, even though "Restrict to Folder" was turned off.
Restricting navigation is intended: since #10808, a dynamic folder always restricts navigation and the
restrictsetting is ignored. The toggle was supposed to be hidden in that case, but its condition was'dynamic' => 'not true'.dynamicis a select (id,slug,author), nevertrue, so the condition always passed and the toggle stayed visible despite having no effect.This PR changes the condition to
'dynamic' => 'empty', so the toggle only shows when no dynamic folder is set.This is only a visual change. Existing
restrictvalues stay in the blueprint YAML, and nothing reads them while a dynamic folder is set.🤖 Generated with Claude Code