Answers.Body: <p>I started experiencing this also, although I was trying to enable the auto wildcard option, which I had previously turned off.</p>
  
  <p>I think it's a bug, but did have success updating it directly in the database as a workaround. In the civicrm_setting table there's a value called includeWildCardinVlaue. s:1:"1" means "yes" it's on, s:1:"0" means "no" it's off.</p>
  
  <p>I'm running Civi 4.7.3 in Wordpress 4.4.2 on civihosting.com.</p>
  
  <p>Looks like it might be happening to Drupal users, too. <a href="https://civicrm.stackexchange.com/questions/10212/why-cant-i-save-search-preferences-specifically-autocomplete-results">Why can&#39;t I save search preferences? Specifically &#39;Autocomplete Results&#39;</a></p>
  
Answers.ContentLicense: CC BY-SA 3.0
Answers.CreationDate: 2016-03-11T16:52:34.647Z
Answers.LastActivityDate: 2016-03-14T17:24:18.153Z
Answers.LastEditDate: 2017-04-13T12:53:13.207Z
Answers.UserDisplayName: Matthew Brown
Answers.Body: <p>This might be related to this issue "Fatal when creating InnoDB fts indexes":
  <a href="https://issues.civicrm.org/jira/browse/CRM-19610" rel="nofollow noreferrer">https://issues.civicrm.org/jira/browse/CRM-19610</a></p>
  
  <p>If your hosting provider doesn't allow the TRIGGER privilege for MySQL, you'll get an error any time you try and save the search preferences. Until this bug is addressed, I think directly updating the database to alter the setting is your only option. If there's an API call that can be made to update that setting, you might be able to use the API Explorer.</p>
  
Answers.ContentLicense: CC BY-SA 3.0
Answers.CreationDate: 2016-12-17T15:38:24.433Z
Answers.LastActivityDate: 2016-12-17T15:38:24.433Z
Answers.UserDisplayName: Dan O'Brien
Body: <p>We are trying to disable the automatic wildcard option in Civicrm (Wordpress 4.7.2).  However, when we try to disable the option and save we get an error that says “Save Failed: DB Error: Unknown Error”.  I tried to disable the automatic wildcard option in the main 4.7.2 Wordpress demo installation of Civicrm and it saved with no error message. We contacted our hosting provider who enabled "Enable Debugging" and "Display Backtrace", and they stated that they could not determine what the issue is without manually debugging the code. They recommend that I ask the Civicrm Stackexchange team for help.</p>
  
  <p>Thanks</p>
  
Comments.ContentLicense: CC BY-SA 3.0
Comments.CreationDate: 2016-12-10T07:12:13.430Z
Comments.Text: After enabling debugging and displaying backtrace, you should get a more detailed error.  Please edit your question to show the more detailed error and folks can help!
Comments.UserDisplayName: Jon G - Megaphone Tech
Tags: <wordpress><search><database><error>
Title: Unknown DB Error When Trying to Disable the Automatic Wildcard Option
ThreadText: # Unknown DB Error When Trying to Disable the Automatic Wildcard Option
  
  (Asked by: username_0 on 2016-02-26)
  
  We are trying to disable the automatic wildcard option in Civicrm (Wordpress 4.7.2). However, when we try to disable the option and save we get an error that says “Save Failed: DB Error: Unknown Error”. I tried to disable the automatic wildcard option in the main 4.7.2 Wordpress demo installation of Civicrm and it saved with no error message. We contacted our hosting provider who enabled "Enable Debugging" and "Display Backtrace", and they stated that they could not determine what the issue is without manually debugging the code. They recommend that I ask the Civicrm Stackexchange team for help.
  
  Thanks
  
  **Tags:** wordpress, search, database, error
  
  > **Comments:**
  > **username_1**: After enabling debugging and displaying backtrace, you should get a more detailed error.  Please edit your question to show the more detailed error and folks can help!  
  
  ---
  
  ## 2 answers
  
  ### Answer by username_2 on 2016-03-11. Score: 2
  
  I started experiencing this also, although I was trying to enable the auto wildcard option, which I had previously turned off.
  
  I think it's a bug, but did have success updating it directly in the database as a workaround. In the civicrm\_setting table there's a value called includeWildCardinVlaue. s:1:"1" means "yes" it's on, s:1:"0" means "no" it's off.
  
  I'm running Civi 4.7.3 in Wordpress 4.4.2 on civihosting.com.
  
  Looks like it might be happening to Drupal users, too. [Why can't I save search preferences? Specifically 'Autocomplete Results'](https://civicrm.stackexchange.com/questions/10212/why-cant-i-save-search-preferences-specifically-autocomplete-results)
  
  
  ---
  
  ### Answer by username_3 on 2016-12-17. Score: 1
  
  This might be related to this issue "Fatal when creating InnoDB fts indexes":
  <https://issues.civicrm.org/jira/browse/CRM-19610>
  
  If your hosting provider doesn't allow the TRIGGER privilege for MySQL, you'll get an error any time you try and save the search preferences. Until this bug is addressed, I think directly updating the database to alter the setting is your only option. If there's an API call that can be made to update that setting, you might be able to use the API Explorer.
  
  
  ---
  
  