Save an explicit Advanced exception draft ability
Trusted developers only: intentionally change one element's scoped CSS or executable Custom JavaScript, after reading its current revision and build contract. Native components/settings must be used when they cover the requirement. This never publishes and never runs code over the editor UI.
What it does#
Trusted developers only: intentionally change one element's scoped CSS or executable Custom JavaScript, after reading its current revision and build contract. Native components/settings must be used when they cover the requirement. This never publishes and never runs code over the editor UI.
Access and execution#
This WordPress Ability runs as the authenticated caller. Site AI access, relevant content permissions, and feature-specific code or design gates still apply. See Automation access for authentication and transport setup. Discover the ability through the installed WordPress Abilities interface rather than guessing a different REST path.
Input schema#
{
"type": "object",
"properties": {
"page_id": {
"type": "integer"
},
"rev": {
"type": "string"
},
"element": {
"type": "integer",
"minimum": 1
},
"intent": {
"type": "string",
"enum": [
"advanced-exception"
]
},
"css": {
"type": "string",
"maxLength": 16384
},
"javascript": {
"type": "string",
"maxLength": 16384
}
},
"required": [
"page_id",
"rev",
"element",
"intent"
],
"additionalProperties": false
}
Output schema#
{
"type": "object"
}
Integration behavior#
Required fields and additionalProperties restrictions are part of the contract. Preserve returned revision tokens as opaque values. If a write reports a conflict, fetch the current source and reconcile before retrying. Draft and publication are separate operations unless this ability explicitly publishes. A successful schema match does not bypass content validation.
Errors use WordPress error responses; inspect their code, message, and status rather than assuming every non-success is retryable. Do not include credentials in diagnostic logs.