Bug #24232
closed
tslib_menu and tslib_Xmenu calls stdwrap on $GLOBALS['TSFE']->cObj instead of this->parent_cObj
0%
Description
Situation:
When having content elements of type "menu/sitemap" and using the subtype "Menu of these pages" then tslib_menu parses the values of config special.value with tslib_content.
Problem:
tslib_menu and tslib_Xmenu calls stdwrap on $GLOBALS['TSFE']->cObj instead of $this->parent_cObj which is not necessarily the same. tslib_content is not a singleton. $GLOBALS['TSFE']->cObj->data holds the data of the current page, whereas $this->parent_cObj->data holds the data of the calling content element or page
Solution:
Replace every occurence of $GLOBALS['TSFE']->cObj with $this->parent_cObj.
Attached Patch fixes the Problem.
(issue imported from #M16601)
Files
Updated by
Updated by Ernesto Baschny almost 14 years ago
Only the two stdWrap calls was indeed wrongly changed in #16446 (rev.
9474 [1]).
The calls to ->callUserFunction and ->exec_getQuery were
always referencing GLOBALS['TSFE'] so this change also adds a new
"feature" in that we support now the current ->data in these places as well.
(e.g. callUserFunction can now access the correct "parent" cObject,
which is passed on to the userFunction class as member variable
$this->cObj).
Committed it to trunk rev. 9733.
[1] http://forge.typo3.org/repositories/revision/typo3v4-core/9474
Updated by