BrendonMills

Good morning.

I am being pressured by the customer to fins a solution to this. Is it something you are likely to be able to resolve today? If not, I’ll need to look for an alternative solution for the site.

Thanks and regards, Brendon

No, it’s not resolved in WP 6.6.1 – that’s what we are running.

I should have added, this is running oin current WordPress in PHP 8.3.10.

Great there are fixes. We are hosting over 400 sites. A plugin or CSS temporary workaround is not practical. I hope that the WordPress team are able to release a 6.6.1 patch within 24 hours of releasing 6.6. I find it very suprising that a bug as basic as this wasn’t picked up during pre-release testing.

Yep I think it’s the same. I’ve updated the Github link too.

We are managing by disabling the plugin, logging in and then switching off the strong password requirement.

Some clients are updating their passwords and finding they don’t work anyway. Either way, implementing this in a default ON position was a poor idea. Sorry, love the plugin otherwise.

Disable iThemes plugin. Should be fine then.