@@ -14,46 +14,54 @@ to find errors within TypoScript.
14
14
.. index ::
15
15
TypoScript; Constants debugging
16
16
Constants; debugging
17
+ .. _typoscript-debugging-constants :
17
18
18
19
Analyzing defined constants
19
20
===========================
20
21
21
- The *TypoScript Object Browser * provides an tree view to all defined constants
22
- on the currently active page.
22
+ .. versionchanged :: 12.0
23
+ The TypoScript management tools are now found in backend module
24
+ :guilabel: `Site Management > TypoScript `. It was formerly found in
25
+ "Page > Template".
23
26
24
- .. include :: /Images/AutomaticScreenshots/TemplatesModul/TemplatesConstants.rst.txt
27
+ The submodule :guilabel: `Active TypoScript ` was renamed from
28
+ "TypoScript Object Browser".
29
+
30
+ The backend submodule :guilabel: `Site Management > TypoScript > Active TypoScript `
31
+ provides a tree view to all defined TypoScript Constants on the currently active page.
32
+
33
+ .. figure :: /Images/ManualScreenshots/TypoScriptModule/ConstantsDisplayActiveTypoScript.png
34
+ :alt: A Screenshot showing the "Constants" section of the "Active TypoScript" submodule.
35
+
36
+ Analyzing defined TypoScript Constants in the :guilabel: `Active TypoScript` submodule.
25
37
26
38
.. index :: TypoScript; Syntax errors
27
39
.. _typoscript-syntax-finding-errors :
28
40
29
41
Finding errors
30
42
==============
31
43
32
- There are no tools that will tell whether the given TypoScript code is 100%
33
- correct. The :guilabel: `TypoScript object browser ` will warn about syntax errors though:
44
+ .. versionchanged :: 12.0
45
+ The TypoScript management tools are now found in backend module
46
+ :guilabel: `Site Management > TypoScript `. It was formerly found in
47
+ "Page > Template".
34
48
35
- .. figure :: /Images/ManualScreenshots/Templates/SyntaxError.png
36
- :alt: The TypoScript Object Browser showing a syntax error
37
- :class: with-shadow
49
+ The submodule :guilabel: ` Active TypoScript ` was renamed from
50
+ " TypoScript Object Browser". It does not display syntax warnings anymore,
51
+ those are displayed in the submodule :guilabel: ` Included TypoScript ` only.
38
52
39
- Errors will also appear in the :guilabel: `template analyzer `, when viewing the content of a
40
- given template. It is also possible to see the full TypoScript code by clicking
41
- on the :guilabel: `View the complete TS listing ` button at the bottom of the template
42
- analyzer:
53
+ The submodule :guilabel: `Included TypoScript ` was renamed from
54
+ "TypoScript Analyzer".
43
55
44
- .. include :: /Images/AutomaticScreenshots/TemplatesModul/TemplatesViewFullListingButton.rst.txt
45
-
46
- The result is a long listing with all compiled line numbers, which makes it
47
- possible to find the error reported by the :guilabel: `TypoScript object browser `.
48
-
49
- .. figure :: /Images/ManualScreenshots/Templates/FullListing.png
50
- :alt: The TypoScript Object Browser showing a syntax error
51
- :class: with-shadow
56
+ There are no tools that will tell whether the given TypoScript code is 100%
57
+ correct. The :guilabel: `Included TypoScript ` will warn about syntax errors though:
52
58
53
- In the frontend, the :guilabel: `admin panel ` is another possibility to debug TypoScript; use
54
- its section called :guilabel: `TypoScript `. It shows selected rendered (configuration)
55
- values, SQL queries, error messages and more.
59
+ .. figure :: /Images/ManualScreenshots/TypoScriptModule/IncludedTypoScriptWarnings.png
60
+ :alt: The submodule 'Included TypoScript' showing a syntax warning
56
61
62
+ In the frontend, the :composer: `typo3/cms-adminpanel ` is another possibility
63
+ to debug TypoScript: use its section called :guilabel: `TypoScript `. It shows
64
+ selected rendered (configuration) values, SQL queries, error messages and more.
57
65
58
66
.. index ::
59
67
TypoScript; Debugging stdWrap
0 commit comments