drupal 11.1.0-beta1

This is a beta release for the next minor (feature) release of Drupal 11. Betas are good testing targets for developers and site builders who are comfortable reporting (and where possible, fixing) their own bugs. Beta releases are not recommended for non-technical users, nor for production websites. More information on beta releases.

This minor release provides improvements and new functionality. It does not break backward compatibility (BC) for public APIs. There may be changes in internal APIs and experimental modules. If so, contributed and custom modules and themes may need updating. This is according to Drupal core's backward compatibility and experimental module policies.

This release may include string changes and additions. Translators can review the latest translation status on localize.drupal.org.

Drupal 11.1.x will receive security support until December 2025. Drupal 11.0.x will continue to receive security support until June 2025.

Important update information

Changes to site-owner-managed files

• A directive has been added to the default .htaccess file that attaches the correct image/webp header for webp images when the MIME Apache module is enabled. This is needed for sites hosted on Apache web servers running on operating systems that do not support the webp image MIME type. Sites should update their .htaccess files to take advantage of this improvement.

• The sid_length and sid_bits_per_character configuration options are no longer supported in PHP 8.4 or Symfony 7.2, so they have been removed from default.services.yml. Sites should remove these settings from any services.yml files.

API and behavior changes

• Assets are now ordered more strictly by dependencies instead of relying on the order that libraries were attached to the page. This is a bug fix that resolves various issues with asset handling, however if a library specifies an individual asset weight that conflicts with its dependencies (i.e. the dependent file would be added to the page before the files it depends on), there may be side-effects in some situations. In these cases, module or theme authors should review their library dependencies and any custom weights.
• The "Access the Content blocks overview page" permission is no longer required to create blocks. This means that roles that have "Create new content block" permission for a given block type will be able to create these blocks when they could not in previous releases. Site owners should audit their Block Content permissions to ensure that block creation access is granted intentionally in all cases, and can also now consider revoking access to the content block overview listing for roles that do not need it.
• The default value of the "Who can register accounts?" setting has changed from "Visitors, but administrator approval is required" to "Administrators only" for any new sites built with either the "Standard" or "Minimal" installation profiles.
• The following pages which supported installing modules and themes via file uploads have been removed without replacement:
  • The "Add new module" page at /admin/modules/install
  • The "Add new theme" page at /admin/theme/install
  • The "Add new module or theme" page at /admin/reports/updates/install

  Using Composer is the only way to safely and correctly add new code to a Drupal installation. See the Additional information, deprecations, and API changes related to installing an extension through the user interface.

• Hooks can now be implemented in classes and most core hook implementations have been moved to classes. Modules that were altering core hook implementations or invoking core hooks directly may need to update their code to match the changes.
• A new workspaces_ui module has been added which provides workspace module's routes and toolbar integration. This is to allow for alternative user interface implementations in core or contrib.

  Sites already using workspaces will have workspaces_ui enabled in an update.

Experimental module changes

• Package Manager has been added as a hidden, experimental module. This is to allow Automatic Updates and Project Browser to be tested and eventually added to future versions of Drupal core.

PHP dependency changes

• Symfony is updated to 7.2.0-rc1.

• Twig is updated to 3.14.2.

• Numerous other dependencies have received minor- and patch-level updates to the latest versions.

PHP development dependency changes

• Composer is updated to 2.8.2.
• OpenTelemetry is updated to 1.1.0. This adds additional development dependencies including the tbachert/spi Composer plugin. When this package is installed by Composer you may be asked whether to trust this plugin; unless you are using OpenTelemetry performance testing in Drupal you can safely answer "no" to this question.

Frontend (CSS and JavaScript) production dependency changes

• CKEditor is updated to 43.1.1.

• jQuery UI is updated to 1.14.0.

Development dependencies

The Nightwatch testing library is updated to version 3.7.0. Reference the Nightwatch developer guide for a list of high-level changes in the 3.0.0 release.

Known issues

Search the issue queue for known issues.