Warning Improvements by Xon

xF2 Add-on Warning Improvements by Xon 2.11.4

No permission to download
Overview FAQ Updates (75) History

2.8.4 - Maintenance update

  • Fix typo in admincp phrase
  • Fix error during updating when Report Improvements files exist, but the add-on isn't active
  • Change "Warning Escalating Defaults" related phrases text to "Escalating default warning expiry" phrases to better reflect the feature

2.8.3 - Bugfix update

  • Improve compatibility with older MySQL/MariaDb versions (Fix column sv_content_spoiler_title can't have a default value)
  • When content is edited, ensure the warning spoiler/disable reaction flags are copied to ensure they are kept in sync

2.7.11 - Bugfix update

  • Fix 'default selected' when using radio-view when issuing a warning not selecting the first warning in the list, and causing nothing to be selected when the custom warning isn't selectable
Click to expand...

2.7.10 - Bugfix update

  • Fix "Force conversation email on warning" option did not trigger for banned users
Click to expand...

2.7.9 - Bugfix update

If using Report Improvements, recommend updating to v2.10.14+ as it may cause issuing a warning to fail with 'conversation title required'.

  • php 8.2 compat fixes
  • Prevent error about a missing function when editing a warning when too old a Report Improvements is installed

2.7.6 - Maintenance update

  • Improve UX around editing a warning when is Warning Acknowledgements enabled
Click to expand...

2.7.5 - Bugfix update

  • Fix that editing a warning's points would not change when the next-page load checks to expire just expired warnings.
  • Fix edit points to zero + expiring a warning did not behave as expected

2.7.4 - Bugfix update

  • Reduce queries when viewing a warning
  • When editing, strip http://https:// out of links which had replacables in Warning Achnologement user notes

2.6.6. Patch 1 - Bugfix update

  • Fix silly bug where non-expiring warnings/bans where ignored when considering the next expiry time.

2.6.6 - Maintenance update

  • Improve robustness of expiring warnings/bans/etc on the next page visit after they have expired.
    • Fix edge case where rebuild pending expiry time-stamp was not triggered as expected
    • On rebuild user caches, also rebuild pending expiry time-stamp

Older versions (XF1?) may have caused an expiry date of 4294967295 instead of 0 for non-expiring. It is recommended to review these warnings and manually expiring them;
Code: 
select * 
from xf_warning
where expiry_date = 4294967295 AND is_expired = 0

After this rebuilding user via tools => rebuild users, or via CLI php cmd.php xf-rebuild:users will recompute the next pending expiry for all users
731Threads
2,287Messages
63,776Members
letooLatest member
Back