yfell

I have the same issue with the amended Hide Backend module. It is useless in its new form. I have temporarily resolved it by copying the old module folder into the new plugin directory so I still have some of the updates. As I don’t have plugin conflicts this works well for now. However this is obviously not best practice. I hope that this can be resolved in a better way soon. Maybe give users a choice to use the module with its older and most powerful functionality if there are no conflicts but also include the newer module as a separate choice to allow others who might have problems to enable the new version instead.

I also ran into this issue. I found another post about this here: https://www.ads-software.com/support/topic/relhttpsapiworg-json-noise-doesnt-validate?replies=16. It doesn’t look like a fix will be happening soon, but at least it’s good to know why it has appeared and why it’s breaking our W3C validation efforts.

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.

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 ??