Title: Bug-report: Activation button in 2FA shortcode
Last modified: July 14, 2023

---

# Bug-report: Activation button in 2FA shortcode

 *  Resolved [karlemilnikka](https://wordpress.org/support/users/karlemilnikka/)
 * (@karlemilnikka)
 * [2 years, 11 months ago](https://wordpress.org/support/topic/bug-report-activation-button-in-2fa-shortcode/)
 * If you enter the wrong OTP code when trying the enable 2FA through the shortcode
   form, you must reload the page before being able to enter the correct OTP code.
   Nothing happens after clicking on the Activate button after the error message
   has been dismissed unless you reload the page.
    - WordPress: 6.2.2
    - Wordfence: 7.10.1
    - Browser: Firefox 115.0.2 on macOS

Viewing 3 replies - 1 through 3 (of 3 total)

 *  Plugin Support [wfpeter](https://wordpress.org/support/users/wfpeter/)
 * (@wfpeter)
 * [2 years, 11 months ago](https://wordpress.org/support/topic/bug-report-activation-button-in-2fa-shortcode/#post-16895105)
 * Hi [@karlemilnikka](https://wordpress.org/support/users/karlemilnikka/), thanks
   for your detailed report.
 * Would it also be possible to check for any red errors in the [browser console](https://www.wordfence.com/help/advanced/troubleshooting/#how-to-inspect-the-browser-developer-tools-console)
   that appear either before or after the first attempted (incorrect) submission?
   Could you paste anything you do see to me here? Were you able to test the outcome
   in any other browsers?
 * It might just help us narrow-down whether there are any elements on the page (
   such as the button) that can’t be identified with JavaScript due to a conflict
   or other problem during the first submission.
 * Thanks,
   Peter.
 *  Plugin Support [wfpeter](https://wordpress.org/support/users/wfpeter/)
 * (@wfpeter)
 * [2 years, 11 months ago](https://wordpress.org/support/topic/bug-report-activation-button-in-2fa-shortcode/#post-16895725)
 * Hi again [@karlemilnikka](https://wordpress.org/support/users/karlemilnikka/),
 * I’ve just seen the report sent to our inbox, so it won’t be necessary to send
   browser console information as I now have further context from our QA team.
 * When an error occurs there is a flag not being reset, which blocks the user from
   trying again unless they refresh. We have scheduled this in for a future plugin
   update. Please keep an eye on our [changelog](https://wordpress.org/plugins/wordfence/#developers)
   for updates regarding this in future releases, as I’m unable to give precise 
   dates here on the forums.
 * Thanks again,
   Peter.
 *  Thread Starter [karlemilnikka](https://wordpress.org/support/users/karlemilnikka/)
 * (@karlemilnikka)
 * [2 years, 7 months ago](https://wordpress.org/support/topic/bug-report-activation-button-in-2fa-shortcode/#post-17144766)
 * This bug is resolved in Wordfence version 7.10.5, released 2023-10-23, three 
   months after reporting. Thanks for fixing!
 * Marked as resolved.

Viewing 3 replies - 1 through 3 (of 3 total)

The topic ‘Bug-report: Activation button in 2FA shortcode’ is closed to new replies.

 * ![](https://ps.w.org/wordfence/assets/icon.svg?rev=2070865)
 * [Wordfence Security - Firewall, Malware Scan, and Login Security](https://wordpress.org/plugins/wordfence/)
 * [Frequently Asked Questions](https://wordpress.org/plugins/wordfence/#faq)
 * [Support Threads](https://wordpress.org/support/plugin/wordfence/)
 * [Active Topics](https://wordpress.org/support/plugin/wordfence/active/)
 * [Unresolved Topics](https://wordpress.org/support/plugin/wordfence/unresolved/)
 * [Reviews](https://wordpress.org/support/plugin/wordfence/reviews/)

## Tags

 * [2fa](https://wordpress.org/support/topic-tag/2fa/)
 * [mfa](https://wordpress.org/support/topic-tag/mfa/)
 * [shortcode](https://wordpress.org/support/topic-tag/shortcode/)

 * 3 replies
 * 2 participants
 * Last reply from: [karlemilnikka](https://wordpress.org/support/users/karlemilnikka/)
 * Last activity: [2 years, 7 months ago](https://wordpress.org/support/topic/bug-report-activation-button-in-2fa-shortcode/#post-17144766)
 * Status: resolved