When attempting to save changes to a Brizy page, if you encounter the following error notification, kindly follow this troubleshooting guide to fix it.   

The above error notification could be due of a security software in your WordPress environment interfering with the Brizy editing functionality. Let's examine two such software that can interfere and how to resolve the issue in each instance.

1. ModSecurity

An open-source web application firewall (WAF) called ModSecurity defends websites against frequent threats. This software is typically found in your hosting cPanel. The "SecRequestBodyLimit" configuration directive in ModSecurity establishes the maximum size of HTTP requests for your websites. You will get the above error in the Brizy editor when attempting to save changes to your page, if the request size for your Brizy page exceeds the upper limit.

To verify whether ModSecurity interferes with the Brizy editing, temporarily disable it by choosing the ON/OFF toggle switch in the cPanel, then check whether you can save changes to your Brizy page.

Kindly revise the "SecRequestBodyLimit" in ModSecurity to resolve this issue. Your host may have set the default SecRequestBodyLimit to 0.125 MB. This limit needs to be increased to 4MB in order to ensure error-free Brizy editing. Please request your hosting provider to update the ModSecurity configuration file with these two configuration directives.

SecRequestBodyLimit 4194304 # Limit request bodies to 4 MB
SecRequestBodyNoFilesLimit 2097152 # Limit non-file request bodies to 2 MB

If your hosting provider forbids changes to the ModSecurity configuration file, find out what level of ModSecurity configuration is permitted in your .htaccess file. If your host permits, follow the steps below to add the ModSecurity configuration directives to your .htaccess file.

A. Access the "File Manager" 

Sign into your cPanel account and select the "File Manager" option under "Tools"

B. Edit the .htaccess file

Select the "Settings" button at the top right corner

and enable the option "Show Hidden Files (dotfiles)"

Under the public_html folder, edit the .htaccess file in your site root

C. Add ModSecurity configuration directives  

Add these ModSecurity configuration directives to your .htaccess file before the "# END WordPress" line

<IfModule mod_security.c>
    SecRequestBodyLimit 4194304
    SecRequestBodyNoFilesLimit 2097152
</IfModule>

Once you have added the above configurations, your .htaccess file may look like this

Click on the "Save Changes" button at the top right corner to save your changes.

2. Wordfence Security

Brizy editing may also get hindered by the Wordfence Security plugin in your WordPress Dashboard. When a plugin exhibits a behavior that resembles known attack patterns, Wordfence Firewall may block it mistaking it as malicious. Wordfence is known to mistake Brizy editing as malicious and this results in the error "This page needs a refresh. You've probably updated the page in a different tab or browser". 

Please activate the Wordfence Firewall's "Learning Mode" to fix this false positive. Wordfence will add any requests that resemble attack patterns to the allow-list when the "Learning Mode" is enabled. Make some changes to a Brizy page and save it after turning this mode on for a few hours. In your WordPress Dashboard under Wordfence - All Options, scroll down to the heading "Firewall Options" and select the "Learning Mode" option and click on 'Save Changes' button at the top right corner.