Fixing problems
Troubleshooting
Most editor problems trace back to a plugin/theme conflict, a caching layer, or a server limit. Start with Safe Mode in Tools if you're not sure where to look — it isolates Stardetha from everything else running on the site.
Jump to
Editor preview won't load
The editor loads your live front-end inside an iframe — if that frame fails, the canvas stays blank or spins forever. Common causes, roughly in order of likelihood:
- A security plugin or server rule blocking pages from loading in an iframe (look for an
X-Frame-OptionsorContent-Security-Policy: frame-ancestorsheader). - A JavaScript error from another plugin or the active theme breaking the page before Stardetha's editor script can attach.
- A fatal PHP error on the front end that only shows once rendered outside wp-admin.
Preview permissions error specifically
Usually the X-Frame-Options/CSP case above — check your security plugin's settings for an "allow framing" or "clickjacking protection" option and add an exception for the editor, or temporarily disable it to confirm.
.htaccess-related preview error
A restrictive rule in your site's .htaccess file (often added by a security plugin or host) can block the internal request the editor makes to load the preview. Temporarily rename .htaccess to test, then re-add rules one at a time.
"Theme files missing" error
Shown when the active theme can't be found or is missing required files (e.g. after an incomplete update, or the theme was deleted while active) — reinstall or reactivate a working theme.
500 Internal Server Error
This is a server-side crash. Check your host's PHP error log first. The most common
causes when it appears right after installing or updating a plugin/theme are a PHP version
below what Stardetha requires, or exhausting your PHP memory limit — try raising
WP_MEMORY_LIMIT in wp-config.php.
Page content missing on the front end
If a page looks fine in the editor but shows blank (or shows old content) on the live site, this is almost always a caching issue — clear any page-cache plugin and your host's or CDN's cache, and confirm you clicked Publish/Update, not just Save Draft.
Flexbox layout changed after an update
A layout engine change to how columns/containers compute widths can very occasionally shift existing pages by a few pixels. If a specific page looks different after updating, open it in the editor and check whether a Container's flex settings (direction, wrap, justify/align) need re-confirming.
App panels (Kit Library, Import/Export, etc.) won't open
These run as a small React app inside wp-admin — a blank panel usually means a JavaScript conflict with another admin-side plugin, or an ad-blocker/privacy extension blocking a request. Try disabling browser extensions first, then check the browser console for errors.
Font Awesome icons look different after an update
Icon libraries occasionally rename or deprecate specific icons between major versions. If a specific icon disappeared or changed, re-pick it from the icon control — the picker will show the current equivalent.