Conditions in the TypoScript syntax

General condition syntax

Conditions are encapsulated in [ and ]

[GLOBAL], [ELSE] and [END]

[ELSE] negates a previous condition criteria and can contain a new body until [END] or [GLOBAL]. [ELSE] is considered if the condition criteria did not evaluate to true.

[END] and [GLOBAL] stop a given condition scope. This is similar to a closing curly brace } in programming languages like PHP.

[date("j") == 9]
  page.10.value = It is the 9th day of the month!
[ELSE]
  page.10.value = It is NOT the 9th day of the month!
[END]

Conditions automatically stop at the end of a text snippet (file or record), even without [END] or [GLOBAL]. Another snippet on the same level is in "global" scope automatically. The backend TypoScript and TSconfig modules may mumble about a not properly closed condition, though.

Combining multiple TypoScript conditions with and or or

Multiple condition criteria can be combined using or or ||, as well as and or &&

[frontend.user.isLoggedIn || ip('127.0.0.1')]
  page.20 = TEXT
  page.20 {
    value = A frontend user is logged in, or the browser IP is 127.0.0.1
    stdWrap.case = upper
  }
[GLOBAL]

Single criteria can be negated using !

TypoScript constant usage in Conditions

Conditions can use constants. They are available in frontend TypoScript "setup" and in TSconfig from "site settings". A simple example if this constant myPageUid = 42 is set:

[traverse(page, "uid") == {$myPageUid}]
    page.10.value = Page uid is 42
[end]

Nesting conditions via TypoScript imports

Conditions can not be nested within code blocks.

# Invalid: Conditions must not be used within code blocks
# someIdentifier {
#    someProperty = foo
#    [frontend.user.isloggedIn]
#       someProperty = bar
#    [GLOBAL]
# }

Conditions can be nested into each other, if they are located in different snippets (files or records), see example below. They can not be nested within the same code snippet.

A second condition that is not [ELSE], [END] or [GLOBAL] stops a previous condition and starts a new one. This is the main reason conditions can not be nested within one text snippet.

@import can be nested inside conditions. This allows conditional includes and is a new feature of the TYPO3 v12 parser.

Using the null-safe operator in conditions

Using the null-safe operator is possible when accessing properties on objects which might not be available in some context, for example TSFE in the backend:

# Previously
# [getTSFE() && getTSFE().id == 123]

# Now
[getTSFE()?.id == 123]