Paragraphs Bundles 2.0.1 Fixes Legacy Sections as Drupal 12 Drops Query Serialisation

Legacy Content Editing and Database Query Compatibility Require Separate Checks
A Discover Drupal poster from The Drop Times titled "Compatibility Needs More Than a Version Check." The illustration shows a website content panel pulled away from a larger system, exposing connected wires and internal components that represent dependencies beneath the visible interface. The poster highlights the need to test editing existing content and review code that stores database query objects before upgrading to Drupal 12, rather than relying on version compatibility alone.

Released on 7 October 2026, Paragraphs Bundles 2.0.1 repairs a save failure affecting older two- and three-column sections. The module’s release notes trace the problem to version 1.0.17, which made an animation field required without filling it on existing sections. Existing sections created before that version could display but lacked the value needed to pass validation when saved.

The fix gives sites moving from 1.x to 2.x a specific content-editing check after upgrading. Separately, Drupal core maintainers have committed a change affecting developers whose code serialises database query objects. The module update is stable and available now, while the core change remains committed but unreleased.

Paragraphs Bundles 2.0.1 Repairs Legacy Sections

Paragraphs Bundles 2.0.1 fills the missing animation value with slide across current sections and every revision. Values already selected by editors are preserved. According to the release notes, the supplied value matches how the affected sections already displayed, so their appearance stays the same.

The release also repairs a 3D-carousel CSS-class regression introduced in 2.0.0. It restores the class used by 1.x while retaining the form printed by 2.0.0, supporting themes written against either version. The release documentation identifies 14 additional 1.x CSS classes omitted from the earlier migration guide. Section labels and help text are also adjusted for upgraded installations, while editor-customised values are preserved; translated strings may require manual updating.

Sites upgrading from 1.x should first install the latest release in that branch and run its database updates. The 2.0 upgrade instructions require schema version 9004 or later. The instructions also require database and file backups because the upgrade has no supported downgrade path. Custom CSS and JavaScript selectors need checking against the changed classes and element IDs.

After installing 2.0.1, maintainers should run drush updatedb as instructed in the release notes and rebuild caches. Editing tests should include existing two- and three-column sections created before 1.0.17. Sites with carousel theme overrides should also check their styling. The maintainer reports testing an upgrade from 1.0.18 across all 39 section types without content loss or edit-form failures; that test does not cover every customised installation.

The 2.x branch declares support for Drupal 11.3 or later within Drupal 11, and Drupal 12. The 2.0.0 release notes identify a dependency constraint: Composer installation on Drupal 12 requires a compatible release of the underlying Paragraphs module. Maintainers need to check the complete dependency stack rather than relying on Paragraphs Bundles’ compatibility declaration alone.

Drupal Core Prepares to Remove Query Serialisation

A separate Drupal core change record published on 8 October 2026 deprecates Query::__sleep() and Query::__wakeup() in Drupal 11.5 and specifies their removal in Drupal 12. The change concerns database query objects rather than Paragraphs Bundles.

Drupal 11.5 introduces deprecations for these methods, while Drupal 12 removes them. The change record concerns the forthcoming core versions and should not be read as a change to existing stable Drupal 11 installations.

The change record says the removal aligns query objects with the rest of Drupal’s Database API. The separate core issue describes concerns about reconnecting restored queries to database connections, but this is a compatibility change rather than a Drupal Security Team advisory.

Developers should review calls to serialize() and unserialize(), including objects that contain database query objects. Query objects passed into persistent storage also warrant inspection. For workflows that resume later, storing the necessary parameters and rebuilding the query when execution resumes offers a practical alternative to retaining the query object itself.

References

  1. paragraphs_bundles 2.0.1, Drupal.org (7 October 2026)

Disclosure: This content is produced with the assistance of AI.

Note: The vision of this web portal is to help promote news and stories around the Drupal community and promote and celebrate the people and organizations in the community. We strive to create and distribute our content based on these content policy. If you see any omission/variation on this please reach out to us at #thedroptimes channel on Drupal Slack and we will try to address the issue as best we can.

Upcoming Events