Project

General

Profile

Actions

Feature #61489

closed

Add AbstractCondition to implement custom TypoScript Conditions

Added by Benni Mack about 10 years ago. Updated about 7 years ago.

Status:
Closed
Priority:
Should have
Assignee:
Category:
TypoScript
Target version:
Start date:
2014-09-09
Due date:
% Done:

100%

Estimated time:
PHP Version:
Tags:
Complexity:
Sprint Focus:

Description

In order to streamline conditions and make
TypoScript conditions more flexible, an abstract class
AbstractCondition is introduced. Any class can extend
this abstract class, and TypoScript seamlessly calls
the class's main function that can completely flexibly
deal with the value that is set after the class.

possible conditions are:

[BigCompanyName\TypoScriptLovePackage\BennisTypoScriptCondition]

[BigCompanyName\TypoScriptLovePackage\BennisTypoScriptCondition = 7]

[BigCompanyName\TypoScriptLovePackage\BennisTypoScriptCondition = 7, != 6]

where the TypoScript Condition can deal with =/!= etc by itself.

Additionally, this change fixes one bug, where the
AbstractConditionMatcher would check on a condition name
and would not match, then there is an additional run.


Related issues 3 (0 open3 closed)

Related to TYPO3 Core - Feature #20450: Use t3lib_div::callUserFunction in typoscript userFunc conditionClosed2009-05-18

Actions
Related to TYPO3 Core - Feature #63600: Add custom TypoScript Conditions also in backendClosed2014-12-05

Actions
Related to TYPO3 Core - Task #94387: Remove unused ext:core AbstractConditionClosed2021-06-19

Actions
Actions

Also available in: Atom PDF