Sulu is een contentmanagementsysteem dat is gebouwd op Symfony, een php-webapplicatieframework. Voor meer informatie over het hoe en wat verwijzen we naar deze pagina. Het ontwikkelteam van Sulu heeft enkele dagen geleden versies 1.6.34, 2.0.8 en 2.1.0-RC2 uitgebracht. De bijbehorende aankondiging en lijst met aanpassingen zien er als volgt uit: Sulu Release 1.6.34, 2.0.8 & 2.1.0-RC2 Finally, we were able to deliver Sulu 2.1.0-RC2! It took us some time because we wanted to make sure that this release works with Symfony 4 and 5, which was relying on the status of some external dependencies. All these dependencies have been updated now, and we were able to make the last adjustments and tag this release. In addition to the (hopefully) last release candidate of Sulu 2.1, we have also tagged bugfix releases for Sulu 1.6 and Sulu 2.0, as these versions will continue to receive bug- and security fixes according to our release policy. Apart from the details below, we have also fixed some types helping to make proper use of a static type checker and added some migration scripts that our users have been looking for. Bugfixes applied to all releases Let’s start with the bugfixes that have been applied to all three releases. The first bugfix might almost be called a feature, because it allows you to further customize the search results. Thanks to Sulu community member and contributor ampaze who has adjusted our search integration in pages. Now, developers can define which fields should be indexed separately. This can be done using a tag for our properties:

Sulu is een contentmanagementsysteem dat is gebouwd op Symfony, een php-webapplicatieframework. Voor meer informatie over het hoe en wat verwijzen we naar deze pagina. Het ontwikkelteam van Sulu heeft enkele dagen geleden versies 1.6.34, 2.0.8 en 2.1.0-RC2 uitgebracht. De bijbehorende aankondiging en lijst met aanpassingen zien er als volgt uit: Sulu Release 1.6.34, 2.0.8 & 2.1.0-RC2 Finally, we were able to deliver Sulu 2.1.0-RC2! It took us some time because we wanted to make sure that this release works with Symfony 4 and 5, which was relying on the status of some external dependencies. All these dependencies have been updated now, and we were able to make the last adjustments and tag this release. In addition to the (hopefully) last release candidate of Sulu 2.1, we have also tagged bugfix releases for Sulu 1.6 and Sulu 2.0, as these versions will continue to receive bug- and security fixes according to our release policy. Apart from the details below, we have also fixed some types helping to make proper use of a static type checker and added some migration scripts that our users have been looking for. Bugfixes applied to all releases Let’s start with the bugfixes that have been applied to all three releases. The first bugfix might almost be called a feature, because it allows you to further customize the search results. Thanks to Sulu community member and contributor ampaze who has adjusted our search integration in pages. Now, developers can define which fields should be indexed separately. This can be done using a tag for our properties:

Sulu is een contentmanagementsysteem dat is gebouwd op Symfony, een php-webapplicatieframework. Voor meer informatie over het hoe en wat verwijzen we naar deze pagina. Het ontwikkelteam van Sulu heeft enkele dagen geleden versies 1.6.34, 2.0.8 en 2.1.0-RC2 uitgebracht. De bijbehorende aankondiging en lijst met aanpassingen zien er als volgt uit: Sulu Release 1.6.34, 2.0.8 & 2.1.0-RC2 Finally, we were able to deliver Sulu 2.1.0-RC2! It took us some time because we wanted to make sure that this release works with Symfony 4 and 5, which was relying on the status of some external dependencies. All these dependencies have been updated now, and we were able to make the last adjustments and tag this release. In addition to the (hopefully) last release candidate of Sulu 2.1, we have also tagged bugfix releases for Sulu 1.6 and Sulu 2.0, as these versions will continue to receive bug- and security fixes according to our release policy. Apart from the details below, we have also fixed some types helping to make proper use of a static type checker and added some migration scripts that our users have been looking for. Bugfixes applied to all releases Let’s start with the bugfixes that have been applied to all three releases. The first bugfix might almost be called a feature, because it allows you to further customize the search results. Thanks to Sulu community member and contributor ampaze who has adjusted our search integration in pages. Now, developers can define which fields should be indexed separately. This can be done using a tag for our properties:

Sulu is een contentmanagementsysteem dat is gebouwd op Symfony, een php-webapplicatieframework. Voor meer informatie over het hoe en wat verwijzen we naar deze pagina. Het ontwikkelteam van Sulu heeft enkele dagen geleden versies 1.6.34, 2.0.8 en 2.1.0-RC2 uitgebracht. De bijbehorende aankondiging en lijst met aanpassingen zien er als volgt uit: Sulu Release 1.6.34, 2.0.8 & 2.1.0-RC2 Finally, we were able to deliver Sulu 2.1.0-RC2! It took us some time because we wanted to make sure that this release works with Symfony 4 and 5, which was relying on the status of some external dependencies. All these dependencies have been updated now, and we were able to make the last adjustments and tag this release. In addition to the (hopefully) last release candidate of Sulu 2.1, we have also tagged bugfix releases for Sulu 1.6 and Sulu 2.0, as these versions will continue to receive bug- and security fixes according to our release policy. Apart from the details below, we have also fixed some types helping to make proper use of a static type checker and added some migration scripts that our users have been looking for. Bugfixes applied to all releases Let’s start with the bugfixes that have been applied to all three releases. The first bugfix might almost be called a feature, because it allows you to further customize the search results. Thanks to Sulu community member and contributor ampaze who has adjusted our search integration in pages. Now, developers can define which fields should be indexed separately. This can be done using a tag for our properties: