TYPO3-Console

Bugfixes

• Fix bug in relation with helhum/typo3-composer-setup

Further changes

The full change log can be examined on Github
The extension can be found at the TER release page.

Features

Improved TYPO3 setup

The complete setup process has been rewritten from scratch.
Most apparently the output is now more compact and looks nicer.

What you can also grasp from the terminal cast above, is that it is now possible
to hand over all argument for the setup process as environment variables.

Here is the complete list of default environment variables:

• TYPO3_INSTALL_DB_USER
• TYPO3_INSTALL_DB_PASSWORD
• TYPO3_INSTALL_DB_HOST
• TYPO3_INSTALL_DB_PORT
• TYPO3_INSTALL_DB_UNIX_SOCKET
• TYPO3_INSTALL_DB_USE_EXISTING
• TYPO3_INSTALL_DB_DBNAME
• TYPO3_INSTALL_ADMIN_USER
• TYPO3_INSTALL_ADMIN_PASSWORD
• TYPO3_INSTALL_SITE_NAME
• TYPO3_INSTALL_SITE_SETUP_TYPE

Just like in previous versions, if you use the --no-interaction flag, only required arguments need to be set. For all optional arguments the default values will be used then.

Last but not least, the whole setup process is now defined in a Yaml file. This means adding new arguments or even completely new steps is a matter of changing configuration.

Overriding the default configuration file is possible by providing the path to your own file with the TYPO3_INSTALL_SETUP_STEPS environment variable. In this file you can decide to either import the default configuration and amend it to fit your needs (e.g. using different environment variables names or even hard code know values), or create a completely customized setup workflow, or even run different setup steps in different scenarios.

We are very much looking forward to what you are going to build with this feature.

Deprecations

• The CommandDispatcher::createFromComposerRun() API changed, so that the first Composer event argument is obsolete. Passing it anyway will continue to work, but is deprecated.

Further changes

The full change log can be examined on Github
The extension can be found at the TER release page.

Bugfixes

• Fix TYPO3 dependency declaration in ext_emconf.php (only affects TYPO3 Extension, not the composer package)

Further changes

The full change log can be examined on Github
The extension can be found at the TER release page.

Bugfixes

• Compatibility with TYPO3 9.3.0
• Fix bug with cache clearing in extension:activate command

Further changes

The full change log can be examined on Github
The extension can be found at the TER release page.

Bugfixes

• Mark as compatible with PHP 7.2

Further changes

The full change log can be examined on Github
The extension can be found at the TER release page.

Features

• Add --json to configuration:set command
  This allows setting array values by providing a JSON string:
  typo3cms EXTCONF/lang/availableLanguages '["de", "fr"]' --json
typo3cms configuration:set SYS/caching/cacheConfigurations/cache_pages/options '{"compression": true}' --json

Bugfixes

• Use --opt for mysqldump in database:export command
• Allow all characters for admin users in backend:createadmin command
• Allow empty parameter annotations

Further changes

The full change log can be examined on Github
The extension can be found at the TER release page.

Bugfixes

• Mark as compatible with TYPO3 9.2
• Correctly evaluate --no-interaction for install:setup
• Allow phpdbg PHP SAPI

Further changes

The full change log can be examined on Github
The extension can be found at the TER release page.

Features

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.

This also means, that aliases can be added as well to command controller commands.

Old registration and command controllers 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.

Bugfixes

• Provide compatibility with latest TYPO3 master
• Harden class loading in non composer mode

Further changes

The full change log can be examined on Github
The extension can be found at the TER release page.

Bugfixes

• Fix TYPO3 compatibility declaration in ext_emconf.php
• Fix and optimize generated command reference manual

Further changes

The full change log can be examined on Github
The extension can be found at the TER release page.

Features

• TYPO3 Console is now compatible with TYPO3 9.1 and above. Compatibility with TYPO3 9.0 has been dropped. Users are advised to upgrade to TYPO3 9.1, or need to stick to TYPO3 Console 5.0.4 in case this is not possible.
• Slightly improve performance for command execution and improve execution compatibility compared to TYPO3 cli binary.

Further changes

The full change log can be examined on Github
The extension can be found at the TER release page.

Bugfixes

• Fixes a bug in the installer, which called the last install step twice. This could lead to two root pages being created when setup type "site" was selected
• Fixes command run on Windows in composer build time context
• Fixes command registration for extension in composer mode. Extensions not installed via composer, are now also detected and their commands shown

Further changes

The full change log can be examined on Github
The extension can be found at the TER release page.

Bugfixes

• Fixes a incompatibility with symfony/process version that is shipped and used with composer and triggered by typo3-console/composer-auto-setup, when trying to setup a TYPO3 instance within a composer install process.
• Output command method return values again, but make clear that this is deprecated functionality
• Fix an issue with not updating the typo3cms binary when upgrading TYPO3 Console from 4.x to 5.x in non composer mode

Further changes

The full change log can be examined on Github
The extension can be found at the TER release page.

Bugfixes

• Fixes an issue with class loading in non composer mode when extension is not activated in extension manager

Further changes

The full change log can be examined on Github
The extension can be found at the TER release page.

Bugfixes

• Includes a fix for typo3-console/composer-auto-setup to work again

Further changes

The full change log can be examined on Github
The extension can be found at the TER release page.

General remarks

We're delighted to present the next generation of TYPO3 command line tooling.
For TYPO3 Console 5.0 the complete application layer (how commands are found and executed)
has been refactored to use Symfony Console.

This means TYPO3 Console 5.0 is faster, more consistent, more compatible and more future proof than ever before.

Features

• TYPO3 Console can now show and execute native Symfony Commands, that are
  registered for a TYPO3 instance. This seemingly small change comes with a whole bunch of improvements:
  • Command controller commands are now on the fly converted to native Symfony console commands.
  • Every command has the option -h ahich shows the help for a command (e.g. use typo3cms cache:flush -h to see the help for the cache flush command).
  • Synopsis (short syntactical info for the command) is shown for commands if something goes wrong.
  • Also authors of new commands get full control over the command name.
  • It is even possible to define aliases for commands, which will make renaming commands much easier in the future.
  • You can now use abbreviated command names. Instead of typing ./typo3cms install:generatepackagestates, you can now also type ./typo3cms i:gen and Symfony will find
    the right command for you as long there is only one matching command.
  • If you still miss-type a command, you will see a list of commands that you probably meant to type.
  • If an exception occurs, you only see the exception message, unless you called the command with -v
  • -v[vv] option is now globally available to increase verbosity
  • Argument and option parsing is now all done by Symfony Console, which makes this part more robust and less error prone
• When installing TYPO3 Console along with TYPO3 8.7 with Composer, you now only have one binary available for cli commands (previously you had typo3 and typo3cms). Since TYPO3 Console 5 has become a complete replacement for the TYPO3 built in command line layer, only typo3cms is left.
• Of course TYPO3 Console is now also compatible with TYPO3 9.0.0 and PHP 7.2
• A new command backend:createadmin was introduced, which allows to add admin users to a TYPO3 instance
• Many TYPO3 Console commands (especially installing or upgrading TYPO3), call other commands in sub processes. It is now possible to pass a custom php.ini file to these processes, by setting the PHP_INI_PATH environment variable.

And many more cleanups, streamlining in the code base as well as the "UI" to make interacting with and creating new commands a more pleasant experience.

Breaking Changes

The good news here is, that the majority of commands will work just like before!
Nevertheless some things needed to be changed in a way that could break current workflows, scripts or commands.

The most important change is, that PHP 5 and TYPO3 7.6 will not be supported with TYPO3 Console 5.
If you need these, you can still use version 4.9.x, which is still maintained and will receive bugfixes, but no new features any more.

• Functionality that has been deprecated before has been removed, most notably here: the dummy extension that was installed by default with composer is now gone. So no need to specify that in your composer.json any more
• The setup type "dist" has been removed from install:setup
• Support for the old dbal extension has been removed
• Our own autocomplete implementation has been removed, because there are better implementations available which work for all Symfony Console applications, so now also for TYPO3 Console
• The typo3 binary is not installed with Composer any more (you won't need it anyway when using TYPO3 Console)
• The command database:export now calls mysqldump with option --single-transaction. This means if you need a consistent state of the dump, make sure all your tables use InnoDB engine (not MyIsam).

Deprecations

A few things are deprecated, which means they still work, but won't work any more in the next major release of TYPO3 Console.

• Symfony has a clear distinction between arguments and options. TYPO3 Command controllers do not have that. Command method arguments can always be used as both, arguments or as options. In order to be consistent and integrate both in a better way, calling arguments with their option name or options as arguments are deprecated.

E.g. arguments as options:
extension:activate --extension-keys foo,bar is deprecated. Use extension:activate foo,bar instead.

E.g. options as arguments:
cache:flush 1 is deprecated. Use cache:flush --force instead

• The commands extension:activate and extension:deactivate are deprecated when TYPO3 is Composer managed (Composer mode). Use install:generatepackagestates to generate the active list of extensions automatically from the composer installed extensions and then extension:setupactive to set all active extensions up in your TYPO3 instance.
• The command extension:removeinactive is deprecated. Only install the extensions you need, instead of installing the code and removing it afterwards.
• For install:setup the option --non-interactive is deprecated. Use the global option --no-interaction instead
• For install:generatepackagestates the option --activate-default is deprecated for Composer managed TYPO3. Instead require the TYPO3 core extensions you need in your project using composer.
• For scheduler:run the option --task-id is deprecated. Use --task instead.
• To avoid naming conflicts, command controller commands optionally made available through their "full identifier" which is vendor:namespace:command. But commands were always callable with this full identifier. This is now still possible but deprecated. Command authors should avoid naming conflicts, or declare that their command replaces a previous command with the same name. If naming conflicts still occur however, the conflicting commands will still be prefixed with the vendor (the package name).

Further changes

The full change log can be examined on Github
The extension can be found at the TER release page.

Bugfixes

• Fix extension:dumpautoload command
• Fix a bug in upgrade:all command, which caused it to fail with upgrade wizards that download and install extensions
• Fix a regression caused by TYPO3 8.7.9, which "suddenly" needs a database connection when building TCA cache

Further changes

The full change log can be examined on Github
The extension can be found at the TER release page.

Bugfixes

• Make extension:dumpautoload a low level command

Further changes

The full change log can be examined on Github
The extension can be found at the TER release page.

Bugfixes

• Fix regression in cache:flush command when being executed low level
• Output error messages if they occur when executing database:updateschema

Further changes

The full change log can be examined on Github
The extension can be found at the TER release page.

General remarks

This release marks the feature freeze of the 4.x branch of TYPO3 Console. All new features will only be implemented in the upcoming 5.x versions. Necessary bugfixes will be added to 4.9.x versions however.

Features

• Added option --skip-extension-setup for install:setup command. This option is enabled by default in non composer setups. The installation finishes with all TYPO3 core extensions set up that are marked as required and as factory default. All local extensions are marked as inactive. Don't use this option in composer setups, when you want the setup to exactly reflect the defined state (all required core extensions active and all third party extensions are active).
• Command controllers can now be placed in subfolders, thus can have an arbitrary number of namespace parts.

Further changes

The full change log can be examined on Github
The extension can be found at the TER release page.

Bugfixes

• Fix regression in cache:flush command

Further changes

The full change log can be examined on Github
The extension can be found at the TER release page.