TYPO3-Console

Changes since 3.1.0

• Fix binary for non composer mode

Full list of changes.
TER release page

Changes since 3.0.0

• Improved documentation of some commands
• Fixed a bug in database:export command
• Minor cleanup and stability improvements
• Nicer error and exception output
• Composer mode improvements (make it possible to disable default bin script in favor of composer bin script generation)

Full list of changes.
TER release page

After over three months of development, we are proud to present a new major version of TYPO3 Console. It has:

• Many new features
• Plenty of usability improvements
• Tons of bugfixes
• A few breaking changes

Features

• TYPO3 Console now comes with a composer plugin, which removes the need for custom script sections in composer.json
• TYPO3 Console auto activates itself in all scenarios. No need to go to the extension manager any more.
• Extensions can add lowlevel commands via Configuration/Commands.php
• Help output is now colorized and ordered and is also shown when the script is called without arguments
• TYPO3 8.x compatibility
• Improved documentation with a auto generated command reference

New or updated commands

• Many new extension:* commands like extension:setup, extension:setupactive and renamed commands like extension:activate
• Added install:fixfolderstructure to create the required TYPO3 folder structure so that e.g. the typo3temp folder can always be discarded and recreated during deployment
• Reworked install:generatepackagestates command to be easier to configure (through environment variable) and more reliable
• New backend:lockforeditors command, which locks the backend only for editors
• A new set of configuration commands, which makes it not only possible to remove, but also to view and change TYPO3 configuration from command line
• New database:import/export commands to interact with the (MySQL) database without the need to specify credentials. It also features an interactive mode which opens a MySQL console.
• Added a --verbose switch to database:updateschema to be able to see the executed SQL during the process.

Other Changes

• Major code cleanup (now requiring PHP 5.5 and TYPO3 7.6)
• Vastly improved command descriptions and help texts
• Multiple usability improvements (e.g. a streamlined installation process)
• Completely adopted Github pull request workflow. All changes are now pushed and tested before merged
• New Team member @mbrodala, with merge permissions. This enables peer reviews for enhanced quality

Breaking changes

• The ./typo3cms script is now a symlink and works only in dedicated TYPO3 directory. This is in line with how composer works and a preparation for having a real composer bin script. Other scripts will stop working.
• The install:generatepackagestates command now takes the to be active TYPO3 packages from an environment variable and not the composer.json any more. Every third party extension is now considered active.
• Composer script section code has been removed.
• Many extension: commands have been renamed for better and more consistent naming
• Internal API changes (e.g. in Schema Update Service). This has no effect on commands, but only if the API is used otherwise

Further changes

The full change log can be examined on Github

This version includes only a few bugfixes compared to version 1.3.0.

There are no braking changes, so upgrading from 1.3.0 should be straightforward.

Starting with this version, we will now follow more clearly a:

Semantic versioning strategy

Versions 2.0.x

Bugfixes will be released by increasing the bugfix version (e.g. going from 2.0.1 to 2.0.2).

Versions 2.x.x

When features are added, that do not break backwards compatibility,
the minor version is increased (e.g. going from 2.1.1 to 2.2.0).

New major versions

When braking changes are incorporated, a new major version will be released.
Dropping support for previously supported TYPO3 versions is now (correctly) considered
to be a breaking change.

Conclusion:

Users with TYPO3 versions 7.6 and above are strongly advised to switch to typo3 console 2.0.0 and higher.
Please set the requirement in your root composer.json files to "helhum/typo3-console": "^2.0.0"!

Users with TYPO3 versions 6.2.x must stay with typo3 console 1.1.x for now.
Please set the requirement in your root composer.json files to "helhum/typo3-console": "~1.1.3"!