Can no longer save edit on front end or change/ assign pages in joomla menu

Hi there,

Thanks for the details. We tested the same setup (Joomla 6, SP Page Builder 6.10.0), and both front-end saving and choosing a page on a menu item work normally. That points to something specific to your site. Please try these steps:

1. Clear all caches

• Joomla: System → Clear Cache. Also turn off System - Page Cache for now if it's on.
• If you use a hosting cache, LiteSpeed Cache, or Cloudflare, purge it and add an exception for option=com_sppagebuilder URLs.
• Then do a hard refresh (Ctrl/Cmd + Shift + R), or log out and back in.

2. Turn off script and CSS optimizers for now
If you use JCH Optimize, Cloudflare Rocket Loader, a minify or defer-JS plugin, or similar, disable it and test again. These tools often break the page-picker popup and the front-end editor.

3. Check the 400 error
The back-end editor saves fine, but the front-end editor sends its save to a different address (index.php?option=com_sppagebuilder&task=page.savePage). A 400 error there usually has one of these causes:

• Expired session / invalid security token. Reload the editor page and save again. You can also raise System → Global Configuration → System → Session Lifetime.
• A server firewall (ModSecurity/WAF) blocking the request. Please ask your host to check the ModSecurity log for blocked POST requests to the address above at the time you tried to save, and to whitelist that rule.
• PHP limits. Make sure max_input_vars is at least 5000 and post_max_size is at least 32M.

4. Try a different template
Briefly set a default Joomla template (Cassiopeia) or Helix Ultimate as the site default and test front-end saving again. That will show whether the current template (Ut_lawstudio) is causing it.

Workaround for the menu
If choosing a page still does nothing: open the menu item, click Select next to Select Page, click the page you want, then Save. If the popup won't close, create a new menu item with type SP Page Builder → Page, choose the page, then unpublish the old menu item.

If it still fails after these steps, please send us:

1. A screenshot of the browser console (press F12 → Console) right after clicking a page in the popup.
2. The response of the failed save request (F12 → Network → click the red savePage request → Response).
3. Temporary Super User access to your site, so we can check it directly.

Best regards,

Hello,

Glad that your issue has been fixed already!

You may accept an answer here in order to close the post.

Have a nice day!

Hi there,

Sorry it's back, and thank you for your patience. Since the problem comes and goes, and your other site with the same setup works fine, the cause is most likely on this site's server, or in this site's page data, rather than in SP Page Builder itself. A 500 error hides the real cause, so the quickest way to fix this is to see the actual error message. Please try these steps:

1. Show the real error

• Go to System → Global Configuration → Server and set Error Reporting to Maximum. Save.
• Open the front-end editor, press F12 → Network, and click Save.
• Click the red savePage request (status 500) and open the Response tab. Please copy the error text or send a screenshot.
• Afterwards, set Error Reporting back to System Default.

2. Check the server error log
In your hosting panel, look under Errors, Error Log or PHP error log for entries from the time you tried to save. Also check the /administrator/logs/ folder. The line with "PHP Fatal error" or "ModSecurity" usually names the exact cause.

3. Compare the two sites
On both sites, open System → System Information → PHP Information and compare these values:

• PHP version
• memory_limit (should be 256M or more)
• max_execution_time (should be 120 or more)
• max_input_vars (should be 5000 or more)
• post_max_size (should be 32M or more)

Any difference between the two sites is a strong lead. Also ask your host whether the account is near its disk, database or process limit, and whether ModSecurity blocked any POST requests to index.php?option=com_sppagebuilder. Shared hosting often enforces these limits only some of the time, which would explain why the problem went away and came back.

4. Is it one page or all pages?
Create a new, simple page and edit and save it from the front end.

• If the new page saves fine, the original page's data is likely damaged. Duplicate that page from SP Page Builder → Pages and work on the copy.
• If no page saves, the cause is on the server, as described above.

If you can't find the cause, please share temporary Super User access, plus FTP or hosting-panel access if possible, using the Hidden content field below the reply box. Only our team can see it. We'll then check the site directly and get this fixed for you as soon as possible.

Best regards,