Manual · 17

Troubleshooting

Problem Cause and solution
“Render error” on the website A template error. When signed in, you see the exact message with the line; the live preview shows it too.
unable to resolve template / snippet "x" does not exist An include, component or extends refers to a Snippet that doesn’t exist (anymore) – check the name, including upper/lower case.
{% fill %} is only allowed inside {% component %} … A fill is outside a component, or an endcomponent is missing.
nested more than 30 levels deep A component calls itself (directly or via others).
HTML appears as text (<b>) Automatic escaping. For HTML fields |safe, for Markdown |markdown; the same for component parameters (text=post.text|markdown).
Page returns 404 although it exists Not published? Check with ?preview=1 while signed in. With several websites: does the requested domain belong to the right website? Locally, open it with the path link from the editor (sets ?_site=).
The wrong website appears Is the domain entered for the website? Unknown domains show the default website. As an admin, switch the remembered selection with ?_site=<ID> of the desired website.
{{ … }} should appear literally Put it in {% verbatim %}…{% endverbatim %}.
Macro import fails The macro needs export: {% macro name(…) export %}.
REST data missing or page aborts Under REST sources → Test request: check status, list path, placeholders. Were the environment variables set at server start?
Changes to images not visible after re-import Browsers cache images for a day – reload with Ctrl+Shift+R.
Format reports an error The HTML is faulty (e.g. an unclosed tag) – line/column are in the message.
Preview shows no data from fetch() The preview is isolated and may not call the API; on the real page it works.