Display Builder 1.0.0-beta4 Released with Stabilisation Fixes and Logging Improvements

Display Builder version 1.0.0-beta4 has been released, with Michael Fanini announcing the update as part of ongoing stabilisation efforts for the module. The release focuses on resolving workflow issues, improving logging behaviour, and refining internal systems as development moves toward a stable version.

The update introduces improvements to the Entity view override feature, enhancing its reliability across different content types and display configurations. Changes to API error logging now generate messages specific to the originating data source, allowing developers to more easily trace and diagnose issues during execution.

Several issues affecting the builder interface and workflow have been addressed. Fixes include restoring expected behaviour in the token modal window, correcting how empty steps are handled in the builder workflow, and resolving errors triggered when invalid data is passed to moveToSlot() during slot attachment. Field management behaviour within entity view overrides has also been corrected to support proper configuration.

Under the hood, the release updates the ui_patterns dependency to its latest version, maintaining alignment with the broader UI Suite ecosystem. The Views integration has also been refactored, with the ViewsManagementController now using ViewDisplay::collectInstances() to standardise instance handling across the codebase.

Test coverage has been updated and restructured to reflect recent changes, supporting continued reliability as the module evolves. According to the release notes, ten issues have been resolved since version 1.0.0-beta3, with contributions from six developers: anruether, fmb, ipumpkin, mogtofu33, nickolaj, and pdureau.

Display Builder 1.0.0-beta4 requires Drupal version 11.3.3 or higher. The module can be installed using Composer with composer require 'drupal/display_builder:^1.0@beta'. Manual installation packages are available, though Composer-based installation remains the recommended approach for managing dependencies in modern Drupal projects.

Find the relaese notes here.