... | ... | @@ -29,16 +29,21 @@ The issue arises from a subtle schema change in the "*Scheduled Reminder*" entit |
|
|
|
|
|
![Edit Scheduled Reminder](/uploads/51b11de87d05f00394d26203eabee5ba/image.png)
|
|
|
|
|
|
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.
|
|
|
In `5.49.0`, the first option ("-neither-") is stored incorrectly -- it is converted to "Also include". This erroneous conversion affected *new reminders* (#3465) as well as *pre-existing reminders* (#3464).
|
|
|
|
|
|
| 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` |
|
|
|
| "Limit to" | `limit_to=1` | `limit_to=1` | `limit_to=1` |
|
|
|
| "Also include" | `limit_to=0` | `limit_to=0` | `limit_to=0` |
|
|
|
|
|
|
The upgrade for `5.49.2` re-enables storage for all three options.
|
|
|
|
|
|
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".
|
|
|
Additionally, `5.49.2` examines the overall settings and restores the `limit_to` option, converting from "Also include" (`limit_to=0`) back to "-neither-" (`limit_to=null`). It should restore *very problematic records* (ones which massively overcommunicate) and *easy records* (which have clearcut histories).
|
|
|
|
|
|
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 |
|
|
However, it may not restore *all* records. From a database perspective, it is not possible to *automatically* distinguish between:
|
|
|
|
|
|
1. Records which are truly set to "Also include".
|
|
|
2. Records which were recently set "-neither-" but which *historically* used a value of "Also include".
|
|
|
|
|
|
Consequently, if your system has any ambiguous "*Scheduled Reminders*" (where it cannot distinguish `#1` and `#2`), then the upgrader will encourage you to review those records manually. |