I’m having the same issue as this thread – when I click to edit certain widgets in live editor, I get a white screen with the date (like – Wed, 10 Jun 2020 15:44:34 GMT) dis[layed top left, and can’t go back to my edits.
I have followed the instruction from this thread:
[The date outputting when you open a widget is a common sign that Wordfence, for whatever reason, has incorrectly flagged the request. To resolve this please navigate to WP AdminWordfenceTools and open the Live Traffic tab. Filter by Blocked by Firewall and search the request you just made, it’ll be associated with your user account and the parm will start with body: instance=%7B%22frames%22%3A%5B%7B%22content. Click Whitelist param from Firewall.]
But when I filter my live traffic / by ‘Blocked by Firewall’ – I am not listed.
Most widgets can edited fine, but specific widgets throw up the same problem repeatedly in Live Editor and normal ‘Edit page’ – using the page builder.
ANy ideas would be appreciated
PS I’ve tried deactivating Wordfence and the problem persists
Hi Sally
Thanks for reaching out and for the additional update.
Please, try reactivating Wordfence and put the plugin into learning mode.
“If Wordfence doesn’t show the blocked request in the Live Traffic tab, you’ll need to put Wordfence into Learning Mode and then repeat the action to trigger the Block. Wordfence won’t block the request this time and you can now disable Safe Mode as it’ll remember not to block this request.”
After putting Wordfence into learning mode, recreating the issue and then returning to the Live Traffic tab, are you now able to find the request?
Thank you. This has worked.
Also, to explain – I thought that deactivating Wordfence would eliminate Wordfence as the culprit, BUT I only deactivated Wordfence on my staging site (using WP staging), not on my live site, so my staging site was still affected by the active Wordfence plugin on my main/live site.
I need to learn about Wordfence learning mode!
Thanks for your help
Super, that’s great news, I’m glad to hear you were able to resolve the problem. Thanks for the update.