The Frontend Editor Canvas is Unusable On Our Site. - Question | JoomShaper

is live, now with multi-currency selling.

The Frontend Editor Canvas is Unusable On Our Site.

Antonio Torres

Antonio Torres

SP Page Builder 2 weeks ago

ENVIRONMENT SP Page Builder Pro 6.8.0 Joomla 5.4.8 Template: Helix Ultimate / Investa Search Engine Friendly URLs: Yes. URL Rewriting: Yes. Site: https://www.aseguratemexico.com

WHAT HAPPENS Opening /<alias>/edit/<id> loads the builder chrome correctly: top bar, Layers panel, element settings, Save. Selecting an element and editing it works, and clicking Save persists the changes to the page. Only the canvas is broken: it shows our 404 page. The form/edit layout outputs this iframe: <iframe name="sp-pagebuilder-view" id="sp-pagebuilder-view" class="builder-iframe-laptop" data-url="https://www.aseguratemexico.com/index.php?option=com_sppagebuilder&view=form&id=120&layout=edit-iframe&Itemid=781"></iframe> With SEF enabled that resolves to /gnp-hospitales/edit-iframe/120, which returns HTTP 404.

TEST RESULTS index.php?option=com_sppagebuilder&view=form&id=120&layout=edit -> 200 OK index.php?option=com_sppagebuilder&view=form&id=120&layout=edit-iframe -> 404 index.php?option=com_sppagebuilder&view=form&id=120&layout=doesnotexist -> 404 For comparison, other components fall back to their default layout instead of returning 404: index.php?option=com_content&view=featured&layout=doesnotexist -> 200 OK index.php?option=com_users&view=login&layout=doesnotexist -> 200 OK So com_sppagebuilder returns 404 for any layout segment it does not recognise, and "edit-iframe" is treated exactly like a layout that does not exist, even though the component's own edit layout generates a URL pointing to it. We also tried 12 alternative layout names (iframe, preview, canvas, editor, frame, edit_iframe, page-iframe, pageiframe, edit-page, builder, default, edit). Only "edit" returns 200.

WHAT WE ALREADY RULED OUT Not page-specific. Reproduced on several pages, e.g. /automoviles/edit-iframe/22 and /gnp-hospitales/edit-iframe/120. Not the Itemid. Same 404 with no Itemid, with Itemid=781 and with Itemid=1320. Not tmpl. Same 404 with and without &tmpl=component. Not a firewall or security rule matching the word "iframe". index.php?option=com_sppagebuilder&view=form&id=120&layout=edit&zz=iframe returns 200. Not permissions or session. We are logged in on the frontend as a Super User, the user profile view loads normally, and saving from the editor works. Not a pending update. SP Page Builder does not appear in Joomla's update list; 6.8.0 is the version offered by the update site. Not a damaged installation. We reinstalled SP Page Builder 6.8.0 over the existing installation and the behaviour is unchanged.

SIDE EFFECT Every attempt to open the frontend editor is logged by com_redirect as a 404. We currently have 41 such entries from 10 different pages, all of the form /<alias>/edit-iframe/<id>.

WORKAROUND WE ARE USING The administrator-side editor works correctly: administrator/index.php?option=com_sppagebuilder&view=editor&tmpl=component#/editor/<id>/ It loads the page structure, opens element settings, and saves without problems.

QUESTIONS Is "edit-iframe" expected to be routable when SEF URLs are enabled? It looks like the component's router only accepts the "edit" segment. Is there a supported configuration that makes the frontend canvas work with SEF enabled? Turning SEF off is not an option for us: the site has around 500 indexed URLs. If this is a known bug, is there a patch or a target release?

0
5 Answers
Mehtaz Afsana Borsha
Mehtaz Afsana Borsha
Accepted Answer
Support Agent 1 week ago #233269

Hello,

Could you please let us know if this solution resolves the issue? If it works, feel free to mark the answer as accepted to close this thread.

Best regards,

0
Mehtaz Afsana Borsha
Mehtaz Afsana Borsha
Accepted Answer
Support Agent 2 weeks ago #233179

Hi,

Thank you for the detailed information and for all the testing you have already done. The results are very helpful.

Based on your tests, this does appear to be related to how SP Page Builder handles the edit-iframe layout when Joomla SEF URLs are enabled. Since the standard edit layout works correctly and the edit-iframe request consistently returns a 404, your Joomla Media, permissions, Itemid, security rules, and installation do not appear to be the cause.

At the moment, there isn't a recommended configuration to disable this specific routing behaviour while keeping SEF enabled.

Since the frontend editor itself is generating the edit-iframe URL, this will need to be reviewed by our development team. I recommend submitting the details you provided, especially the direct URL tests and the fact that the administrator editor works correctly, so the team can reproduce and investigate the routing issue.

For now, the administrator-side editor can be used as a workaround.

Please avoid modifying the SP Page Builder router/core files manually, as those changes could be lost during an update.

Thank you for providing such a thorough report.

-Regards.

0
Atick Eashrak Shuvo
Atick Eashrak Shuvo
Accepted Answer
Support Agent 1 week ago #233229

Hello,

Thank you for providing the detailed information and troubleshooting results.

Could you please try one additional step on your website?

  1. Go to System → Plugins.
  2. Search for and open the System - SEF plugin.
  3. In the plugin settings, check whether Strict Routing is enabled.
  4. If it is enabled, please disable Strict Routing.
  5. Clear the Joomla cache afterward.
  6. Then, please open the SP Page Builder frontend editor again and check whether the canvas loads correctly.

The Strict Routing option can affect how Joomla handles component routes and may cause certain component URLs to return a 404 when the requested route or layout is not explicitly recognised.

Please let us know whether disabling this option resolves the issue.

0
Antonio Torres
Antonio Torres
Accepted Answer
1 week ago #233276

Excellent! It's working now; that was the problem. Thank you very much!!

0
Mehtaz Afsana Borsha
Mehtaz Afsana Borsha
Accepted Answer
Support Agent 1 week ago #233322

Glad to know that and thanks for accepting the answer.

0