Frontend Editor broken on fresh Joomla installs (404 with SEF ON / 500 with SEF OFF) due to Strict Routing - Forum | JoomShaper
Awaiting an answer SP Page Builder Joomla 6 v6.10.0

Frontend Editor broken on fresh Joomla installs (404 with SEF ON / 500 with SEF OFF) due to Strict Routing

Asked by S-D CONSULTING 2 days ago Last activity 4 hours ago

Hello,
I have isolated a critical compatibility issue between SP Page Builder's Frontend Editor and Joomla's "System - SEF" plugin on recent Joomla versions.

I didn't notice this issue on my older websites because Joomla's "Strict Routing" feature is turned off by default on older/upgraded sites. However, on fresh Joomla installations (where Strict Routing is often enabled by default or recommended), the Frontend Editor breaks immediately.

Here is the exact behavior I am experiencing on new installations:

Scenario A: SEF Enabled + Strict Routing Enabled (The 404 Error)
When trying to edit a page in the Frontend Editor, the main shell loads, but the internal iframe (/edit-iframe/{id}) gets caught in a 301 redirect loop and ultimately throws a 404 Component Not Found error. The Joomla router considers the /edit-iframe/ URL as an irregular or duplicate route and redirects it.Temporary Fix: Disabling "Strict Routing" in the System - SEF plugin stops the 301 loop and the editor loads perfectly.

Scenario B: SEF Disabled (The 500 Error)
If I disable SEF entirely to bypass the router issue, the Frontend Editor triggers a 500 Internal Server Error.
Upon checking the server logs, the non-SEF URL (index.php?option=com_sppagebuilder&view=form&layout=edit-iframe...) generates a massive HTML payload that exceeds 1MB. This triggers a ModSecurity block: ModSecurity: Output filter: Response body too large (over limit of 1048576).
While I can whitelist this on my server, it highlights how heavy the raw output is when SEF is disabled.

Steps to reproduce the 404 issue:

On a fresh Joomla install, go to Plugins > System - SEF.

Set "Strict Routing" to YES.

Open any SP Page Builder page in the Frontend Editor.

Inspect the network tab or screen to see the 404 error inside the iframe.

Request:
Could your development team update the SPPB routing class (router.php) to explicitly declare the /edit/ and /edit-iframe/ endpoints as valid routes? Without this fix, the Frontend Editor will continue to break on any modern Joomla site enforcing strict URL routing.

Thank you for your support.

3 replies

Matt Hunt

I am experiencing this same issue on multiple sites.

S-D CONSULTING Asked this

For new installations, I’ve resolved this by modifying Joomla’s System SEF settings: you need to disable "strict routing."

However, this issue should primarily be addressed within the Page Builder development itself—specifically in the route.php file that handles this routing. Joomla needs to recognize that edit and edit-iframe are intended parts of the URL structure.

Atick Eashrak Shuvo Staff

We sincerely apologize for the inconvenience.

Thank you for providing such a detailed explanation of the issue and the steps to reproduce it. I have forwarded this compatibility issue to our development team for further investigation.

The team will work on addressing this in a future SP Page Builder update. However, since the upcoming version is already in the testing phase, the fix may not be included in the immediate next release.

We appreciate you taking the time to report this issue and provide detailed technical information. Thank you for your patience and understanding while we work toward a solution.

Robert
5 hours ago · edited

So it was the latest SP Pagebuilder what caused the issue? Had the same but not on all my sites and they are all updated to latest version.. Took me a while what caused the issue, was looking in Admin tools. We had so many updates in a short periode that this kind of issues (how small or big) can take quite some time to figure out what is changed. In this case it took me over an hour to find the issue. Looks like older build sites are not having this issue.

"The team will work on addressing this in a future SP Page Builder update. However, since the upcoming version is already in the testing phase, the fix may not be included in the immediate next release."

Imo is the testing phase the ideal moment to fix this. And the benefit we get one update instead of two. I bet more people are gonna waste a lot of time when they run into this issue.

S-D CONSULTING Asked this

Hi, in my opinion, this is a combination of two issues:
The system SEF plugin—which is native to Joomla and introduced this functionality—and, almost certainly, recent security-related updates to Page Builder.

Page Builder definitely needs to fix its route.php file.

I’ve noticed that on my older sites, the Joomla update didn’t enable this feature by default; it only did so on more recent ones.

Robert

That’s correct; I’ve also compared a few sites: the setting is only enabled ('yes') on the most recently built websites, while it remains disabled ('no') on the others. They are likely conducting the test phase on older installations... As soon as testing is carried out on new installations, this issue immediately pops up. It actually forms a key foundation of the builder. That's why I find it quite remarkable the next release may not have the fix included.

S-D CONSULTING Asked this

I agree with you, Robert.
I have a high regard for this project, even though I did come across a few shortcomings—which I promptly reported.

Unfortunately, in this world, it’s hard to find a "perfect" project—not least because security flaws are always lurking around the corner. That said, by using PageBuilder alongside AI, I’ve managed to develop some interesting projects that are yielding great results—even in terms of GEO/SEO, which I never would have expected!

I’m confident that the issue will be fixed. After all, anyone already familiar with PageBuilder—especially those who develop multilingual sites with SEF (Search Engine Friendly) URLs enabled—will be well aware of the problem involving language suffixes. Depending on the default language setting, these can trigger 404 errors; you have to manually correct the suffix (e.g., /en or /fr) in the URL bar, otherwise the page won’t load.

S-D CONSULTING Asked this

Thanks, Robert; I’ll definitely check them out.
I’m currently working on several projects. I’m not particularly fond of Claude; I prefer a different ecosystem.
One of my own projects has been running autonomously for six months now, and it’s yielding remarkable results. It’s a multi-agent system focused on the culinary world—celebrating cuisine—and includes a guided tour that also covers fine wines and craft beers. I’m quite pleased with it.
I’m also developing a number of other projects, and the ecosystem I’ve chosen is proving very rewarding—especially since, in several instances, I’ve integrated it with the Joomla APIs, and it works exactly as it should.

Robert

Cool, have build several tools for the maritime world and safety. A combination of knowhow, 35 years of experience and AI. The QHSE managers are using the tools and custom made editors now. Especially now that the forms and tools appear immediately in a modern corporate style. No need for Office anymore.

Log in to reply.