Danny Santoro

Hi @2candela2 !

This appears to be working on my test install for shorter passwords. Length isn’t actually factored in.

Password length doesn’t really play much into password security. While it helps, there are a lot of other factors that are much more important which I cover in the plugin documentation here: https://github.com/DanielSantoro/wc-password-strength-settings/wiki/How-Password-Strength-is-Determined

WordPress uses a script from Dropbox called zxcvbn for password strength. You can see a calculator here: https://lowe.github.io/tryzxcvbn/

If I type in as a test password twelvecharacters (which is actually 14 characters), you get a password strength of 2/4 which would take two days at 10 guesses per second. However, if I do six crayons (which is 11 characters), your password is already stronger at 3/4 which would take 7 months at 10 guesses per second.

In short, passwords are weird! Length very rarely has anything to do with strength, though it could in theory help. If you’d like to add an issue on GitHub then I can look into adding an optional length requirement in a future release: https://github.com/DanielSantoro/wc-password-strength-settings/issues

I hope this helps, and if not then if you can let me know your site URL then I can take a look for conflicts.

Danny

• This reply was modified 1 week, 4 days ago by Danny Santoro. Reason: Details

Happy to help! 3.0.1 should have pushed just now, it looks like the wrong trunk was marked as the latest. Let me know if it is still throwing errors for you!

It should already be marked compatible – their guide just needs a function added which should have been in a few weeks ago. Weird. In any case, pushing the flag up now. Thank you.

Hi @alexlever17 ,

I am so sorry I didn’t reply – the www.remarpro.com support forums are really bad about notifications and didn’t seem to ping me directly.

There isn’t actually a way to modify the rules on what makes it strong in the plugin since we use the zxcvbn tool: https://github.com/DanielSantoro/wc-password-strength-settings/wiki/How-Password-Strength-is-Determined

If you’d like to send me an email then you can give some examples of the ones you were trying and we can figure out why they were being rejected: https://danielsantoro.com/support/

Hey @nossileee !

Definitely – the plugin shouldn’t actually be impacted by HPOS since it uses different tables than the ones that are being changed, but I’ll look at the latest on GitHub to see what is making it throw errors. It might be that I need to move the settings out of the WooCommerce submenu and put it under Users or something.

I’ve been meaning to make it apply to all logins even without WooCommerce which might help with some themes that override the login, so this is as good of a reason as any. I’ll look at it today and tomorrow. While I don’t have an ETA, you can expect a plugin update which should get rid of the error ASAP (and before the release). Thanks for letting me know!

Ah, understood! I’ve unfortunately been out of the WooCommerce loop for a little while and hadn’t seen the compatibility function code. Thanks for that – a new version will be deploying shortly that declares compatibility. ??

I appreciate the catch!

Hi @bigbugsy – Sure thing, but I seem to be having trouble replicating an issue. Could you describe what you’re seeing that is broken with the sign in?

Edit: To clarify, from what I can see in the HPOS documentation, it relates specifically to order information which this plugin doesn’t touch. If it changes the login then I’ll need to do some digging.

• This reply was modified 1 year, 8 months ago by Danny Santoro.

Hi @mazaadiksa,

Everything should continue to work as expected. I’ll soon be moving the controls out of the Accounts page and into it’s own (likely under “Users”).

The only thing I can’t test are certain popular paid themes, but if you run into an issue then feel free to reach out and I’ll work to get it resolved.

I hope this helps!

Hi @scuffed ,

Absolutely! The “how” of it depends a bit on your site. If you don’t mind, send me an email from this link with your site’s URL and an example page where it isn’t showing up and I should be able to take it from there. ?? https://danielsantoro.com/contact/

I’ll respond to your email from my contact form and see if we can figure it out!

Hi @eftcolumbus !

I haven’t had any issue reports or problems on client sites I manage with the new version.

The re-code was really just clean up and re-coding what I wrote a few years ago with the knowledge I have now. A key part of that are some safeguards so another plugin wouldn’t impact this one (or vice-versa), make the code easier to update, and to make the plugin more flexible if WooCommerce changes its user interface.

If you have any sort of problem when you update then by all means post here – I’ll gladly jump on and help figure out what it could be and how to fix it.

Hi there! It looks like you may have double posted a review or comment from another plugin, but if this plugin is broken then please let me know. ??

Thanks for the notice, I’ll likely update it when I have the time this or next week.

Hi @camilo517 ,

Thanks for reaching out! It recently was deprecated, but it shouldn’t impact functionality. Are you having issues with the plugin or did you find the notice through one of the new checking tools?

Hi @vmarko,

I apologize for the delay, I got sidetracked and dropped the ball on responses here. I am using one configuration file since the number of sites is pretty high – it would be very unwieldy to have a separate configuration per site.