mystic_knownbugs
Differences
This shows you the differences between two versions of the page.
Both sides previous revisionPrevious revisionNext revision | Previous revision | ||
mystic_knownbugs [2020/01/08 21:43] – information about known 2020 bug avon | mystic_knownbugs [2020/02/05 02:14] (current) – content updates avon | ||
---|---|---|---|
Line 1: | Line 1: | ||
- | ====== | + | ====== Significant |
- | This page has been created to alert sysops to a significant | + | This page details any significant |
- | ==== Incorrect data deletion since 1 Jan 2020 ==== | + | ===== Mystic |
- | There is a known bug in Mystic 1.12 A43 that has appeared | + | There is a known bug in Mystic 1.12 A43 that appeared |
- | The bug covers two **MUTIL** functions | + | ==== Incorrect data deletion since 1 Jan 2020 ==== |
+ | |||
+ | The bug covers two **MUTIL** functions | ||
The bug sees Mystic assuming any year that is less than 20 (e.g. 2019) as being part of the 21st century (e.g. 2019) while years that are 20 or greater are seen to be part of the 20th century (e.g. 1920). | The bug sees Mystic assuming any year that is less than 20 (e.g. 2019) as being part of the 21st century (e.g. 2019) while years that are 20 or greater are seen to be part of the 20th century (e.g. 1920). | ||
Line 28: | Line 30: | ||
! Jan 03 00: | ! Jan 03 00: | ||
- | Until the author fixes this bug it is recommended: | + | === Recommended Steps === |
+ | |||
+ | If you are using Mystic 1.12 A43 it' | ||
* Do not use the **PurgeUserBase** function at all. | * Do not use the **PurgeUserBase** function at all. | ||
* Do not set //**Max Msg Age**// in message bases and then run the **PurgeMessageBases** function. | * Do not set //**Max Msg Age**// in message bases and then run the **PurgeMessageBases** function. | ||
+ | * Upgrade your BBS to a newer version of Mystic BBS - check the [[http:// | ||
+ | |||
+ | **Note:** If you still wish to use Mystic 1.12 A43 it is still OK to use the **PurgeMessageBases** function with the //**Max Msgs**// option. This option of purging does not rely on a date but rather just looks at the total number of messages in a base when deciding on how many to purge. That said, you really should update to the latest version to get the benefit of bug fixes and new features. | ||
- | **Note:** It is still OK to use the **PurgeMessageBases** function with the //**Max Msgs**// option. This option of purging does not rely on a date but rather just looks at the total number of messages in a base when deciding on how many to purge. |
mystic_knownbugs.1578541387.txt.gz · Last modified: by avon