Hello,
Thank you for showing interest in our plugin. Can you please give us more details on what is happening? So far you’ve done the following:
1. Installed and activated plugin.
2. Trying to reset user password
3. Upon trying to do so yu get a “form not valid” error?
We cannot reproduce it. Can you please send us an email on support@wpwhitesecurity.com with the screenshots etc so we can look into your issue?
Thank you very much and sorry for any inconvenience caused.
Hi again. Something tells me the problem might be here :
– on the form, the inputs names are password_1 and password_2, while in your plugin’s code they’re referenced by $_POST[‘pass1’] and $_POST[‘pass2’] ; is this normal ?
Thanks !
Hi simaooliveira,
I came across your post after searching for my problem, which looks like it’s the same as yours. I realise it’s been a few weeks since your last post, so I don’t know if you resolved your issue, but thanks to your hint I did resolve mine. Apparently the Profile page in wp-admin uses inputs called ‘pass1’ and ‘pass2’, but the front end form for changing a password uses ‘password_1’ and ‘password_2’. Hopefully the plugin author will make that change in the next version, but I thought I should mention it here anyway so that if other users of the plugin do change the code they are aware of the difference. The only code you need to edit is in a few places inside the public function ValidatePasswordReset, in wp-password-policy-manager.php.
Thanks again for posting this! It was a big help 🙂
Hello guys
Sorry for the late reply 🙁
And thank you for letting me know about this issue. I have an update ready and going through testing right now and it should be out on Aug 17th.
I’ll see what I can do to have a fix for this until then.
Thanks again!
Regards,
Costin
Hi We are now experiencing this problem on our website is there a fix for this?
Kind regards
Nat
Hi Nat,
Just saw your post. I did not see an update that fixes this problem in the latest version of the plugin and I believe the plugin author was having a problem reproducing the error. Are you using Woocommerce by any chance? I think the problem is only affecting websites that use Woocommerce, which is potentially why the error has been difficult for the author to reproduce. If so, the fix I posted back in May should help you in the interim. It’s not a good way to work with plugins but it does fix the issue and it’s easy to implement temporarily.
