Hello, saving a page after making changes using the frontend editor results in an infinite loop. Changes are saved correctly when using the backend editor. I am using Joomla 5.4.10 and SP Page Builder 6.10.
Frontend recording is looping
Accepted answer
Marked as the solutionGlad to know that your issue has been solved already:)
You may accept the most useful answer here in order to close the post.
Have a nice day!
3 more replies
Hello,
Thanks for reaching out, and sorry for the trouble.
We tested SP Page Builder 6.10 on Joomla 5 and saving from the frontend editor works normally. So this is most likely caused by something specific to your site. When the backend saves fine but the frontend editor keeps spinning, the save request usually gets an unexpected response. Please check the following:
- Caching: disable the System - Page Cache plugin and any cache extension (JCH Optimize, LiteSpeed Cache, Cloudflare, etc.), or exclude
option=com_sppagebuilderfrom caching. Then clear the Joomla cache and your browser cache. - Domain mismatch: make sure you open the frontend editor on the exact same URL as your site (www vs non-www, http vs https). If they differ, the save request is redirected and never completes. Check that
$live_siteinconfiguration.phpis empty or correct, and check the "Force HTTPS" setting. - PHP errors in the response: go to System → Global Configuration → Server and set Error Reporting to "None". Any notice or warning printed into the response breaks the save.
- Third-party system plugins: temporarily disable system plugins that change frontend output (security tools like Admin Tools or RSFirewall, cookie consent, minify/compress plugins), then try saving again.
- Server limits / firewall: large pages can be blocked by ModSecurity or limits like
post_max_sizeandmax_input_vars. Your host can check the error log at the moment you click Save.
If it still loops, please press F12 → Network tab, click Save, and send us:
- the status code and the Response of the
task=page.saveDatarequest - any red errors from the Console tab
A temporary Super User login (shared privately) would also help, and we'll check it directly.
Best regards,
Problem solved, server updated following PHP vulnerabilities.
Thanks for accepting the answer:)
Have a nice day!