Report Improvements by Xon 2.21.3

• Fix searching reports from NixFifty's Tickets by category

• Fix type error when indexing reports when 3rd party content returns returns null instead of something string-like
• Fix error on search results page as the result of a add-on conflict.
  • Removes @NixFifty's Ticket support for search result terms as this is moved to v2.6.0 of the Tickets add-on

• Fix internal server error when a warning with a title > 255 characters was issued

Thanks to @NamePros for sponsoring this update.
This add-on is now available on atelieraphelion.com

This update will require a full search rebuild, truncating the index before re-indexing.

• Require php 7.2+
• Require Standard Library by Xon v1.18.0+
• Require Search Improvements v2.9.0+ (was previously an optional dependency, now hard required)
• Fix report resolve alert reason wasn't indexed
• Fix reports with hard-delete content would not be re-indexed when required
• Fix public banner wasn't capture for new warnings
• Fix support for user renames/deletes/merges
• Fix assigning a report to a non-moderator was unreliable depending due to unstable sorting of the non-moderator list
• Fix the report assignable lists could become stale when permissions where changed
• Fix assignable user list could sometimes be unsorted
• Track user who assigned a report to another user (limited back-dating on install)
• Enrich @NixFifty's Tickets reports to display coontent date like post reports do
• Improvements which require ElasticSearch (aka Xenforo Enhanced Search)
  • Search by min/max number of comments, sort by number of comments
• Overhaul Report/Warning search. Many new criteria, a number require ElasticSearch Essentials.
  • Split Report search tab into Report and Warning search tabs
  • Rework most criteria, old search links will not work
  • New report criteria: Reported user/With assigned/By assigner/Participants/Reported for content in/Comment count/With report state/etc
  • New warning criteria: Warned user/Warning issuer/"Search only the latest version"/Warning log type/Warned for content in/Warning definition/Expiry date
    • If you are searching by expiry date, you probably want "Search only the latest version" checked!
  • Support searching reports/warnings by "Reported/Warned for content in", ie reports/warnings from a given forum.

• Fix error blocking deleting a warning when the content it was linked to has been hard-deleted

• Fix public content banner not being captured when a warning is created
• Fix warning in report did not indicate if the banner was the same as the public warning title
• Add missing search terms ("With warnings" and "Warned users: X") on results page

• php 8.2 compatibility update
• If installed, require Search Improvements v2.6.0+
• Support Search Improvements v2.7.0+ search term display

• Fix editing another user's report comment would change the user of that report comment
  • The permission for this was not granted by default to any group

• Fix being unable to set "Maximum non-moderator users who can handle reports" to zero
• Fix some report centre permissions (view/edit/view attachment) where not assigned to moderators on install
• Harden the new-install code path of the installer to only add report queue permissions to the stock Moderator/Administrator groups if they have the dependent permissions, not any user-group which may have moderator only permissions
• Add CLI command "sv-dev:export-report-users" to export non-moderators for a report
• Fix report assignment list would not include non-moderators who had been allowed the "view report queue" and "update report" permissions at the report queue level (when Report Centre Essentials is installed & active)
• Fix possible misleading "Potential miss-configuration detected. X users have access to handle/update this report via permissions" being logged
  • This is the result of the report assignment list could include non-moderators who had been denied the "view report queue" and "update report" permissions at the global level.
  • These users could not see, be alerted by or interact with the report, they where just being added to the dropdown as being assignable. Actual permission checks prevented them doing anything with the report they could potentially be assigned to.

• Fix missing column default causing errors when the add-on is disabled