jmunzo
Forum Replies Created
-
David, you are awesome! It’s working perfectly on my end, and my pages all sign in/reload correctly. Thanks again for your quick response and continued support!
Update –
I played around with ‘tfa.js’ and got it working to my satisfaction on my end. Not sure if it’s everything that needs to be done, but I can at least help out on where to start looking…
From what I can tell, it’s most definitely the ‘#wp-submit’ issue that I previously mentioned.
Basically, I tried to account for the incremental values by setting –
var $submit_button_inc = $('[id^=wp-submit]');And then substituted out the calls to –
$('#wp-submit')and#wp-submitadjusting appropriately of course (can’t just do a find-replace).I’m sure there’s more to it than that, just trying to help out as best I can.
Thanks again!
David, you are awesome! It works great now, no more duplicate fields!
When my site is ready to go live, I am definitely going to pick up the Premium Version of this. Thank you so much!
Follow up –
It turns out I am experiencing this duplicate fields issue without using Page Builder at all. It appears to be exclusive to Theme My Login.
With only the Two Factor Authentication plugin installed and using the default wp-login.php page, everything works correctly. Theme My Login pages provide the duplicate field issue for me.
Very confusing…
Hi David, my reply to you doesn’t seem to be showing up… I apologize if this is in error, or if you wind up getting multiple copies of this…
Thanks so much for the prompt response. I unfortunately am still having this same issue with the two fields appearing using the TML widget and shortcode.
This issue is occurring on two local test environments. I don’t know if any of this information helps out, but –
My first is using MAMP 4.2 on OSX. My settings are –
– PHP 7.0.20 no cache
– Apache
– MySQL 5.6.35My second is using MAMP 3.3.1 on Windows 10. Those settings are –
– PHP 7.1.5 no cache
– Apache
– MySQL 5.6.34In both cases, I basically create a new database and install a fresh installation of WordPress 4.8.1 with the Twenty Seventeen theme. I login and go to the Plugins menu. I delete Akismet and Hello Dolly, so I have a blank slate to work with. Then I click Add New, and in this order I search for, install and activate –
– Page Builder by SiteOrigin 2.5.12
– SiteOrigin Widgets Bundle 1.9.10
– Theme My Login 6.4.9
– Two Factor Authentication 1.2.28After the plugins are activated, I go to Settings -> Permalinks, and switch to Post Name so I don’t have to memorize Page ID Numbers. After that, I go to Pages -> All Pages -> Log In to verify the default content. The default content of the Log In page is the shortcode [theme-my-login].
Now I go through the steps of activating Two Factor Authentication for my account. I logout, and head to the Log In page.
I enter my username and password, and am presented with two “One Time Password (i.e. 2FA) fields, one above the Log In button, and one just below the Log In button.
What is interesting, is if I only supply the code to the field below the Log In button, I am logged in successfully. Whereas if I supply it to the top field only, and leave the bottom field blank, I am told my code was not provided and I have to sign in again.
Moving on, if I provide my One Time Password and log in successfully, I then head back to Pages -> All Pages -> Log In. I then click the Page Builder tab in the Visual Editor, and set up my page in Page Builder as follows –
– Add Row, 2 Columns, 50% 50%
– Add Theme My Login widget in the first columnI update the page and log out.
When I try to login again, I provide my username and password. Then I get the same issue with the two “One Time Password (i.e. 2FA)” fields appearing.
In console, I can clearly see two instances of –
POST XHR http://localhost/test/wp-admin/admin-ajax.php Raw Data "action=simatfa-init-otp&user=test"My feeling is that something on the page is triggering the command to display this field twice… I only wish I knew more about programming to properly help.
My apologies for the wall of text, I understand how difficult it can be tracking down a bug so I’m trying to be as specific as possible. Thanks again for all your help, and for working so hard on this plugin.