• Resolved rgfine

    (@rgfine)


    Since 8.0 it’s not possible for me to access the settings page of ithemes security. It ends with an fatal error:

    “plugins/better-wp-security/core/modules/two-factor/providers/class.two-factor-provider.php verursacht. Error: Cannot declare class Two_Factor_Provider, because the name is already in use”

    It seems that there exist some problems if you have installed other 2FA plugins. Could you please correct this?

Viewing 5 replies - 16 through 20 (of 20 total)
  • Ah, ok. That last piece of info will certainly help iThemes fix the issue.

    Originally the error occurred (for the topic creator) when attempting to access the Security > Settings page (free plugin).

    But now the same error happens for you when navigating to the Security > Dashboard page (pro 7.0.3 plugin). The Settings page seems to be fine.

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

    Hi @laboiteare,

    Just out of curiosity, why not simply switch from using the Two Factor plugin to using the iTSec (pro) plugin 2fa ?

    Does the Two-Factor plugin offer feature(s) that is (are) missing in the iTSec (pro) plugin 2fa ?

    Hi @nlpro, very good question.

    1) I think the Two Factor is developed as close as possible to the native functioning of wordpress and very light.

    2) It offers Yubikey/Yubiko authentification while ITSec doesn’t

    ??

    @laboiteare, @timothyblynjacobs

    Ok, I see.

    Have you received any response from iThemes ?

    If you do, please share it with the community ??

    Oh, one last thing. I’ve setup a test environment which allowed me to reproduce your issue. Also it’s not just the Dashboard page that has a conflict…

    As stated in a previous post the iTSec PR0 plugin instantiates the ITSEC_Two_Factor_Helper class in several other plugin features. So this is not going to be an easy fix, which means it will probably take some time…

    Perhaps the easiest thing to do for iThemes is to sync the iTSec plugin 2fa feature set with the Two Factor plugin. This way the need to run both plugins concurrently may be eliminated.

    • This reply was modified 3 years, 7 months ago by nlpro.
    Plugin Author Timothy Jacobs

    (@timothyblynjacobs)

    Yep, we’re working on a fix, but as @nlpro mentioned, it is a bit tricky.

    The reason for the conflict is that both plugins were intentionally developed with the same API so that when the Two-Factor Feature Plugin is eventually merged into Core, there could be a seamless transition process. However, the plugins were never meant to run side-by-side and in the intervening years, the code bases have diverged a bit.

Viewing 5 replies - 16 through 20 (of 20 total)
  • The topic ‘Fatal error on Settings Page with other 2FA plugin installed’ is closed to new replies.