-
Notifications
You must be signed in to change notification settings - Fork 32
- Protects comments, user registration & login forms
- Protects GiveWP forms & helps prevent testing stolen credit cards
- Protects Contact Form 7 form submissions
- Protects Gravity Forms, Contact Form 7, WPForms, Formidable Form Builder & Fluent Forms forms
- Protects MemberPress & WooCommerce registrations
- Protects Mailchimp for WordPress sign-ups
- and can be integrated into any existing theme or plugin
- the offending IP and/or email address,
- offense type (registration, comment, etc.),
- and basic site information like the name, URL, and site email.
Site emails are never shared with other parties and are used to help support requests & provide important announcements. No personal data is shared. However, the user's IP address may be considered personal data under GDPR and CCPA.
Not by itself. WordPress Zero Spam does not block IP addresses by itself. Visitors that are getting blocked have either been manually blocked by the site admin or appear in one of the IP blacklists like Stop Forum Spam, Project Honeypot, or the Zero Spam IP database.
If a legitimate user is getting blocked, check the Log (Admin > Dashboard > Zero Spam > Log) to get further details why they were blocked. You can adjust how strict the 3rd-party blacklist checks are or disable those if you find that your users are prone to being flagged as spam/malicious.
No. WordPress Zero Spam is unable to integrate Jetpack. For more information, see https://wordpress.org/support/topic/incompatible-with-jetpack-comments.
Enabled caching. Caching is highly recommended and will prevent repeated calls to third-party API and access checks on each page visit.
You can also adjust the cache and API timeout settings in admin depending on your server and specific needs.
-
wp zerospam autoconfigure— Auto-configures with recommended settings. -
wp zerospam settings— Displays all plugin settings. -
wp zerospam set --[SETTING_KEY]=[VALUE]— Updates a plugin setting.
Some hosts have issues with they way they access files. If you're seeing a ftp_fget PHP notice, setting the FS_METHOD constant to direct in wp-config.php above the line /* That's all, stop editing! Happy Pressing. */ should solve the problem:
define('FS_METHOD', 'direct');
If hosting with Pantheon, see their known issues page for more information and what to do to resolve it with their $_ENV['PANTHEON_ENVIRONMENT'] variable check.