Thread Starter
wp_edu
(@alemao2k6)
I have contacted Buddyboss support, which has shown no will to contribute in this fix. They say it’s the plugin developer’s responsibility to find the fix, even though I’m positive that this behavior is coming from Buddyboss’s login implementation which is conflicting with the plugin.
I guess now it’s a matter of communication between melapress and buddyboss.
Hello @alemao2k6,
Thank you for all the details you’ve shared so far — they’re very helpful. We’ve also received your email, and we’ll continue troubleshooting there so we can exchange the necessary information safely and look into this more thoroughly.
We truly appreciate your patience and cooperation while we get this resolved.
Just wanted to add my experience here as well in case it’s helpful to others. Using WP-2FA 3.0.
Updated to Buddy Boss Platform 2.14.4 from version 2.9.20 seemed to be the problem (even if you deactivate buddy boss platform, the problem persists). My Buddyboss Theme was not updated. The grace period modal, code required modal, and all other modals after sign in would not appear (either from my custom URL site login or wp-login). I rolled back Buddyboss to 2.9.20 and it’s returned to showing the appropriate modals.
Thread Starter
wp_edu
(@alemao2k6)
Thank you for the insight. We rely heavily on Buddyboss and will prefer to keep it updated. Unfortunately we might have to try another 2fa solution if this can’t be fixed soon.
Hi everyone,
Just jumping in with some clarification.
We’ve investigated this behavior and can confirm that it is not caused by any recent changes in WP 2FA—nothing in our latest releases modifies the login flow or BuddyBoss integration. However, the latest update of Uncanny Toolkit 3.8.0 introduced a new change in their login system:
“Improved Melapress WP 2FA integration using the REST API #423”
Because this adjustment happens on their side, it affects the flow before WP 2FA gets control, which unfortunately means we have very limited influence over this part of the process.
For reference, our REST API documentation is here if needed.
At this point, the best next step is to contact the Uncanny Toolkit team directly as they might have full insight into what changed internally and how to adjust it. We’re happy to answer any follow-up questions from their side if they need clarification about WP 2FA’s endpoints or expected behavior.
Thanks, and I hope this helps point things in the right direction.
Thread Starter
wp_edu
(@alemao2k6)
I have rolled back to 3.7.0.4 and it works. Amazing how you found that out. I’ll wait and monitore each new update of Uncanny Toolkit above 3.8.0.2, hoping that they will fix this. Thanks
Thank you for your understanding @alemao2k6 @engineeringdev ! The Uncanny team is already aware of this issue and they should provide a fix soon. It’s best indeed to keep an eye on their upcoming updates and changelog.
