Try to install this : WPS Limit Login
I have the error messages on the new login page with the plugin WPS Hide Login, you must have a plugin that hides these errors.
Hello,
I don,t have any plugin that is hiding this errors when I deactivate your plugin the errors are back I tried another plugin (Rename wp-login.php) and the same problem occured. This happens when the url changes from wp-login.php to login
Hi There, I wanted to back up @teeboy4real here and mention that I notice the same behavior, error messages about wrong password won’t show. I *will* see cookies need to be activated errors when changing cache settings, however.
However, when I deactivate WPS Hide Login, errors about “wrong password” or “Username doesn’t exist” will return. When I deactivate all plugins except WPS Hide Login, the error messages still don’t show.
I would be happy to give you access to my test site if you would like to explore the issue further.
Actually, Nikolas, @teeboy4real I was researching through notes and saw a clue that may be the problem: If you route your DNS through a firewall or caching service, it breaks the error message functionality. Checking my “notes to be done” I see that this problem with my error messages on login began occurring when I setup a firewall service.
Okay… one more addendum…. I found a workaround:
This issue seems to occur in combination with WPS Hide Login, a caching service, and any theme or plugin that adds functionality to either the wp_Login_failed or wp_authenticate hooks.
I did a search for both of these in all my plugins and themes. They were both referred used in a membership plugin. I simply commented out the two lines connected to the “add_action()” commands that called those hooks, and it works perfectly now.
For further example, the lines looked like this:
add_action('wp_login_failed', 'name_of_custom_failed_login_function' );
add_action('wp_authenticate', 'name_of_custom_authentication_function',10,2);
**SIDE NOTE*** make sure to test your logins and failed logins. I got pretty lucky, but make sure that this doesn’t break anything that requires extra functionality.
Theoretically, this means there should be some JS (and probably css) files that output the error and control the shake that are messed up by caching. They may just need to be added as exceptions for my caching service. I don’t know what those are yet, but if I find them I will let you know. Mr. Kulka, if you would take a look at a similar setup with a CDN and a membership plugin (or plugin that lets you customize the look of wp-login.php) you should replicate this issue.
