Jelenlegi hely

Drupal.org

Feliratkozás Drupal.org hírcsatorna csatornájára
Frissítve: 1 óra 17 perc

drupal 8.9.3

2020, augusztus 5 - 23:53

This is a patch (bugfix) release of Drupal 8 and is ready for use on production sites. Learn more about Drupal 8.

Drupal 8.9 is the final minor release of the 8.x series. It is a long-term support (LTS) version, and will receive security coverage until November 2021. It provides the same public API as Drupal 9.0 aside from deprecated code and dependency changes. (Learn more about Drupal 9.)

If you are upgrading to this release from 8.8.x, read the Drupal 8.9.0 release notes before you upgrade.

Known issues

Search the issue queue for known issues.

All changes since Drupal 8.9.2 Release type: Bug fixes
Kategóriák: Informatika

drupal 9.0.3

2020, augusztus 5 - 23:52

This is a patch (bugfix) release of Drupal 9 and is ready for use on production sites. Learn more about Drupal 9.

Drupal 9.0.x will receive security coverage until June 2, 2021 when Drupal 9.2.0 is released.

If you are upgrading from Drupal 8, read upgrading a Drupal 8 site to Drupal 9 and the 9.0.0 release notes before upgrading to this release.

If your site is on 8.8.x or earlier, you may wish to upgrade to Drupal 8.9.3 instead, and upgrade to Drupal 9 at a later date after preparing your site.

Known issues

Search the issue queue for known issues.

All changes since Drupal 9.0.2 Release type: Bug fixes
Kategóriák: Informatika

drupal 8.9.2

2020, július 8 - 21:40

This is a patch (bugfix) release of Drupal 8 and is ready for use on production sites. Learn more about Drupal 8.

Drupal 8.9 is the final minor release of the 8.x series. It is a long-term support (LTS) version, and will receive security coverage until November 2021. It provides the same public API as Drupal 9.0 aside from deprecated code and dependency changes. (Learn more about Drupal 9.)

If you are upgrading to this release from 8.8.x, read the Drupal 8.9.0 release notes before you upgrade.

Known issues

Search the issue queue for known issues.

All changes since Drupal 8.9.1 Release type: Bug fixes
Kategóriák: Informatika

drupal 9.0.2

2020, július 8 - 21:39

This is a patch (bugfix) release of Drupal 9 and is ready for use on production sites. Learn more about Drupal 9.

Drupal 9.0.x will receive security coverage until June 2, 2021 when Drupal 9.2.0 is released.

If you are upgrading from Drupal 8, read upgrading a Drupal 8 site to Drupal 9 and the 9.0.0 release notes before upgrading to this release.

If your site is on 8.8.x or earlier, you may wish to upgrade to Drupal 8.9.2 instead, and upgrade to Drupal 9 at a later date after preparing your site.

Known issues

Search the issue queue for known issues.

All changes since Drupal 9.0.1 Release type: Bug fixes
Kategóriák: Informatika

drupal 7.72

2020, június 17 - 20:13

Maintenance and security release of the Drupal 7 series.

This release fixes security vulnerabilities. Sites are urged to upgrade immediately after reading the notes below and the security announcement:

No other fixes are included.

Important update information
  • Previously, if a form failed submission failed Drupal's cross-site request forgery protection, the submitted form values would be re-displayed to the user along with a message advising them to copy their previously submitted values and reload the page. Beginning with this release, the form is shown without any values for security reasons, and the user is prompted to press the back button to return to their previously entered values.

    The user-facing error message that appears when a form is outdated has also been changed, and translations of it will need to be updated.

  • No changes have been made to the .htaccess, web.config, robots.txt, or default settings.php files in this release, so upgrading custom versions of those files is not necessary if your site is already on the previous release.

Release type: Security update
Kategóriák: Informatika

drupal 8.8.8

2020, június 17 - 20:12

Maintenance and security release of the Drupal 8 series.

This release fixes security vulnerabilities. Sites are urged to upgrade immediately after reading the notes below and the security announcement:

No other fixes are included.

Which release do I choose? Security coverage information
  • Drupal 8.8.x will receive security coverage until December 2, 2020 when Drupal 9.1.0 is released.
  • Versions of Drupal 8 prior to 8.7.x are end-of-life and do not receive security coverage.
Important update information
  • Previously, if a form failed submission failed Drupal's cross-site request forgery protection, the submitted form values would be re-displayed to the user along with a message advising them to copy their previously submitted values and reload the page. Beginning with this release, the form is shown without any values for security reasons, and the user is prompted to press the back button to return to their previously entered values.

    The user-facing error message that appears when a form is outdated has also been changed, and translations of it will need to be updated.

  • No changes have been made to the .htaccess, web.config, robots.txt, or default settings.php files in this release, so upgrading custom versions of those files is not necessary if your site is already on the previous release.

Release type: Security update
Kategóriák: Informatika

drupal 8.9.1

2020, június 17 - 20:12

Maintenance and security release of the Drupal 8 series.

This release fixes security vulnerabilities. Sites are urged to upgrade immediately after reading the notes below and the security announcement:

No other fixes are included.

  • Drupal 8.9.x is a long-term support release that will receive security coverage until November 2021.
  • Sites on 8.8.x or earlier should update immediately to Drupal 8.8.8 instead, and plan to update to the latest 8.9.x or 9.0.x release before December 2, 2020 (when Drupal 9.1.0 is scheduled for release and 8.8.x security coverage ends).
  • Versions of Drupal 8 prior to 8.8.x are end-of-life and do not receive security coverage.
Important update information
  • Previously, if a form failed submission failed Drupal's cross-site request forgery protection, the submitted form values would be re-displayed to the user along with a message advising them to copy their previously submitted values and reload the page. Beginning with this release, the form is shown without any values for security reasons, and the user is prompted to press the back button to return to their previously entered values.

    The user-facing error message that appears when a form is outdated has also been changed, and translations of it will need to be updated.

  • No changes have been made to the .htaccess, web.config, robots.txt, or default settings.php files in this release, so upgrading custom versions of those files is not necessary if your site is already on the previous release.

Release type: Security update
Kategóriák: Informatika

drupal 9.0.1

2020, június 17 - 20:11

Maintenance and security release of the Drupal 9 series.

This release fixes security vulnerabilities. Sites are urged to upgrade immediately after reading the notes below and the security announcement:

No other fixes are included.

Which release do I choose? Security coverage information
  • Drupal 9.0.x will receive security coverage until June 2, 2021 when Drupal 9.2.0 is released.
  • Sites on 8.8.x or earlier should update immediately to Drupal 8.8.8 instead, and plan to update to the latest 8.9.x or 9.0.x release before December 2, 2020 (when Drupal 9.1.0 is scheduled for release and 8.8.x security coverage ends).
  • Versions of Drupal 8 prior to 8.8.x are end-of-life and do not receive security coverage.
Important update information
  • Previously, if a form failed submission failed Drupal's cross-site request forgery protection, the submitted form values would be re-displayed to the user along with a message advising them to copy their previously submitted values and reload the page. Beginning with this release, the form is shown without any values for security reasons, and the user is prompted to press the back button to return to their previously entered values.

    The user-facing error message that appears when a form is outdated has also been changed, and translations of it will need to be updated.

  • No changes have been made to the .htaccess, web.config, robots.txt, or default settings.php files in this release, so upgrading custom versions of those files is not necessary if your site is already on the previous release.

Release type: Security update
Kategóriák: Informatika

drupal 9.0.0

2020, június 3 - 23:58

This is the first supported release of the new Drupal 9 major version, and it is ready for use on production sites! Learn more about Drupal 9 and the Drupal 8 and 9 release cycles.

Drupal 9.0.0 has been released simultaneously with Drupal 8.9.0. Drupal 8.9 is a long-term support version that will be supported until November 2021, with no new feature development (whereas Drupal 9 development and support will continue beyond that date). Drupal 8.9 has most of the changes that Drupal 9 does, but retains backwards compatibility layers added through Drupal 8's release, and is a good choice to update to first if you have an existing Drupal site, to ensure maximum compatibility and the smallest necessary changes for the Drupal 9 update.

If you are starting a new Drupal 9 project, you have a choice between Drupal 8.9 and 9.0, and generally want to choose Drupal 9.0 for forward compatibility with later releases.

Regardless of which version you choose now, features will only be added to Drupal 9 minor releases, so plan to be on Drupal 9 this year so that you can easily update to Drupal 9.1 and later.

Refer to How to prepare your Drupal 7 or 8 site for Drupal 9 for tools you can use to check the Drupal 9 compatibility of modules, themes and sites.

Both 9.0.0 and 8.9.0 include all the latest commits, and they have the same APIs and features. This also means modules and themes can be compatible with Drupal 8 and 9 at the same time! The key changes in 9.0 are:

  1. Deprecated code has been removed.
  2. Dependencies have been updated to new major versions as appropriate.
  3. Platform requirements (supported PHP and database versions) have been increased.

For all other changes, refer to the 8.9.x branch.

Important update information Updating from Drupal 8

For information on updating from Drupal 8 to Drupal 9, see Upgrading a Drupal 8 site to Drupal 9.

Sites on 8.7 or earlier must update to either 8.8 or 8.9 before updating to Drupal 9 as all Drupal 8 update functions from before Drupal 8.8.0-rc1 were removed from Drupal 9. We recommend updating to 8.8.7 or 8.9.0, as well as updating all contributed modules, before updating to any Drupal 9 release.

The migration paths from Drupal 6 and Drupal 7 to Drupal 9 will remain supported throughout Drupal 9's release cycle.

Note for users of the Experimental Workspaces module

Existing Drupal 8 sites using the experimental Workspaces module must update to at least Drupal 8.8.2 before updating to Drupal 9. (This is due to a required data integrity fix.) Remember that Workspaces is currently in beta status and is not intended for production.

Upgrading from Drupal 7

Drupal 7 users can continue to migrate to Drupal 8.8 or 8.9, or migrate to 9.0 directly. The upgrade path for multilingual sites is stable in Drupal 9.0.0, 8.9.0, and 8.8.7!

Server and database requirements

Drupal 9 requires PHP 7.3 or higher, and the version requirement for Apache has been increased to Apache 2.4.7 or higher. The following database versions are supported by Drupal 9 core:

  • MySQL or Percona 5.7.8.
  • MariaDB 10.3.7 (Note that this is a more recent release than the MySQL version.)
  • PostgreSQL 10 with the pg_trgm extension.
  • SQLite 3.26 (PHP does not always use the system-provided SQLite, so verify that your PHP is compiled with at least this version).

A MySQL contributed database driver is available to provide support for older supported versions of MySQL, Percona, and MariaDB until their end of life, and a similar PostgreSQL contributed database driver provides support for PostgreSQL 9.6. (Be sure to review these drivers' project information before installing one.)

Database driver handling improvements
  • The default database is now checked when Drupal is updated to ensure it complies with the minimum version supported by the database driver. (Previously, this only happened during installation.) Updates will not proceed if the requirement is not met.

    If you see an error about your database version when running update.php, ensure your database meets the minimum database requirements or install one of the legacy database drivers provided as contributed projects.

  • Database drivers provided by modules can now be placed in src/Driver/Database. These drivers will be listed in the installer. Existing custom or contributed drivers do not need to make any changes and will continue to work as before.

  • The databases supported by Drupal 9 core all have JSON support. Future minor releases of Drupal 9 may take advantage of that JSON support. Maintainers of contributed database drivers are encouraged to monitor that issue to see how that will impact them. Change records and release notes will be added for releases that introduce those changes.

Removal of Drupal 8's deprecated APIs

All code that was marked deprecated in Drupal 8 has been removed from Drupal 9.0.0. Many contributed modules are already Drupal-9-compatible; however, you should use Upgrade Status on a fully up-to-date Drupal 8.8 or Drupal 8.9 site to check for issues in your contributed projects and custom code, before attempting to update to Drupal 9.

Update system improvements and upgrade path fixes
  • Drupal now shows a more user-friendly warning when a site tries to upgrade to a new version without having run required intermediate database updates first.

    If you see 'Unsupported schema version' when attempting to run updates, you should:

    1. Back up your site and codebase.
    2. Locate an older version of the contributed module which contains the updates you missed.
    3. Downgrade the module to that version in your code base, and attempt to run updates again.

    When this error is shown, it will now also prevent any updates from proceeding, so may make a persistent issue on an existing site more obvious.

    Ideally, you should always attempt updates of contributed modules and core on a backup of your site (such as a local development environment) prior to running them on production.

  • Drupal 9 will halt an attempted update from Drupal 8 if the Drupal 8 site has missing or incompatible modules, missing updates from core or contrib modules, or certain types of data integrity issues. In these cases a clear error message will be shown, and you should fix the errors on your Drupal 8 site prior to attempting an update again. Several critical upgrade path bugs that affected updates to 8.8 or later have been fixed in both Drupal 8.8 and Drupal 8.9.

  • The Views configuration fixes previously applied as post-updates in #2846614: Incorrect field name is used in views integration for multi-value base fields are now applied at every Views save in order to resolve an upgrade path bug. The old configuration structures are now formally deprecated in 9.0.0 and will be removed from 10.0.0. For more information on the changes that introduced this in previous releases, see the related change records:

Migration system improvements

The migration path from Drupal 6 and Drupal 7 to Drupal 8 or 9 is stable, including multilingual migrations and many features which were moved into core for Drupal 9. Drupal 9 contributed modules are responsible for providing their own migrations into Drupal 9 and this is something to audit during the process of migrating a Drupal 6 or 7 site. Read more on Upgrading from Drupal 6 or 7 to 8 and newer.

  • Multilingual migrations are now stable and have been moved into the main Migrate Drupal module. The experimental Multilingual Drupal Migrate module is therefore no longer required, and will be uninstalled automatically on upgrade.

  • A new 'complete node migration' is now available and will migrate all nodes and node revisions, including translated nodes and the translated node revisions. The complete node migration is named d*_node_complete.yml (where * is the major version, 6 or 7) will eventually replace the existing trio of node migrations, d*_node, d*_node_revision, and d*_node_translation. See the change record on the complete node migration for more information.

  • Drupal 7 Entity Translation revision migrations for nodes are now supported.

Contributed project versioning improvements

Contributed modules may now declare compatibility with multiple major versions of core (so the same module codebase can be compatible with Drupal 8 and 9 at the same time. Furthermore, semantic versioning is also now supported for contributed projects, so Drupal 9-compatible modules may have versions in patterns like either (e.g.) 8.x-3.2 or (e.g.) 4.0.7. For more information on module versions in Drupal 9, review the change record on our semantic versioning support.

Render array hardening against remote code execution

The security fixes required for SA-CORE-2018-002 and SA-CORE-2018-004, as well as other publicly disclosed security issues, all indicated that the render system needs to be stricter about what may be called by a callback. If you have code that adds a render callback (#access_callback, #lazy_builder, #pre_render or #post_render), it might need to be updated to work in Drupal 9. Read more in the change record for limitations on what can be called by a callback in render arrays.

Removed core modules Changes to core themes and theme APIs
  • A new Stable 9 base theme has been added for backwards-compatible markup and assets. Its templates and CSS files have been updated to match with the most recent versions in modules. Drupal 8's Stable theme will still be shipped in Drupal 9 along with Stable 9, but will be deprecated during the Drupal 9 lifecycle to be removed in Drupal 10.

  • Drupal core themes, Bartik, Claro, Seven and Umami no longer depend on Classy or Stable. Now, all these themes set base theme: false. All templates and CSS not overridden in these themes will be inherited directly from core. This allows core's internal themes to receive bugfixes directly from module changes in minor releases (rather than developers having to copy the fixes into every theme). (Extending Classy or Stable 9 is still recommended for contributed or custom themes requiring stability between releases.)

Backend (PHP) dependency changes Symfony

Symfony has been updated from Symfony 3.4.32 to 4.4.9. Like Drupal, Symfony follows a continuous upgrade path and deprecation policy, so that Symfony 4.0 has the same API as 3.4, minus deprecated code. Read about Symfony's Backward Compatibility Promise.

symfony/mime and symfony/var-dumper have been updated from 5.0.7 to 5.0.8, and symfony-cmf/routing has been updated from 2.1.1 to 2.3.1.

Twig

Twig has been updated from 1.38.2 to 2.12.5. The changes for PHP developers and template creators are listed at Preparing for use of Twig 2 in Drupal 9.

Composer dependency changes
  • Drupal's Composer dependency requirement has been updated from 1.9.3 to 1.10.0.

  • All backend (Composer) dependencies have received minor- and patch-level updates to the latest versions.

  • The Composer plugins provided by Drupal -- the scaffold plugin, the vendor hardening plugin, and the project message plugin -- are now compatible with Composer 2, and Drupal core now allows either Composer 1 or 2.

  • The composer/installers development dependency is no longer pinned to 1.9.0 in drupal/core-recommended. Version 1.9 is now the minimum requirement, and composer/installers may be upgraded whenever a new version is available and a Composer-managed site runs composer update.

    Additionally, Composer has been updated from 1.10.0 to 1.10.5, and composer/ca-bundle has been updated from 1.2.6 to 1.2.7.

  • The wikimedia/composer-merge-plugin dependency has been removed because it is incompatible with Composer 2. It was deprecated in Drupal 8.8.0, and has not been used in core since that release. Any sites that have a separate requirement for this project should add it as a direct dependency.

Doctrine packages
  • SimpleAnnotationReader has been dropped from the master branch of Doctrine Annotations. It consequently has been forked into Drupal core to maintain the same functionality. Contributed modules should not be relying on this library directly.

  • Most Doctrine packages have received minor- and patch-level updates to their latest versions. doctrine/reflection 1.2.1 has been added as a dependency, replacing our need fo doctrine/common. doctrine/common and its dependencies (doctrine/cache, doctrine/collections, and doctrine/inflector) have been removed as they are no longer used by Drupal core.

Laminas (ZendFramework) dependencies.

Following the project's move, ZendFramework/* packages have been updated to their Laminas equivalents. The packages have also been updated to their latest versions, including a major version update for Diactoros from 1.8.7 to 2.3.0.

Automated testing dependencies Changes to backend polyfills
  • The empty paragonie/random_compat PHP 5 polyfill has been removed and will no longer be packaged as a dependency of Drupal 9, since Drupal 9 requires PHP 7.3.

  • Similarly, brumann/polyfill-unserialize (which backported PHP 7 serialization functionality to older versions) has been removed since it is no longer required.

  • Finally, symfony/polyfill-php70 has been removed since PHP 7.0 is not supported by Drupal 9 nor Symfony 4.

Other noteworthy backend dependency changes
  • Wherever possible, backend production and development dependencies have been updated to the latest major, minor, or patch-level versions.

  • Guzzle's minimum version was updated from 6.3 to 6.5.4.

  • The TYPO3 Phar Stream Wrapper has been updated from 2.1.2 to 3.1.4.

  • The package easyrdf/easyrdf is no longer a runtime dependency of Drupal and will not be included in tagged releases. Contributed or custom modules using EasyRDF need to add the dependency to their composer.json.

  • Drupal is now using stable releases for behat/mink (1.8.0) and behat/mink-selenium2-driver (1.4.0). These were previously pinned to development versions because a critical bug affecting Drupal core had not been resolved in any stable release.

  • Drupal 9 uses Composer's APCu optimised classloader by default. If you were setting $settings['class_loader_auto_detect'] = FALSE; in your settings.php to use only Composer's classloader in Drupal 8, this is no longer necessary and can be removed. See https://www.drupal.org/node/3116384 for more information.
    Support for using a wincache based classloader is removed from Drupal 9. See https://www.drupal.org/node/3116297 for more information.

Frontend (CSS and JavaScript) dependency changes jQuery

The jQuery library was updated from 3.4.1 to 3.5.1, which includes the full, forward-compatible fix for the security issue mitigated by SA-CORE-2020-002. Read more in jQuery's release history.

The jQuery update introduces security fixes that may be disruptive to some modules, themes, or sites that used self-closing HTML tags incorrectly for tags that did not support them (e.g., <div /> instead of <div></div>). For more information, read the change record on the jQuery 3.5 update.

Drupal 9 will retain a dependency on jQuery 3.x as long as jQuery 3.x is supported (since a stable version of jQuery 4 is not yet available).

jQuery UI

Most jQuery UI components were deprecated in Drupal 8.8 and removed in Drupal 9.0. The libraries are now provided as contributed modules to make updating easier for any modules or themes that depend on them. See the change record on the removal of these jQuery UI libraries for more information.

The libraries that are still in use as of Drupal 8.8 were forked into Drupal 9 core to make it easier to fix any potential security issues with jQuery UI before Drupal 9's end-of-life. We plan to deprecate and remove all of these forked components prior to Drupal 10.0.0's release.

For a simple upgrade path to Drupal 9, see the change record for information on how to use the provided contributed projects that provide replacements for any modules or themes that depend on these deprecated asset libraries.

Since jQuery UI itself is no longer actively supported, it is recommended to find an alternative for the longer term.

Browser polyfills

The following browser support polyfill libraries were deprecated in 8.8.0 and have been removed from Drupal 9.0 because they are no longer required by any of the browsers supported by Drupal core:

  • html5shiv
  • matchMedia
  • domready (Replaced by a single simple function that will now work in all supported browsers. See domready is deprecated for more information.)
  • classList

For sites that need to support older browsers, the contributed html5shiv module and matchmedia module provide identical replacements for the core libraries.

jQuery Cookie replaced by js-cookie

The jquery.cookie has been replaced with js-cookie version 3.0.0-rc.0. The core/js-cookie library is introduced, and a backwards-compatible shim is provided as core/jquery.cookie for Drupal 9.

This also required removing jQuery Joyride's dependency on jQuery Cookie. If your site or module initializes Joyride manually, read the change record about the change to Joyride.

Other frontend dependency changes
  • The Normalize.css dependency has been updated from 3.0.3 to 8.0.1. Themes that are not extending Stable or Classy should manually test in case they need to update. Drupal 8's Stable theme will continue using normalize.css 3.0.3 for backwards compatibility. Read the change record on the normalize.css upgrade for more information.

  • The Popper.js library has been updated to version 2.0.6. This migration guide is available for anyone that needs to convert their Popper.js 1.x compatible code to 2.x.

  • Drupal 9 will continue to depend on CKEditor 4, as the CKEditor maintainers have agreed to coordinate CKEditor 4 security fixes with the Drupal project until the end of 2023.

JavaScript development dependency changes Known issues

Search the issue queue for known issues.

All changes since 9.0.0-rc1 Release type: Bug fixesNew features
Kategóriák: Informatika

drupal 8.9.0

2020, június 3 - 19:01

This is a minor version (feature release) of Drupal 8 and is ready for use on production sites. Learn more about Drupal 8 and the Drupal 8 release cycle.

This minor release provides improvements without breaking backward compatibility (BC) for public APIs. There may be changes in internal APIs and experimental modules that require updates to contributed and custom modules and themes per Drupal core's backwards compatibility and experimental module policies.

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

Drupal 8.9 is the final minor release of the 8.x series. It is a long-term support (LTS) version, and will be supported until November 2021. It also provides the same public API as Drupal 9.0 aside from deprecated code and dependency changes. For more information on the Drupal 9 release, read the Drupal 9.0.0 release notes.

Drupal 8.9 is a good choice to update to first if you have an existing Drupal site, to ensure maximum compatibility and the smallest necessary changes for the Drupal 9 update.

If you are starting a new Drupal project, start with Drupal 9.0 for forward compatibility with later releases.

Regardless of which version you choose now, new features will only be added to upcoming Drupal 9 minor releases, so you should prepare your site for Drupal 9 this year in order to continue receiving the new features in Drupal 9.1 and 9.2.

Important update information Recommended PHP version increased

Drupal 8.9 runs on all PHP 7 versions; however, it is recommended to update to at least PHP 7.3. Only PHP 7.3 and 7.4 are supported by the PHP maintainers until Drupal 8.9's end-of-life in November 2021. Users will see a status report message with this information.

Database driver handling improvements
  • The default database is now checked when Drupal is updated to ensure it complies with the minimum version supported by the database driver. (Previously, this only happened during installation.) Updates will not proceed if the requirement is not met.

  • If you see an error about your database version when running update.php, ensure your database meets the minimum database requirements or install one of the legacy database drivers provided as contributed projects.

  • Database drivers provided by modules can now be placed in src/Driver/Database. These drivers will be listed in the installer. Existing custom or contributed drivers do not need to make any changes and will continue to work as before.

Update system improvements and upgrade path fixes
  • Drupal now shows a more user-friendly warning when a site tries to upgrade to a new version without having run required intermediate database updates first.
    If you see 'Unsupported schema version' when attempting to run updates, you should:

    1. Back up your site and codebase.
    2. Locate an older version of the contributed module which contains the updates you missed.
    3. Downgrade the module to that version in your code base, and attempt to run updates again.

    When this error is shown, it will now also prevent any updates from proceeding, so may make a persistent issue on an existing site more obvious.

    Ideally, you should always attempt updates of contributed modules and core on a backup of your site (such as a local development environment) prior to running them on production.

  • Additionally, module developers may now specify when they have removed post-update hooks, using the new hook_removed_post_updates(). See the change record on hook_removed_post_updates() for more details.

  • Previously, corrupt menu link or taxonomy term data could cause fatal errors when sites attempted to update to Drupal 8.7 from 8.6 or earlier, due to two separate issues with the upgrade path.

    Some of this data will now be repaired automatically on upgrade. In some cases, this could result in content that was not displayed reappearing. If you previously encountered this upgrade path issue, review the change notice on the fixed menu and taxonomy upgrade path for more details on how to check for possible side effects from this change.

    Other data integrity issues that cannot be automatically repaired will result in an error message when update.php is run. If you were unable to update to 8.7 due to issues with menu link or taxonomy term data, Drupal 8.9.0 now adds instructions for resolving this issue. Try installing 8.8.4 and running update.php again. If you see an error that there are "Integrity issues detected" for your site data, follow the instructions in this change record to attempt to repair the data so that updates can be run.

  • The Views configuration fixes previously applied as post-updates in #2846614: Incorrect field name is used in views integration for multi-value base fields are now applied at every Views save in order to resolve an upgrade path bug. The old configurations are now formally deprecated in 9.0.0 and will be removed from 10.0.0. For more information on the changes that introduced this in previous releases, see the related change records:

    1. Multi-value base fields in views no longer use an incorrect field name
    2. Drupal\node\Plugin\views\field\Path deprecated, Drupal\views\Plugin\views\field\EntityLink now provides this functionality
    3. Exposed filters can now limit which operator they expose
Migration system improvements

The migration path from Drupal 6 and Drupal 7 to Drupal 8 or 9 is stable, including multilingual migrations and many features which were moved into core for Drupal 9. Drupal 9 contributed modules are responsible for providing their own migrations into Drupal 9 and this is something to audit during the process of migrating a Drupal 6 or 7 site. Read more on Upgrading from Drupal 6 or 7 to 8 and newer.

  • Multilingual migrations are now stable and have been moved into the main Migrate Drupal module. The experimental Multilingual Drupal Migrate module is therefore no longer required, and will be uninstalled automatically on upgrade.

  • A new complete node migration, d7_node_complete.yml (for Drupal 7) and d6_node_complete.yml (for Drupal 6) is now available. This migration will migrate all nodes and node revisions, including translated nodes and translated node revisions. The complete node migration will eventually replace the existing trio of node migrations. See change record on the new 'complete node migration' for more information on the new migrations.

PHPUnit forward-compatibility APIs

Drupal 9 updates PHPUnit to PHPUnit 8, which introduces backwards compatibility breaks and new deprecations. In order to provide a continuous upgrade path from Drupal 8 (which uses PHPUnit 6 and 7), we've added forward-compatibility shims to provide bc and support the new APIs on older PHPUnit versions. Read the change record on the forward-compatibility shims for more information on the methods you can implement in your PHPUnit tests.

Theme system changes

Theme functions were deprecated prior to Drupal 8.0.0's release in favor of Twig templates. However, the deprecation did not use Drupal's deprecation APIs to notify module and theme developers. Starting with Drupal 8.9.0 the use of theme functions will start to trigger deprecation notices. (In Drupal 9, this error will also be logged because theme functions bypass the sanitization functionality provided by Twig.)

Changes to page caching with the Shortcut module

The Shortcut module disabled the cache for Dynamic Page Cache for users with access to shortcuts. These pages will now be cached which should result in a performance improvement. In rare cases, cache coherency (invalidation) bugs which were previously hidden by the disabled cache may now be surfaced. If content for authenticated users with access to shortcuts is cached incorrectly after upgrading to this release, the module that provides the incorrectly cached content might need a fix to its cache handling code (for example, cache tags or contexts).

Corrected deprecation errors

A handful of deprecation errors triggered were not actually classified as deprecation errors, and were being raised as silenced notices instead. E_USER_DEPRECATED were added to each to correct the problem. This means a small number of sites or modules might see deprecation errors in their tests when they did not previously. Only a handful of methods are affected. See #3137713: [D8 only] Update deprecation notices in NodeNewComments constructor and #3138591: [D8 only] Add missing E_USER_DEPRECATED to deprecation notices for the affected APIs.

Backend (PHP) dependency changes
  • Drupal is now using stable releases for behat/mink (1.8.0) and behat/mink-selenium2-driver (1.4.0). These were previously pinned to development versions because a critical bug affecting Drupal core had not been resolved in any stable release.

  • Since the Zend Framework has become Laminas, Drupal 8.9 now uses the Laminas components for several dependencies in place of the previous Zend Framework components. Code should be updated to use the new Laminas classes. A backwards compatibility layer is provided by laminas/laminas-zendframework-bridge. See the change record on updating to the Laminas components for examples of how to change your code.

  • The Composer plugins provided by Drupal -- the scaffold plugin, the vendor hardening plugin, and the project message plugin -- are now compatible with Composer 2, and Drupal core now allows either Composer 1 or 2.

    Additionally, Composer has been updated from 1.9.1 to 1.10.6, and other Composer components have received minor- and patch-level updates.

  • The project composer/installers is no longer pinned in drupal/core-recommended. It may now be upgraded whenever a new version is available, and a Composer-managed site runs composer update. We are releasing this fix on 8.8.x for Composer 2 forward-compatibility and to mitigate against an unusual composer upgrade path problem See #3134648: [backport, needs scheduling] Don't pin the composer/installers version in drupal/core-recommended for background information on this bug, and #3135247: Composer's "prefer-stable" setting cannot be relied on to produce a stable release for the direction we are taking to prevent future such problems.

  • The wikimedia/composer-merge-plugin dependency has been removed because it is incoƒmpatible with Composer 2. It was deprecated in Drupal 8.8.0, and has not been used in core since that release. Any sites that have a separate requirement for this project should add it as a direct dependency.

  • Earlier this year, Symfony released an advisory for a security vulnerabilities, CVE-2019-18888. Drupal core was not affected by these vulnerabilities, so back in November, we updated Druapl's lock file to provide only the secure version of Symfony to tarball installations.

    In this release, the version constraint of symfony/http-foundation has been increased to 3.4.35, to ensure Composer-built sites are also secure. Going forward, we may adopt this strategy for other packages where Drupal is not affected by a security issue, or we might add an external dependency that adds constraints for insecure versions of packages.

    Additionally, all other Symfony components have been updated from 3.4.32 to 3.4.41 the lockfile.

  • Drupal 8.9's production and development dependencies have all been updated to new patch and minor-level versions where appropriate. Some highlights:

    • Guzzle has been updated from 6.3.3 to 6.5.4.
    • The TYPO3 Phar Stream Wrapper has been updated from 2.1.2 to 3.1.4.
    • asm89/stack-cors has been updated from 1.2.0 to 1.3.0.
    • The seld/jsonlint development dependency has been updated from 1.7.0 to 1.8.0.
    • Various Symfony polyfills have been updated from 1.12.0 to 1.17.0.
    • New Symfony polyfills have been added for PHP 7.2 and for idn_to_ascii() and idn_to_utf8() functions.
    • brumann/polyfill-unserialize has been removed.
Frontend (CSS and JavaScript) dependency changes
  • The jQuery library was updated from 3.4.1 to 3.5.1, which includes the full, forward-compatible fix for the security issue mitigated by SA-CORE-2020-002. Read more in jQuery's release history. Review the ”Update to jQuery 3.5.1” issue for more information.

  • The js-cookie library has been added as a Drupal-9-compatible replacement for jquery.cookie, which is deprecated. A core/js-cookie library has been introduced, and a backwards-compatible shim is provided as core/jquery.cookie for Drupal 9.

    8.9.0 uses js-cookie version 3.0.0-rc.0 and will update to the stable 3.0.0 release once it is available. Review the change record on js-cookie for more information.

  • The Sortable library (added in Drupal 8.8 as a replacement for deprecated jQuery UI functionality) has been updated to 1.10.2. If your module or site depends directly on Sortable, review the changes listed here: Sortable 1.10.2 changelog

  • Drupal core's minimist JavaScript development dependency requirement has been updated from 1.2.0 to 1.2.2.

  • All of Drupal's JavaScript development packages have been updated to the latest secure versions. This does not affect production sites.

Changes to coding standards
  • The development dependency drupal/coder has been updated from 8.3.7 to 8.3.9. New coding standards rules are now available with this update. php_codesniffer has also been updated from 3.5.0 to 3.5.5.

  • The Drupal.Classes.ClassFileName rule is now enabled in the core ruleset to ensure classes are named properly so that they can be autoloaded.

  • The DrupalPractice.General.ExceptionT rule has been enabled, to ensure that no exception messages are translated. Ourconventions for exceptions disallow using the string translation or formatting APIs because they interfere with exception handling and because exception messages that differ from the codebase complicate the debugging process for developers.

  • Drupal.Commenting.DocComment.TagGroupSpacing has been enabled for better whitespace formatting of docblocks.

Known issues

Search the issue queue for known issues.

All changes since 8.9.0-rc1 Release type: Bug fixesNew features
Kategóriák: Informatika

drupal 8.8.7

2020, június 3 - 19:00

This is a patch release of Drupal 8 and is ready for use on production sites. Learn more about Drupal 8.

If you are upgrading to this release from 8.7.x, read the Drupal 8.8.0 release notes before upgrading to this release.

This is the final normal bugfix release of 8.8.x. Further bugfixes will be available in 8.9.0 and 9.0.0, also released today. Drupal 8.8.x will receive security coverage until December 2, 2020 when Drupal 9.1.x is released.

If you are running Drupal 8.7.x or earlier, you should update to Drupal 8.8.7 immediately in order to have the latest critical bug and security fixes applied. Sites that wish to receive regular bug fixes should plan to update to Drupal 8.9 in the near future and may consider preparing their site for Drupal 9.

If you are starting a new Drupal project, start with 9.0 for forward compatibility with later releases.

Important update information Dependency update information
  • The project composer/installers is no longer pinned in drupal/core-recommended. It may now be upgraded whenever a new version is available, and a Composer-managed site runs composer update. We are releasing this fix on 8.8.x for Composer 2 forward-compatibility and to mitigate against an unusual composer upgrade path problem See #3134648: [backport, needs scheduling] Don't pin the composer/installers version in drupal/core-recommended for background information on this bug, and #3135247: Composer's "prefer-stable" setting cannot be relied on to produce a stable release for the direction we are taking to prevent future such problems.

  • Earlier this year, Symfony released an advisory for a security vulnerabilities, CVE-2019-18888 Drupal core was not affected by these vulnerabilities, so back in November, we updated Drupal's lock file to provide only the secure version of Symfony to tarball installations.

    In this release, the version constraint of symfony/http-foundation has been increased to 3.4.35, to ensure Composer-built sites are also secure. Going forward, we may adopt this strategy for other packages where Drupal is not affected by a security issue, or we might add an external dependency that adds constraints for insecure versions of packages.

  • Drupal is now using stable releases for behat/mink (1.8.0) and behat/mink-selenium2-driver (1.4.0). While we wouldn't normally do a minor update to dependencies in a patch release, these were previously pinned to development versions because a critical bug affecting Drupal core had not been resolved in any stable release.

    This change will also make it easier to transition sites away from minimum-stability: "dev", which is no longer recommended. (See #3135247: Composer's "prefer-stable" setting cannot be relied on to produce a stable release from the known issues below for more information on our plans to address future issues with minimum-stability.)

  • All of Drupal's JavaScript development packages have been updated to the latest secure versions. This does not affect production sites.

Known issues

Search the issue queue for known issues.

All changes since 8.8.6 Release type: Bug fixes
Kategóriák: Informatika

drupal 7.71

2020, június 3 - 10:30

Maintenance release of the Drupal 7 series. Includes bug fixes and small API/feature improvements only (no major, non-backwards-compatible new functionality).

No security fixes are included in this release.

This is the first release to fully support PHP 7.4. Please test and report any bugs in the issue queue.

No changes have been made to the .htaccess, web.config, robots.txt or default settings.php files in this release, so upgrading custom versions of those files is not necessary.

Major changes since 7.68: All changes since 7.68: Release type: Bug fixes
Kategóriák: Informatika

drupal 8.9.0-rc1

2020, május 23 - 01:02

This is a release candidate for the next minor version (feature release) of Drupal 8. Release candidates are not supported for production sites, but they are intended for widespread testing in preparation for the upcoming stable release. More information on release candidates.

This release (as well as 8.9.0-beta3) fixes security vulnerabilities present in 8.9.0-beta2. Sites are urged to upgrade immediately after reading the security announcement and notes below:

This minor release provides new improvements without breaking backward compatibility (BC) for public APIs. There may be changes in internal APIs and experimental modules that require updates to contributed and custom modules and themes per Drupal core's backwards compatibility and experimental module policies.

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

Drupal 8.9 is the final minor release of the 8.x series. It is a long-term support (LTS) version, and will be supported until November 2021. It also provides the same public API as Drupal 9.0 aside from deprecated code. For more information on the upcoming Drupal 9 release, read the Drupal 9.0.0-rc1 release notes.

Important update information
  • jQuery was updated to 3.5.1 in 9.0.0-beta3 for the above security advisory, and as a result, 9.0.0-beta2 and earlier have been marked insecure. The jQuery update introduces security fixes that may be disruptive to some modules, themes, or sites that used self-closing HTML tags incorrectly for tags that did not support them (e.g., <div /> instead of <div></div>). For more information, read the change record on the jQuery 3.5 update.
Changes to coding standards

The following additional rules have been enabled in the core ruleset since 9.0.0-beta3:

  • The DrupalPractice.General.ExceptionT rule has been enabled, to ensure that no exception messages are translated. Our conventions for exceptions disallow using the string translation or formatting APIs because they interfere with exception handling and because exception messages that differ from the codebase complicate the debugging process for developers.
  • Drupal.Commenting.DocComment.TagGroupSpacing has been enabled for better whitespace formatting of docblocks.
Other important bug fixes Known issues All changes since 8.9.0-beta3 Release type: Bug fixesNew features
Kategóriák: Informatika

drupal 9.0.0-rc1

2020, május 23 - 00:39

This is a release candidate for the next major version of Drupal. Release candidates are not supported for production sites, but they are intended for widespread testing in preparation for the upcoming stable release. More information on release candidates.

This release (as well as 9.0.0-beta3) fixes security vulnerabilities present in 9.0.0-beta2. Sites are urged to upgrade immediately after reading the security announcement and notes below:

Refer to How to prepare your Drupal 7 or 8 site for Drupal 9 for tools you can use to check the Drupal 9 compatibility of modules, themes, and sites. For more information on 9.0.x development, see #3007300: [META] Release Drupal 9 on June 3 2020.

The 9.0.x branch also includes all the latest commits that will be backported to 8.9.x and earlier branches. 9.0.x and 8.9.x have the same APIs and features. The key changes in 9.0.x are:

  1. Deprecated code will be removed.
  2. Dependencies will be updated to new major versions as appropriate.
  3. Platform requirements (supported PHP and database versions) will be increased.

For all other changes, refer to the 8.9.x branch.

Important update information
  • jQuery was updated to 3.5.1 in 9.0.0-beta3 for the above security advisory, and as a result, 9.0.0-beta2 and earlier have been marked insecure. The jQuery update introduces security fixes that may be disruptive to some modules, themes, or sites that used self-closing HTML tags incorrectly for tags that did not support them (e.g., <div /> instead of <div></div>). For more information, read the change record on the jQuery 3.5 update.

  • Drupal 7 entity_translation revision migrations for nodes are now supported
Changes to coding standards

The following additional rules have been enabled in the core ruleset since 9.0.0-beta3:

  • The DrupalPractice.General.ExceptionT rule has been enabled, to ensure that no exception messages are translated. Our conventions for exceptions disallow using the string translation or formatting APIs because they interfere with exception handling and because exception messages that differ from the codebase complicate the debugging process for developers.
  • Commenting.DocComment.TagGroupSpacing has been enabled for better whitespace formatting of docblocks.
Other important bug fixes Known issues All changes since 9.0.0-beta3
  • #3076447 hotfix by daffie, catch
  • #3110200 by himanshu_sindhwani, kiamlaluno, tdnshah, xjm: Comments make a reference to filter_process_format(), which no longer exists
  • #3132964 by jungle, longwave, sja112, dww, xjm, daffie: assertResponse() does not actually support a $message parameter, so stop passing one
  • #3076447 by quietone, jungle, shaktik, catch, heddn, alexpott: Migrate D7 entity translation revision translations
  • #3100712 by daffie, tim.plunkett, milindk, StevenPatz, xjm, alexpott, dorficus, tedbow, bircher, marcuschristopher, opdavies: Drupal 8.7.10 to 8.8.0 update fails if views have invalid configuration
  • #3135310 by alexpott: Remove completely unused 'database_ready' install state logic
  • #3138731 by jungle, dww: Fix "inheritdoc" typos in core
  • #3138671 by dww: Fix "incompatitable" typos in core
  • #3137414 by shaal, dww, Gábor Hojtsy, sja112, codersukanta, jungle, xjm, hestenet, Dries: Remove D8 branding from D9 status report
  • #2830326 by dww, mpdonadio, cebasqueira, Wim Leers, amateescu, jungle, xjm, daffie, Pasqualle: Broken link to 'Put your site into maintenance mode' on update.php results in WSOD
  • #3136302 by Webbeh, bnjmnm, catch, xjm: Replace UPDATE.txt with links to d.o documentation
  • #2937513 by eltori, longwave, klausi, catch, idebr: Fix 'Drupal.Commenting.DocComment.TagGroupSpacing' coding standard
  • Revert "Issue #3062446 by a.qala: duplicate if statements in "MenuLinkContent.php" on line 151 and 156 - Code Improvement in "Custom Menu Links" module"
  • #2983452 by ridhimaabrol24, Kwadz, cburschka, jungle, somersoft, julienjoye, dhirendra.mishra, beram, daffie, alexpott: Improve support for SQLite in memory database
  • #2821499 by jungle, Andy_D, nikitagupta, lomasr, bbombachini, alexpott, andypost, Mile23, quietone, Sophie.SK, mtodor, barone, kuldeep_mehra27, vsujeetkumar, swatichouhan012, jhodgdon: Enable phpcs rule DrupalPractice.InfoFiles.NamespacedDependency
  • #3135390 by munish.kumar, jungle, mondrake, xjm, daffie: Replace assertions involving calls to is_readable() and is_writeable() on files and directories with PHPUnit assertions
  • #3137268 by benjifisher, mikelutz, quietone, phenaproxima, heddn: Add benjifisher as a sub-system maintainer for migrate
  • #3120731 by alexpott, japerry, daffie, codersukanta, rfay, xjm, tim.plunkett, catch, andypost: Incorrect "Drupal already installed" if any database settings are wrong or unsatisfactory
  • #3136668 by dww, dawehner, pavnish, catch, daffie, alexpott, xjm: Invalid system.schema key_value entry causes fatal on updating to 8.8.5
  • #3123933 by greg.1.anderson, alexpott, longwave, xjm: Determine whether ComposerProjectTemplatesTest is testing the internet, and if it is, avoid that
  • #3062446 by a.qala: duplicate if statements in "MenuLinkContent.php" on line 151 and 156 - Code Improvement in "Custom Menu Links" module
  • #2055851 by andypost, jungle, dawehner, Mac_Weber, sja112, borisson_, fietserwin, init90, Gábor Hojtsy, xjm, effulgentsia, tim.plunkett: Remove translation of exception messages
  • #3137455 by sja112, mondrake, longwave: AssertLegacyTrait - change links in @trigger_error deprecations to point the relevant change record
  • Revert Issue #3110669 by quietone, Gábor Hojtsy: Migrate d7 menu language content settings
Release type: Bug fixes
Kategóriák: Informatika

drupal 7.70

2020, május 20 - 17:42

Maintenance and security release of the Drupal 7 series.

This release fixes security vulnerabilities. Sites are urged to upgrade immediately after reading the notes below and the security advisories:

No other fixes are included.

Important update information
  • This release provides a backwards compatibility layer to minimize disruptions in this security release. However, some sites may experience disruptions in jQuery code for certain edge cases. See the security advisory for more information.
  • Visiting update.php is required for this update in order to ensure a site cache clear. (There are no changes to database schemata.)
  • No changes have been made to the .htaccess, web.config, robots.txt, or default settings.php files in this release, so upgrading custom versions of those files is not necessary if your site is already on the previous release.
Release type: Security update
Kategóriák: Informatika

drupal 8.8.6

2020, május 20 - 17:30

Maintenance and security release of the Drupal 8 series.

This release fixes security vulnerabilities. Sites are urged to upgrade immediately after reading the notes below and the security announcement:

No other fixes are included.

Which release do I choose? Security coverage information
  • Drupal 8.8.x will receive security coverage until December 2, 2020 when Drupal 9.1.0 is released.
  • Sites on 8.7.x or earlier should update immediately to Drupal 8.7.14 instead, and plan to update to the latest 8.8.x release before June 3, 2020 (when Drupal 8.9.0 is scheduled for release and 8.7.x security coverage ends).
  • Versions of Drupal 8 prior to 8.7.x are end-of-life and do not receive security coverage.
Important update information
  • This release provides a temporary backwards compatibility layer to minimize disruptions in this security release. However, some sites may experience disruptions in jQuery code for certain edge cases. See the security advisory for more information.

  • Visiting update.php is required for this update in order to ensure a site cache clear. (There are no changes to database schemata.)

  • No changes have been made to the .htaccess, web.config, robots.txt, or default settings.php files in this release, so upgrading custom versions of those files is not necessary if your site is already on the previous release.

Release type: Security update
Kategóriák: Informatika

drupal 8.7.14

2020, május 20 - 17:29

Maintenance and security release of the Drupal 8 series.

This release fixes security vulnerabilities. Sites are urged to upgrade immediately after reading the notes below and the security announcement:

No other fixes are included.

Which release do I choose? Security coverage information
  • Sites on 8.7.x will receive security coverage until June 3, 2020 (when Drupal 8.9.0 is scheduled for release).
  • Versions of Drupal 8 prior to 8.7.x are end-of-life and do not receive security coverage.
Important update information
  • This release provides a temporary backwards compatibility layer to minimize disruptions in this security release. However, some sites may experience disruptions in jQuery code for certain edge cases. See the security advisory for more information.

  • Visiting update.php is required for this update in order to ensure a site cache clear. (There are no changes to database schemata.)

  • No changes have been made to the .htaccess, web.config, robots.txt, or default settings.php files in this release, so upgrading custom versions of those files is not necessary if your site is already on the previous release.

Release type: Security update
Kategóriák: Informatika

drupal 8.9.0-beta3

2020, május 17 - 22:07

This is a beta release for the final, long-term support minor version of Drupal 8. Beta releases 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 new improvements without breaking backwards compatibility (BC) for public APIs. There may be changes in internal APIs and experimental modules that require updates to contributed and custom modules and themes per Drupal core's backwards compatibility and experimental module policies.

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

Drupal 8.9 is the final minor release of the 8.x series. It is a long-term support (LTS) version, and will be supported until November 2021. It also provides the same public API as Drupal 9.0 aside from deprecated code. For more information on the upcoming Drupal 9 release, read the Drupal 9.0.0-beta1 release notes.

Important update information

For a full list of important changes since 8.8, also see the following:

Recommended PHP version increased
  • Drupal 8.9 runs on all PHP 7 versions; however, it is recommended to update to at least PHP 7.3. Only PHP 7.3 and 7.4 are supported by the PHP maintainers until Drupal 8.9's end-of-life in November 2021.

Database driver handling improvements
  • The default database is now checked when Drupal is updated to ensure it complies with the minimum version supported by the database driver. (Previously, this only happened during installation.) Updates will not proceed if the requirement is not met.

    If you see an error about your database version when running update.php, ensure your database meets the minimum database requirements or install one of the legacy database drivers provided as contributed projects.

  • Database drivers provided by modules can now be placed in src/Driver/Database. These drivers will be listed in the installer. Existing custom or contributed drivers do not need to make any changes and will continue to work as before.

Upgrade path changes

The Views configuration fixes previously applied as post-updates in #2846614: Incorrect field name is used in views integration for multi-value base fields are now applied at every Views save in order to resolve an upgrade path bug. The old configurations are now formally deprecated in 9.0.0 and will be removed from 10.0.0. For more information on the changes that introduced this in previous releases, see the related change records:

Updates and changes to dependencies
  • The Composer plugins provided by Drupal -- the scaffold plugin, the vendor hardening plugin, and the project message plugin -- are now compatible with Composer 2, and Drupal core now allows either Composer 1 or 2.

    Additionally, Composer has been updated from 1.9.1 to 1.10.5, and other Composer components have received minor- and patch-level updates.

  • The wikimedia/composer-merge-plugin dependency has been removed because it is incompatible with Composer 2. It was deprecated in Drupal 8.8.0, and has not been used in core since that release. Any sites that have a separate requirement for this project should add it as a direct dependency.

  • Drupal is now using proper stable releases for behat/mink (1.8.0) and behat/mink-selenium2-driver (1.4.0).

  • Drupal 8.9's other PHP dependencies have been updated to the latest compatible minor and patch versions wherever possible. In particular:

    • Laminas components have been updated to the latest patch versions.
    • Guzzle has been updated from 6.3.3 to 6.5.3.
    • Symfony components have been updated from 3.4.35 to 3.4.40, and various Symfony polyfills have been updated from 1.12.0 to 1.15.0.
    • New Symfony polyfills have been added for PHP 7.2 and for idn_to_ascii() and idn_to_utf8() functions.
    • Twig has been updated from 1.42.3 to 1.42.5.
    • asm89/stack-cors has been updated from 1.2.0 to 1.3.0.
    • Pear libraries have received patch-level updates.
    • egulias/email-validator has been updated from 2.1.11 to 2.1.17.
    • The ypo3/phar-stream-wrapper library has been updated from 3.1.3 to 3.1.4.
    • Other development dependencies have received patch- and minor-level updates.
  • jQuery has been updated from 3.4.1 to 3.5.1.

  • The core/js-cookie library (which was introduced in Drupal 8.9.0-beta1 as the forward-compatible replacement jquery.cookie) has updated its js-cookie dependency from version 2.2.1 to version 3.0.0-rc.0. A summary of the differences in 2.2.1 and 3.0.0-rc.0 can be found by reviewing js-cookie's release history. Code that interacts with js-cookie via the shim provided by core/jquery.cookie is not impacted by this change.

    Review the change record on js-cookie for more information.

Changes to coding standards
  • The development dependency drupal/coder has been updated from 8.3.7 to 8.3.9. New coding standards rules are now available with this update. php_codesniffer has also been updated from 3.5.0 to 3.5.5.

  • The Drupal.Classes.ClassFileName rule is now enabled in the core ruleset to ensure classes are named properly so that they can be autoloaded.

Other important bugfixes Known issues All changes since 8.9.0-beta2 Release type: Bug fixesNew features
Kategóriák: Informatika

drupal 9.0.0-beta3

2020, május 16 - 02:09

This is a beta release for the next major version of Drupal. Drupal 9 beta releases are intended for site owners and module or theme authors to test compatibility and upgrade paths for Drupal 9.0. Beta releases are not intended for production.

Refer to How to prepare your Drupal 7 or 8 site for Drupal 9 for tools you can use to check the Drupal 9 compatibility of modules, themes, and sites. For more information on 9.0.x development, see #3007300: [META] Release Drupal 9 on June 3 2020.

The 9.0.x branch also includes all the latest commits that will be backported to 8.9.x and earlier branches. 9.0.x and 8.9.x have the same APIs and features. The key changes in 9.0.x are:

  1. Deprecated code will be removed.
  2. Dependencies will be updated to new major versions as appropriate.
  3. Platform requirements (supported PHP and database versions) will be increased.

For all other changes, refer to the 8.9.x branch.

Important update information

For a full list of important changes in 9.0, also see the following:

Database driver handling improvements
  • The default database is now checked when Drupal is updated to ensure it complies with the minimum version supported by the database driver. (Previously, this only happened during installation.) Updates will not proceed if the requirement is not met.

    If you see an error about your database version when running update.php, ensure your database meets the minimum database requirements or install one of the legacy database drivers provided as contributed projects.

  • Database drivers provided by modules can now be placed in src/Driver/Database. These drivers will be listed in the installer. Existing custom or contributed drivers do not need to make any changes and will continue to work as before.

  • Contributed and custom database drivers no longer need to extend core's database-agnostic database classes unless they need to override functionality provided by that code. The core database drivers have had unnecessary classes removed. Read the change record for the full list of classes removed.

Upgrade path changes Updates and changes to dependencies
  • Drupal 9's PHP dependencies have been updated to the latest compatible versions wherever possible. In particular:

    • Symfony components have been updated from 4.4.7 to 4.4.8. symfony/mime and symfony/var-dumper have been updated from 5.0.7 to 5.0.8, and symfony-cmf/routing has been updated from 2.1.1 to 2.3.1.
    • doctrine/annotations has been updated from 1.8.0 to 1.10.2, and doctrine/reflection has been updated from 1.1.0 to 1.2.1.
    • Diactoros has been updated from 2.2.2 to 2.3.0, and other Laminas components have received patch-level updates.
    • Guzzle has been updated from 6.5.2 to 6.5.3.
    • PHPUnit has been updated from 8.5.2 to 8.5.4.
    • psr/log has been updated from 1.1.2 to 1.1.3.
    • Other development dependencies have received patch-level updates.
  • The Composer plugins provided by Drupal -- the scaffold plugin, the vendor hardening plugin, and the project message plugin -- are now compatible with Composer 2, and Drupal core now allows either Composer 1 or 2.

  • The composer/installers development dependency is no longer pinned to 1.9.0 in drupal/core-recommended. Version 1.9 is now the minimum requirement, and composer/installers may be upgraded whenever a new version is available and a Composer-managed site runs composer update.

    Additionally, Composer has been updated from 1.10.0 to 1.10.5, and composer/ca-bundle has been updated from 1.2.6 to 1.2.7.

  • The wikimedia/composer-merge-plugin dependency has been removed because it is incompatible with Composer 2. It was deprecated in Drupal 8.8.0, and has not been used in core since that release. Any sites that have a separate requirement for this project should add it as a direct dependency.

  • jQuery has been updated from 3.4.1 to 3.5.1.

  • The core/js-cookie library (which was introduced in Drupal 9.0.0-beta1 to replace jquery.cookie) has updated its js-cookie dependency from version 2.2.1 to version 3.0.0-rc.0. A summary of the differences in 2.2.1 and 3.0.0-rc.0 can be found by reviewing js-cookie's release history. Code that interacts with js-cookie via the shim provided by core/jquery.cookie is not impacted by this change.

    Review the change record on js-cookie for more information.

  • Node.js is a development dependency for Drupal core. In Drupal 9, Drupal core's Node.js requirement has been updated from 8.11.0 to 12.0.0. (Information on changes in Node.js 12.) An updated version of Node.js can be installed directly or with nvm. This only affects sites that have installed Drupal core's JavaScript development dependencies with npm or yarn.

Changes to coding standards
  • The development dependency drupal/coder has been updated from 8.3.7 to 8.3.9. New coding standards rules are now available with this update. php_codesniffer has also been updated from 3.5.4 to 3.5.5.

  • The Drupal.Classes.ClassFileName rule is now enabled in the core ruleset to ensure classes are named properly so that they can be autoloaded.

  • The new Drupal.Commenting.Deprecated rule has been enabled to ensure that @deprecated documentation follows a standard format with relevant information for upgrading the code. See the deprecation policy for documentation of the standard.

Other important bugfixes Known issues All changes since 9.0.0-beta2 Release type: Bug fixesNew features
Kategóriák: Informatika

Theme by me