TYPO3 v8 has reached its end-of-life March 31st, 2020 and is not maintained by the community anymore. Looking for a stable version? Use the version switch on the top left.

You can order Extended Long Term Support (ELTS) here: TYPO3 ELTS.

Debugging / Analyzing

Debugging TypoScript can be complicated as there are many influences like the active page and conditions. Also constants can be used which get substituted. The following sections provide information about how to debug TypoScript and how to find errors within TypoScript.

Analyzing defined constants

The TypoScript Object Browser provides an tree view to all defined constants on the currently active page.

Overview of the defined constants

Finding errors

There are no tools that will tell whether the given TypoScript code is 100% correct. The TypoScript Object Browser will warn about syntax errors though:

The TypoScript Object Browser showing a syntax error

Errors will also appear in the Template Analyzer, when viewing the content of a give template. It is also possible to see the full TypoScript code by clicking on the "View the complete TS listing" button at the bottom of the Template Analyzer:

The TypoScript Object Browser showing a syntax error

The result is a long listing with all compiled line numbers, which makes it possible to find the error reported by the TypoScript Object Browser.

The TypoScript Object Browser showing a syntax error

In the frontend, the Admin Panel is another possibility to debug TypoScript; use its section called "TypoScript". It shows selected rendered (configuration) values, SQL queries, error messages and more.


TypoScript itself offers a number of debug functions: