Paddy Landau

Thank you again for your response, Olga.

I looked at wp-admin/includes/class-wp-site-health.php, and tried going to the website at .../wp-admin/includes/class-wp-site-health.php:1908, but it gave a 404 Not Found response.

I don’t know what get_test_rest_availability means. I looked it up but didn’t understand what I found.

Thank you for your reply, Olga.

I am able to edit and save a Page in the block error without any problem whatsoever. In the console, one error was reported as in the screenshot below.

https://pasteboard.co/JHCJ9ml.png

I enabled debugging with these two commands in wp-config.php:

define( 'WP_DEBUG', true );
define( 'WP_DEBUG_LOG', true );

However, the file wp-content/debug.log was not created when I edited, updated and viewed a Page.

I’m flummoxed.

Thank you, Yani.

I completely agree that regex is not user-friendly.

Thanks for your reply, Niall.

There are two separate accounts, both on GoDaddy, holding the various websites. The one in question is shared with two other websites that work.

I’ve looked at that first link that you gave, and searched all of the WordPress files for add_filter and auto_update_plugin on the same line. It looks like there are a couple of plugins that are messing with that filter.

Now that I have diagnosed the problem, I can discuss with the owner what to do about it.

Thanks again. I’ll mark this as resolved.

@christiesoda — Please see the ticket for this issue. If you agree with it, “star” the ticket to show your support (you might have to log in first).

These emails really need to be optional.

I have created a ticket for this issue. If you agree with it, please visit the ticket, log in if required, and “star” it.

@edwardsh — Thank you, I missed that I had type twice!

I did as you suggest, and this time it has worked. Yay!

I’ve seen Authenticator before, but I didn’t realise that it automatically added the 2FA into the field. I’ll have another look.

Thanks again

@edwardsh — I installed Theme My Login, and it still had the same problem.

The problem is obviously not in the TFA plugin, but in how Chrome determines the username field.

Yes, I agree.

I looked at your example code. Obviously, I can’t fiddle with the id, name or class, but I added value="". Unfortunately, that still failed to work.

My complete input field now looks like this:
<input type="text" name="two_factor_code" id="simba_two_factor_auth" autocomplete="one-time-code" value="" type="number" pattern="[0-9]{6}" data-lpignore="true">

I guess that we’ll just have to wait until Google fixes Chrome.

@edwardsh — I don’t fully understand your question. This is the forum for the plugin Two Factor Authentication. This isn’t the forum for the Theme My Login plugin.

Are you saying that it works for you when you use that plugin together with this one? If so, I shall give it a try.

If you are correct in that Chrome thinks that the 2FA field is in fact a username, the question becomes, “Why does it think that?” Is it something to do with the ID of the field?

It’ll auto-fill with a username that doesn’t match the required pattern?

Yes, it does! Bizarre.

Presumably then it complains if you try to submit it?

Yes, at least it has the sense to prevent submission.

I have tested those suggestions, using pattern="[0-9]{6}", but it doesn’t make a difference for me. Oh well. Let’s wait for Google to fix Chrome.

Thanks for the recommendation. I’ve tried it, and I still get my username shown as the recommended value for the OTP.

According to what I’ve read — but please be aware that I am not an expert — only the values “off” and “on” are specified for autocomplete. If I’m right, “tfa” would be non-standard.

Thanks, anyway. I’ll just have to live with it until Google fixes Chrome.

Ah, thank you for that. Yes, I’m using Chrome.

I’ve starred the issue. I hope that they do something with it.

@joyously —
Thank you for the advice, Joy. I have raised an enhancement request there.