Repository navigation
[6.x] Fix Search utility when index names are customized - #15729
Merged
duncanmcclean merged 1 commit intoOct 27, 2026
Merged
duncanmcclean merged 1 commit into
duncanmcclean merged 1 commit into
Conversation
Member
|
Thanks! |
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
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.
When index names are customized with
Index::resolveNameUsing(), updating an index from the Search utility in the Control Panel throws:The utility page posts each index as
{name}::{locale}. The controller then tried to turn the name back into the configured handle by removing the_{locale}suffix, but once a resolver has changed the name, that string can't be reversed.This PR looks the index up by its name in
Search::indexes(), which is keyed by name. It's the same approach #15024 took for thesearch:updatecommand.