You are here

Drupal.org

drupal 8.9.0-rc1

2020, May 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
Categories: Informatika

drupal 9.0.0-rc1

2020, May 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
Categories: Informatika

drupal 7.70

2020, May 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
Categories: Informatika

drupal 8.8.6

2020, May 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
Categories: Informatika

drupal 8.7.14

2020, May 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
Categories: Informatika

drupal 8.9.0-beta3

2020, May 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
Categories: Informatika

drupal 9.0.0-beta3

2020, May 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
Categories: Informatika

drupal 8.7.13

2020, April 2 - 22:19

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.6.x, read the Drupal 8.7.0 release notes before upgrading to this release.

Further bugfixes are available in Drupal 8.8. Drupal 8.7.x will receive security coverage until June 3rd, 2020 when Drupal 9.0.0 and 8.9.0 are released.

Important update information

This release resolves several upgrade path critical bugs that may have prevented sites from updating from Drupal 8.6 or earlier:

Known issues

Search the issue queue for known issues.

All changes since 8.7.12 drupal-8.7.13.tar.gzRelease file SHA-1 hash: a778c68ff987eeb9bd0ea4573498d7653a39ef00Release file SHA-256 hash: 87bc9cbd19c10eae3418bed0b12a486c4294bca53a7989b499fa586b1b502e4dc602aed82b1047cca97486b604f9f44b drupal-8.7.13.zipRelease file SHA-1 hash: 5b1d93d16cce633a9e14431b4cf53e9045577fdeRelease file SHA-256 hash: 8441967acd5896ab3eaadb6119afa63e3f2988b0b13c89a33b3d3ba7c8a18313782d88829b3f59a34744b322669783da VCS Label: 8.7.13Core compatibility: 8.xRelease type: Bug fixesPackaged Git sha1: 5360d9ece38465a40401de4bbbb839eb37eeb639
Categories: Informatika

drupal 8.8.5

2020, April 2 - 22:17

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 or earlier, read the Drupal 8.8.0 release notes before upgrading to this release.

Drupal 8.8.x will receive security coverage until December 2, 2020 when Drupal 9.1.0 is released.

Important update information

This release resolves several upgrade path critical bugs that may have prevented sites from updating from Drupal 8.7 or earlier:

Known issues

Search the issue queue for known issues.

All changes since 8.8.4 drupal-8.8.5.tar.gzRelease file SHA-1 hash: 3ac94168d38f97984fadc1bdd96f815564b60748Release file SHA-256 hash: 8cbb0df82d1a19c085e785952d28bcfe5105b895940fb3cc28846b9c422fc58611e595f6aa42fca4ab4423bff0b09c28 drupal-8.8.5.zipRelease file SHA-1 hash: 0482c8bc06061b785d9281dc72f71e6a7883ed5bRelease file SHA-256 hash: 5dae6ba8f8515089caf91334788bfe3248e22d106421276d8ad668c2bd2611f900160756dddebef13d9f10df34f2b640 VCS Label: 8.8.5Core compatibility: 8.xRelease type: Bug fixesShort description: Actively maintained with new features and backwards-compatible improvements every six months. Use this version for the best compatibility with future releases.Packaged Git sha1: cb0cd8079ede8b953ff282eab82aeb2c1f0e667f
Categories: Informatika

drupal 8.9.0-beta2

2020, April 2 - 22:16

This is a beta release for the final, long-term support minor version of Drupal 8. 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 release fixes security vulnerabilities present in 8.9.0-beta1. 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-beta1 release notes.

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

Known issues

Search the issue queue for known issues.

All changes since 8.9.0-beta1 drupal-8.9.0-beta2.tar.gzRelease file SHA-1 hash: fb3e64b39c0b49e779c58a839c6d265bd87a36f5Release file SHA-256 hash: 3d30dbf5f61a71064febf449b3c23baa260d7698271dc3e434082792ec7075b6c4ff64852b7f4cf2997e70939fdf725c drupal-8.9.0-beta2.zipRelease file SHA-1 hash: a8c00fa1c00164d0bde56c9db3d979ad55f534d0Release file SHA-256 hash: a06d91e858f24ea2f8a87a9e50af9277d250daee2ec3d1ba54c38e9dfdd872f101492c70e7fd51a81535580d9bc45b79 VCS Label: 8.9.0-beta2Core compatibility: 8.xRelease type: Bug fixesNew featuresShort description: 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.Packaged Git sha1: 07b36f592d2cc4d6f16ed2d76cd7a01ab44542dd
Categories: Informatika

drupal 9.0.0-beta2

2020, March 30 - 21:21
drupal-9.0.0-beta2.tar.gzRelease file SHA-1 hash: a78a8d99e2963f4fc90d0e9c8e867b9a08b1149aRelease file SHA-256 hash: aeefad0d1df318762b6e3842916d17c112b00c45a71e6b38c07c656714e3c27b8c45d8abb2a6f09326de40ae845a4435 drupal-9.0.0-beta2.zipRelease file SHA-1 hash: 1212d9d184753e7d04eefad0ef3c8c88a56ccd5dRelease file SHA-256 hash: e95f4b454a31cf7334674c706ccd9cf95bbcbf9f8974c3d3572ec1d17c3b25a733568e2d009a166c54ae862fda2a8823

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.

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

Note that Drupal 8 is not affected by the Symfony vulnerabilities above.

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 Known issues

Search the issue queue for known issues.

All changes since 9.0.0-beta1 VCS Label: 9.0.0-beta2Release type: Security updateBug fixesShort description: Drupal 9 betas are for testing sites and projects with the upcoming Drupal 9.0 release. They are not for production.Packaged Git sha1: 772aa3faa0ec9da0b8627a4359044cfce6e1999f
Categories: Informatika

drupal 8.9.0-beta1

2020, March 26 - 23:41

This is a beta release for the final, long-term support minor version of Drupal 8. 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 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-beta1 release notes.

Important update information
  • 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.)

  • 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).

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.8.4 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.

Migrate system changes
  • 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.

Dependency changes
  • jquery.cookie has been deprecated in Druapl 8.9 and removed in Drupal 9.0 in favor of js-cookie version 2. A core/js-cookie library has been introduced, and a backwards-compatible shim is provided as core/jquery.cookie for Drupal 9. We may upgrade to js-cookie 3 if it is available before 9.0.0-rc1 and 8.9.0-rc1.

  • 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 Sortable library updated to 1.10.2. If your module or site depends directly on Sortable, review the changes listed here: Sortable 1.10.2 changelog

Other important bug fixes Known issues

Search the issue queue for known issues.

All changes since 8.8.0

Browse the commit log for 8.9.x.

drupal-8.9.0-beta1.tar.gzRelease file SHA-1 hash: 21d3edab69b622657c1546b87501b43c1a393756Release file SHA-256 hash: 04ff39b4fd26599652c5f3cbc46e5d014936e1ade027ebf4051884f9cb84560ea1e8f17527ba1edd52ecae2d88cbdf9c drupal-8.9.0-beta1.zipRelease file SHA-1 hash: 0b3f969847b7f4b986ba44eb063bf3bb6d380fb7Release file SHA-256 hash: 2d2d4eb957ab89b89a4094834a809345079949bfe0d855b2621536fe2ea8a8778bf79a4ec8c53ed4f68c895721947913 VCS Label: 8.9.0-beta1Core compatibility: 8.xRelease type: Bug fixesNew featuresShort description: 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.Packaged Git sha1: 1e0e0e09cbe8cfb5113f3b32f15f84aa0cda38be
Categories: Informatika

drupal 10.0.x-dev

2020, March 22 - 15:27

This release is a placeholder for the Drupal 10.0.x major development branch. It does not contain the actual 10.0.x codebase and is not intended for use for anything other than the Drupal core issue queue version selector.

VCS Label: 10.0.x
Categories: Informatika

drupal 9.0.0-beta1

2020, March 20 - 20:30
drupal-9.0.0-beta1.tar.gzRelease file SHA-1 hash: 874f4f28570cd581fcd1b53833db8bf53010abfbRelease file SHA-256 hash: c2c07d8bc3c7416321c56bc69a8410e829f56d3bf08fe6674fb0915a0950d033f68e669e0a50859c2fce1a0da8455d8a drupal-9.0.0-beta1.zipRelease file SHA-1 hash: 7fd10152a2f0ab0d803119fdf1533168284eb9e1Release file SHA-256 hash: 31506d005cc23e4cf71ef8b3b494f016e3a9e7f62386ca9f344ba555be279dc11c6f318fa1dda286849b2a917f7d0812

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 changes since 9.0.0-alpha2

For a full list of important changes in Drupal 9.0, be sure to also read the 9.0.0-alpha1 release notes and 9.0.0-alpha2 release notes.

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.
  • MariaDB10.3 (Note that this is a more frequent release than the MySQL version.)
  • PostgreSQL 10 with the pg_trgm extension.
  • SQLite 3.26 (PHP 7.4 does not use the system-provided SQLite, so verify that your PHP is compiled with at least this version).

A contributed database driver is available to provide support for older supported versions of MySQL, Percona, and MariaDB until their end of life. (A similar driver could be created for PostgreSQL 9.)

All identifiers (table names, database names, field names and aliases) are quoted in database queries. Column names or aliases should be wrapped in square brackets when using Connection::query(), db_query(), ConditionInterface::where() or SelectInterface::addExpression. Custom or contrib database drivers should read All identifiers should be quoted in database queries to see what changes are necessary.

Theme system improvements
  • 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.

  • Classy is no longer a base theme of core themes. Work is underway to further decouple core themes from the Drupal 8 Stable theme. Once this work is complete, the core internal themes will directly receive bugfixes from module changes in minor releases (rather than developers having to copy the fixes into every theme).

Dependency updates
  • 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.

  • Additional Composer dependency versions have been updated since 9.0.0-alpha2. (Note that Drupal core is incompatible with symfony/dom-crawler version 4.4.5, and this is reflected in the dependency's compatibility constraint.)

jQuery Cookie replaced by js-cookie

The jquery.cookie has been replaced with js-cookie version 2. 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.

We may upgrade to js-cookie 3 if it is available before 9.0.0-rc1.

jQuery UI

The jQuery UI asset libraries not in use by Drupal core have been marked deprecated and have been removed from core in Drupal 9.

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.

Upgrading from Drupal 8

Drupal 8 sites can update to Drupal 9 using update.php or drush. Updates will only run on sites that have already been updated to 8.8.0 or later, and we recommend updating from the latest patch release of Drupal 8.8 (or Drupal 8.9.x once that is out), as well as updating all contributed modules, before updating to Drupal 9. Although Drupal 9 is not yet ready for production, we encourage testing of the upgrade path with the beta release.

Even if you are not ready to begin upgrading to Drupal 9, if you are on 8.7.x or older Drupal versions, you should aim to get onto Drupal 8.8.x as soon as possible.

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 and the forthcoming Drupal 8.9 release, updating to Drupal 9.0.x can then happen following its release.

The upgrade path for multilingual sites will be stable in Drupal 9.0.0-beta1, also included in forthcoming releases of Drupal 8.9.x and Drupal 8.8.x

Known issues All changes since 9.0.0-alpha2 VCS Label: 9.0.0-beta1Release type: Bug fixesShort description: Drupal 9 betas are for testing sites and projects with the upcoming Drupal 9.0 release. They are not for production.Packaged Git sha1: 005e3934c1767835aad4d684a71f6efebf21332b
Categories: Informatika

drupal 8.8.4

2020, March 18 - 18:16

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.12 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

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.

drupal-8.8.4.tar.gzRelease file SHA-256 hash: 2e466736aa9908c47bebfa48c0d2f4edaa88c87d3a2a3c4132efc24e3b6e66703d08163b296ed947c4337992d439094aRelease file SHA-1 hash: 25859eb57f57afe596fb826a947769ea713cf7797 drupal-8.8.4.zipRelease file SHA-256 hash: a65b6635a8b31d8c7023b7fcd08f7079d6216fcd3d8ffa3c7825caebd67de1c8adf81e4be166c58d6ca7c66a38fac6f6Release file SHA-1 hash: f0e707a7699f1209af9d56fc25d897e632f0a0452 VCS Label: 8.8.4Core compatibility: 8.xRelease type: Security updateShort description: Actively maintained with new features and backwards-compatible improvements every six months. Use this version for the best compatibility with future releases.Packaged Git sha1: b41facbb7853266788c489ad3c4f932dbdd18809
Categories: Informatika

drupal 8.7.12

2020, March 18 - 18:16

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

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.

drupal-8.7.12.tar.gzRelease file SHA-1 hash: 2acf8f1cfbba90da7f82809f6f5ffc26b78e43dcRelease file SHA-256 hash: 58a187d51032ef4436c978e60dc7913cd71f0238b44c6a262f6d5f526c36f4e93c267482febea33e28444075a2f23870 drupal-8.7.12.zipRelease file SHA-1 hash: a22a1997cf3274d2100a0bb3174f37609e8367f5Release file SHA-256 hash: 9971b75f752a398225f23eb911633e43a9b9c3bf99f9045dbf357e50fa32262b3366f975761f17ef65233da90574e71f VCS Label: 8.7.12Core compatibility: 8.xRelease type: Security updateShort description: Actively maintained with new features and backwards-compatible improvements every six months. Use this version for the best compatibility with future releases.Packaged Git sha1: 6b8876efb37dd2b57aa96d5cec66572a72550869
Categories: Informatika

drupal 9.0.0-alpha2

2020, March 4 - 19:41
drupal-9.0.0-alpha2.tar.gzRelease file SHA-1 hash: f82370c5d14306721224afae44cf96a67925ecdcRelease file SHA-256 hash: 1976b03dc2c4cc1d561954e7dc2d7f5ed7e678e248e9a12960928697c908d6881b7c43687239ba61025710feaebd7e1b drupal-9.0.0-alpha2.zipRelease file SHA-1 hash: 2a66ad8d4086759d122a1e82284e8dd3f280d0faRelease file SHA-256 hash: e5b956513da1f08c453b38fcd946cf07d4d8837f54fe9a764fdd46a53def6d5346e8edad93decfe308eecf7b6d0c29d7

This is an alpha release for the next major version of Drupal. Drupal 9 alpha releases are intended for site owners and module or theme authors to begin testing whether their sites and code are compatible with significant dependency changes in Drupal 9.0.x. Drupal 9 alpha releases should not be used in production. No upgrade path is provided between Drupal 9 alpha releases or to Drupal 9.0.0-beta1.

Note that Drupal 9 alphas are not inclusive of all the backwards-compatibility breaking changes that will be included in 9.0.0. Any further alpha releases as well as the first beta release will include more dependency updates and remove more of the previously identified deprecated APIs. 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 will be nearly identical to 8.9.x except for the following:

  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 changes since 9.0.0-alpha1

Read the Drupal 9.0.0-alpha1 release notes for various important information about the new major release.

What's next?

We may release further alpha versions as needed. There are three release scenarios for Drupal 9. If we complete all Drupal 9.0.0 beta requirements by March 13, the first beta will be released in mid-March and Drupal 9.0.0 will be released on June 3rd, 2020. If the beta requirements are not completed by then, one of the later beta windows will be used.

All changes since 9.0.0-alpha1 VCS Label: 9.0.0-alpha2Release type: Bug fixesNew featuresShort description: Drupal 9 alphas are for initial testing of whether sites and projects are compatible with Drupal 9.0. They are not for production.Packaged Git sha1: db83fa88baf806336c67a9eb4bf21090ab6a399c
Categories: Informatika

drupal 8.8.3

2020, March 4 - 19:09

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

Important update information

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

  • CKEditor has been updated from 4.13.0 to 4.13.1, which includes numerous bug fixes and improvements.

  • To allow modules to be compatible with Drupal 8 and 9 at the same time and to support semantic versioning for contributed projects, the Update Manager module now requests an alternative XML feed from updates.drupal.org. The path for the new feed ends in /current rather than /8.x. The new feed will include both module releases with version numbers starting with 8.x- (e.g. 8.x-3.1) and all releases that use the new semantic version numbering.

    Site owners will not need to make any changes for this change but may notice changes to update pages and contributed project version schemes. For developers, the differences between the new and old XML feeds the differences are detailed in this documentation page.

  • Starting with Drupal 8.8.3, the status report will display a message about the security coverage for the current minor version. Drupal 8.8.x will receive security coverage until December 2rd, 2020.

Known issues All changes since 8.8.2 drupal-8.8.3.tar.gzRelease file SHA-1 hash: f43f91503fe30cca3fa919f17fc3bc25e9e74446Release file SHA-256 hash: 511ba0a1d5fbca2b78ad73e5c9c5ac7b0dc515d7ca183b0a63f5f6dbee1da888f524df904f9d4ba5586eed8203e1c58c drupal-8.8.3.zipRelease file SHA-1 hash: 1ebe1bf70c62a256b33383dbf8cad32209c93bcfRelease file SHA-256 hash: 351657f5062079715f522f0df464bdbb132ef14403da6cfe0c75c61e0379e40bac8bc2205ceb138b0f2491e5b0f95a21 VCS Label: 8.8.3Core compatibility: 8.xRelease type: Bug fixesShort description: Actively maintained with new features and backwards-compatible improvements every six months. Use this version for the best compatibility with future releases.Packaged Git sha1: f4c3b7dc4b38127e06b687b2ae30f148dcfc46ab
Categories: Informatika

drupal 9.0.0-alpha1

2020, February 11 - 19:35
Download Size md5 hash drupal-9.0.0-alpha1.tar.gz 15.92 MB d6966108add1d681774406209981fb77 drupal-9.0.0-alpha1.zip 26.73 MB 6384cfb849b0f04d87523a1a9f90e204 Last updated: 11 Feb 2020 at 19:05 UTCRelease notes

This is an alpha release for the next major version of Drupal. Drupal 9 alpha releases are intended for site owners and module or theme authors to begin testing whether their sites and code are compatible with significant dependency changes in Drupal 9.0.x. Drupal 9 alpha releases should not be used in production. No upgrade path is provided between Drupal 9 alpha releases or to Drupal 9.0.0-beta1.

Drupal 9 alphas do not include all the breaking changes that will be included in 9.0.0. Any further alpha releases as well as the first beta release will include more dependency updates and remove more of the previously identified deprecated APIs. 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 will be nearly identical to 8.9.x except for the following:

  1. Deprecated code will be removed.
  2. Dependencies will be updated to new major versions as appropriate.

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

Information on updating to Drupal 9

Drupal 8 sites on 8.7 or earlier must update to either 8.8 or 8.9 before updating to Drupal 9 with update.php. All Drupal 8 update functions from before Drupal 8.8.0-rc1 were removed from Drupal 9. Note: The migration paths from Drupal 6 and Drupal 7 to Drupal 8 and 9 will remain supported throughout Drupal 9's release cycle.

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

Removal of Drupal 8's deprecated APIs

85% of all mentions of @deprecated APIs have been already removed, including the removal of the deprecated EntityManager service, and the removal of drupal_set_message() among others.

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.

Ongoing changes to core themes and theme APIs Backend (PHP) dependency updates

This alpha release includes the following key PHP dependency updates compared to Drupal 8.9.x:

Frontend (CSS and JavaScript) dependency updates

Drupal 9 will continue to depend on CKEditor 4 and jQuery 3.4.

  • 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.

  • 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.

Other planned dependency updates

The following dependency updates are still outstanding and will be resolved before 9.0.0-beta1:

What's next?

We may release further alpha versions as needed. There are three release scenarios for Drupal 9. If we complete all Drupal 9.0.0 beta requirements by the end of February, the first beta will be released in the first week of March and Drupal 9.0.0 will be released on June 3rd, 2020. If the beta requirements are not completed by the end of February, one of the later beta windows will be used.

All changes since 8.8.0

Browse the commit log for 9.0.x.

Official release from tag: 9.0.0-alpha1Release type: Bug fixesNew featuresShort description: Drupal 9 alpha releases are intended for site owners and module or theme authors to begin testing whether their sites and code are compatible with significant dependency changes in Drupal 9.0.0.Packaged Git sha1: 1e7dfe0df82f2bac92e2159c7b500bd66967169a
Categories: Informatika

Theme by me