justmejames

Thanks Peter,

Last night I managed to recreate it on my staging site, and then tried again today using a backup from 2nd April to try and replicate it, and now it won’t. I did re-enable Wordfence on the live site, and it did it again, so quickly disabled and it carried on throwing 404’s… so I went through and updated WordPress to 6.5 (I often hold a day or two if it’s not a security release) and that seemed to fix it all.

My concern now however is a bit like the tree falling in the forest and no one hearing it. I picked up this 404 issue very quickly, because I was using a transaction test where a bot clicks on each link etc and visits a page, however many of my sites are more simple portfolio sites and I just check for a string to make sure they’re up, and ignore the 404’s as often they’re for outdated projects and just redirect the user to the homepage.

So could this be that some sites could get in a loop and redirect to the homepage and I’d not know anything about it? I’m assuming this 404 is an error rather than a block? And it’s interesting it was all ‘woocommerce’ based pages.

Is there a simple way of checking for this error / issue, and should I be a little less paranoid?

Perfect! Thanks for confirming, regarding the issue prior to 2.0.4 did it just mean that people could (rather elaborately) be tricked into having their better fontawesome settings being updated?