Warnings/Bans with time-based expiry are now be removed on the 1st visit after the expiry time, rather than needing to wait for the hourly cron task to run.
If Warning Acknowledgement (paid) add-on is installed, by design the user will remain in the selected 'warned' user groups until all warnings are acknowledged, even the expired ones.
Criteria for warning count + include/exclude expired warnings, which can be date-range limited
update to jsTree 3.3.4 (from 3.3.3)
Fix deleting a warning category with a warning action attached to it
Allow warning fixup task to always run from the installer
Ensures account warning points are in sync with active warnings
Purges any should-be inactive warning actions
Allow editing Warning Actions to have no category
Fix expiring point-based warning actions with categories
A background task will correctly expiry warning actions on any affected accounts. Usernames will be logged the error log when detected & corrected
Fix unexpected recursion which blocks deleting/expiring warnings
Workaround for XF behavior (bug?) of issuing an expired warning which applies warning points to the account, but never removes them.
Should handle when a future update of XF fixes this behaviour.
Fix scrolling though warnings on an ipad
Handle if the warning category has been unexpectedly deleted by throwing a no permission error instead of erroring.
On install, update warnings which are using missing warning categories.
Fix: "Undefined index: warning_category_id" when logging a warning as a reply to a thread
Fix SQL error when importing warning groups from [TH] Warnings into Warning Categories.
[TH] Warnings must be installed and enabled when installing Warning Improvements.
Please disable [TH] Warnings after the install finishes due to add-on conflicts in the AdminCP.