atnjqt

Actually maybe this was restored in 6.4.x but maybe is since changed in 6.5.x — I don’t manage content so this isn’t a problem for me, but I have been fielding complaints for WP sites I maintain!

@tapiwaz that isn’t really something to publicly share, that you’re prioritizing convenience over security. There is a well published security bulletin outlining all the security fix since WP core 6.2.x here: https://www.ads-software.com/news/category/security/

I have the same issue, end users are complaining that this is a major inconvenience given the simplicity of the original workflow. It’s a frustration that should / could be alleviated by having a setting to apply as a default that all hyperlinks should have that checked on creation.

• This reply was modified 1 year, 2 months ago by atnjqt.

@caseproof any update on this?

I’ve never cloned an SVN repo so not entirely sure how to fork the source and apply these changes myself for a PR… or if those NPM fix are breaking changes for the plugin

Alright as suggested, rolling back to 7.6.1 immediately resolves my issues on local. I’ll try 7.7.x… Actually it’s probably a subsequent plugin update and likely not the 7.8.x release… will update again once I’ve identified

Thoughts on this one, @wfsupport

• This reply was modified 1 year, 11 months ago by atnjqt.
• This reply was modified 1 year, 11 months ago by atnjqt.

I am also experiencing some similar weirdness w/ WordFence 7.8.0-7.8.2 on WP Core 6.1.1 and PHP 8

This is impacting my local and production environment.. Users are unable to login, the 2FA prompt never shows. I am able to get into the site by append the 2FA code immediately after my pw (the legacy 2FA)

I’m going to try and roll back to 7.6.x given that was the last working version. Quite frustrating!