2FAS

Hi,
This cannot be fixed as long as WordPress’s core is not dependent on dependencies (installed by php Composer dependency manager).
In short, many plugins use external libraries which come in different versions, e.g. 2FAS Prime and WP RSS use PHP-DI libraries so one of these plugins will not work. We decided that we will not struggle with it anymore and only display an error message (previously, as you mentioned, the user got an error and the whole website did not work properly).
Besides, you can meet many other plugins that also won’t work because they also use this library.
In summary, this cannot be solved at the plugin level.

Hi,

This flag only disables conflict checking with other plugins, it does not disable your server’s requirements checking.
In the latest version 3.3 we will raise the minimum PHP version that the plugin can run on to 7.2 (because there are problems on the latest version 8.0), so this is a probable reason. The error message states exactly which requirement is not met.

Hello again, we released version 3.3 witch includes updates for this issue, so you shouldn’t get this error.

Hi,

We will upgrade this package in next release in our plugin (probably in the next week).

Hi,

Previously, we had this functionality because our mobile application did not have the backup and synchronization of codes between devices.
Now it is possible, so we removed the possibility of re-scanning the code, which should only be read once. It is still possible to transfer the code to other devices if the mobile application has synchronization (such as in the 2FAS Authenticator App) or if it does not have such a function by manually entering the Secret Key (which can be displayed during configuration and should also be in the mobile application).

Hi,

Thank you for your information.
You can put this code on the end of file before:
/* That's all, stop editing! Happy publishing. */ WordPress comment

Hi,

We add script which checks potential conflicts with other plugins (when other plugin use the same 3rd party library as 2FAS Prime but in another version) – then you get Fatal Error on your site.
You can turn off conflict checking if the plugin worked properly before.
To do this, change constants.php file
define( ‘TWOFAS_LIGHT_CHECK_CONFLICTED_PLUGINS’, true ); and set to define( ‘TWOFAS_LIGHT_CHECK_CONFLICTED_PLUGINS’, false );
If the plugin works correctly, it means there is no conflict because the plugin uses the same libraries and you can copy this piece of code to your wp-config.php file so that the next time you update it does not overwrite your settings.

Hi,

Thank you for your information.
We add script which checks potential conflicts with other plugins (when other plugin use the same 3rd party library as 2FAS Light but in another version) – then you get Fatal Error on your site.
We fix it in version 3.1.1. Now you should get the correct plugin name with which there may be a problem.
You can also turn off conflict checking if the plugin worked properly before.
To do this, change constants.php file
define( 'TWOFAS_LIGHT_CHECK_CONFLICTED_PLUGINS', true ); and set to define( 'TWOFAS_LIGHT_CHECK_CONFLICTED_PLUGINS', false );
If the plugin works correctly, it means there is no conflict because the plugin uses the same libraries and you can copy this piece of code to your wp-config.php file so that the next time you update it does not overwrite your settings.

Hi,

We fixed the path in the script that checks for conflicts with plugins in version 3.1.1 so you can update it. Now you should get the correct plugin name with which there may be a problem.
You can also turn off conflict checking if the plugin worked properly before.
To do this, change constants.php file
define( 'TWOFAS_LIGHT_CHECK_CONFLICTED_PLUGINS', true ); and set to define( 'TWOFAS_LIGHT_CHECK_CONFLICTED_PLUGINS', false );
If the plugin works correctly, it means there is no conflict because the plugin uses the same libraries and you can copy this piece of code to your wp-config.php file so that the next time you update it does not overwrite your settings.

Hi,

We have implemented version 3.1
Please check that your problem has been fixed and plugin working properly.

Hi,

We know about this interference, WP Cerber introduced change in their login process in one of last updates and that’s causes this problem.
We have an update prepared that introduces many changes but should also fix this issue. We plan to implement it this or next week.

Hi,

Can you tell us name of this theme? Because we want to check it ourselves.
Is version 3.0.2 working properly for you?

Hi,
It looks like one of your installed plugin using php-di library which we are using but in older version.
These versions are in conflict with each other and cannot be used simultaneously and unfortunately there’s no way around it.

Hi,

No, at this moment we supports only default wp-login.php page

Hi,

We released 3.0.2 which should fix this issue but we cannot reproduce this bug.
Do you have using any theme in your WordPress admin dashboard?