Differences

This shows you the differences between two versions of the page.

--- mystic_knownbugs [2020/01/20 00:41] – [Please Read] avon
+++ mystic_knownbugs [2020/02/05 02:14] (current) – content updates avon
@@ Line 1: / Line 1: @@
-====== Please Read ======
+====== Significant Bugs ======
-This page has been created to alert sysops to a significant bug that has been reported since the start of 2020.
+This page details any significant bugs reported for Mystic. It's recommended that you always run the latest release of Mystic and those files can be found on [[http://mysticbbs.com/downloads.html|Mystic BBS]] website.
-//**Update:** As at 20 Jan 2020 it's known that the author is working on a fix for this which will appear when Mystic 1.12 A44 is released. Timing for this release is still TBC.//
+===== Mystic 1.12 A43 =====
-==== Incorrect data deletion since 1 Jan 2020 ====
+There is a known bug in Mystic 1.12 A43 that appeared from 1 Jan 2020 onward.
-There is a known bug in Mystic 1.12 A43 that has appeared since 1 Jan 2020.
+==== Incorrect data deletion since 1 Jan 2020 ====
 The bug covers two **MUTIL** functions [[mutil_purge_userbase|PurgeUserBase]] and [[mutil_purge_message_bases|PurgeMessageBases]] and relates to the way Mystic incorrectly calculates dates when looking to purge inactive users or messages by age.
@@ Line 30: / Line 30: @@
   ! Jan 03 00:45:06      Purge #1003 date 01/01/20 days 36527
-Until the author fixes this bug it is recommended:
+=== Recommended Steps ===
+If you are using Mystic 1.12 A43 it's recommended that you:
   * Do not use the **PurgeUserBase** function at all.
   * 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://mysticbbs.com/downloads.html|Mystic BBS website]] for updates.
+**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.