Report Improvements by Xon

Report Improvements by Xon 2.10.9

No permission to download
  • Fix additional blank form row when reporting a post on a non-reported/warned/thread banned user
  • Fix 'Attempt to read property "user_id" on null' on report search results for deleted users when the viewer can not view reporter's usernames
  • Fix error reverting edit history for a report comment
  • Fix leaving a report in an open state when issuing a thread replyban and warning and the option to resolve the report is used.
  • Fix "Call to a member function hydrateRelation() on null" error when a reply-ban references a hard-deleted thread
  • If installed, strongly recommend updating to Warning Improvements v2.7.3+ after installing this add-on
  • If installed, strongly recommend updating to Report Centre Essentials v2.6.4+ after installing this add-on
  • Fix incorrectly stating a new report will be created when issuing a warning
  • Fix edge case where report resolve alerts where not sent as expected when issuing warnings
  • Reduce N+1 query behaviour with many thread reply bans on a report
  • Reshuffle permissions to support per-report queue permissions.
    • Requires Report Centre Essentials to activate per-report queue permissions, and per-report queue permissions analysis
  • Log the user's IP when a user makes a report or a moderator comments on a report
  • Log warning public banner into reports
  • Add preview support for report comments
  • Add edit support for report comments
  • Add attachment support for report comments
  • Support using Persistent Alert add-on's xf_user_alert.sv_container_id when checking for report comment alerts for hopefully improved performance on alerting
  • Fix report title's been indexed into search as escaped
    • Re-indexing reports/reports comments really only matters if using ElasticSearch Essential's exact title match feature.
  • Fix double escaping when rendering report titles in search results
  • Fix report comment alert would miss-classify warning operation types as new warnings
  • Fix "Call to undefined method XF\Entity\User::canReportSearch()" that can occur during upgrading
  • When a post is being reported; inject 'user has been warned for this post' notice, and a 'has been reply-banned' notice if SV/ThreadReplyBanTeeth add-on is installed
  • On making non-closing report comments; do not record a comment as sent if the 'send alert' checkbox is set, despite not actually sending the alert
  • Force global namespace for functions which are known to be optimizable to bytecode in php
  • Implement php 7 type hinting
  • Add option "Resolve report - Alerts" configure alerting default when rejecting/resolving reports
  • Add "Send resolution alert" checkbox when issuing/deleting/expiring warnings and issuing thread reply bans