Eeek! Sorry about that, let me test it out on another site and see if I can replicate … she’s still in 1.0.0 so I anticipated a few bugs but was hoping nothing major.
Can you check your .htaccess file and see if the rewrites are still in there?
Just tested on a blank install and didn’t have any issues, can you please provide as many details as possible?
Are you requiring activation or just using it for permalinks?
Are you using any other “authentication” or “login” plugins?
Are you using email or actual username for login?
Thanks!
It is a fresh installation that I did last night. It is intended to be used as a practice site where I can try out new plugins to make sure there is no problem before I use them on my main site.
This is the entire contents of the .htaccessfile:
# BEGIN WordPress
<IfModule mod_rewrite.c>
RewriteEngine On
RewriteBase /practice/
RewriteRule ^index\.php$ – [L]
RewriteRule ^login/? /practice/wp-login.php [QSA,L]
RewriteRule ^lost-password/rp/? /practice/wp-login.php?action=rp [QSA,L]
RewriteRule ^lost-password/resetpass/? /practice/wp-login.php?action=resetpass [QSA,L]
RewriteRule ^lost-password/confirm/? /practice/wp-login.php?checkemail=confirm [QSA,L]
RewriteRule ^lost-password/expired/? /practice/wp-login.php?action=lostpassword&error=expiredkey [QSA,L]
RewriteRule ^lost-password/invalid/? /practice/wp-login.php?action=lostpassword&error=invalidkey [QSA,L]
RewriteRule ^lost-password/? /practice/wp-login.php?action=lostpassword [QSA,L]
RewriteRule ^activate/pending/? /practice/wp-login.php?action=activation&step=pending [QSA,L]
RewriteRule ^activate/password/? /practice/wp-login.php?action=rp&step=activate [QSA,L]
RewriteRule ^activate/invalid/? /practice/wp-login.php?action=lostpassword&error=invalidkey [QSA,L]
RewriteRule ^activate/expired/? /practice/wp-login.php?action=lostpassword&error=expiredkey [QSA,L]
RewriteRule ^activate/([^/]*)/([^/]*)/ /practice/wp-login.php?action=rp&key=$2&login=$1 [QSA,L]
RewriteRule ^register/disabled/? /practice/wp-login.php?registration=disabled [QSA,L]
RewriteRule ^register/? /practice/wp-login.php?action=register [QSA,L]
RewriteRule ^logout/? /practice/wp-login.php?loggedout=true [QSA,L]
RewriteCond %{REQUEST_FILENAME} !-f
RewriteCond %{REQUEST_FILENAME} !-d
RewriteRule . /practice/index.php [L]
</IfModule>
# END WordPress
I am using my actual username to login in and once the plugin works properly and it is installed on the main site, It will be used for registration and activation.
These are the plugins I curently have installed on the practice site:
Akismet
Captcha
Coming Soon Page & Maintenance Mode
Disable XML-RPC
Limit Login Attempts
Wordpress Simple Firewall
WP Super Cache
Note: Last night after activating the plugin, I repeatedly got a failed username/password message. The only way I could reach the backend of the site was to deleted WP Login Flow plugin via my ftp.
Note: Once I was able to get to the backend, the same username/password worked.
So I don’t think this is related to the plugin (from my testing so far) as my function doesn’t get called until priority 30 and priority 20 is internal WP core checks the User/Pass and then passes a WP_User or WP_Error object to my plugin …
With that said, all my plugin does is check that user account for pending activation, and if it’s not pending it will return the object that was sent to my plugin …. SO with that said, it has to be something else with your site as the authentication from my plugin passes along the object it receives or discards object received and returns a new WP_Error if account is pending activation.
The only possible issue I see is the fact that I used add_action() instead of add_filter(), but really it’s the same thing, so that shouldn’t be an issue either.
Thanks for the rewrite rules, do you have Skype by chance? If so can you message me on Skype my username is “tripflex”
If not, can you send me an email here (dont want to post email address on public forum):
https://plugins.smyl.es/contact/
Few questions, what version of WordPress are you using? Is it an Apache web server?
You said it gives you a username/password is incorrect error, right? Not an error saying the account hasn’t been activated?
Just saw your response, it has to be one of those plugins causing the problem. Just looking at them I know that limit login attempts is mad old and probably outdated so that could be the cause but there’s so many factors it’s hard to tell without testing that exact setup.
Thanks for your time. I’m not interested in working that hard so I’ll go to plan B.
FYI, like I thought it is the Limit Login Attempts plugin … working on a fix which you can track here:
https://github.com/tripflex/wp-login-flow/issues/7
OK. Thanks. I’ll stay with login on the backend for now and monitor your progress to see if the modifications work.
Good luck!
