Calling database:updateschema with short name (like d:u) does not work #684
Comments
|
The functional tests cover that Please provide a full backtrace with the error message you are seeing. |
|
I have already provided the full backtraces. I'll check without any 3rd party extensions. |
|
ah, didn't see the backtraces, as they are folded in (didn't know this before) |
|
hm, what is the exact console version you are using? "user" does not seem to be a valid version number ;) |
|
Whoops, damn clipboards, I've added the version (5.1.1). |
|
ah, got it |
|
I guess That is pretty hard to fix though… |
helhum
changed the title
helhum
added a commit
to helhum/TYPO3-Console
that referenced
this issue
Mar 10, 2018
I order to be able get rid of Configuration/Console/Commands.php in the future, we now unify command registration. All commands can now be registered with "command:name" => [ // Command configuration ] This includes also commands from command controllers. Run level, booting steps, replaces, aliases and vendor name are now part of this configuration. All these are optional with proper defaults in case they are missing. Defaults are: runLevel: full booting steps: none replaces: none aliases: none vendor name: package name (or extension key for TYPO3 extensions) This allows to specify arbitrary aliases also for command controller commands. Even different command names would be possible. Old registration and command controllers registered in $GLOBALS['TYPO3_CONF_VARS']['SC_OPTIONS']['extbase']['commandControllers'] still work, as their registration is migrated to the new format. Because this migrated configuration is merged with existing new configuration, it is possible to just supply some command controller commands with aliases, while not having to register every single command. However all commands within TYPO3 Console are converted to the new format. This will make the transition to native Symfony commands much easier, because now every single command is registered. Fixes: TYPO3-Console#684
helhum
added a commit
to helhum/TYPO3-Console
that referenced
this issue
Mar 10, 2018
I order to be able get rid of Configuration/Console/Commands.php in the future, we now unify command registration. All commands can now be registered with "command:name" => [ // Command configuration ] This includes also commands from command controllers. Run level, booting steps, replaces, aliases and vendor name are now part of this configuration. All these are optional with proper defaults in case they are missing. Defaults are: runLevel: full booting steps: none replaces: none aliases: none vendor name: package name (or extension key for TYPO3 extensions) This allows to specify arbitrary aliases also for command controller commands. Even different command names would be possible. Old registration and command controllers registered in $GLOBALS['TYPO3_CONF_VARS']['SC_OPTIONS']['extbase']['commandControllers'] still work, as their registration is migrated to the new format. Because this migrated configuration is merged with existing new configuration, it is possible to just supply some command controller commands with aliases, while not having to register every single command. However all commands within TYPO3 Console are converted to the new format. This will make the transition to native Symfony commands much easier, because now every single command is registered. Fixes: TYPO3-Console#684
helhum
added a commit
to helhum/TYPO3-Console
that referenced
this issue
Mar 10, 2018
I order to be able get rid of Configuration/Console/Commands.php in the future, we now unify command registration. All commands can now be registered with "command:name" => [ // Command configuration ] This includes also commands from command controllers. Run level, booting steps, replaces, aliases and vendor name are now part of this configuration. All these are optional with proper defaults in case they are missing. Defaults are: runLevel: full booting steps: none replaces: none aliases: none vendor name: package name (or extension key for TYPO3 extensions) This allows to specify arbitrary aliases also for command controller commands. Even different command names would be possible. Old registration and command controllers registered in $GLOBALS['TYPO3_CONF_VARS']['SC_OPTIONS']['extbase']['commandControllers'] still work, as their registration is migrated to the new format. Because this migrated configuration is merged with existing new configuration, it is possible to just supply some command controller commands with aliases, while not having to register every single command. However all commands within TYPO3 Console are converted to the new format. This will make the transition to native Symfony commands much easier, because now every single command is registered. All this also streamlines and hardens the way run levels are defined and allows selecting the correct run level even when the command is called with an alias or in short form. Fixes: TYPO3-Console#684
helhum
added a commit
to helhum/TYPO3-Console
that referenced
this issue
Mar 10, 2018
I order to be able get rid of Configuration/Console/Commands.php in the future, we now unify command registration. All commands can now be registered with "command:name" => [ // Command configuration ] This includes also commands from command controllers. Run level, booting steps, replaces, aliases and vendor name are now part of this configuration. All these are optional with proper defaults in case they are missing. Defaults are: runLevel: full booting steps: none replaces: none aliases: none vendor name: package name (or extension key for TYPO3 extensions) This allows to specify arbitrary aliases also for command controller commands. Even different command names would be possible. Old registration and command controllers registered in $GLOBALS['TYPO3_CONF_VARS']['SC_OPTIONS']['extbase']['commandControllers'] still work, as their registration is migrated to the new format. Because this migrated configuration is merged with existing new configuration, it is possible to just supply some command controller commands with aliases, while not having to register every single command. However all commands within TYPO3 Console are converted to the new format. This will make the transition to native Symfony commands much easier, because now every single command is registered. All this also streamlines and hardens the way run levels are defined and allows selecting the correct run level even when the command is called with an alias or in short form. Fixes: TYPO3-Console#684
|
I saw that you added a test for this which works fine now. Thanks for fixing! |
|
yupp, fixed, tested, released with 5.2.0 :) |
|
Better late than never: I also just confirmed that the issue was fixed, thanks. 👍 |
Sign up for free
to join this conversation on GitHub.
Already have an account?
Sign in to comment
If the DB tables
cf_cache_hashdoes not exist, the whole CLI is broken, not evendatabase:updateschemacan be executed which could create this table. Having that table created (e.g. by a dump import) leads to the next error withcf_extbase_object, after that withcf_extbase_object_tags. After adding these three tablesdatabase:updateschemaworks as expected.Output without cf_cache_hash
Output without cf_extbase_object
Output without cf_extbase_object_tags
The text was updated successfully, but these errors were encountered: