Critical error after trying to update to latest version (1.14.8)

  • Resolved debbieweeks2

    (@debbieweeks2)


    2 years, 1 month ago

    Hi,

    I just tried to update this plugin today, and I got a critical error message on both my live and staging sites.

    I updated the plugin on my live site first and got the critical error message, so I restored my website to the previous back up, and all seemed fine. Then I tried updating the plugin on my staging site and got the critical error message again.

    When I went back into my live site, the critical error returned even though it is the previous version (1.14.7). It wasn’t showing this error before today.

    In my staging site, I tried deactivating, deleting and reinstalling the plugin and the error has not returned so far, but if I leave it deactivated it is still asking me for my OTP code when I try to log into WordPress. (Why?)

    Below are the error details in the emails I received from WordPress. Please note that line numbers and error details are slightly different.

    WordPress version 6.0.2
    Active theme: My Listing (version 2.9.4) Current plugin: Two Factor Authentication (version 1.14.7) PHP version 8.0.22

    1st time (after updating in my live site)

    Error Details
    =============
    An error of type E_COMPILE_ERROR was caused in line 9 of the file /var/www/wp-content/plugins/two-factor-authentication/simba-tfa/includes/login-form-integrations.php. Error message: Cannot declare class Simba_TFA_Login_Form_Integrations, because the name is already in use

    2nd time (after updating in staging)

    Error Details
    =============
    An error of type E_COMPILE_ERROR was caused in line 8 of the file /var/www/wp-content/plugins/two-factor-authentication/simba-tfa/providers/totp-hotp/loader.php. Error message: Cannot declare class Simba_TFA_Provider_TOTP, because the name is already in use

    Thanks in advance,
    Debbie

    • This topic was modified 2 years, 1 month ago by debbieweeks2.
    • This topic was modified 2 years, 1 month ago by debbieweeks2.
Viewing 4 replies - 1 through 4 (of 4 total)

  • Same Issue: had to enter recovery mode to get the site back up

    WordPress version 6.0.2
    Active theme: Enfold (version 5.1.2)
    Current plugin: Two Factor Authentication (version 1.14.8) PHP version 7.4.29

    Error Details
    =============
    An error of type E_COMPILE_ERROR was caused in line 9 of the file …/wp-content/plugins/two-factor-authentication/simba-tfa/includes/login-form-integrations.php. Error message: Cannot declare class Simba_TFA_Login_Form_Integrations, because the name is already in use

    Plugin Author David Anderson

    (@davidanderson)

    Hi,

    This is related to having both this plugin and All-In-One-Security activated at the same time. Recent releases of All-In-One-Security include a new TFA module which is a version of this plugin. So actually if you have both AIOS and this plugin (free version) activated, you can just de-activate this plugin, and use the bundled version in AIOS.

    Of course, the fatal error isn’t meant to happen – apologies for it. If you update this plugin to today’s release, it should be gone.

    David

    Thread Starter debbieweeks2

    (@debbieweeks2)

    Thank you David for your very speedy reply and explanation.

    I have checked the 2FA settings in AIOS and it’s basically exactly the same as the 2FA plugin, so I have left it enabled and removed 2FA plugin. Bonus now I have one less plugin.

    Seems to have now been resolved. Thanks again for your help.

    Thanks David. That’s sorted it for me too.

Viewing 4 replies - 1 through 4 (of 4 total)
  • The topic ‘Critical error after trying to update to latest version (1.14.8)’ is closed to new replies.