Two-factor configuration

Hi @borjamerino, thanks for reaching out! I understand some of your clients cannot skip the 2FA Onboarding after logging in because the “skip” and “continue” links are not working.

Are your clients using Solid Security Pro? If so, the 2FA setup will be required if they enable the Require Two Factor?option in the User Groups settings.

But if they’re using Solid Security Basic, the onboarding process is not enforced. Could you please describe what happens when the skip/continue links are clicked? What happens if they load /wp-admin in the URL instead of skipping the 2FA Onboarding step? I tried replicating the issue, but skipping it works fine (here’s a quick demo). If they see any errors on the browser console and network tabs when they click the skip/continue links, please send them here. Could you also confirm if the issue persists when they deactivate all the other plugins except Solid Security and temporarily switch to a default WordPress theme?

Looking forward to hearing from you!

• Could you please describe what happens when the skip/continue links are clicked?
  • When the customer clicks the jump button doesn’t work, it clicks and doesn’t work. It’s like disabled.
• What happens if they load /wp-admin in the URL instead of skipping the 2FA Onboarding step?
  • I have not tried. But I’m almost sure it would access wp-admin correctly. Because they log in correctly.
• Could you also confirm if the issue persists when they deactivate all the other plugins except Solid Security and temporarily switch to a default WordPress theme?
  • Unfortunately no, all sites are in production. If another of my clients suffers from this again, I will try it.

I have recreated the problem again. I have created a user (in solid basic) and when I go to log in with his username and password, this window pops up:

It is impossible to jump or configure. But you do access the website if you visit /wp-admin/ In addition, a warning appears in the console, I don’t know if it is directly related to it.

On this website, it would be the third similar case that I have come across. Different from the other two websites.

• This reply was modified 1 year, 4 months ago by NIMBADA..
• This reply was modified 1 year, 4 months ago by NIMBADA..

After testing, I got this error in Apache.

[Thu Nov 09 10:26:36.177626 2023] [proxy_fcgi:error] [pid 2758756:tid 139926377051904] [client 170.253.22.15:0] AH01071: Got error 'PHP message: PHP Fatal error:  Uncaught ArgumentCountError: 6 arguments are required, 5 given in /home/XXXXCENSOREDXXXXX/www/wp-content/plugins/better-wp-security/core/modules/two-factor/includes/template.php:94\nStack trace:\n#0 /home/XXXXCENSOREDXXXXX/www/wp-content/plugins/better-wp-security/core/modules/two-factor/includes/template.php(94): printf('En dispositivos...', '</a>', '<a href="https:...', '<a href="https:...', '<a href="https:...')\n#1 /home/XXXXCENSOREDXXXXX/www/wp-content/plugins/better-wp-security/core/modules/two-factor/class-itsec-two-factor-on-board.php(299): require_once('/home/XXXXCENSOREDXXXXX/w...')\n#2 /home/XXXXCENSOREDXXXXX/www/wp-content/plugins/better-wp-security/core/lib/class-itsec-lib-login-interstitial.php(672): ITSEC_Two_Factor_On_Board->render(Object(ITSEC_Login_Interstitial_Session), Array)\n#3 /home/XXXXCENSOREDXXXXX/www/wp-content/plugins/better-wp-security/core/lib/class-itsec-lib-login-interstitial.php(418): ITSEC_Lib_Login_Interstitial->login_html(Object(ITSEC_Login_Interstitial_Session))\n#4 /home/XXXXCENSOREDXXXXX/www/wp-content/plugins/...', referer: https://XXXXCENSOREDXXXXX/wp-login.php?XXXXCENSOREDXXXXX

Hi @borjamerino,

It turns out that the PHP fatal error is caused by an incorrect (Spanish) translation string on translate.www.ads-software.com.

Below the string to translate:

For iOS devices, the %2$s Authy%1$s, %3$s Google Authenticator%1$s, or %4$s FreeOTP Authenticator%1$s apps are the most popular token generators.

Currently (incorrectly) translated on translate.www.ads-software.com as:

En dispositivos iOS, las aplicaciones %2$s Authy%1$s, %3$s Google Authenticator%1$s, %4$s FreeOTP Authenticator%1$s o %5$s Toopher%1$s son las más populares para generar tokens.

And it should be (correctly) translated as below:

En dispositivos iOS, las aplicaciones %2$s Authy%1$s, %3$s Google Authenticator%1$s o %4$s FreeOTP Authenticator%1$s son las más populares para generar tokens.

Note the Toopher app was removed.

So to fix this, the Spanish (Spanish) string translation needs to be corrected on translate.www.ads-software.com. Once that is done you’ll need to update the SolSec plugin translation in WordPress.

Oh almost forgot, there are several different Spanish translations, so it could be you are using eg Spanish (Colombia) etc. I have not checked all Spanish languages, but I can confirm this is an issue with the Spanish (Spanish) SolSec plugin translation.

I have same problem above seems like a whole load of problems I dont want to deal with suggestions of alternative two factor?

Hi @borjamerino, thank you for providing additional details about the issue! Could you please try out the suggestion provided by @nlpro and see if that helped with the 2FA step issue?

Hi @gnfbto, to follow the forum guidelines, could you please open a new support topic? We’ll be sure to respond there. Thank you!

Hi @shanedelierrr.

Do I have to apply a translation to something that I have not modified? I don’t know what I should modify. I have no idea what the problem is.

Hi @borjamerino,

The translation process is community driven, which means you can contribute to the translation of WordPress, plugins and themes.

Visit How to translate for an explanation of the full translation process.

Alternatively contact Fernando Tellado for help.

Hi @borjamerino, as mentioned by @nlpro, translations for all WordPress-related are community-driven. You may contact the above person for help or ask for guidance via the Slack #polyglots channel mentioned in the Before you get started section. If you haven’t joined Slack yet, you can register for free using the instructions?here.

Please let us know how it goes!

Hi there,

I hope the information provided above helped resolve the issue. Tracking notifications on this forum can become tricky over time, and since we haven’t received a response, I’ll mark this post resolved.

If you still require further assistance, feel free to open a new support topic, and we’d be happy to assist.

Thank you!

Hi everyone,

I have encountered a similar problem, and have changed the translation to match the English version and avoid this error. As soon as a translation editor approves the suggested change, this should be resolved.