support search indexing and searching for multi-instance fields - #13991
Merged
brandonkelly merged 8 commits intoOct 3, 2026
Merged
brandonkelly merged 8 commits into
brandonkelly merged 8 commits into
Conversation
i-just
marked this pull request as draft
December 5, 2023 11:56
i-just
marked this pull request as ready for review
December 6, 2023 08:51
i-just
marked this pull request as draft
December 6, 2023 09:35
i-just
marked this pull request as ready for review
December 6, 2023 09:58
…-instance-fields # Conflicts: # src/config/app.php
Contributor
📚 Storybook previews@craftcms/ui — open Storybook No changed components detected in this Storybook. resources/js — open Storybook No changed components detected in this Storybook. |
brandonkelly
deleted the
bugfix/13987-searching-and-indexing-for-multi-instance-fields
branch
October 3, 2026 01:27
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
We can no longer rely solely on the one-to-one relationship between the field handle and
fieldId.layoutElementUidcolumn to thesearchindextable.layoutElementUid.layoutElementUidand fall back on thefieldId.Upgrade impact:
When updating from c4 to c5, after all migrations are run, a resave command with update search index param should be run for all element types that have custom field layouts (e.g.
craft resave/entries --update-search-index=1,craft resave/addresses --update-search-index=1etc.). This is so thatlayoutElementIdis populated in thesearchindextable. This is needed to support the indexing and searching through the multi-instance fields.Related issues
#13987