Skip to content

Commit 0ecb26e

Browse files
authored
Merge pull request #995 from nep/patch-19
Update entries.md
2 parents 03ab08f + 7f9a377 commit 0ecb26e

File tree

1 file changed

+2
-0
lines changed

1 file changed

+2
-0
lines changed

docs/channels/entries.md

Lines changed: 2 additions & 0 deletions
Original file line numberDiff line numberDiff line change
@@ -501,6 +501,8 @@ The "search:" parameter allows you to constrain Channel Entries output based on
501501
NOTE: **Note:** Some fields store their content in a manner that affects the ability to work with this parameter. Grid fields, for instance, can only use this parameter for columns with "Include in search?" enabled (For performance, EE groups those columns into a searchable blob.). You can, however, search on Grid columns by using Pro Search's [`{exp:pro_search:results}`](add-ons/pro-search/tags.md#exppro_searchresults) tag and the [Field Search filter](/add-ons/pro-search/filters.md#field-search). Pro Search can also be used to filter entries by [title](/add-ons/pro-search/filters.md#searchtitle), [url_title](/add-ons/pro-search/filters.md#searchurltitle), [status](/add-ons/pro-search/filters.md#searchstatus), and [more](/add-ons/pro-search/filters.md#field-search). Relationship fields cannot be searched using the "search:" parameter.
502502

503503

504+
NOTE: **Note:** You can also use search:title and search:url_title in addition to searching field content. Remember that it is best to use url_title="something" if you're looking for an exact url_title match.
505+
504506
#### "Exact" Matching
505507

506508
Use "Exact" matching when you only want entries whose fields match your terms exactly. To trigger "Exact" matching, precede your search terms with an equal sign (=). You may provide a pipe-delimited list of terms:

0 commit comments

Comments
 (0)