Answers.Body: <p>Looks like cividesk.normalize based on the pastebin.</p>
  
  <p>Actually looks like it's already patched in master: <a href="https://github.com/cividesk/com.cividesk.normalize/commit/221562b8bf4fb56fe677eaaf9122d3af5c3cce74" rel="nofollow noreferrer">https://github.com/cividesk/com.cividesk.normalize/commit/221562b8bf4fb56fe677eaaf9122d3af5c3cce74</a></p>
  
Answers.ContentLicense: CC BY-SA 4.0
Answers.CreationDate: 2020-05-27T21:51:03.327Z
Answers.LastActivityDate: 2020-05-27T22:04:11.057Z
Answers.LastEditDate: 2020-05-27T22:04:11.057Z
Answers.UserDisplayName: Demerit
Body: <p>In the ConfigandLog directory, this error is produced every minute:</p>
  
  <pre><code>[warning] Deprecated function CRM_Core_Config::defaultContactCountry, use CRM_Core_BAO_Country::defaultContactCountry.
  Array
  (
      [civi.tag] =&gt; deprecated
  )
  </code></pre>
  
  <p>What configuration do I have wrong that is making this occur?</p>
  
  <p>On Civi 5.24.4 / Wordpress 5.4.1. Multisite.</p>
  
Comments.ContentLicense: CC BY-SA 4.0
Comments.CreationDate: 2020-05-27T20:02:03.470Z
Comments.Text: My guess would be it's coming from an extension. Try `grep -r defaultContactCountry your_extensions_folder` to see what comes up.
Comments.UserDisplayName: Demerit
Comments.ContentLicense: CC BY-SA 4.0
Comments.CreationDate: 2020-05-27T21:47:32.227Z
Comments.Text: https://pastebin.com/v7skYeWP
Comments.UserDisplayName: Andy Burns
Comments.ContentLicense: CC BY-SA 4.0
Comments.CreationDate: 2020-05-27T21:57:19.360Z
Comments.Text: Just noticed it's already patched in master. Have updated answer.
Comments.UserDisplayName: Demerit
Comments.ContentLicense: CC BY-SA 4.0
Comments.CreationDate: 2020-05-28T16:13:51.993Z
Comments.Text: We were on 1.0. Apparently the ext does not give an upgrade notice. Now running into enabling issue https://github.com/cividesk/com.cividesk.normalize/issues/11#issuecomment-634971434. Should I care that the enabling didn't go smoothly but still says enabled?
Comments.UserDisplayName: Andy Burns
Comments.ContentLicense: CC BY-SA 4.0
Comments.CreationDate: 2020-05-28T16:59:10.403Z
Comments.Text: That seems like a separate error but upgrading just to 1.1 won't help with the original problem since the patch is only in master (latest dev). They might be open to releasing a new version 1.2 since it's been a while since the last release. For this second error, if it only comes up during enabling then it's probably because of changes in which hooks run during enabling - hook_civicrm_config probably isn't called anymore. So if you don't see the error during regular use it's probably ok.
Comments.UserDisplayName: Demerit
Comments.ContentLicense: CC BY-SA 4.0
Comments.CreationDate: 2020-05-28T17:21:09.190Z
Comments.Text: Should I try master or just do the patch?
Comments.UserDisplayName: Andy Burns
Comments.ContentLicense: CC BY-SA 4.0
Comments.CreationDate: 2020-05-28T17:23:36.633Z
Comments.Text: Me personally I would probably just do the patch.
Comments.UserDisplayName: Demerit
Tags: <error><tags><configandlog>
Title: Deprecated function CRM_Core_Config::defaultContactCountry error
ThreadText: # Deprecated function CRM_Core_Config::defaultContactCountry error
  
  (Asked by: username_0 on 2020-05-27)
  
  In the ConfigandLog directory, this error is produced every minute:
  [warning] Deprecated function CRM_Core_Config::defaultContactCountry, use CRM_Core_BAO_Country::defaultContactCountry.
  Array
  (
      [civi.tag] => deprecated
  )
  
  What configuration do I have wrong that is making this occur?
  On Civi 5.24.4 / Wordpress 5.4.1. Multisite.
  
  **Tags:** error, tags, configandlog
  
  > **Comments:**
  > **username_1**: My guess would be it's coming from an extension. Try `grep -r defaultContactCountry your_extensions_folder` to see what comes up.  
  > **username_0**: https://pastebin.com/v7skYeWP  
  > **username_1**: Just noticed it's already patched in master. Have updated answer.  
  > **username_0**: We were on 1.0. Apparently the ext does not give an upgrade notice. Now running into enabling issue https://github.com/cividesk/com.cividesk.normalize/issues/11#issuecomment-634971434. Should I care that the enabling didn't go smoothly but still says enabled?  
  > **username_1**: That seems like a separate error but upgrading just to 1.1 won't help with the original problem since the patch is only in master (latest dev). They might be open to releasing a new version 1.2 since it's been a while since the last release. For this second error, if it only comes up during enabling then it's probably because of changes in which hooks run during enabling - hook_civicrm_config probably isn't called anymore. So if you don't see the error during regular use it's probably ok.  
  > **username_0**: Should I try master or just do the patch?  
  > **username_1**: Me personally I would probably just do the patch.  
  
  ---
  
  ## 1 answers
  
  ### Answer by username_1 on 2020-05-27. Score: 0 | Accepted answer
  
  Looks like cividesk.normalize based on the pastebin.
  
  Actually looks like it's already patched in master: <https://github.com/cividesk/com.cividesk.normalize/commit/221562b8bf4fb56fe677eaaf9122d3af5c3cce74>
  
  
  ---
  
  