Answers.Body: <p>That's because Craft doesn't do fuzzy searching by default.  You'd need to use the wildcard <code>'Peru*'</code> to match <code>'Peruvian'</code>.  You can see the full list of supported search syntaxes here: <a href="http://buildwithcraft.com/docs/searching" rel="nofollow">http://buildwithcraft.com/docs/searching</a></p>
  
  <p>Related, you might want to vote for this feature request: <a href="http://feedback.buildwithcraft.com/forums/285221-feature-requests/suggestions/8459443-add-option-to-enable-fuzzy-search-as-default" rel="nofollow">http://feedback.buildwithcraft.com/forums/285221-feature-requests/suggestions/8459443-add-option-to-enable-fuzzy-search-as-default</a></p>
  
  <p><strong>Update:</strong>
  As of <a href="https://craftcms.com/changelog#build2750" rel="nofollow">Craft 2.5</a>, you can enable <a href="https://craftcms.com/help/enabling-fuzzy-search-by-default" rel="nofollow">fuzzy</a> searching by default.</p>
  
Answers.ContentLicense: CC BY-SA 3.0
Answers.CreationDate: 2015-10-13T07:15:02.527Z
Answers.Text: Voted. Thanks. Can't expect site visitors to use wildcards!
Answers.UserDisplayName: Clive Portman
Answers.ContentLicense: CC BY-SA 3.0
Answers.CreationDate: 2015-10-13T09:35:41.310Z
Answers.Text: If Craft had an ```onBeforeSearch``` event that exposed the search query, wildcards and other search modifiers could be added there as well – there's a feature request for this too: http://feedback.buildwithcraft.com/forums/285221-feature-requests/suggestions/8267127-add-events-for-onbeforesearch-and-onsearch
Answers.UserDisplayName: Mats Mikkel Rummelhoff
Answers.ContentLicense: CC BY-SA 3.0
Answers.CreationDate: 2016-04-21T08:54:36.867Z
Answers.Text: Just seen this has been updated. Brilliant.
Answers.UserDisplayName: Clive Portman
Answers.ContentLicense: CC BY-SA 3.0
Answers.CreationDate: 2015-10-12T15:32:21.050Z
Answers.LastActivityDate: 2015-12-04T23:31:30.920Z
Answers.LastEditDate: 2015-12-04T23:31:30.920Z
Answers.UserDisplayName: Brad Bell
Body: <p>Is it me, or can we not search using partial words in Craft CMS? This seems to be the case in the backend when search entry titles or assets, but a client has recently pointed it out on the front-end as well.</p>
  
  <p>For example, we've got an entry title containing the word 'Peruvian' but searching for 'Peru' returns no results, while searching for 'Peruvian' does return a result.</p>
  
Tags: <search>
Title: How to search using partial words?
ThreadText: # How to search using partial words?
  
  (Asked by: username_0 on 2015-10-12)
  
  Is it me, or can we not search using partial words in Craft CMS? This seems to be the case in the backend when search entry titles or assets, but a client has recently pointed it out on the front-end as well.
  
  For example, we've got an entry title containing the word 'Peruvian' but searching for 'Peru' returns no results, while searching for 'Peruvian' does return a result.
  
  **Tags:** search
  
  
  ---
  
  ## 1 answers
  
  ### Answer by username_1 on 2015-10-12. Score: 5 | Accepted answer
  
  That's because Craft doesn't do fuzzy searching by default. You'd need to use the wildcard `'Peru*'` to match `'Peruvian'`. You can see the full list of supported search syntaxes here: <http://buildwithcraft.com/docs/searching>
  
  Related, you might want to vote for this feature request: <http://feedback.buildwithcraft.com/forums/285221-feature-requests/suggestions/8459443-add-option-to-enable-fuzzy-search-as-default>
  
  **Update:**
  As of [Craft 2.5](https://craftcms.com/changelog#build2750), you can enable [fuzzy](https://craftcms.com/help/enabling-fuzzy-search-by-default) searching by default.
  
  > **Comments:**
  > **username_0**: Voted. Thanks. Can't expect site visitors to use wildcards!  
  > **username_2**: If Craft had an ```onBeforeSearch``` event that exposed the search query, wildcards and other search modifiers could be added there as well – there's a feature request for this too: http://feedback.buildwithcraft.com/forums/285221-feature-requests/suggestions/8267127-add-events-for-onbeforesearch-and-onsearch  
  > **username_0**: Just seen this has been updated. Brilliant.  
  
  ---
  
  