Commit | Line | Data |
---|---|---|
91726809 TO |
1 | # CiviCRM 5.49.2 |
2 | ||
3 | Released May 19, 2022 | |
4 | ||
5 | - **[Synopsis](#synopsis)** | |
6 | - **[Bugs resolved](#bugs)** | |
7 | - **[Credits](#credits)** | |
8 | - **[Feedback](#feedback)** | |
9 | ||
10 | ## <a name="synopsis"></a>Synopsis | |
11 | ||
12 | | *Does this version...?* | | | |
13 | | --------------------------------------------------------------- | -------- | | |
14 | | Change the database schema? | no | | |
15 | | Alter the API? | no | | |
16 | | **Require attention to configuration options?** | **yes** | | |
17 | | **Fix problems installing or upgrading to a previous version?** | **yes** | | |
18 | | Introduce features? | no | | |
19 | | **Fix bugs?** | **yes** | | |
20 | ||
21 | ## <a name="bugs"></a>Bugs resolved | |
22 | ||
23 | * **_Scheduled Reminders_: Fix storage of "Limit To" option. ([dev/core#3464](https://lab.civicrm.org/dev/core/-/issues/3464), [dev/core#3465](https://lab.civicrm.org/dev/core/-/issues/3465): [#23497](https://github.com/civicrm/civicrm-core/pull/23497))** | |
24 | ||
25 | On sites which used 5.49.0 or 5.49.1, scheduled reminders could store incorrect values of the "Limit To" option. This | |
26 | can lead to excessive notifications. The upgrader should significantly reduce this risk, but it may advise you to | |
27 | review the configuration. ([Learn more](https://civicrm.org/redirect/reminders-5.49)) | |
28 | ||
29 | ## <a name="credits"></a>Credits | |
30 | ||
31 | This release was developed by the following authors and reviewers: | |
32 | ||
33 | Wikimedia Foundation - Eileen McNaughton; Megaphone Technology Consulting - Jon Goldberg; | |
34 | JMA Consulting - Monish Deb; CiviCRM - Tim Otten; Agileware - Justin Freeman | |
35 | ||
36 | ## <a name="feedback"></a>Feedback | |
37 | ||
38 | These release notes are edited by Tim Otten and Andie Hunt. If you'd like to | |
39 | provide feedback on them, please login to https://chat.civicrm.org/civicrm and | |
40 | contact `@agh1`. |