Project

General

Profile

Actions

Bug #69170

closed

Context Menu Typoscript: ###ID### is not replaced by openCustomUrlInContentFrame

Added by Christian Seifert over 9 years ago. Updated about 7 years ago.

Status:
Closed
Priority:
Must have
Category:
Backend API
Target version:
Start date:
2015-08-18
Due date:
% Done:

100%

Estimated time:
TYPO3 Version:
6.2
PHP Version:
5.5
Tags:
Complexity:
easy
Is Regression:
No
Sprint Focus:

Description

The intention is to add a new click menu in the page tree redirecting to a backend module with the selected page uid.

Following [[https://docs.typo3.org/typo3cms/CoreApiReference/6.2/JavaScript/UsingExtjs/PageTree/?highlight=click#context-menu-custom-callbacks]], you can use "callbackAction = openCustomUrlInContentFrame" and configure the URL in "customAttributes.contentUrl". In 6.2 you can use the function getModuleUrl to generate the URI:

$clickMenuUrl = \TYPO3\CMS\Backend\Utility\BackendUtility::getModuleUrl(
    'txmymodule',
    array('id' => '###ID###')
);

So ###ID### is expected to be replaced by the according Ext.js function "openCustomUrlInContentFrame" (actions.js).
Unfortunately, the parameters of the generated URL are URI encoded, so that there is no chance to replace ###ID###. It is submitted as %23%23%23ID%23%23%23 instead.
Automatical replacement of the dynamic ID parameter doesn't seem to work at the moment.

Actions

Also available in: Atom PDF