elementor/clear-cache clears the Elementor cache at post scope, site scope, or both.
regenerate_css additionally invalidates the per-post CSS meta for one post.
At a glance
| Ability | elementor/clear-cache |
| Toolset | Elementor — toolset/elementor |
| Group | Elementor › System & Maintenance |
| Requires | Elementor, active on the site |
| Capability | manage_options |
| Safety | Writes data |
| Repeatable | Idempotent — running it twice leaves the same result |
| Ships in | AcrossAI Abilities Manager 0.0.34 and later |
Two caches, two scopes
Elementor generates a CSS file per post and caches it. A change to the document does not change the rendered page until that CSS is regenerated, which is why elementor/clear-cache is the second half of several operations here.
Post-scope CSS covers what a single document needs: the styling of its own elements. Site-scope CSS comes from the kit and covers globals, so a kit change needs the site scope and a page edit needs the post scope.
Clearing the wrong one produces the same symptom as clearing nothing: a change that is stored, visible in the editor, and absent on the front end.
The regenerate_css flag goes a step further than clearing, invalidating the meta that records a post’s generated CSS so it is rebuilt rather than merely re-served. That is the one to use when a post’s CSS is not just stale but wrong.
This is the second half of a great many operations in this suite. Anything that changes a document or a kit is not visible until the CSS catches up.
Idempotent and cheap.
Input
| Name | Type | Required | What it is |
|---|---|---|---|
scope | string | No — defaults to both | post, site or both. |
post_id | integer | For post scope | Which post. |
regenerate_css | boolean | No | Also invalidate the per-post CSS meta so it is rebuilt. |
What comes back
| Name | Type | What it is |
|---|---|---|
cleared | array | What was cleared. |
success | boolean | Whether the call completed. |
message | string | A one-line summary of what happened, suitable for showing a human. |
error_code | string | Present only on failure — a stable machine-readable reason, such as a missing field, a wrong field type or an unmet confirmation. |
Example
Ask your assistant:
My Elementor changes are not showing — clear the cache.
It resolves to one call:
{
"ability": "elementor/clear-cache",
"parameters": {
"scope": "both"
}
}Worth knowing
- Kit changes need site scope; page edits need post scope.
- Clearing the wrong scope looks identical to clearing nothing.
regenerate_cssrebuilds rather than re-serves.- The second half of most write operations here.
Related abilities
- Update Elementor Kit Settings — needs site scope
- Merge Elementor Element Settings — needs post scope
Get the plugins:
AcrossAI Abilities Manager · AcrossAI MCP Manager
Browse the rest: Every ability, by category