doctrine/orm 2.10 and doctrine/dbal 3 compatibility
The newly released version 2.10.0 of the doctrine/orm package and version 3.1.3 of the doctrine/dbal package contain some changes that were incompatible with the Sulu codebase. We are happy to say that we were able to merge a pull request that restores compatibility with the newest packages one day after the release of the doctrine packages.
When upgrading your project, you need to update the schema of your database because the new doctrine packages dot not longer support the "json_array" column type. Have a look at the Sulu UPGRADE.md and the doctrine/dbal 3 UPGRADE.md for a detailed description how to upgrade your project.
ALTER TABLE se_role_settings CHANGE value value JSON NOT NULL; ALTER TABLE we_analytics CHANGE content content JSON NOT NULL; -- if you use audience targeting, the following statement is required too: ALTER TABLE at_target_group_conditions CHANGE condition condition JSON NOT NULL
Sulu 1.6.42
The new LTS release brings support for the latest version of the FFmpeg image converter. While Sulu 2 was already compatible with the newest FFmpeg version for some time, Sulu 1.6 did not support recent versions of the executable. We want to thanks our community member boboda for backporting the compatibility fix to Sulu 1.6!
FFmpeg allows to generate preview images for videos that are uploaded to the Sulu media section. If you do not use ffmpeg in your project yet, we recommend you to check out the FFMpeg configuration section in our documentation.
What is coming next?
In addition to the Sulu 2.4 release, we are also working on the next major release for the SuluArticleBundle. The new major version builds on top of the SuluContentBundle and will no longer require an Elasticsearch server. This will make the bundle more flexible and easier to setup even for small projects.
