TYPO3-Console

Changes since 4.2.0

Bugfixes

• Bugfix for Windows users
• Bugfix in install:setup command

Full list of changes.
TER release page

New Features (since version 4.1.0)

• It is now possible to exclude database tables when using the database:export command
• Composer packages (not only TYPO3 extensions) can now define console commands. This makes it possible to create micro packages with just one command.
• Compatibility with TYPO3 8.6.x

Additionally a lot of cleanup was done to pave the way for groundbreaking new features in upcoming releases.

Bugfixes

• The command database:import now also works when the database is empty.

Further changes

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

Changes since 4.1.1

Bugfixes

• Fix a bug in database:updateschema command that can lead to data loss, when auto_increment fields needs to be changed
• Adapt CLI user handling to latest changes in master. All tests are now green again.
• Show column names again for database:import --interactive command (thx @stucki)

Full list of changes.
TER release page

Changes since 3.5.1

Bugfixes

• Fix a bug in database:updateschema command that can lead to data loss, when auto_increment fields needs to be changed

Full list of changes.
TER release page

Changes since 1.1.8

Bugfixes

• Fix a bug in database:updateschema command that can lead to data loss, when auto_increment fields needs to be changed

Full list of changes.
TER release page

Changes since 4.1.0

Bugfixes

• Fix a cache related bug in extentsion:activate command

Full list of changes.
TER release page

New Features (since version 4.0.0)

• The command install:fixfolderstructure now also creates the needed directories for all active extensions
• Compatibility with TYPO3 8.5.x
• Command arguments that can be separated by comma, get their value automatically trimmed and filtered. This means commands like extension:activate "foo, bar, baz" now work nicely
• The command extension:setupactive is now multiple times faster, because the database schema operation fixes have been reduced to one call instead of one per extension. Regarding the database schema, calling extension:setupactive is now functionally equivalent to calling database:updateschema "safe" (or database:updateschema "safe" or database:updateschema "*.change,*.add,table.clear", which are as well functionally equivalent). This means, that database:updateschema calls in the deployment process can be safely removed in favor of just calling extension:setupactive

Bugfixes

• The commands extension:setupactive and extension:activate have been fixed to avoid potential data loss (see #382).

Further changes

The full change log can be examined on Github
TER release page

Changes since 4.0.0

Bugfixes

• Fix a small mistake in database:updateschema command

Full list of changes.
TER release page

After over three months of development since release of 3.0.0, we are proud to present a new major version of TYPO3 Console. It again comes with new features, usability improvements, a lot of bugfixes and very few breaking changes. It is now better prepared than ever for TYPO3 8.4.0 and higher.

Compared to the 3.5.1 release only a few, but still nice features have been added.

New Features (since version 3.0.0)

• Command to generate an autocomplete script
• The required cli user is now auto created. Basically TYPO3 Console adds it, when it is required by TYPO3. This completes the auto activation feature which was started in 3.0.0, so now the console is now available once the code is installed
• The database:updateschema command has been reworked. The main goal was full TYPO3 8.x support (doctrine support), but user experience has also been improved.
• database:updateschema now by default executes all "safe" schema update operations
• database:updateschema now has a --dry-run option to preview potential schema updates
• helhum/typo3-console is now a composer library, not an extension. A dummy extension is installed now, but this is deprecated and will be removed with the next major version and can be disabled by composer configuration.
• extension:list command to list available extensions in the system

Breaking changes

• The ./typo3cms script is now a regular composer binary. This means if you install helhum/typo3-console with composer, it is installed in the bin directory defined the root composer.json (by default vendor/bin). Previously it was always installed along side with the composer.json file. If you use the console as TYPO3 extension, the script will still be installed in the TYPO3 root directory.
• Deprecated commands have been removed. Now the extension:* commands differ from the ones in TYPO3
• The ext_emconf.php files have been removed from the git repository

Further changes

The full change log can be examined on Github
TER release page

Changes since 3.5.0

Bugfixes

• Fix a small error in database:updateschema command
• Disable database:updateschema command in TYPO3 8.4 and higher to avoid potential data loss. The next version of TYPO3 Console will fully support this TYPO3 version

Full list of changes.
TER release page

Changes since 1.1.7

Features

• Add install:fixfolderstructure command
• Make help the default command
• Add verbose output to schema update

Bugfixes

• Various bugfixes

Full list of changes.
TER release page

Changes since 3.4.1

Features

• New command to list extensions (active, inactive or all)
• Compatibility with TYPO3 8.4.0

Bugfixes

• Fix an error that installed dummy extension files into project root
• Fix cache:flush command to not truncate a hardcoded list of tables, but to use TYPO3 API

Full list of changes.
TER release page

Changes since 3.4.0

Bugfixes

• Fix bug in database:updateschema

Full list of changes.
TER release page

Changes since 3.3.1

Features

• Make a dummy TYPO3 extension available, when installing console via composer. This provides the possibility for other extensions to depend on typo3_console, e.g. when providing commands
• Changed database:updateschema command to not remove fields or tables with *.change type. To get tables or fields removed, the table.prefix and field.prefix type was added.
• Streamline installation procedures. Especially disallow installation if LocalConfiguration.php already exists

Bugfixes

• Hide cache:flush command if TYPO3 isn't set up yet
• Make it possible to set db configuration with configuration:set command
• Improve class loading behavior in TYPO3 non composer mode
• Fix Symfony console dependency

Full list of changes.
TER release page

Changes since 3.3.0

Bugfixes

• Fix a bug triggered by a breaking change in TYPO3 7.6.x
• Fix other inconsistencies related to changes in TYPO3 master
• Fix fatal error in cache flush groups command
• Additional minor cleanups in code and docs

Full list of changes.
TER release page

Changes since 3.2.0

Feature

• Add autocomplete command, to generate shell code for auto completion. Works for bash and zsh shell.

Additionally 3.3.0 incorporates some bugfixes and improved documentation

Full list of changes.
TER release page

Changes since 3.2.2

Bugfixes

• Fix extension:dumpautoload command

Full list of changes.
TER release page

Changes since 3.2.1

Bugfixes

• Do not throw exceptions on E_STRICT notices any more
• Fix path issues in TYPO3 non composer mode

Full list of changes.
TER release page

Changes since 3.2.0

Bugfixes

• Fix install:setup command with latest TYPO3 master

Full list of changes.
TER release page

Changes since 3.1.1

New features

helhum/typo3-console is not an extension any more, but a regular composer binary, which will
be pulled into your vendor folder in composer based TYPO3 projects. Not required files
will then no longer be delivered, when fetching the composer package as distribution and not by source.

The git repository itself still contains all TYPO3 extension files, so cloning will work until the next major version release. It is however not recommended to do so.

If you need the console as extension in non composer based projects, then download and install it from TER, by using the TYPO3 extension manager.

Deprecations

• Cloning the repository as way to install it has been deprecated. The extension files will be removed with the next major release.
• Installing and using the typo3cms binary from the project root is now deprecated. It is recommended to use the composer installed binary instead. Custom installation code will be removed with the next major version.

Bugfixes

• Flush correct cache directory when doing cache:flush --force with TYPO3 8.x
• Make frontend:request work again with TYPO3 8.x

Full list of changes.
TER release page