This condition will match if the visitor opens the website with Internet Explorer on Windows (but not on Mac)

[browser = msie] && [system = win]

This will match with either Opera or Firefox browsers

[browser = opera] || [browser = firefox]

This will match with either Firefox or Internet Explorer. In case of Internet Explorer, the version must be above 6.

[browser = firefox] || [browser = msie] && [version => 6]

[browser = browser1,browser2,...]

The condition works with the user agent string. The user agent is parsed with a regular expression, which searches the string for matches with the identifications named above. If there are multiple matches, the rightmost match is finally used, because it mostly is the most correct one.

An example user agent could look like this:

Mozilla/5.0 (Windows; U; Windows NT 5.1; de; rv:1.9.2.15) Gecko/20110303 Firefox/3.6.15

This string contains the identifications "Gecko" and "Firefox". The condition

[browser = firefox]

evaluates to true.

Older TYPO3 versions

Until TYPO3 4.2 the user agent was determined differently: Each value was compared with the ($browsername.$browserversion, e.g. "netscape4.72") using strstr(). So if the value was "netscape" or just "scape" or "net" all netscape browsers would match. If the value was "netscape4" all Netscape 4.xx browsers would match. If any value in the list matched the current browser, the condition returned true.

TYPO3 version 4.2 or older does not detect all the browsers listed above.

This will match with Chrome and Opera-browsers:

[browser = chrome, opera]

[version = value1, >value2, =value3, <value4, ...]

Values are floating-point numbers with "." as the decimal separator.

The values may be preceded by three operators:

This matches with exactly "4.03" browsers

[version=  =4.03]

This matches with all 4+ browsers and Netscape 3 browsers

[version=  >4][browser= netscape3]

[system= system1,system2]

Comparison with the operating system, which the website visitor uses. The system is extracted out of the useragent string.

Values are strings and a match happens if one of these strings is the first part of the system-identification.

For example if the value is "win9" this will match with "win95" and "win98" systems.

This will match with windows and mac -systems only

[system= win,mac]

Older TYPO3 versions and backwards compatibility

TYPO3 version 4.4 or older does not detect all the systems listed above.

For backwards compatibility, some systems are also matched by more generic strings.

It is recommended to use the new identifiers documented above, but the following are valid, too:

[device= device1, device2]

Values are strings and a match happens if one of these strings equals the type of device

This will match WAP-phones and PDA's

[device = wap, pda]

[useragent = agent]

This is a direct match on the useragent string from getenv("HTTP_USER_AGENT")

You have the options of putting a "*" at the beginning and/or end of the value agent thereby matching with this wildcard!

If the HTTP_USER_AGENT is "Mozilla/4.0 (compatible; Lotus-Notes/5.0; Windows-NT)" this will match with it:

[useragent = Mozilla/4.0 (compatible; Lotus-Notes/5.0; Windows-NT)]

This will also match with it:

[useragent = *Lotus-Notes*]

... but this will also match with a useragent like this: "Lotus-Notes/4.5 ( Windows-NT )"

A short list of user-agent strings and a proper match:

These are some of the known WAP agents:

[language = lang1, lang2, ...]

The values must be a straight match with the value of getenv("HTTP_ACCEPT_LANGUAGE") from PHP. Alternatively, if the value is wrapped in "*" (eg. "*en-us*") then it will split all languages found in the HTTP_ACCEPT_LANGUAGE string and try to match the value with any of those parts of the string. Such a string normally looks like "de,en-us;q=0.7,en;q=0.3" and "*en-us*" would match with this string.

[IP = ipaddress1, ipaddress2, ...]

The values are compared with the getenv("REMOTE_ADDR") from PHP.

You may include "*" instead of one of the parts in values. You may also list the first one, two or three parts and only they will be tested.

These examples will match any IP-address starting with "123":

[IP = 123.*.*.*]

or

[IP = 123]

These examples will match any IP-address ending with "123" or being "192.168.1.34":

[IP = *.*.*.123][IP = 192.168.1.34]

[hostname = hostname1, hostname2, ...]

The values are compared to the fully qualified hostname of getenv("REMOTE_ADDR") retrieved by PHP.

Value is comma-list of domain names to match with. *-wildcard allowed but cannot be part of a string, so it must match the full host name (eg. myhost.*.com => correct, myhost.*domain.com => wrong)

[hour = hour1, > hour2, < hour3, ...]

Note: The first "=" sign directly after the word "hour" is always needed and is no operator. After that follow the operator and then the hour.

Possible values are 0 to 23 (24-hours-format). The values in floating point are compared with the current hour of the server time.

As you see in the section "Syntax" above, you can separate multiple conditions in one with a comma. The comma will then connect them with a logical disjunction (OR), that means the whole condition will be true, when one or more of its operands are true.

This will match, if it is between 9 and 10 o'clock (according to the server time):

[hour = 9]

This will match, if it is before 7 o'clock:

[hour = < 7]

This will match, if it is before 15 o'clock:

[hour = <= 14]

The following examples will demonstrate the usage of the comma inside the condition:

This will match, if it is between 8 and 9 o'clock (the hour equals 8) or after 16 o'clock (the hour is bigger than or equal to 16):

[hour = 8, >= 16]

This will match between 16 and 8 o'clock (remember that the comma acts as an OR):

[hour = > 15, < 8]

In contrast a condition matching for 8 until 16 o'clock would be:

[hour = > 7] && [hour = < 16]

[minute = ...]

Minute of hour, possible values are 0-59.

Apart from that this condition uses the same way of comparison as hour.

[month = ...]

Month, from January being 1 until December being 12.

Apart from that this condition uses the same way of comparison as hour.

[year = ...]

Year, as a 4-digit number.

Apart from that this condition uses the same way of comparison as hour.

[dayofweek = ...]

Day of week, starting with Sunday being 0 until Saturday being 6.

Apart from that this condition uses the same way of comparison as hour.

[dayofmonth = ...]

Day of month, possible values are 1-31.

Apart from that this condition uses the same way of comparison as hour.

[dayofyear = ...]

Day of year, 0-364 (or 365 in leap years). That this condition begins with 0 for the first day of the year means that e.g. [dayofyear = 7] will be true on the 6th of January.

Apart from that this condition uses the same way of comparison as hour.

[usergroup = group1-uid, group2-uid, ...]

The comparison can only return true if the grouplist is not empty (global var "gr_list").

The values must either exists in the grouplist OR the value must be a "*".

This matches all logins:

[usergroup = *]

This matches logins from users members of groups with uid's 1 and/or 2:

[usergroup = 1,2]

[loginUser = fe_users-uid, fe_users-uid, ...]

Matches on the uid of a logged in frontend user. Works like 'usergroup' above including the * wildcard to select ANY user.

This matches any login (use this instead of "[usergroup = *]" to match when a user is logged in!):

[loginUser = *]

Additionally it is possible to check if no FE user is logged in.

This matches when no user is logged in:

[loginUser = ]

[treeLevel = levelnumber, levelnumber, ...]

This checks if the last element of the rootLine is at a level corresponding to one of the figures in "treeLevel". Level = 0 is the "root" of a website. Level=1 is the first menu level.

This changes something with the template, if the page viewed is on level either level 0 (basic) or on level 2

[treeLevel = 0,2]

[PIDinRootline = pages-uid, pages-uid, ...]

This checks if one of the figures in "treeLevel" is a PID (pages-uid) in the rootline.

This changes something with the template, if the page viewed is or is a subpage to page 34 or page 36

[PIDinRootline = 34,36]

[PIDupinRootline = pages-uid, pages-uid, ...]

Do the same as PIDinRootline, except the current page-uid is excluded from check.

[compatVersion = x.y.z]

Require a minimum compatibility version. This version is not necessary equal with the TYPO3 version, it is a configurable value that can be changed in the Upgrade Wizard of the Install Tool.

"compatVersion" is especially useful if you want to provide new default settings but keep the backwards compatibility for old versions of TYPO3.

[globalVar = var1 = value1, var2 > value2, var3 < value3, var4 <= value4, var5 >= value5, var6 != value6, ...]

The values in floating point are compared to the global variables "var1", "var2" ... from above.

You can use multiple conditions in one by separating them with a comma. The comma then acts as a logical disjunction, that means the whole condition evaluates to true, whenever one or more of its operands are true.

This will match with a URL like "...&print=1":

[globalVar = GP:print > 0]

This will match, if the page-id is higher than or equal to 10:

[globalVar = TSFE:id >= 10] 

This will match, if the page-id is not equal to 316:

[globalVar = TSFE:id != 316] 

This will match the non-existing GET/POST variable "style":

[globalVar = GP:style = ]

This will match, if the GET/POST variable "L" equals 8 or the GET/POST variable "M" equals 2 or both:

[globalVar = GP:L = 8, GP:M = 2]

This will match with the pages having the layout field set to "Layout 1":

[globalVar = TSFE:page|layout = 1]

If the constant {$constant_to_turnSomethingOn} is "1" then this matches:

[globalVar = LIT:1 = {$constant_to_turnSomethingOn}]

[globalString =   var1=value,  var2= *value2, var3= *value3*, ...]

This is a direct match on global strings.

You have the options of putting a "*" as a wildcard or using a PCRE style regular expression (must be wrapped in "/") to the value.

If the HTTP_HOST is "www.typo3.com" this will match with:

[globalString = IENV:HTTP_HOST = www.typo3.com]

This will also match with it:

[globalString = IENV:HTTP_HOST = *typo3.com]

... but this will also match with an HTTP_HOST like this: "demo.typo3.com"

You can use values from global arrays and objects by dividing the var-name with a "|" (vertical line).

The global var $HTTP_POST_VARS['key']['levels'] would be retrieved by "HTTP_POST_VARS|key|levels"

Also note that it's recommended to program your scripts in compliance with the php.ini-optimized settings. Please see that file (from your distribution) for details.

Caring about this means that you would get values like HTTP_HOST by getenv() and you would retrieve GET/POST values with t3lib_div::_GP(). Finally a lot of values from the TSFE object are useful. In order to get those values for comparison with "globalVar" and "globalString" conditions, you prefix that variable's name with either "IENV:"/"ENV:" , "GP:", "TSFE:" or "LIT:" respectively. Still the "|" divider may be used to separate keys in arrays and/or objects. "LIT" means "literal" and the string after ":" is trimmed and returned as the value (without being divided by "|" or anything)

Notice: Using the "IENV:" prefix is highly recommended to get server/environment variables which are system-independent. Basically this will get the value using t3lib_div::getIndpEnv(). With "ENV:" you get the raw output from getenv() which is NOT always the same on all systems!

This will match with a remote-addr beginning with "192.168."

[globalString = IENV:REMOTE_ADDR = 192.168.*]

This will match with the user whose username is "test":

[globalString = TSFE:fe_user|user|username = test]

[userFunc = user_match(checkLocalIP)]

This call the function "user_match" with the first parameter "checkLocalIP". You write that function. You decide what it checks. Function result is evaluated as true/false.

Put this function in your localconf.php file:

function user_match($cmd) {

switch($cmd) {

case 'checkLocalIP':

if (strstr(getenv('REMOTE_ADDR'), '192.168')) {

return TRUE;

}

break;

case 'checkSomethingElse':

// ....

break;

}

}

This condition will return true if the remote address contains "192.168" - which is what your function finds out.

[userFunc = user_match(checkLocalIP)]