Preston

They fixed it! I would love to remove this thread, but I think it is good that it remains because it shows a company responding professionally (albeit after some deep breathing on my part).

I am still hoping to write a redeeming post speaking of their stepping up and helping me out, and renewing faith in the franchise. …hope springs eternal!

…more news as it (hopefully) happens!

I think its time we talk to WordPress about having them pull this plugin. The developers seem not to care AT ALL about their customers. Pathetic.

Hi Greg,

I was wondering if they ever got back to you on this matter. I might be in the same boat, not sure yet.

Best,
Preston

Very Good! Thank you, Sir!

Quick Update (also posted to Members’ Support page)

I revisited Site Ground’s recommendation to deactivate Members plugin, clear cache and try again (which DID work).

But this time, I just cleared the cookies for the site (using edit this cookie) and left the Members plugin activated and it worked! I did get the 2FA challenge.

So maybe its NOT a conflict with the Members plugin?

Thanks,
Preston

• This reply was modified 2 years, 6 months ago by Preston.

Quick Update

I was able to reproduce the error, but I revisited Site Ground’s recommendation to deactivate Members plugin, clear cache and try again (which DID work).

But this time, I cleared the cookies for the site (using edit this cookie) and left the Members plugin activated and it worked! I did get the 2FA challenge.

…go figure!

• This reply was modified 2 years, 6 months ago by Preston. Reason: typo in "edit this cookie" name

Interesting. I will pass it on to SiteGround. Thanks for your help.

…more news as it happens!

Preston

Greetings,

In reading the details for the SG Security Plugin, it appears they only enable 2FA for the “Admin” and “Editor” Roles. However they do provide a filter hook called sg_security_2fa_roles which one can use to add additional roles.

Also, no, I did NOT modify the default Editor’s role’s caps.

Preston

Update: I have notified the support staff for the Members plugin of the situation.

…more news as it happens!

Preston

Greetings @georgiganchev

I have inspected the issue and I found that this behavior is caused by the plugin you are using called “members”….You may deactivate the plugin, flush your browser cache and repeat the same process again. The Editor user will be prompted for 2FA generation.

I have done this and can confirm that taking the above actions does show that it works as described. I will take this up with the developers of the Members plugin and report back there response (for anyone else that may run into this issue in the future).

Thanks again!

…more news as it happens!

Preston

Well, that’s not happening. As you can see from this video, I can login as an Editor and no notice or prompt appears. What am I missing?

Be Advised:

1.) The site is hosted on SiteGround.
2.) I tested this from two different computers (Linux and Windows).

Same results as video.

• This reply was modified 2 years, 7 months ago by Preston. Reason: Additional Details added

For further clarification, I plan to enable other user roles to require 2FA. Not just the main site admin.

Sounds good!

Thanks for a great plugin.

Preston

• This reply was modified 2 years, 7 months ago by Preston.

Update: After the initial lack of support (and after I posted a message here) they absolutely got busy trying to resolve the issues we had. So I plan to update the post to suggest that support did get it together.

So in trying to fix our issues they suggested it was our server (it wasn’t, was happening on 3 different servers: Digital Ocean, SiteGround and Local), they suggested it might be the fact that we were using an “old MyISAM DB Engine” (we weren’t, we were using InnoDB), they said it might be our cache (we disabled all caching everywhere, still broke).

Eventually, they wound up modifying their plugin code (and rolled out an update) and suggested that that would fix the problem. But unfortunately by that time (several weeks) and after multiple attempts to solve my problem, the client lost all confidence in the plugin and made us uninstall it.

So did they (eventually) come around, support-wise? Yes. Absolutely. Did it help us? Not really. Not in this case.

• This reply was modified 3 years, 9 months ago by Preston.