Frontend Editor Redirects To Homepage + Broken Stylesheet Path (SPPB 6.7.1)
Sabine Schwind von Egelstein
Frontend Editor redirects to homepage + broken stylesheet path (SPPB 6.7.1)
Site: schwindvonegelstein.de Joomla version: 5.4.7 SP Page Builder version: 6.7.1 (Pro) Other relevant extension: JCH Optimize Pro 9.3.0 (currently set to Development mode)
ISSUE Clicking "Frontend Editor" next to any page in the Pages list redirects me to the site's homepage instead of opening the actual page in edit mode. The frontend editing overlay/toolbar never loads.
CONSOLE ERROR The browser console repeatedly shows: "Refused to apply style from 'https://schwindvonegelstein.de/media/x/style.css' because its MIME type ('text/html') is not a supported stylesheet MIME type, and strict MIME checking is enabled."
SOURCE OF THE BROKEN PATH I found the exact cause in the page's rendered HTML. In the <head> section, this line is output:
<link href="/media/com_sppagebuilder/assets/iconfont/../../../x/style.css" rel="stylesheet">
Resolving the relative path (three levels up) results in exactly "/media/x/style.css" - matching the console error above. This is not a caching artifact; it's a malformed path being generated directly in the HTML, likely where a page ID or asset filename should be inserted instead of the literal "x". This is reproducible directly from the page source on the backend editor screen (com_sppagebuilder view=editor).
STEPS ALREADY TAKEN (none resolved the issue)
- Disabled JCH Optimize completely (all three plugins: System - JCH Optimize, System - JCH Optimize Page Cache, Console - JCH Optimize) and cleared all caches - no change.
- Toggled SP Page Builder's "Production Mode" off and on (Settings > Advanced) and used "Purge Cached CSS" - no change.
- Disabled Joomla debug mode in configuration.php ($debug = false) - no change.
- Cleared Joomla system cache and browser cache repeatedly, tested in a fresh browser profile - no change.
- Confirmed there is no compromise/injected file: checked the /media directory structure manually, no unexpected "x" folder or suspicious files present.
ADDITIONAL OBSERVATION There also appears to be no working frontend login on this site (no visible login module, and the standard com_users login URL redirects immediately to the homepage). This may be related, since Frontend Editor likely requires an authenticated frontend session distinct from the backend/administrator session - but the malformed stylesheet path above seems to be the primary, reproducible issue.
Could someone help identify what generates the "media/x/style.css" path in the icon font stylesheet link, and confirm whether a working frontend session/login is a prerequisite for Frontend Editor to function?
Thanks in advance for any pointers.
Atick Eashrak Shuvo
Accepted AnswerHi there!
Thank you for bringing this to our attention, and I sincerely apologize for the inconvenience caused.
To assist you more effectively, may I kindly request temporary administrative access to your site? This will allow me to thoroughly investigate and resolve the issue for you.
Before sharing the credentials, I strongly recommend taking a complete backup of your site to ensure all data remains secure.
Looking forward to your response.
Best regards
Sabine Schwind von Egelstein
Accepted AnswerHi Atick,
Thank you so much for looking into this — really appreciate the quick response!
I've set up a separate temporary admin account for you (rather than sharing my own login), and I took a full backup beforehand as you suggested. I've added the login details below using the Hidden Content box.
Please let me know once you're done so I can remove the temporary account again. Thanks again for your help!
Best, Sabine
Atick Eashrak Shuvo
Accepted AnswerIs this schwindvonegelstein.de/ your site url? If yes then please recheck the credentials you have shared
Atick Eashrak Shuvo
Accepted AnswerCould I take a full backup of your website so I can investigate the issue on my local environment? This will help me reproduce the problem and perform a more thorough analysis.
Sabine Schwind von Egelstein
Accepted AnswerHi Atick,
Since this involves personal/business data, would it be possible to just get the relevant template and plugin files (without the database) for your local testing? The issue sounds like it's related to file paths/redirects rather than the database content.
Thanks! Sabine
