Conflicts with latest Symfony Framework Bundle release
On 29th March, the symfony/framework-bundle released a new version that inadvertently contains breaking changes. The Symfony team has already resolved the issue; but until they release a new version, you need to make sure you're not running Symfony 5.2.6. The updated versions of Sulu will make sure you're not running on 5.2.6 if you install them with Composer because we've added symfony/framework-bundle:5.2.6 as a conflict. The error only affects people who updated the production environment of their Sulu installation between 29th March and 31st March.
Also some other bugs were reported over the last week which were fixed in this release. One concerned the version restoration not working correctly on pages that have children. Another issue, whereby the FormOverlay in BlockSettings and Profile Edit didn't reload their data, was fixed. Both fixes are part of these releases.
Upgrading your project
We encourage you to have a look at our Upgrading Sulu 2.x documentation when upgrading your project. The documentation provides a step-by-step guide to upgrading Sulu in your projects. Feel free to contact us if you have any questions or problems during the upgrade process.
What is coming next?
We are also still working on the basic event system for the next minor version. The release of the first 2.x version of the SuluAutomationBundle is planned soon. Also we are still working on improving the SuluHeadlessBundle.
We are always happy to receive your feedback about newly released features and bug fixes. Feel free to create an issue or a discussion on Github about bugs and feature requests. You can also contact us via our Slack channel anytime.