#16974Provide general AJAX call handler for backend functions/modules with mID technique
Description
This is a feature request for TYPO3 4.2.
To avoid that every backend module has to create and use its own AJAX handler, a general handler class is required. According to the eID of the TYPO3 front-end there shall be a mID (module identifier) for back-end purpose.
The stack to register and enable a module and an action could look like this:
$TYPO3_CONF_VARS[‘BE’][‘mID_include’][<package>][<action>] = array(<br> ‘handler’ => ‘<handler>‘,<br> ‘required’ => array(’<php-class-file-1>‘, ‘<php-class-file-2>‘),<br> ‘encodeUTF8’ => <boolean><br>);</boolean></php-class-file-2></php-class-file-1></handler></action></package>
The extended Backus-Naur (eBNF) form of the key ‘handler’ could look like this:
handler ::= <static> | <instance><br>static ::= <class> “::” <function><br>instance ::= (<variable>|<class>) “->” {<object> “->”} <method><br>variable ::= “$” <valid-php-identifier><br>class ::= <valid-php-identifier><br>object ::= <valid-php-identifier><br>function ::= <valid-php-identifier><br>method ::= <valid-php-identifier><br>(* @see <a href="http://www.php.net/manual/en/language.variables.php" target="_blank" rel="noreferrer">http://www.php.net/manual/en/language.variables.php</a> *)<br>valid-php-identifier = ? chars that are valid in PHP for variables ?</valid-php-identifier></valid-php-identifier></valid-php-identifier></valid-php-identifier></valid-php-identifier></method></object></class></variable></function></class></instance></static>
Currently affected parts of the TYPO3 core:
- Kasper’s new backend functionalities
- AJAX page tree and file tree
- Inline Relational Record Editing
This feature could be used by any backend function of individual user extensions.
(issue imported from #M4966)
Reviews 0
No change resolves or names this issue in its commit message, and no comment links one.