Bot releases are hidden (Show)
Published by helhum over 8 years ago
Published by helhum over 8 years ago
database:export
commandFull list of changes.
TER release page
Published by helhum over 8 years ago
After over three months of development, we are proud to present a new major version of TYPO3 Console. It has:
Configuration/Commands.php
extension:*
commands like extension:setup
, extension:setupactive
and renamed commands like extension:activate
install:fixfolderstructure
to create the required TYPO3 folder structure so that e.g. the typo3temp folder can always be discarded and recreated during deploymentinstall:generatepackagestates
command to be easier to configure (through environment variable) and more reliablebackend:lockforeditors
command, which locks the backend only for editorsconfiguration
commands, which makes it not only possible to remove, but also to view and change TYPO3 configuration from command linedatabase: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.--verbose
switch to database:updateschema
to be able to see the executed SQL during the process../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.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.extension:
commands have been renamed for better and more consistent namingThe full change log can be examined on Github
Published by helhum over 8 years ago
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:
Bugfixes will be released by increasing the bugfix version (e.g. going from 2.0.1 to 2.0.2).
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).
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.
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"
!