• A valid XenForo Licence validation token will be required to complete signup and purchasing.
    This may retrieve this from the XenForo Customer Area.
  • All XenForo 2.3+ add-ons require at least php 8.0, recommend php 8.2+
    All XenForo 2.2+ add-ons require at least php 7.2, recommend php 8.x
    All XenForo 2.0-2.1 add-ons require at least php 5.6, recommend php 7.x.
    The Standard Library add-on is also required.
    Older php versions are not supported, and add-ons will either refuse to install or fail to function.
  • Automatic discounts are applied for orders above $100 USD (10%) or for early renewals (5%)

Signup abuse detection and blocking 1.7.0

Change log

Fixes:
  • Fix "Duplicate entry 'xx-0' for key 'report'" when a race condition occurs and the record is saved but not reported
  • Only delete "User registration log" entry for a deleted user if "Full delete for GDPR" option is set

New features:
  • Rework "ignore for future events" option to actively exclude that set of users detected with those detection details rather than passively being ignored
  • Run Xenforo's spam checker over user profile fields and custom fields on signup
  • Add option "Registration spam phrases" (default empty)
  • Add option "Link Spam checker: Registration default action" (default moderate)
  • Add option "Request Website on signup" (default disabled)
  • "Email domain moderation" ie require explicit approval by domain and moderate unknown email domains
    • Add option "Non-allowed email action" (default none)
    • New permission; "[SignupAbuse] Allow approving email domains" (default not granted)
    • Import/export as CSV or XML
  • Allow banning an email domain from the approval queue
    • New permission; "[SignupAbuse] Allow banning email domains" (default not granted)
  • Allow banning an ISP/ASN from the approval queue
    • New permission; "[SignupAbuse] Allow banning ASN" (default not granted)
  • Work-around for a user approval design flaw in XenForo where a user may not have yet had their email confirmed.

    When manual approval is configured, there are two flows which result in the use user ending in the approval queue;
    • register => spam checker says moderate => approval queue. No email confirmation.
    • register => email confirm => approval queue. Has email confirm.
    The only hint on which flow has triggered is the user registration record has a non-approved status.
    The "Require email confirmation (always notifies)" feature is now flagged enabled if it detects the user's email likely has not been confirmed and avoids the email_confirm => moderated => email_confirm loop that could potentially happen
Back
Top