Troubleshooting by symptom
Diagnose editor access, saving, layout, dynamic content, media, and published-output problems.
Watch the video
Chapters and transcript Captions are included.
The editor does not open#
Confirm the correct WordPress account, page-editing capability, page mode, plugin activation, license state, and the ?edit URL. Inspect the actual error. A public page loading successfully does not prove that editor access is authorized. See Licenses and Choosing an editor.
A save fails or conflicts#
Keep the current work intact. Read the message and HTTP status. A 409 often means another change made the current revision stale. Fetch the latest version, compare, and reconcile before retrying. A permission error needs the correct identity or capability, not repeated retries. A validation error needs a corrected payload.
If a network request times out, verify whether the change was stored before submitting again. Check draft state and history. Avoid opening multiple competing editor tabs for the same page during recovery.
The public page did not change#
Save and Publish are different. Confirm publication of the correct owner: page, shared part, global, or template. Then inspect a signed-out page and the host/CDN cache. Check whether a theme template or dynamic source supplies the visible content.
A control appears empty or has no effect#
An empty style field commonly means inherit. Confirm the selected element, active screen, interaction state, and style target. Check whether a class, theme rule, parent layout, fixed dimension, or more specific setting determines the visible result. For aspect ratio, follow the inspector's measured-conflict guidance.
A phone layout overflows#
Inspect fixed widths, minimum widths, long unbroken text, grids, gaps, and positioned elements. Use the live device canvas and the real visitor page. Check both sides of active breakpoint boundaries. A desktop value can remain inherited when no smaller override exists.
Dynamic content is blank#
Confirm the binding's context, fallback, public metadata key, query, publication status, and image availability. A saved placeholder is not proof that the current queried post has a value. Test a second item and the empty state.
A form does not deliver#
Verify the page and action settings are published, fields validate, recipients are configured, and the relevant delivery service works. Preview does not send. A stored submission proves storage, not email receipt. For files, check PHP/server limits and private download access.
Custom code does not run#
Check the explicit code execution gates, signature validity, author permissions, disable constants, and whether the current mode permits execution. Ordinary Preview does not run arbitrary element code. Use the code-specific diagnostics and keep the last working content before changing it.
Useful support evidence#
Record the plugin version, WordPress/PHP versions, browser, page type, selected mode, exact steps, expected result, actual message, and whether it reproduces after a saved reload. Include a safe screenshot or short recording. Remove license keys, cookies, tokens, private submissions, and unrelated browser content.