Answers.Body: <p>When that's mentioned in the release notes, it's not that everyone must make configuration changes, but it's good to read through and pay attention to what items mention configuration changes, because choices have been made, new options added, etc.</p>
  <p>In the case of 5.62.0, the things I'd look out for are:</p>
  <ul>
  <li>if you have custom code depending upon legacy custom searches, that's now in an extension (enabled by default, but still something that could be an issue)</li>
  <li>the enabled components (e.g. CiviMail, CiviCase) now take effect across all domains in a CiviCRM installation rather than as separate options for each domain</li>
  <li>the warning that will appear if you have activity revisions in CiviCase</li>
  </ul>
  <p>As you can see in each of those issues, developers and reviewers take care that for most sites most things are smooth/consistent, but it could still come as a surprise if you do have less common configurations.</p>
  
Answers.ContentLicense: CC BY-SA 4.0
Answers.CreationDate: 2023-07-04T09:24:38.520Z
Answers.Text: Thank you. It'd be helpful if there was something in the notes that explained why that question was flagged in the synopsis - similar to how Drupal lists the direct issue links for any changes to default.settings.php, .htaccess, etc under a 'major changes' heading.
Answers.UserDisplayName: somnolentsurfer
Answers.ContentLicense: CC BY-SA 4.0
Answers.CreationDate: 2023-06-30T20:46:15.190Z
Answers.LastActivityDate: 2023-06-30T20:46:15.190Z
Answers.UserDisplayName: Andie Hunt
Body: <p>The <a href="https://github.com/civicrm/civicrm-core/blob/master/release-notes/5.62.0.md" rel="nofollow noreferrer">release notes for 5.62.0</a> say that this update requires attention to configuration options but I can't see anything more about what it is that requires attention. There's no mention of 5.62.0 on the <a href="https://docs.civicrm.org/sysadmin/en/latest/upgrade/version-specific/" rel="nofollow noreferrer">version-specific upgrade tasks</a> page. Is there something I need to pay attention to when upgrading?</p>
  
Tags: <upgrade>
Title: 5.62.0 configuration options?
ThreadText: # 5.62.0 configuration options?
  
  (Asked by: username_0 on 2023-06-28)
  
  The [release notes for 5.62.0](https://github.com/civicrm/civicrm-core/blob/master/release-notes/5.62.0.md) say that this update requires attention to configuration options but I can't see anything more about what it is that requires attention. There's no mention of 5.62.0 on the [version-specific upgrade tasks](https://docs.civicrm.org/sysadmin/en/latest/upgrade/version-specific/) page. Is there something I need to pay attention to when upgrading?
  
  **Tags:** upgrade
  
  
  ---
  
  ## 1 answers
  
  ### Answer by username_1 on 2023-06-30. Score: 2 | Accepted answer
  
  When that's mentioned in the release notes, it's not that everyone must make configuration changes, but it's good to read through and pay attention to what items mention configuration changes, because choices have been made, new options added, etc.
  
  In the case of 5.62.0, the things I'd look out for are:
  
  * if you have custom code depending upon legacy custom searches, that's now in an extension (enabled by default, but still something that could be an issue)
  * the enabled components (e.g. CiviMail, CiviCase) now take effect across all domains in a CiviCRM installation rather than as separate options for each domain
  * the warning that will appear if you have activity revisions in CiviCase
  
  As you can see in each of those issues, developers and reviewers take care that for most sites most things are smooth/consistent, but it could still come as a surprise if you do have less common configurations.
  
  > **Comments:**
  > **username_0**: Thank you. It'd be helpful if there was something in the notes that explained why that question was flagged in the synopsis - similar to how Drupal lists the direct issue links for any changes to default.settings.php, .htaccess, etc under a 'major changes' heading.  
  
  ---
  
  