corestack_ error_ pages_ validate
Check an error page.
When to use it
Check one error or maintenance page without saving it, before corestack_error_pages_update. The answer is {diagnostics, bytes}: the same checks as corestack_error_pages_preview without the HTML.
Each diagnostic has severity, code, message, line and column. A warning whose code starts with removed_ is something the save removes (for example Removed <script>: scripts are not allowed); the saved page is the page without it. An error blocks the save until you fix it: an unknown tag, a tag inside a link or CSS, <!--#, or a page over 64 KiB. Other warnings (no <!DOCTYPE html>, no viewport, an empty tag, a resource on another host) do not block anything.
Leave source out to check the saved page, or send null for the platform's page; message likewise.
Ask for it
Using the Corefinity MCP server, call corestack_error_pages_validate with site_id 4211, page 503, source <!DOCTYPE html>
<html lang="en"><head><meta charset="utf-8"><title>{{status_text}}</title></head><body><h1>{{status_text}}</h1><p>{{message}}</p></body></html>
. (Check an error page.) Tell me what it returned.Inputs
The {{message}} text. Left out: the saved one. Null: the default. Up to 300 characters.
The page: maintenance, 404, 500, 502, 503 or 504.
maintenance404500502503504The environment row. At least 1.
The HTML to check. Left out: the saved page. Null: the platform's page. Up to 65,536 characters.
Example call
{
"name": "corestack_error_pages_validate",
"arguments": {
"site_id": 4211,
"page": "503",
"source": "<!DOCTYPE html>\n<html lang=\"en\"><head><meta charset=\"utf-8\"><title>{{status_text}}</title></head><body><h1>{{status_text}}</h1><p>{{message}}</p></body></html>\n"
}
}If it is refused
| Reason | What to do |
|---|---|
feature_off | Error pages are not available to you yet. |
managed_elsewhere | Another control panel manages this site, so use that control panel for it. This is refused before anything else about the site, as in the Control Panel and the API. Nothing was done. |
invalid_arguments | The arguments do not match the tool's input schema, or the Control Panel refused a field. Fix the fields named in the answer and call again. |
tenant_mismatch | The object does not exist or the token may not see it. Check the id. |
scope_required | The token lacks a scope this call needs. Open the link in the answer to add it, then call again. |
pin_refused | The grant is limited to chosen clusters, sites or environments, and this call is outside them. Open the link in the answer to widen it. |
rate_limited | Too many calls. Wait for the number of seconds the answer names. |
temporarily_unavailable | The Control Panel could not answer just now. Nothing was started; try again shortly. |
internal_error | Something went wrong on our side. Quote the trace id to support. |