Who this is for. The developer on support who has a report such as "the form doesn't work" and a live site that shows only its error page. Afterwards you can find that request's entry among the day's errors, read every field, and reproduce it where the stack trace is visible.
What the error log records
The admin's Template Errors screen (/cdna-admin/sites/errors) lists errors raised while the platform rendered a page for a visitor:
- PHP errors and warnings raised inside a template, such as reading a key that does not exist, with the template file named.
- Any exception thrown while a page was being rendered, the ones that end in the site's error page.
- A few notices the platform records for site builders, such as a page path or an image path that was not found.
It does not hold API requests, admin screens, background tasks or job runs, and a request the page cache answered never reaches it. The line number is dropped from template errors, because it would point into the compiled copy of the template rather than the file you edit; the template's name and the message are what you have.
Narrowing to one site and one time window
The screen has two filters: the site, all sites of the account unless you choose one, and the range, counted back from now: 5, 15 or 30 minutes; 1, 2 or 8 hours; 1, 2, 5, 7 or 14 days. Errors older than 14 days are not shown. The filters are kept in the address, so a link to one site's last hour, /cdna-admin/sites/errors?site=12&range=3600, can be shared with whoever is helping.
Narrow by site and range first, then search the list for the hostname or the path: each entry's URL carries the hostname.
What an entry holds
The list shows each error's time and message. Opening one shows its fields:
| Field | What it holds |
|---|---|
timestamp | When it happened, in the admin's time zone and date format |
message | The error text, with server paths removed |
template | The template file the error came from, when it came from one |
url, path | The full address, hostname and query string included, and the path with its query string |
method | GET, POST and so on |
referrer | The page the visitor came from, when the browser sent it |
data | The submitted form fields, with password, confirmPassword, currentPassword and client_secret replaced by *** |
user | The username of the visitor, when they were signed in |
level, severity | How serious the platform judged it |