Spam Protection Without Captcha

Beschreibung

Protect Login, Register, Lost & Reset Password, Comment, woocommerce, Contact Form 7, bbpress, BuddyPress forms. No user interaction needed.

Supported Forms

  • Login
  • Register
  • Lost Password
  • Reset Password
  • Comment Form
  • Multisite User Signup
  • Multisite blog Signup
  • WooCommerce Login
  • WooCommerce Register
  • WooCommerce Lost Password
  • WooCommerce Reset Password
  • Contact Form 7
  • bbPress New topic
  • bbPress reply to topic
  • BuddyPress register

Privacy Notices

  • If you check „Cookie Check“ (checked by default) then a hash will be stored in user browser cookie.
  • If you check „stopforumspam Check“, this plugin send IP address to stopforumspam.com for spam database check. Please read Stop Forum Spam Privacy.

Screenshots

  • Admin settings

Installation

  1. Upload „spam-protection-without-captcha“ to the „/wp-content/plugins/“ directory.
  2. Activate the plugin through the „Plugins“ menu in WordPress.
  3. Go to plugin settings page for setup.

FAQ

Can i use this plugin to my language?

Yes. this plugin is translate ready. But If your language is not available you can make one. If you want to help us to translate this plugin to your language you are welcome.

Does it support multiple form in same page?

Yes. It support unlimited number of forms in same page.

How to login if i am locked out?

Enable javaScript of your browser and accept cookie. If „stopforumspam Check“ is checked and your ip is not in whitelisted and you are getting ip spam error, try another device with another ip if possible.
If not, you can access your file via FTP or file manager and rename „spam-protection-without-captcha“ folder to something else. Then login as normal. Then rename back this folder.

Rezensionen

Lies alle 1 Rezension

Mitwirkende & Entwickler

„Spam Protection Without Captcha“ ist Open-Source-Software. Folgende Menschen haben an diesem Plugin mitgewirkt:

Mitwirkende

Änderungsprotokoll

1.2

  • Now admin can select which forms need to validate.
  • Now secure token is used.
  • Verify token using hash_equals instead of normal equal.
  • Now set cookie using php as well.

1.1

  • Initial release.