Bug #63307
closedEpic #68075: Remove ExtJS from backend
Page tree - context menu with predefined callback in 6.2
0%
Description
According to the page http://docs.typo3.org/typo3cms/CoreApiReference/JavaScript/UsingExtjs/PageTree/Index.html, it is possible to define a predefined callback in a custom action using the following code :
720 = ITEM 720 { name = someCustomeAction label = LLL:EXT:extension/locallang.xml:someCustomeAction icon = ' . \TYPO3\CMS\Core\Utility\GeneralUtility::locationHeaderUrl(\TYPO3\CMS\Core\Utility\ExtensionManagementUtility::extRelPath($_EXTKEY) . 'ext_icon.gif') . ' spriteIcon = displayCondition = callbackAction = openCustomUrlInContentFrame customAttributes.contentUrl = mod.php?M=web_WorkspacesWorkspaces&id=###ID### }
The problem on v6.2 (not tested on v4.x, but I suppose it works with v4.5) is that the ###ID### marker is not replaced, but also can corrupt the URL if placed before the "M" parameter (in that case it removes the moduleToken parameter).
Files
Updated by Fabrice Morin almost 10 years ago
It's a regresion because of AbstractContextMenuDataProvider->replaceModuleTokenInContentUrl() method.
Call to parse_url() function considers ###ID### as a URL fragment, so it is removed from URL parameters when URL is rebuilt.
Updated by Henning Bopp over 9 years ago
- File quickfix-replaceModuleTokenInContentUrl.diff quickfix-replaceModuleTokenInContentUrl.diff added
Came across that one while trying to use the marker for self-made context menu content.
As I need this function I wrote a litte quickfix (based on TYPO3 CMS 6.2.9). Thanks to Fabrice for pointing out the technical problem.
See diff-File attached for fix.
Updated by Christian Heindl over 9 years ago
Quickfix works also for me, should be integrated in any form in the core.
Updated by Benni Mack over 7 years ago
- Status changed from New to Needs Feedback
we've reworked the ContextMenu in 8.6. Can you see if this helps?
Updated by Riccardo De Contardi over 7 years ago
- Status changed from Needs Feedback to Closed
No feedback within the last 90 days => closing this issue.
If you think that this is the wrong decision or experience the issue again or have more info about how to reproduce it, then please reopen it or open a new issue with a reference to this one. Thank you.