Bug #61254
closedparseUserFuncArguments getting no single arguments to user_functions in conditions
0%
Description
Example: installed version 1.0.0 of extension rgnewsimg, Typo3 6.2.4 on PHP 5.4.31 (ubuntu 12.4)
@includeLibs.rgnewsimg = EXT:rgnewsimg/condition.php
[userFunc = user_rgnewsimg(0)]
...
[global]
[userFunc = user_rgnewsimg(1)]
...
[global]
@
Typoscript code:
@includeLibs.rgnewsimg = EXT:rgnewsimg/condition.php
[userFunc = user_rgnewsimg(0)]
...
[global]
[userFunc = user_rgnewsimg(1)]
...
[global]
@
as per extension manual, which is working fine with prior versions of Typo3 up to 6.1.7 .
Frontend Result is an Exception: 11 TYPO3\CMS\Core\Error\ErrorHandler::handleError(2, "Missing argument 1 for user_rgnewsimg()", "/httpdocs/typo3conf/ext/rgnewsimg/condition.php", 31, array)
10 user_rgnewsimg()
9 call_user_func_array("user_rgnewsimg", array)
8 TYPO3\CMS\Core\Configuration\TypoScript\ConditionMatching\AbstractConditionMatcher::evaluateConditionCommon("userFunc", "user_rgnewsimg(0)")
...
Workaround:
Typoscript code:
@includeLibs.rgnewsimg = EXT:rgnewsimg/condition.php
[userFunc = user_rgnewsimg(0,0)]
...
[global]
[userFunc = user_rgnewsimg(1,1)]
...
[global]
@
does work, so if more than one argument is given, only the 2nd and following are delivered to the user_function.
Updated by Markus Klein about 10 years ago
- Status changed from New to Closed
Closing as duplicate of #61256