knittingtheweb

Thank you for the update. I’m not comfortable downgrading to a previous version since, according to the changelog, the last two versions included fixes for security vulnerabilities. I will install Hustle updates as they become available and hope that the CTA conversion tracking bug is fixed soon.

Sorry for the delay. Here is the link to the pop-up export.

You’re correct, I had re-enabled Wordfence pending additional help. ??

Thank you for the detailed instructions for whitelisting my IP address in Wordfence Central. That did the trick; I was able to log in, disable and then re-enable 2FA, and save my new recovery codes.

Brilliant! Thank you so much, Margaret. Wordfence is such a great plugin and now I know their support is top-notch, too!

I should have also mentioned that none of my recovery codes are working.

Thank you for your reply, Margaret. I do not have Wordfence Login Security installed.

I tried again:

1. I renamed the Wordfence folder to wordfence.bak via SFTP.
2. I opened the login form in a new incognito Chrome window.
3. I entered my admin username and password.
4. I again received the “CODE REQUIRED: Please provide your 2FA code when prompted” message.

Any other suggestions? I’ve worked through this new phone/Wordfence 2FA issue on 10 websites hosted by WP Engine, and in every case renaming the folder allowed me to log in and reset 2FA. The fact that it’s not working on this website is concerning. It’s on shared hosting by Namecheap/EasyWP, if that information is useful.

Really hoping there’s a patch soon! This is the only syntax highlighter plugin I’ve found that works with bbPress forums. It’s very important to our website and I’d hate to have to deactivate it.

• This reply was modified 1 year, 1 month ago by knittingtheweb.

Thanks, @tnchuntic. In v2.2.5, I’m getting a different error message in some Visual Link Preview boxes: “Error loading block: The response is not a valid JSON response.” Again, this does not affect the VLP block display on the front end, only in the editor. If I toggle the VLP block in the editor to “Edit as HTML” and then back to “Edit visually” it temporarily displays properly but shows errors randomly pop up again if I save changes and refresh the editor.

I installed the Health Check plugin to check for incompatibilities but it was a little more difficult to use in the editor than on a front end display. I suspect for me it may be a conflict with Kadence Blocks – Gutenberg Blocks for Page Builder Features because if I drag a VLP block that is throwing an error out of the Kadence accordion block, the error message disappears.

I am also experiencing this issue. The visual link previews look fine on the front end of the website. But when I open the page in the block editor, some of the previews are fine and some of them say “This block has encountered an error and cannot be previewed.”

For example, on that page, all of the previews under Designing, Building, and Maintaining Outdoor Learning Spaces > Articles and Posts show the error message. But under Accessibility, Equity, and Inclusion > Articles and Posts, the preview block shows properly with no error message.

I’ve temporarily turned this feature off (Settings > Anti-Spam by CleanTalk > Advanced Settings > Forms to Protect > Test default WordPress search form for spam) until we hear from support. I don’t want my site visitors to have a frustrating experience searching my site.

I am also seeing legitimate search requests blocked on my wikiwatershed.org and leafpacknetwork.org websites.

I found eight “notices” in the server log for the registration event in question. Nothing jumps out at me as a network issue. Is there a way to send that information to you privately so you can review?

Thanks for the quick reply! The problem is sporadic and most registrations are being screened, so I’m not surprised your test didn’t show a protection issue. I’ll try keeping a log of missed registrations to see if I can see any patterns.

@baseapp You are my hero! I was desperately trying to find a replacement for Crayon Syntax Highlighter after I realized it breaks with PHP 7.3. I would never have figured out that a single backslash would fix the issue. THANK YOU for sharing your knowledge with us! Now if only someone would adopt this plugin …

Yikes!!! Please disregard the earlier code. I can’t seem to delete it. Apparently it was directing all traffic to my website to the login page. Guess I should stop messing around in code I don’t completely understand!

I’m unable to solve this problem with the email digest links so I turned to a much broader fix. I found the following code at https://wordpress.stackexchange.com/questions/16004/redirect-user-to-original-url-after-login and added it to functions.php in my child theme.

function restrict_access_if_logged_out(){
    if (!is_user_logged_in() && !is_home()){
        $redirect = home_url() . '/wp-login.php?redirect_to=' . urlencode( $_SERVER['REQUEST_URI'] );
        wp_redirect( $redirect );
        exit;
    }
}
add_action( 'wp', 'restrict_access_if_logged_out', 3 );

Now when someone tries to follow a link to private content without being logged in, they will be routed to the login form, and then once they have logged in they will be redirected to the original URL they were attempting to reach.