• Resolved cravaus

    (@cravaus)


    I have tried out the 2FA feature on my site and it works for me but with the following quirks:

    1. All the buttons on my site need at least two taps to work.
    2. At log in, the 2FA code field will not process by pushing the button at all. On the PC I have to hit the return key (twice) and on the Android phone I have to hit Go on the key board twice.
    3. There is a long delay to log in. And no spinner or progress bar to indicate that anything is happening. I have learned that I just need to wait about 20 seconds.

    All the above are true site wide when 2FA is activated even for user roles that are not selected for 2FA. So I have deactivated it. Any idea why these things could be happening with the option activated.

Viewing 3 replies - 1 through 3 (of 3 total)
  • Plugin Support wfpeter

    (@wfpeter)

    Hi @cravaus, thanks for getting in touch!

    This seems quite unusual behavior for 2FA as it seems to be theme or script-related to affect button presses, and I’ve not seen this reported before by Wordfence customers.

    On your login page (or other pages affected) when 2FA is enabled, do you see any errors in the browser console? You can screenshot any results using a service like Snipboard.

    Thanks,

    Peter.

    Thread Starter cravaus

    (@cravaus)

    Hello Peter,

    I have updated to PHP7.4 and so things move a little faster. I have tried 2FA again and now I am only noticing that on my login page (Theme-My-Login) I have to hit my log in button twice to make it work. And in the console, I do not see any significant errors:

    
    This page uses the non standard property “zoom”. Consider using calc() in the relevant property values, or using “transform” along with “transform-origin: 0 0”. login
    JQMIGRATE: Migrate is installed, version 3.3.2 jquery-migrate.min.js:2:709
    Some cookies are misusing the recommended “SameSite“ attribute 3
    init popups ✔ pum-site-scripts.js:7:12349
    plugin scripts activated scripts.js:6:11
    Source map error: Error: request failed with status 404
    Resource URL: https://www.mysite.com/wordpress/wp-content/themes/shapely/assets/css/bootstrap.min.css?ver=5.8.2
    Source Map URL: bootstrap.min.css.map
    
    Cookie “enforce_policy” has been rejected because it is already expired.
    

    On the second hit of the Login button I get this:

    
    Cookie “_fbp” will be soon rejected because it has the “SameSite” attribute set to “None” or an invalid value, without the “secure” attribute. To know more about the “SameSite“ attribute, read https://developer.mozilla.org/docs/Web/HTTP/Headers/Set-Cookie/SameSite fbevents.js:24:77394
    This page uses the non standard property “zoom”. Consider using calc() in the relevant property values, or using “transform” along with “transform-origin: 0 0”. pm
    JQMIGRATE: Migrate is installed, version 3.3.2 jquery-migrate.min.js:2:709
    init popups ✔ pum-site-scripts.js:7:12349
    plugin scripts activated scripts.js:6:11
    Some cookies are misusing the recommended “SameSite“ attribute 2
    Source map error: Error: request failed with status 404
    Resource URL: https://www.mysite.com/wordpress/wp-content/themes/shapely/assets/css/bootstrap.min.css?ver=5.8.2
    Source Map URL: bootstrap.min.css.map
    
    Cookie “enforce_policy” has been rejected because it is already expired. log
    
    • This reply was modified 1 year ago by cravaus.
    • This reply was modified 1 year ago by cravaus.
    • This reply was modified 1 year ago by cravaus.
    Plugin Support wfpeter

    (@wfpeter)

    Hi @cravaus,

    This is a bit of a legacy solution, but feel it might work in your case here now I’ve seen those issues.

    WordPress itself used to use jquery-migrate, but it was deprecated in the WordPress 5.5 update last year. Wordfence was updated accordingly to prevent compatibility issues. There is a chance that if you’re seeing things like this, one of your plugins or theme still hasn’t been updated to comply so the Enable jQuery Migrate Helper could still be of assistance.

    There may be a plugin, or part of your theme that is causing the cookie and jQuery issues so for a more permanent solution it might be worth replacing any plugins reported as “abandoned” by Wordfence. If there are none, you could check if there are any recent updates to your theme or disable/enable plugins until these issues disappear. You’ll then know the cause and be able to check in with the appropriate support team at their end.

    Thanks,

    Peter.

Viewing 3 replies - 1 through 3 (of 3 total)
  • The topic ‘2FA Issues’ is closed to new replies.