Critical errors

Hi @hampalm1, thanks for getting in touch.

Do you have any examples of the critical error messages, as these could help me identify the scripts or plugin that might be causing them, and critically whether they are directly linked to Wordfence. I wouldn’t rule out a Javascript/plugin conflict at this stage, you can show us errors here to assist with a service like Snipboard.

In the mean time, you could also try disabling all plugins except for Wordfence and reverting to a default theme such as Twenty Twenty-One. Does the behaviour continue when Wordfence is the only plugin enabled? If not, re-enable your plugins one-by-one and finally your theme to see when it starts reoccurring. You can install a maintenance mode plugin during this time if site visitors are likely to be affected. Browser extensions can also sometimes interfere with these pages so disabling those at the same time, or using a different browser to your default may be an idea during this period of testing too!

Let me know how you get on!

Peter.

Thanks Peter
Does this help: https://www.loom.com/share/43113fd88e094d2580b43dd0cf5514a0 ?

I did try turning all plugins off except wordfence and still got the errors it was only without wordfence on it would work and that was with the other plugins on.

Kind regards

Andrew

Hi @hampalm1, thanks for your very detailed video.

The key error for me is the E_ERROR mentioned at the bottom of the email caused by your theme. It states that an object cannot be converted to a string so something is being passed in the background as a variable of the wrong data type. You may need to contact your theme developers to see if a recent theme update may have either broken, or if you haven’t updated and there are updates available, fix this issue.

You could try running Wordfence in Learning Mode just in case there is a block happening in the background that is causing the object/string issue that causes the theme to fail, although I cannot guarantee this will help.

From the Wordfence Dashboard click on Manage WAF. Then you will see Basic Firewall Options > Web Application Firewall Status. Change the option to Learning Mode. Now perform the actions that were causing issues as shown in your video. This will help Wordfence learn that these actions are normal and it will allow them in the future. After you have finished performing the actions, switch the WAF from Learning Mode back to Enabled and Protecting. Now test to see if these actions work correctly.

Thanks again,

Peter.

OK, I’ll have to review this properly tomorrow. Thanks, Andrew