[TYPO3-core] RFC: Feature #5613: Enable/integrate conditions in Page TSconfig

[Oliver Hader]

This is an SVN patch request.

Type: Feature

Bugtracker references:

Branch: Trunk

Problem:
doc_core_tsconfig tells us "The syntax is as usual TypoScript, only
difference is that you cannot use any Constants or Conditions."

In some situations conditions make also sense for the TYPO3 page.
Imagine you'd like to set TSconfig for sub-pages of the current one.
There is currently no "next Level" functionality in the backend like it
is in templates for the frontend.

Imagine the following page strucutre:
1
|-- 2
|-- 3

With the following Page TSconfig, only the pages 2 and 3 are affected:
[PIDupinRootline=1]
mod.SHARED.colPos_list=0
[end]

Solution:
Integrate conditions also for the backend. Therefore
t3lib_matchConditions was split in two now classes - one for frontend
and one for backend. An abstract class has the common functionality that
will be extended by the accordant disposal (e.g. in backend TSFE is not
available and stuff like that).
A configuration in TYPO3_CONF_VARS 'TSconfigConditions' allows to enable
the backend conditions.

Notes:
The documentation is similar to the current frontend conditions, except
that you cannout use "[globalVar = TSFE:whatever]". A new condition
"isAdmin" was integrated for the backend.

The feature was pending in the core list since 2007 and the development
of TYPO3 4.2. Besides that it was on the list of planned features for
TYPO3 4.3. Thus, this feature is one exception to be integrated even
after the feature freeze.

The test cases are taken from t3lib_matchCondition_testcase and modified
for the accordant disposal. Thus, most functionality can be covered and
tested.

Thanks also to Berndhard Kraft, Benni Mack and Helmut Hummel for working
on this feature!


olly
-- 
Oliver Hader
TYPO3 Release Manager 4.3