@susie.Q –
1. In your dashboard go to ‘Settings>General’ and make sure ‘Anyone can register is UNCHECKED.
2. In the WP-Members Options, I UNCHECKED the ‘Hide Registration’ box.
These would be unrelated to your issue.
3. I read on line that sometimes caching pages for plugins that force login to the front end like WP-Members does can cause a problem.
I use WP Super Cache so in ?he WP-Super Cach Settings>Advanced settings I added the strings for the WP-Member pages that force those pages not to be cached,ex. /register/, /members-area/, /sign-in/
Of anything you’ve mentioned, this is the only thing that would probably be your issue. While WP Super Cache shouldn’t cause any issues with login, it certainly could be possible depending upon your configuration.
4. If you are using something other than the recaptcha that is suggested in the WP-member settings, you may have to deactivate ?hat plugin as it may cause a conflict.
WP-Members has built in support for reCAPTCHA and Really Simple CAPTCHA for registration. But these would be unrelated to login. If you use a plugin that incorporates a CAPTCHA into the backend login (wp-login.php), then that will most likely cause a problem.
That particular problem stems from the fact that these plugins remove the wp_authenticate_username_password function from the authenticate process and replace it with their own. That creates a problem because they add a third level of authentication (username, password, AND captcha) to WP’s autheticate process, which WP-Members also uses when validating a login. But the front end login won’t be passing that third value and will then fail (that is what @grigoris’s problem was).
There are no issues with WP 4.0.1 and WP-Members. There’s nothing in the update that effects the plugin.
