Report Centre Essentials

Report Centre Essentials 2.13.6

No permission to buy ($45.00)
  • Fix installer not triggering permission rebuilds are triggered when default permissions are applied.
  • Add missing phrase when sorting report queue rules
  • php 8.2 compatibility fix
  • Fix adding a new report queue did not trigger permissions rebuild
  • Add "Container owner state" to report queue rules for detecting if the reporter/reported is the owner of a thread (or profile for profile posts/comments)
  • Change "All user groups"/"None" option to "Disabled" for reporter/reported user criteria to better represent how matching actually works.
  • Require for Report Improvements 2.10.8+
  • Improve how report queue feature is bolted onto the Reports controller.
  • Require Report Improvements v2.10.0+
  • Fix admin 'manage report queues' was not enforced
  • Fix " Macro public:svReportImprov_report_macros :: resolve_report() error: Macro argument report is required and no value was provided" on deleting threads
  • Fix resolving reports on thread move/delete was offers to moderators would could not resolve reports
  • Fix only a single thread of reports could be resolved at a time via move/delete
  • Remove redundant query on checking for watched report state
  • Remove redundant query on rendering reported user's banners
  • Rework various 'resolve report on moderator actions' to be more standardized and consistent UI wise
  • Implement per-report queue permissions rather than simple group membership can-view checks
    • Convert old "view report stats' permission into 'view all report stats' permission
    • Add 'view report stats' permission that is per-queue
  • Like
Reactions: Joe Link
  • Fix "Template error: [E_USER_WARNING] Macro public:svReportCentreEssentials_report_macros:resolve_report is unknown" on deleting a thread
  • Fix NF/Discord compatibility
  • Add php 7 type hinting
  • Require Report Improvements v2.8.0
  • Force global namespace for functions which are known to be optimizable to bytecode in php
  • Fix report queue last action column updating
    • Now includes recently closed/rejected reports, these will age out (after a day).
    • Bulk actions now update it
    • Report comments which did not change the report state now update it
  • Move report queue read tracking into database instead of session
  • Add report queue criteria;
    • Criteria on report
      • Is automatic report (automatic report vs user report)
      • Report action type (ie user/moderator)
    • Additional reporter/reported user criteria
      • Is user banned
      • Is staff member
  • Add option to resolve reports in a thread when moving
  • Add option to resolve reports when deleting profile post comments
  • Report Improvements reaction support
  • Add report/warning search links to user reports
  • Add 'Search warnings in thread' link to various search links (If XFES is installed)
  • Add watch/unwatch support for reports
  • Reduce memory usage when computing pre-user-per-report-queue counts
  • Fix potential infinite recursion when attempting to discover the linked report for an approval queue item
  • Require php 7.0+
  • Require Report Improvements v2.6.0+
  • Now depends on Standard Library by Xon (v1.1.0+)
  • Compatibility fix for User Essentials for XF2.2+
  • Compatibility fix for Report Improvements reaction support
  • Fix double-encoding of cache values, which is surprisingly expensive
  • Fix that report comment statistics included non-comment actions (ie filter out report comments without a message)
  • Improve approval queue finding relevant report for 3rd party content, or defaulting to the user's report
  • Conform support for XF2.2
  • Fix information disclosure leak via old XF1.x user report's previous reported content history feature to users who can access the report queue but not the admin-cp.
    This is done via redact XF1.x style report information for user reports to match XF2.x structure
  • Fix report stats pre-set date ranges not working as expected
  • When rendering report queue stats, push the current domain into history not the canonical domain as otherwise this can trigger poorly reported JS errors
Back
Top Bottom