[BUGFIX] Mixed up parameters in call to replaceMarkersInWhereClause 12/23012/3
authorAnja Leichsenring <aleichsenring@ab-softlab.de>
Fri, 9 Aug 2013 15:01:47 +0000 (17:01 +0200)
committerWouter Wolters <typo3@wouterwolters.nl>
Fri, 9 Aug 2013 15:51:07 +0000 (17:51 +0200)
The patch for #21892 breaks functionality due to a mixed up parameters
list in BackendUtility.

Resolves: #50976
Releases: 6.2
Change-Id: I46585d995ec345561f605a19202d91614ad5e8d8
Reviewed-on: https://review.typo3.org/23012
Reviewed-by: Philipp Gampe
Tested-by: Philipp Gampe
Reviewed-by: Wouter Wolters
Tested-by: Wouter Wolters
typo3/sysext/backend/Classes/Utility/BackendUtility.php

index 58ba1bd..019b2ac 100644 (file)
@@ -3069,7 +3069,7 @@ class BackendUtility {
                $foreign_table = $fieldValue['config'][$prefix . 'foreign_table'];
                $rootLevel = $GLOBALS['TCA'][$foreign_table]['ctrl']['rootLevel'];
                $fTWHERE = $fieldValue['config'][$prefix . 'foreign_table_where'];
-               $fTWHERE = static::replaceMarkersInWhereClause($fTWHERE, $field, $TSconfig, $foreign_table);
+               $fTWHERE = static::replaceMarkersInWhereClause($fTWHERE, $foreign_table, $field, $TSconfig);
                $wgolParts = $GLOBALS['TYPO3_DB']->splitGroupOrderLimit($fTWHERE);
                // rootLevel = -1 means that elements can be on the rootlevel OR on any page (pid!=-1)
                // rootLevel = 0 means that elements are not allowed on root level