Crează un cont nou

Anonymous's picture
Description

Release notes

Drush users: Update to Drush 8.1.12+ or higher

Versions of Drush earlier than 8.1.12 will not work with Drupal 8.4.x. Update Drush to 8.1.12 or higher before using it to update to Drupal core 8.4.x or you will encounter fatal errors that prevent updates from running.

  • If Drush is installed globally (i.e., generally available on the web host), Drush 8.1.12 and higher will successfully update Drupal 8.3.x to 8.4.0, but users may still see other error messages after updates have run.)
  • If the site is built with Composer and includes Drush as a local dependency (less common), you should update your composer.json file to require at least Drush 8.1.15. Drush 8.1.14 will not work in the same composer project as Drupal 8.4.

Updated browser requirements: Internet Explorer 9 and 10 no longer supported

In April 2017, Microsoft discontinued all support for Internet Explorer 9 and 10. Therefore, Drupal 8.4 has as well. Drupal 8.4 still mostly works in these browser versions, but bugs that affect them only will no longer be fixed, and existing workarounds for them will be removed beginning in Drupal 8.5.

Additionally, Drupal 8's browser requirements documentation page currently lists incorrect information regarding very outdated browser versions such as Safari 5 and Firefox 5. Clarifications to the browser policy and documentation are underway.

Known Issues

Drupal 8.4.0 includes major version updates for two dependencies: Symfony 3.2 and jQuery 3. Both updates may introduce backwards compatibility issues for some sites or modules, so test carefully. For more information, see the "Third-party library updates" section below. Known issues related to the Symfony update include:

See the '8.4.0 update' tag for a list of known issues across projects.

Search the issue queue for known issues.

Important fixes since 8.3.x

Translators should take note of several string additions and changes since the last release.

File usage tracking

Drupal 8 has several longstanding file usage tracking bugs. To prevent further data loss, Drupal 8.4 has disabled the automatic deletion of files with no known remaining usages. This will result of the accumulation of unused files on sites, but ensures that files erroneously reporting 0 usages are not deleted while in use. Additionally, an issue with validation errors when saving content referencing these files has also been resolved.

The change record explains how sites can opt back into marking files temporary. If you choose to enable the setting, you can also set "Delete orphaned files" to "Never" on /admin/config/media/file-system to avoid permanent deletion of the affected files.

While the files will no longer be deleted by default, file usage is still not tracked correctly in several scenarios, regardless of the setting. Discussion on how to evolve the file usage tracking system is underway.

Configuration export sorting

Revision data integrity fixes

Other critical improvements

New stable modules

The following modules, previously considered experimental, are now stable and safe for use on production sites, with full backwards compatibility and upgrade paths from 8.4.0 to future releases:

Datetime Range

The Datetime Range module provides a field type that allows end dates to support contributed modules like Calendar. This stable release is backwards-compatible with the 8.3.x experimental version and shares a consistent API with other Datetime fields.

Future releases may improve Views support, usability, Datetime Range field validation, and REST support. For bugs or feature requests for this module, see the core Datetime issue queue.

Layout Discovery

The Layout Discovery module provides an API for modules or themes to register layouts as well as five common layouts. Providing this API in core enables core and contributed layout solutions to be compatible with each other. This stable release is backwards-compatible with the 8.3.x experimental version and introduces support for per-region attributes.

Media

The new core Media module provides an API for reusable media entities and references. It is based on the contributed Media Entity module.

Since there is a rich ecosystem of Drupal contributed modules built on Media Entity, the top priority for this release is to provide a stable core API and data model for a smoother transition for these modules. Developers and expert site builders can now add Media as a dependency. Work is underway to provide an update path for existing sites' Media Entity data and to port existing contributed modules to the improved core API. Both versions cannot be used at the same time, so we also prevent the 1.x version of the contributed Media Entity module from being enabled at the same time as the core Media module.

Note that the core Media module is currently marked hidden and will not appear on the 'Extend' (module administration) page. (Enabling a contributed module that depends on the core Media module will also enable Media automatically.) The module will be displayed to site builders normally once user experience issues with it are resolved. Similarly, the REST API and normalizations for Media is not final and support for decoupled applications will also be improved in a future release.

Inline Form Errors

The Inline Form Errors module provides a summary of any validation errors at the top of a form and places the individual error messages next to the form elements themselves. This helps users understand which entries need to be fixed, and how. Inline Form Errors was provided as an experimental module from Drupal 8.0.0 on, but it is now stable and polished enough for production use. See the core Inline Form Errors module issue queue for outstanding issues.

Workflows

The Workflows module provides an abstract system of states (like Draft, Archived, and Published) and transitions between them. Workflows can be used by modules that implement non-publishing workflows (such as for users or products) as well as content publishing workflows.

Drupal 8.4 introduces a final significant backwards compatibility and data model break for this module, moving responsibility for workflow states and transitions from the Workflow entity to the Workflow type plugin. Read Workflow type plugins are now responsible for state and transition schema for full details on the API and data model changes related to this fix. Now that this change is complete, the Workflows module became stable!

While the module can be installed as-is, it is not useful in itself without either Content Moderation and/or some other module that requires it.

Content authoring and site administration improvements

REST and API-first improvements

Performance and scalability improvements

Developer experience improvements

Automated testing improvements

Third-party library updates

Experimental modules

Migrate (beta stability)

Migrate provides a general API for migrations. It will be considered completely stable once all issues tagged Migrate critical are resolved.

  • This release includes numerous developer experience improvements for Migrate and Migrate Drupal, including deprecating outdated references to "CCK", simplifying field type mapping, renaming several plugins to better capture their and many other API and documentation improvements. (Backwards compatibility is provided in each case Migrate is in beta.)
  • Added the ability to provide the source module to migrations to help site owners review what data is being migrating, especially for cases where the source and destination module are not the same (for example if a new Drupal 8 module replaces old functionality.

Migrate Drupal and Migrate Drupal UI (alpha stability)

Migrate Drupal module provides API support for Drupal-to-Drupal migrations, and Migrate Drupal UI offers a simple user interface to run migrations from older Drupal versions.

Content Moderation (beta stability)

Content Moderation allows workflows from the Workflows module to be applied to content. Notable improvements in this release:

As per the experimental module process, there were some backwards-incompatible changes since Drupal 8.3.x. Experimental modules do not offer a supported upgrade path, but an unofficial upgrade path is available.

Field Layout (alpha stability)

This module provides the ability for site builders to rearrange fields on content types, block types, etc. into new regions, for both the form and display, on the same forms provided by the normal field user interface. Field Layout has had several bugfixes since 8.3.0, but no significant changes. See the entity display layout roadmap for the next steps for this module, which needs to become stable by 8.5.0 to remain in Drupal core.

Settings Tray (beta stability)

The Settings Tray module allows configuring page elements such as blocks and menus from the frontend of your site. Settings Tray has improved significantly since Drupal 8.3.0, including numerous user interaction and accessibility fixes, better compatibility with stable core modules like Quick Edit and Contextual Links, added documentation, and a CSS reset for better themer experience.

The module reached beta stability following completion of moving the off-canvas dialog renderer into a core component, and renaming the machine name of the module to settings_tray, to match its user-facing name. We hope to make Settings Tray stable by 8.5.0. To track progress, see the "outside in" roadmap issue.

Place Blocks (alpha stability)

This feature allows the user to place a block on any page and see the region where it will be displayed, without having to navigate to a backend administration form. 8.4.0-alpha1 was the deadline for Place Blocks to stabilize, but the module's roadmap was not completed. Furthermore, the module is not intended as a standalone feature and should instead be a built-in part of the Block system. For these reasons, Place Blocks module has been marked hidden in this release (it can still be enabled with Drush). The Place Blocks module itself will be turned into an empty module in Drupal 8.5.x, since ideally the core Block system will offer the same functionality in 8.5.0 (though this depends on completion of a core patch for the feature.)

Download Size md5 hash
drupal-8.4.0.tar.gz 12.76 MB 074795a2f5fc0b599a7dcfb9d1fb03f5
drupal-8.4.0.zip 21.14 MB 60ed1b57a672366eaa54335621ec89fe
Last updated: 4 Oct 2017 at 19:44 UTC
Official release from tag: 
8.4.0
Core compatibility: 
Release type: 
Short description: 
The latest minor release includes new features and backwards-compatible API improvements, and is ready for new development and production sites.
Packaged Git sha1: 
abfe77673a5a6194ef13600e05f1ca2c5dd59db8
Undefined