Atick Eashrak Shuvo Staff
Hi There,
We've looked into the problem you're having when saving your page, and we
wanted to reassure you first: this is not a fault in your website or in SP
Page Builder. It's a security setting on your hosting server that needs a small
adjustment.
What's happening:
When you save a page, its content is sent to the server in one request. Your
server's security firewall (ModSecurity) limits how many individual items a
single request may contain, and your larger pages are above that limit. So the
firewall blocks the save before it reaches your website, which is why you see
an error such as "Bad Request" or the save simply not completing.
This only affects larger, content-rich pages, and it is purely a server
configuration limit.
What needs to be done:
This has to be adjusted by your hosting provider. Please contact your hosting
provider's support team and forward the request below (or let us know and, with
your permission, we can contact them on your behalf):
Saving pages in SP Page Builder is being blocked by ModSecurity with a "400 Bad
Request". The save request contains a large number of arguments (several
thousand, and over twenty thousand for bigger pages), which exceeds
ModSecurity's "SecArgumentsLimit". Please raise SecArgumentsLimit to at least
50000 for our site, or whitelist the ModSecurity rule for POST requests to:
/index.php?option=com_sppagebuilder&task=page.savePage
Note: this is not PHP's max_input_vars (the request body is JSON, which that
setting does not apply to); it is ModSecurity's argument limit.
Once your hosting provider has made this change, please try saving your page
again. If the problem is still there after the change, let us know and we will
investigate further.
Best regards