Full support for Symfony 5!
The most important change since the first release candidate is the full support of Symfony 5. We know that Symfony developers always want to use the most recent features of their beloved framework, therefore we always try to be compatible with the latest version as soon as possible.
We had already done everything we could in the RC1, but some of our dependencies were not compatible with Symfony 5. We contributed some fixes to them, but we had to wait for them to appear in a stable release since this was not in our hprobablyands. This was actually also one of the reasons our roughly half-year release cycle got delayed by so much. We wanted to make sure that the Symfony 5 support landed in this release because otherwise, you would have had to wait for another 6 months before enjoying the new and shiny Symfony features.
Nested blocks, filtering lists, and deep links
These are the new features of this release, included since the first 2.1 release candidate, so check out this release blog post, where they are explained in more detail.
I still want to quickly summarize what problems these features are solving:
Nested blocks allow developers to avoid snippets or other structures when elements should be repeatable within blocks.
Filtering lists by certain columns enable content managers to handle data more efficiently.
Deep links in referencing field types lead to a smoother navigation experience for the content manager and therefore improves the UX.
Further improvements and bugfixes
This release also contains all the bug fixes being released in Sulu 1.6 and 2.0, including the fixes from Sulu 2.0.9. We released these at the same time — they are mostly typing and continuous integration errors, which should not affect you. But it also adds the missing publish icons in the list view of the pages and fixes the usage of a SingleMediaSelection field type as a search field.
In addition to that, there have been two more fixes since RC1, related to the update of Symfony. These issues have been found through our release process including release candidates, and we have to thank our community for testing their applications with them already. You are awesome!
The first issue was about a deprecated controller from Twig, which was removed in Symfony 5. Since we are still supporting Symfony 4 as well, we’ve had to handle that in a special way.
Another issue was discovered by our community member Pablo Lozano. When any error happened, the actual error was not shown in the browser, because the error template itself erred while rendering the error (that’s a lot of errors…). Thank you, Pablo, for also fixing this issue on your own.