Recent content by Xon

Check the spam trigger log, it logs rejected signups there.

Thanks, I'll review the setup/upgrade code again as it shouldn't be doing that. But at least it should be an easy reproducer.

This can easily exhaust API calls when using various backend providers. I have been considering email verification, but simply haven't had time to research these. I've found fingerprinting is very difficult and often doesn't give useful results when identify an exact individual and this add-on...

Xon updated Signup abuse detection and blocking with a new update entry: 1.20.4 - Maintenance update Read the rest of this update entry...

Xon updated Content Ratings with a new update entry: 2.8.10 - Bugfix update Read the rest of this update entry...

Xon updated Threadmarks Pro with a new update entry: 2.24.6 Read the rest of this update entry...

Xon updated Advanced Bb Codes Pack with a new update entry: 1.18.4 - Bugfix update Read the rest of this update entry...

Yes that would be fine. You'll need to remove entries in xf_report and xf_report_comment table, and then rebuild the search index for reports and report comments to flush those out.

Xon updated Limit bots with a new update entry: 2.5.0 - Feature update Read the rest of this update entry...

Xon updated Search Improvements with a new update entry: 2.19.0 - Feature & bugfix update Read the rest of this update entry...

Xon updated Report Centre Essentials with a new update entry: 2.15.4 - Bugfix update Read the rest of this update entry...

Xon updated Content Ratings with a new update entry: 2.8.9 - Compatibility & Bugfix update Read the rest of this update entry...

This requires database queries (or code to manually poke the delete method on the entity) as the XF UI doesn't support deleting reports.

Check if you've got customizations to the svReportCentreEssentials_report_macros template and the template is out of date or has unmerged changes. The macro report_response exists in there in the default style.

It took about +40 seconds to manually prune the table in batches of 50k rows. Looking at the on-disk copy of the table shows why: $ du -hs --apparent-size /var/lib/mysql/sbforums/xf_search.ibd 14G /var/lib/mysql/sbforums/xf_search.ibd