misatotremor

Hello @robert681

Thank you very much for the update! I can confirm this fixes the issue for us.

This warning is triggered upon login. It happens for users with 2FA enabled and those who don’t have it enabled.

On our sites the options wp_2fa_policy value is a:0:{} therefor the current code tries to access a non-existing array key. I could fix this in my install by changing https://plugins.trac.www.ads-software.com/browser/wp-2fa/trunk/includes/classes/Admin/User.php#L361 and #L362 from
$settings = SettingsUtils::get_option( WP_2FA_POLICY_SETTINGS_NAME );
if ( ! is_array( $settings ) || 'do-not-enforce' === $settings['enforcement-policy'] ) {
to
if ( 'do-not-enforce' === WP2FA::get_wp2fa_setting( 'enforcement-policy' ) ) {.

• This reply was modified 3 years, 3 months ago by misatotremor.

Whoa nice. Thanks!

Maybe it’s related: I noticed part of the code is run through wpcf7_autop / wpautop, making the code invalid HTML, e.g. the last step button code looks like this:
<p><button type="button" class="cf7mls_back action-button" name="cf7mls_back" id="cf7mls-back-btn-cf7mls_step-3">BACK</button></div></fieldset></p>. Thus </div> and </fieldset> don’t match their opening tags anymore.
It happens just after the cf7mls_multistep_shortcode_callback function returns.

I don’t have the 2.6.2 version at hand, so I can’t check if this issue is just a 2.6.3 one.

Hello,

Please also note that WP2FA also enqueues it’s version of select2 JS on any admin page, which A) is pinned to an outdated (and buggy) version of select2 and B) is not the full version of select2, which causes issues on other plugins pages that use features of the full version, when the wp-2fa script is enqueued first (i.e. Advanced Custom fields).