silverstripe-framework/docs/en/02_Developer_Guides/07_Debugging/03_Template_debugging.md
Aaron Carlino 6888901468
NEW: Update docs to be compliant with Gatsby site (#9314)
* First cut

* Temporarily disable composer.json for netlify build

* POC

* New recursive directory query, various refinements

* Fix flexbox

* new styled components plugin

* Apply frontmatter delimiters

* Mobile styles, animation

* Search

* Redesign, clean up

* Nuke the cache, try again

* fix file casing

* Remove production env file

* ID headers

* Move app to new repo

* Add frontmatter universally

* Hide children changelogs

* Add how to title

* New callout tags

* Revert inline code block change

* Replace note callouts

* Fix icons

* Repalce images

* Fix icon

* Fix image links

* Use proper SQL icon
2019-11-18 17:58:33 +13:00

24 lines
537 B
Markdown

---
title: Template debugging
summary: Track down which template rendered a piece of html
icon: bug
---
# Debugging templates
## Source code comments
If there is a problem with the rendered html your page is outputting you may need
to track down a template or two. The template engine can help you along by displaying
source code comments indicating which template is responsible for rendering each
block of html on your page.
```yml
---
Only:
environment: 'dev'
---
SilverStripe\View\SSViewer:
source_file_comments: true
```