FIX Handle composite fields in GridFIeldFilterHeader #11609
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
In the CMS search filter, composite fields would always appear empty after submitting the form because their prefix was missing. This could also introduce conflicts if a same-named field was in the main edit form.
This was referenced Feb 12, 2025
emteknetnz
approved these changes
Feb 13, 2025
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.
In the CMS search filter, composite fields would always appear empty after submitting the form (even though it applies the filter) because their prefix was missing. That could also introduce conflicts if a same-named field was in the main edit form.
Issue
CMSMain/HierarchyModelAdminsilverstripe-cms#2949