---
title: "Feature: #61489 - Allow own TypoScript Condition implementations"
manual: "TYPO3 Core Changelog"
version: "main"
permalink: "https://docs.typo3.org/permalink/changelog:feature-61489"
source: "Changelog/7.0/Feature-61489-AbstractTypoScriptCondition.rst"
modified: "2026-09-15T10:46:36+00:00"
---

# Feature: #61489 - Allow own TypoScript Condition implementations

See [forge#61489](https://forge.typo3.org/issues/61489)

## Description

It is now possible to add own TypoScript conditions via a
separate API.

An extension / package can now ship an implementation of a new
abstract class AbstractCondition. Via the existing TypoScript
Condition Syntax the class is called by the simple full namespaced
class name.
The class's main function "matchCondition" can flexibly evaluate
any parameters given after the class name.

Usage:

```typoscript
[BigCompanyName\TypoScriptLovePackage\BennisTypoScriptCondition]

[BigCompanyName\TypoScriptLovePackage\BennisTypoScriptCondition = 7]

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

[BigCompanyName\TypoScriptLovePackage\BennisTypoScriptCondition = {$mysite.myconstant}]
```

where the TypoScript Condition class deals with =/!= etc itself.

## Impact

If you've previously used the "userFunc" condition, you are encouraged
to use this new API for your own TypoScript conditions.