[BUGFIX] Fix condition for USERDEF2 in procesItemState 41/49241/3
authorStefan Bürk <stefan.buerk@impactmedia.de>
Thu, 28 Jul 2016 10:21:27 +0000 (12:21 +0200)
committerSusanne Moog <susanne.moog@typo3.org>
Thu, 28 Jul 2016 19:54:14 +0000 (21:54 +0200)
Fix a wrong condition in the procesItemState method for MENU handling
for the USERDEF2 itemstate, so it would not be ignored anymore.

Initializing the USERDEF2conf was never done, even if one or more
USERDEF2 item states was found, because the condition was checking
for NULL === TRUE, which will never be TRUE.

Resolves: #77284
Releases: master, 7.6
Change-Id: I16c1d21f03c9aa3565744cae90b7f0cb487ec009
Reviewed-on: https://review.typo3.org/49241
Tested-by: Bamboo TYPO3com <info@typo3.com>
Reviewed-by: Markus Klein <markus.klein@typo3.org>
Tested-by: Markus Klein <markus.klein@typo3.org>
Reviewed-by: Wouter Wolters <typo3@wouterwolters.nl>
Reviewed-by: Susanne Moog <susanne.moog@typo3.org>
Tested-by: Susanne Moog <susanne.moog@typo3.org>

index 817ac77..73c7c50 100644 (file)
@@ -1496,7 +1496,7 @@ abstract class AbstractMenuContentObject
             foreach ($NOconf as $key => $val) {
                 if ($this->isItemState('USERDEF2', $key)) {
                     // If this is the first active, we must generate USERDEF2.
-                    if ($USERDEF2conf) {
+                    if ($USERDEF2conf === null) {
                         $USERDEF2conf = $this->tmpl->splitConfArray($this->mconf['USERDEF2.'], $splitCount);
                         // Prepare active rollOver settings, overriding normal active settings
                         if (!empty($this->mconf['USERDEF2RO'])) {