Hello Henk de Gans,

Thank you for reaching out to our technical support forum. I’m sorry to hear about the trouble you’re experiencing. Rest assured, I will look into this issue for you and work to resolve it as quickly as possible.

Please share your administrator access here to check the issue. Use the Hidden Content box to share the credentials. Make sure that you have a full site backup before sharing.

Best regards

Great, thanks in advance! Look in Hidden!

I have checked your issue. Please try these steps:

1. Switch PHP to 8.2
2. Increase memory_limit to 256M+
3. Disable mod_security (ask your hosting provider)

After each step, check the issue. You might not need to do every steps described above. One step might solve the issue or other.

Strange advice! I have Joomla 6, which requires at least PHP 8.3 (tried what you suggested, but that doesn't work). I adjusted the memory settings, but no result. I have now put the question to the hosting provider. But as I mentioned, I am also running a subdomain here (https://www.skg.gelderseparkietenfederatie.nl/) to test with another website, using the same Joomla and Joomshaper version, and that one runs fine.

Oh! my bad. Test it on PHP 8.3 if you have not already. Let me know if disabling mod_security fixes the issue.

My hosting provider advises against running Disable mod_security! The website has since received a Joomla update, but the problem persists. I am currently unable to do anything. Please take prompt action, otherwise I will be forced to restore a working backup to Joomla 5, which I would rather avoid! I look forward to hearing from you. I have also noticed that I cannot save Joomla articles either, in addition to pages I create with sp.

Thank you for the update—this additional detail is very important.

Since you’re unable to save both SP Page Builder pages and Joomla articles, this clearly indicates that the issue is not specific to SP Page Builder, but rather a server-level or environment-level problem affecting all POST save requests in Joomla.

👉 The failure is happening before or outside of the application logic, typically due to:

• Server security rules (e.g. mod_security)
• PHP configuration limits
• Server restrictions on POST requests

⚠️ About mod_security

I understand your hosting provider’s concern. However, in many cases like this, mod_security does not need to be fully disabled—instead, specific rules can be adjusted or whitelisted.

👉 Please ask your hosting provider to:

• Check the server error logs for the exact blocked rule
• Whitelist the request instead of disabling mod_security entirely

/home/u171167p184363/domains/gelderseparkietenfederatie.nl/public_html/plugins/finder/jevents/jevents4.php on line 30\n, referer: https://gelderseparkietenfederatie.nl/ [Fri Apr 03 15:10:57.126770 2026] [lsapi:warn] [pid 85184:tid 140098754545408] [client 2a02:a469:aa93:0:3838:d377:22b8:abeb:49483] [host gelderseparkietenfederatie.nl] Backend log: PHP Warning: require_once(/home/u171167p184363/domains/gelderseparkietenfederatie.nl/public_html/administrator/components/com_finder/helpers/indexer/adapter.php): Failed to open stream: No such file or directory in /home/u171167p184363/domains/gelderseparkietenfederatie.nl/public_html/plugins/finder/jevents/jevents4.php on line 30\n, referer: https://gelderseparkietenfederatie.nl/administrator/index.php?option=com_content&view=article&layout=edit&id=71 [Fri Apr 03 15:12:12.799702 2026] [lsapi:warn] [pid 96070:tid 140098637047552] [client 2a02:a469:aa93:0:3838:d377:22b8:abeb:64884] [host gelderseparkietenfederatie.nl] Backend log: PHP Warning: require_once(/home/u171167p184363/domains/gelderseparkietenfederatie.nl/public_html/administrator/components/com_finder/helpers/indexer/adapter.php): Failed to open stream: No such file or directory in /home/u171167p184363/domains/gelderseparkietenfederatie.nl/public_html/plugins/finder/jevents/jevents4.php on line 30\n, referer: https://gelderseparkietenfederatie.nl/administrator/index.php?option=com_sppagebuilder&view=editor&tmpl=component

It doesn't ring a bell, but this is the last part of the PHP error log. Can you do anything with this?