Local object configuration ignored in CLI context
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?
Updated by Benni Mack over 1 year ago
- Status changed from New to Closed
we've deprecated (v9) and removed (v10) the CLI requests of Extbase as we're promoting to use the simplified Symfony Console Commands where somebody can bootstrap Extbase to fit their needs - especially due to a lot of "lets assume we take the first tree root on CLI" logic, which does not work as expected. Same goes for the TypoScript loading, and ConfigurationManager.
I hope that's ok with you, if not ping me on slack, and I can re-open this issue.