SpamPot
Adds a honeypot form field on the registration and login pages to trap spammers.
Maintenance 20/1003458d since update
Active installs
10
Downloads
1,848
Reviews
0
Age
9.7y
Tagsspamhoneypothoney pothoney trapspam trap
Plugin info
Total downloads: 1,848
Active installs: 10
Total reviews: 0
Average rating: 0
Support threads opened: 0
Support threads resolved: 0 (0%)
Available in: 1 language(s)
Contributors: 1
Last updated: 7/13/2016 (3458 days ago)
Added to WordPress: 4/8/2016 (9 years old)
Minimum WordPress version: 3.8
Tested up to WordPress version: 4.5.33
Minimum PHP version: f
Maintenance & Compatibility
Maintenance score
Possibly abandoned • Last updated 3458 days ago
20/100
Is SpamPot abandoned?
Possibly abandoned (last update 3458 days ago).
Compatibility
Requires WordPress: 3.8
Tested up to: 4.5.33
Requires PHP: f
Similar & Alternatives
Explore plugins with similar tags, and compare key metrics like downloads, ratings, updates, support, and WP/PHP compatibility.
No similar plugins found yet.
Description
Blocks spam signups by adding an invisible field to your registration and login forms, and switching its id with the real username or email form field.
When spam bots blindly fill the “required” fake field in, WP will redirect them to an error message and not let them register or login.
No 3rd party service, no intrusive captchas.
Installation
- Upload the plugin files to the /wp-content/plugins/spampot/ directory, or install the plugin through the WordPress plugins screen directly.
- Activate the plugin through the ‘Plugins’ screen in WordPress
- That’s it, no more configuration needed.
Frequently Asked Questions
Will This Stop Everything?
- This honeypot technique works against the lazy “drive by” automated spambots (ie. most of them), but will not be effective against spammers specifically targetting your site nor spammers signing up by hand.
Review feed
No reviews available
Screenshots
No screenshots available
Changelog
0.3
- Initial release.
0.31
- Fix for 4.5’s changed login text.
0.32
- Changed the way the honeypot field was inserted to avoid a conflict with my Custom Logins plugin.
0.33
- If the honeypot field is unable to be inserted, then the form will continue working and notify the admin by email of this failure.
0.34
- Changed the regex that matches the “normal” username field to be slightly more robust.