- 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
- Fix "Force conversation email on warning" option did not trigger for banned users
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
- Improve UX around editing a warning when is Warning Acknowledgements enabled
- 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
- Reduce queries when viewing a warning
- When editing, strip http://https:// out of links which had replacables in Warning Achnologement user notes
- Fix silly bug where non-expiring warnings/bans where ignored when considering the next expiry time.
- 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 of4294967295
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 CLIphp cmd.php xf-rebuild:users
will recompute the next pending expiry for all users
- Hook up warning criteria take #2
- Simplify phrase sv_please_enter_note_with_at_least_x_characters
- When issuing a warning; add "required" flag to user notes if configured
- Minor code cleanup
- Actually implement warning criteria. Broken since initial v2.0.0 release