Possible Problem

Hi there,

I understand your frustration with encountering a block while saving a post, but let me explain what happened and why.

The Aggressive Block Data option is designed to detect potentially malicious requests, but it’s very strict and can cause false-positive blocks, which is why it is disabled by default and comes with a clear warning that it may cause false-positive blocks. The warning is indicated in the option description and in our help documentation. For example, in the option description:

By choosing to enable this option, normal actions — like saving a post — can trigger a block, which is what happened in your case. It’s important to note that Shield did not enable this option for you; it was a choice made in your site’s configuration.

The firewall block page clearly shows which firewall rule and request parameter were triggered. For example:

The same details can be found in the WP Activity Log too.

As the site admin, you have full control over your security configuration. In this case, you can disable the Aggressive Block Data option or whitelist the specific parameter to stop the block and solve the problem quickly. Detailed instructions and explanations for handling these blocks are also available in our documentation here and through the Help/Info links inside the plugin.

So Shield isn’t dictating which settings you can or cannot use. Site admins always control how Shield behaves, and you can decide how strict — or less strict — you want the firewall to be. The plugin just provides the tools, shows what was blocked and leaves the choice to you.

Also, if Shield ever blocks you,  WP Activity Log can be your best ally. It monitors and records your site in real-time and tracks specific actions. It will show you the exact type of block that was triggered so you can adjust Shield’s settings to prevent it from happening again.

I hope this clarifies things a little bit for you.

Regards,

Jelena