• Resolved Vanessa Roseline Siegl

    (@cpulchra)


    We are using the latest version of this plugin an since we updated the initial popup keeps looping back to the setting where you can choose between old and new interface… This started rihjt after the update and redered the backend unsusable. We tried the steps listed in an older post, but it didn’t get rid of the problem.

    The site is using the Kalium Theme: Version: 3.35

    here’s a list of our active plugins

    Advanced Custom Fields PRO 6.8.10
    Better Search Replace 1.4.11
    Borlabs Cookie 3.4.4
    Disable REST API 1.8
    Disable XML-RPC 1.0.1
    Google Apps Login 3.5.2
    Limit Login Attempts Reloaded 3.3.10
    Simple History 5.34.0
    Slider Revolution 6.7.40
    The SEO Framework 5.1.4
    WP Mail SMTP 4.9.0
    WPBakery Page Builder 9.0.1
    WPS Hide Login 1.9.19

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

    (@lucianwpwhite)

    Hello again @cpulchra

    Thanks for sending all those details. The plugin list and theme information are very helpful.

    Could you please try the following workaround to manually switch WP 2FA to the new interface?

    The setting is stored in the WordPress database in the WP_OPTIONS table, in the wp_2fa_settings entry. The value we’re looking for is:

    a:1:{s:17:"use_new_interface";b:1;}

    The b:1 means that the new interface is enabled. So, if you have access to the database through phpMyAdmin or a similar tool, please check the wp_2fa_settings , entry and make sure the use_new_interface value is set to 1.

    After making that change, please clear any WordPress/server/cache layers and then log back into the admin area to see whether the interface loads normally.

    This type of looping is most often related to caching, particularly after an update, so I’d also like to narrow that down if the issue continues. Could you let us know:

    • Which version of WP 2FA you updated from before installing the latest version?
    • Whether you have any page/object/server caching enabled that might be affecting the WordPress admin.
    • If the loop still happens after the database change, whether you can see any JavaScript errors in the browser console when it occurs. A screenshot or copied error message would be very useful.

    The Kalium theme and the other plugins you listed are also useful context, and we’ll keep those in mind while investigating.

    Hopefully the manual database adjustment gets you out of the loop straight away. If it doesn’t, the version you upgraded from and any browser-console errors should give us a much better lead on what is happening.

    Thanks again for working through this with us.

    Thread Starter Vanessa Roseline Siegl

    (@cpulchra)

    Thank you so much!! That fixed the problem. The old version was 3.1.1.2..

    No Caching… Apache with nginx proxy and php 8.2.33

    Plugin Support Lucian Padureanu

    (@lucianwpwhite)

    Hi Vanessa @cpulchra

    Thank you for confirming that for me! I’m really happy to hear that the workaround got things back to normal.

    I’ve made a note of what happened, and we’ll investigate this further on our side so we can improve the experience. There should really only have been a one-time prompt when we introduced the new interface in 4.0, so I’m confident we can make sure this behaves much better going forward.

    Also, if you don’t mind sparing a minute, we’d really appreciate it if you could share your experience with WP 2FA and our support in a review on the WordPress.org forums. It’s genuinely helpful to us and helps us understand what we’re doing well and where we can improve:

    https://wordpress.org/support/plugin/wp-2fa/reviews/#new-post

    Thanks again for your patience while we worked through this, Vanessa!

    Best regards,
    Lucian

Viewing 3 replies - 1 through 3 (of 3 total)

You must be logged in to reply to this topic.