jahrat

Hello Tim,
I tried what you suggested and it did not change the User. However, I found that adding an administrator for a sub-site as a user to the main site (added as an existing user – contributor – and skipped confirmation email) changes the 2FA status from “Not Allowed” to inactive and I can now access settings for them. The original user from the first sub-site is still not added to the main site, but their 2FA is still active. No other user is capable of using 2FA.

• This reply was modified 4 years, 8 months ago by jahrat.

Hello Tim,
Email sent as requested.
Jah Rat

Thanks. I will keep an eye there.

Hello Gerroald,
I tried sending you some screenshots privately but you probably did not get them. As the Super Admin my screen shows the Wordfence Login Security on the user’s profile as disabled. The user does not see a field for Wordfence Login Security.
I have enabled 2FA for all users on the site.

All is good now. Seems there was some configuration errors.

Thanks for all your help. I have it working now and signed in. Everything seem to work. New site created and public on the front end. The new problem is that although I can see the site front end, I cannot log into the back end. I used Redirect-Checker.org and found it is stuck in a 302 loop.
Any suggestions to fix this one?
Thanks.

Hello Mike,
The adjustments worked fine. However, instead of using
<?php the_title(); ?>
I used
<?php echo basename( get_wpfc_sermon_meta( ‘sermon_notes’ ) ); ?> and
<?php echo basename( get_wpfc_sermon_meta( ‘sermon_bulletin’ ) ); ?>
Thanks for your help.

That worked perfectly. Wish AAM had mentioned in their documentation there would be a conflict.
Thanks.