newimage submitted a new resource:
Warning Improvements by Xon 2.4.7 - Warning
Read more about this resource...
Warning Improvements by Xon 2.4.7 - Warning
Read more about this resource...
A Collection of improvements to XF's warning system
This add-on expects all users able to issue warnings to be a member of the default Registered User's group. If this is not the case, you will not have permission to issue warnings until you:
or
- Add every into the Registered Users group
Warning; All user group titles will be visible if they are applied in a Warning Action
- Adjust the permissions in each Warning Category.
- ...
php 8 compatibility fix
Fix regression causing additional checkbox options when issuing a warning to always be selected
Fix anonymize warning conversations
Fix incorrect boolean check in anonymize warning conversation feature
- Force global namespace for functions which are known to be optimizable to bytecode in php
- Fix {points} replacables in warning conversations was pulling from the wrong user, and ensure {staff}/{staff_user_id} replacables respect anonymized warning issuer configuration
Fix php-version dependent typo "syntax error, unexpected token "\"
Fix editing custom warning in admincp
- When issuing a warning, ensure the default warning titles are rendered in the warned user's language
- 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
2.6.6 - Maintenance update
- 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 of...
- If installed, require Report Improvements v2.10.1+
- XF2.2.6 compatibility update; fix per-warning "Allow editable warning title when giving warning" option disappearing
- Allow editing virtually all details for a warning, supports Report Improvements and Warning Acknowledgements.
- Allow sending an alert to the warned user on editing or deleting warnings, with an optional reason
- Reduce queries when viewing a warning
- When editing, strip http://https:// out of links which had replacables in Warning Achnologement user notes
- 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
- Improve UX around editing a warning when is Warning Acknowledgements enabled
- Only show previous warnings if a user can see them
- Add missing permission check for if a report can be resolved when editing a warning
- Fix that "resolve report" checkbox could be shown to users who can't resolve reports when editing warnings
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
- Fix "Force conversation email on warning" option did not trigger for banned users
- 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
- 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