consent/rebuild-banner rebuilds the cached banner from the current cookies, categories and settings.
It changes no data and is safe to run at any time.
At a glance
| Ability | consent/rebuild-banner |
| Toolset | CookieYes — toolset/cookieyes |
| Group | CookieYes › The Banner |
| Requires | CookieYes, 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 |
What it repairs
The banner a visitor receives is not assembled on the fly. It is cached HTML, built from the declared cookies, the consent categories and the settings, and rebuilt only when the consent plugin’s own save hooks fire. Write the consent tables any other way — through the database abilities, through another plugin — and the row reads back correctly while every visitor still sees the previous banner, with no error anywhere to say so.
That is the situation this fixes. Somebody edited the consent tables through the database abilities, or imported them, or another plugin wrote them — the data is correct, the banner is not, and nothing has reported a problem because from the plugin’s point of view nothing happened.
The rebuild reruns the build step the save hooks would have run. It reads what is there now and regenerates the HTML for every language.
Because it only regenerates from existing data, it is idempotent and cannot lose anything. Running it when nothing was wrong reports no change.
Input
This ability takes no input.
What comes back
| Name | Type | What it is |
|---|---|---|
changed | boolean | Whether the rebuild actually altered the served banner. |
note | string | A short account of what the rebuild found. |
languages | array | The languages the banner is built for. |
rendered | object | The size of the built banner, per language. |
pending_rebuild | boolean | Whether the banner is still waiting to be rebuilt. True after a write means the change is stored but not yet being served. |
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:
The cookie banner is showing old text — rebuild it.
It resolves to one call:
{
"ability": "consent/rebuild-banner",
"parameters": {}
}Worth knowing
- Reads and regenerates only. No consent data is modified.
- Idempotent — running it twice is the same as running it once.
- The first thing to try when a consent change did not appear.
- Will not fix a banner that is switched off. Check the settings for that.
Related abilities
- Get Banner Status — check before and after
- Get Consent Settings — if the banner is off entirely
Get the plugins:
AcrossAI Abilities Manager · AcrossAI MCP Manager
Browse the rest: Every ability, by category