... | ... | @@ -8,9 +8,11 @@ Please keep this document readable / authoritative (reflecting currently release |
|
|
|
|
|
# Overview
|
|
|
|
|
|
"Scheduled Reminders" in v5.49 may be operating with incorrect configuration data - leading to extra/unintended notifications.
|
|
|
"*Scheduled Reminders*" in v5.49.0 may store incorrect configuration data - in which case, the system may send extra notifications to *all* contacts. The issue is generally fixed in v5.49.2+, but some configurations should be reviewed.
|
|
|
|
|
|
For analysis and on-going discussion, see https://lab.civicrm.org/dev/core/-/issues/3464 and https://lab.civicrm.org/dev/core/-/issues/3465
|
|
|
For analysis and discussion, see https://lab.civicrm.org/dev/core/-/issues/3464 and https://lab.civicrm.org/dev/core/-/issues/3465
|
|
|
|
|
|
(*This page is ever-green and may be updated if recommendations or techniques change.*)
|
|
|
|
|
|
# Current Recommendations
|
|
|
|
... | ... | @@ -18,14 +20,25 @@ The recommendations depend on your current version: |
|
|
|
|
|
| Current Version | Recommendation |
|
|
|
| -- | -- |
|
|
|
| `5.48.x` or older | If you use "Scheduled Reminders", refrain from upgrading to `5.49`. |
|
|
|
| `5.49.{alpha,beta,0,1}` | If you use "Scheduled Reminders", disable them. Stand by for next version. |
|
|
|
| `5.48.x` or older | Upgrade to `5.49.2+` at your leisure. You will not be affected by this advisory. |
|
|
|
| `5.49.beta`, `5.49.0`, `5.49.1` | Upgrade to `5.49.2+` as soon as possible.<br/>After upgrading, review the "Scheduled Reminders".<br/>If you cannot upgrade, then disable "Scheduled Reminders". |
|
|
|
|
|
|
# Affected data
|
|
|
|
|
|
The issue arises from a subtle schema change in the "*Scheduled Reminder*" entity, which includes a field named "*Limit or Add Recipients*" (`civicrm_action_schedule`.`limit_to`):
|
|
|
|
|
|
![Edit Scheduled Reminder](/uploads/51b11de87d05f00394d26203eabee5ba/image.png)
|
|
|
|
|
|
# Relevant Data
|
|
|
In `5.49.0`, the first option ("-neither-") is stored incorrectly - and converted to "Also Include". This erroneous conversion affected new reminders as well as pre-existing reminders.
|
|
|
|
|
|
TODO
|
|
|
| Option | Stored Value (5.48) | Stored Value (5.49.0) | Stored Value (5.49.2) |
|
|
|
| -- | -- | -- | -- |
|
|
|
| "-neither-" | `limit_to=null` | `limit_to=0` (*incorrect*) | `limit_to=null` |
|
|
|
| "Limit To" | `limit_to=1` | `limit_to=1` | `limit_to=1` |
|
|
|
| "Also Include" | `limit_to=0` | `limit_to=0` | `limit_to=0` |
|
|
|
|
|
|
# Risk Factors
|
|
|
The upgrade for `5.49.2` re-enables storage for all three options.
|
|
|
|
|
|
TODO
|
|
|
Additionally, `5.49.2` restores the `limit_to` option, converting from "Also Include" (`limit_to=0`) back to "-neither-" (`limit_to=null`). However, it may not restore *all* records. Some records may be incorrectly left behind with "Also Include".
|
|
|
|
|
|
Consequently, if your system has any "*Scheduled Reminders*" with the "Also Include" option, you should look at them and consider whether it is properly configured. During upgrade, the upgrader will advise you if it finds any entities that merit consideration. |
|
|
\ No newline at end of file |