Black Friday 2026 50% off every plan Our biggest deal of the year on #1 Joomla products.
Ends in 13d 05h 49m 56s
Claim 50% off
Solved SP Page Builder Joomla 5 Last

SP Page Builder returns 404 on every page I try to edit

Asked by carloxp 2 days ago Last activity 2 days ago

Hello JoomShaper Support Team,

I'm experiencing a serious issue with SP Page Builder on my Joomla staging website.

Whenever I try to open any page for editing through SP Page Builder, I receive a 404 – Page Not Found error instead of the editor.

The problem affects every page, making it completely impossible to edit any content using SP Page Builder.

Some additional information:

  • The issue occurs on my staging website and on production.
  • SP Page Builder was working correctly the last time I used it, approximately 40 days ago.
  • I have already cleared the cache, but the problem persists.
  • The error page displayed is my website's custom 404 page.

I've attached a screenshot showing the error.

This is a critical issue for me because I currently cannot work on any of my pages.

Could you please help me identify the cause and restore normal SP Page Builder functionality?

Please let me know if you need any additional information or access to the staging environment.

Thank you very much for your assistance.

Best regards,
Carlo

Page not Found

Accepted answer

Marked as the solution

2 more replies

Paul Frankowski Senior Staff
2 days ago · edited

Solved; it was a problem with the System - SEF plugin settings. The solution was/is in the documentation. Do the same simple change on the production site.

ok3.jpg

Risolto; si trattava di un problema legato alle impostazioni del plugin System - SEF. La soluzione era/è riportata nella documentazione. Effettua la stessa semplice modifica sul sito di produzione.

carloxp Asked this

Hi Paul

Thank you very much for your help!

Changing Strict Routing from Yes to No in the System - SEF plugin completely resolved the issue. SP Page Builder's frontend editor is now working correctly on all pages.

Interestingly, this setting had been enabled for about a year without causing any problems, so I wonder what might have changed recently to trigger this behavior.

Anyway, I'm very glad the issue has been resolved.

Thanks again for your prompt assistance!

Best regards,
Carlo

Log in to reply.