Back to Overview
MASSIVE ART_Daniel Mathis_640x640circle
Daniel Mathis

Core Developer

Sulu Core Developer with a soft spot for home automation and gaming, because why do things manually when you can script them?

Back to Overview

Six Sulu Bundles released for 3.0

We're excited to announce stable Sulu 3.0 releases for six ecosystem bundles: Form, Headless, Community, Redirect, Automation and Comment. With these releases, the most widely used Sulu bundles are now compatible with the new content architecture introduced in Sulu 3.0. This architecture replaces the PHPCR storage layer with Doctrine ORM, the document manager with a dimensions-based content model, and MassiveSearch with the SEAL  search abstraction.

A guiding goal of these releases was to stay as close to the 2.6 behaviour as possible, so existing projects can upgrade with minimal changes. Some breaking changes remain and are documented in each bundle's upgrade guide. A maintained 2.x line also stays available for projects still on Sulu 2.6.

Headless Bundle updated for the new content architecture

The new architecture affected the Headless bundle most, so it saw the largest internal rewrite. We adapted its content resolvers and serializers to the new Doctrine ORM content model, and its search endpoint now uses the SEAL abstraction instead of MassiveSearch. The search response changes accordingly: the indices parameter becomes index, results return as a flat list, and each hit includes a serialized media object alongside its resource key and id.

Smart Content gained a groups option, the excerpt now exposes a single image object instead of an array to match Sulu core, and navigation items carry a linkType. These response changes are breaking for existing API clients, as is the removal of the bundled reference JavaScript implementation. The upgrade guide lists every changed field.

Automation Bundle migrated to the message bus

Scheduled publishing and unpublishing now integrates with Sulu 3.0's message bus architecture. Dedicated handlers for pages, articles and snippets replace the previous generic document handler, enabling automation for each content type individually. 

We updated the underlying php-task library to version 3, and a stored task now references the task entity directly rather than by id. In the admin, the automation view now displays a correctly named tab for each article group, where previously it showed only the last group. The removed handler classes and changed task entity are breaking changes for projects that customise task handling; see the upgrade guide.

Form Bundle Keeps Template Compatibility

The Form bundle runs on the new content architecture while preserving template compatibility with Sulu 2.6. The single form selection content type again resolves to a ready-to-render form, so existing templates render unchanged and most projects upgrade without any template work. Internally, the form type now uses the plural resource key (pages, articles, snippets), with a Doctrine migration updating the type stored for existing submissions. Type declarations across the bundle were also hardened, and admin form metadata now falls back to the configured translator locale rather than German for locales the bundle does not translate. Only code that extends the bundle needs to account for the tightened signatures, listed in the upgrade guide.

Community, Redirect and Comment Bundles

These bundles mainly focus on Sulu 3.0 compatibility, with a few targeted improvements: 

The Community bundle adds configurable registration rules for controlling sign-ups, returns an HTTP 422 response for invalid form submissions, and now requires Symfony Mailer in place of SwiftMailer (upgrade guide). 

The Redirect bundle replaces ramsey/uuid with symfony/uid and moves its import endpoint under the new admin API path (upgrade guide). 

The Comment bundle replaces its deprecated page and pageSize parameters with limit and offset (upgrade guide). All three drop the PHPCR and FOSRest dependencies they no longer require.

Continued support for Sulu 2.6

Each bundle keeps a 2.x release line compatible with Sulu 2.6. Recent 2.x releases focused on maintenance and forward compatibility, including Symfony 7 support, dropping end-of-life PHP versions, and migrating REST routing to Symfony routing. The Headless bundle added an analytics route on the 2.6-compatible line, and the Community bundle published its first stable release.

Get in touch

With these releases, the core Sulu ecosystem is now largely available on the Sulu 3.0 content architecture. As always, feedback from real-world upgrades is invaluable. Every bug report and piece of feedback helps make the next release smoother for everyone. Reach out through GitHub Discussions or the Slack community, and if you'd like a hand with your upgrade, our support services are there no matter how big or small your project is.

MASSIVE ART_Daniel Mathis_640x640circle
Daniel Mathis

Core Developer

Sulu Core Developer with a soft spot for home automation and gaming, because why do things manually when you can script them?