Contao news

Contao version 4.5.0 is available.

Previous announcements

• Contao 4.5.0-beta1 is available
• Contao 4.5.0-beta2 is available
• Contao 4.5.0-beta3 is available
• Contao 4.5.0-RC1 is available

Database backup – this time for real!

Contao 4.5 uses InnoDB as database engine and utf8mb4_unicode_ci as collation and the install tool will try to adjust the tables accordingly. In case this goes wrong, having a database backup is essential.

Consider the script runtime

To adjust the collation, MySQL has to adjust every text field in every record. For tables with several thousand entries (thinking about tl_search_index here) this can take longer than the install tool is allowed to run. In this case you can copy the update statements containing CONVERT TO CHARACTER SET in the install tool and run them manually. So for example:

mysql -e "ALTER TABLE tl_member CONVERT TO CHARACTER SET utf8mb4_unicode_ci"

SQLSTATE[23000]: Duplicate entry

When updating contao.org, I had a problem that a table with a unique index could not be converted:

SQLSTATE[23000]: Integrity constraint violation: 1062 Duplicate entry '…' for key 'username'

To solve the issue, I have converted the existing unique index to a normal index in PhpMyAdmin and then started the table update in the install tool again. Now the table could be updated and the unique index was reset by the install tool.

Also see: Core tickets | Version comparison | Core change log | Release overview