Bug #58138
closed
CSRF with registerModule and navFrameScript
Added by Falk Aaron about 10 years ago.
Updated over 5 years ago.
Description
How to use \TYPO3\CMS\Extbase\Utility\ExtensionUtility::registerModule with navFrameScript parameter?
It does not work, as the modules are loaded before the BE_USER, so BackendUtility::getModuleUrl does only retrieve a "dummyToken".
May you help me out?
- Status changed from New to Needs Feedback
You want to have a custom navFrame, right? How does the URL to your navigation must look like? is it mod.php?M=<moduleName> ... ?
Can you also show me how you tried to register this navigation component?
Thanks
'navFrameScript' => BackendUtility::getModuleUrl('RolRkchannelRkchannel_RolRkchannelM3', array('tx_rolrkchannel_rolrkchannelrkchannel_rolrkchannelm3[action]'=> 'tree'))
Thats how i configure the navFrameScript. It's not working like that.
- Status changed from Needs Feedback to Accepted
- Status changed from Accepted to Under Review
Falk Aaron wrote:
'navFrameScript' => BackendUtility::getModuleUrl('RolRkchannelRkchannel_RolRkchannelM3', array('tx_rolrkchannel_rolrkchannelrkchannel_rolrkchannelm3[action]'=> 'tree'))
Thats how i configure the navFrameScript. It's not working like that.
Please check the patch in the review system.
Apply the patch and configure the navigation as follows:
'navigationFrameModule' name of the module that is loaded in the navigation frame
'navigationFrameModuleParamters' additional parameters (if needed and specified)
- Status changed from Under Review to Resolved
- % Done changed from 0 to 100
- Status changed from Resolved to Under Review
Patch set 1 for branch TYPO3_6-2 of project Packages/TYPO3.CMS has been pushed to the review server.
It is available at http://review.typo3.org/32676
- Status changed from Under Review to Resolved
Seems the patch made it's way only in TYPO3 Version 7 but not in the 6.2 Branch. Just as info.
Two messages above it mentions the 6.2 backport. This change is in 6.2 as well.
Wouter Wolters wrote:
Two messages above it mentions the 6.2 backport. This change is in 6.2 as well.
Yes, it absolutely is in 6.2 as well!
I see, sorry for confusion.
Functionality seems just being in another file - not in ModuleLoader.php but in MenuModuleView.php
- Status changed from Resolved to Closed
Also available in: Atom
PDF