Bug #60381

Local object configuration ignored in CLI context

Added by Mathias Brodala over 5 years ago. Updated almost 4 years ago.

Status:
New
Priority:
Must have
Category:
Extbase
Target version:
-
Start date:
2014-07-18
Due date:
% Done:

0%

TYPO3 Version:
6.2
PHP Version:
Tags:
Complexity:
Is Regression:
No
Sprint Focus:

Description

Local object configuration (module.tx_myext.objects in addition to config.tx_extbase.objects) is ignored when executing command controllers through the Extbase CLI script.

This is due to the fact that at the time object configuration is processed in Bootstrap::configureObjectManager(), the name of the extension is not yet available. It is only available after the Mvc\Cli\RequestBuilder has built the CLI request object based on the command to execute.

The only workaround ATM is to register an own CLI script which basically copies the CommandLineLauncher.php from Extbase but invokes Bootstrap with the extensionName as configuration argument.

My suggestion now is that in Mvc\Cli\RequestHandler::handleRequest() object registration is performed once more. Any other ideas?


Related issues

Related to TYPO3 Core - Feature #68837: Allow closures on command line scripts Closed 2015-08-07
Duplicated by TYPO3 Core - Bug #61995: Extbase: Overwriting objects by TS not working in CommandController? Closed 2014-10-01

History

#1 Updated by Mathias Schreiber almost 4 years ago

  • Target version deleted (next-patchlevel)

Also available in: Atom PDF