Permissions, sanitization, and trust
Understand the distinct gates for content editing, site design, automation, and executable code.
WordPress capabilities#
Being signed in is not sufficient for every action. The server checks the relevant page or site capability on each protected operation. Developer mode changes the interface and feature access; it does not replace server authorization. Site-wide sources and design settings require broader capabilities than editing one page.
Browser REST calls use the authenticated WordPress session and REST nonce. External automation uses its authorized WordPress identity and the AI access gate. Public form submission and popup-event routes are deliberately public but still validate their own payload and context.
HTML and CSS#
Saved content passes a defined HTML allowlist, URL validation, responsive declaration validation, and feature-specific sanitizers. Editor-only marks and generated output are removed. Unrecognized markup may be rejected or stripped; inspect warnings and the saved result rather than assuming arbitrary pasted HTML is preserved.
Element CSS has a scoped grammar and authoring gate. It is not equivalent to an unrestricted site stylesheet. Responsive properties are validated consistently on the client and server.
JavaScript and PHP#
Executable code is a separate trust boundary. Element JavaScript uses signed ownership and lifecycle rules. Element PHP uses immutable private resources and stronger native file-code permissions. Ordinary content APIs and templates do not grant arbitrary code execution.
See the dedicated JavaScript and PHP contracts for signing, revocation, preview, and disabling execution.
Concurrency and audit#
Read a fresh revision before writing. Treat a 409 conflict as a request to reconcile, not as a transient failure to blindly repeat. Automation audit records are designed to identify operations without retaining full page words, prompts, or credentials.
Private data#
Form action settings and submissions, license keys, drafts, and executable source resources have different storage and disclosure rules. Public dynamic fields exclude protected metadata. Never assume that hiding an element grants access protection to a linked resource.