litespeed/purge-taxonomy purges the cached archive pages for categories or tags.
It accepts either slugs or numeric term IDs, and resolves the IDs itself.
At a glance
| Ability | litespeed/purge-taxonomy |
| Toolset | LiteSpeed Cache — toolset/litespeed |
| Group | LiteSpeed Cache › Purging |
| Requires | LiteSpeed Cache, 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 |
Why the IDs have to be resolved
LiteSpeed’s own taxonomy purge takes a slug. Hand it a numeric ID and it does not error — it simply does not match anything, and the call returns successfully having purged nothing.
That is a bad failure to hand a caller who has a term ID, which is the form most programmatic callers have. So IDs are resolved to slugs before the purge, and terms that do not exist are reported back rather than quietly dropped.
Archive pages go stale in ways individual posts do not: a post moved out of a category changes that category’s archive without changing any single post page, and nothing in the post save necessarily purges it.
For a post edit, litespeed/purge-post already covers the archives. This is for when the archive itself is the thing that changed.
Input
| Name | Type | Required | What it is |
|---|---|---|---|
taxonomy | string | Yes | The taxonomy, for example category. |
terms | array | Yes | Slugs or numeric term IDs. |
What comes back
| Name | Type | What it is |
|---|---|---|
purged | array | The terms that were purged. |
not_found | array | Terms that do not exist. |
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:
Clear the cached archive for the news category.
It resolves to one call:
{
"ability": "litespeed/purge-taxonomy",
"parameters": {
"taxonomy": "category",
"terms": ["news"]
}
}Worth knowing
- IDs are resolved to slugs. Passing an ID to LiteSpeed directly would purge nothing.
- Unknown terms are reported back.
- Purging a post already covers its archives — this is for archive-only changes.
- Idempotent.
Related abilities
- Purge Posts — which covers archives too
- Purge Cache — the broad version
Get the plugins:
AcrossAI Abilities Manager · AcrossAI MCP Manager
Browse the rest: Every ability, by category