Crează un cont nou

Anonymous's picture

Release notes

This is a release candidate for the next 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 minor release provides new improvements and functionality 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.

For a full list of other API and feature additions included in the 8.4.0 release candidate compared to 8.3.x, see the 8.4.0-alpha1 and 8.4.0-beta1 release notes.

Drush users: Update to Drush 8.1.12

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

Known issues

Major version updates for dependencies

Drupal 8.4.0-alpha1 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.

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

Revision data integrity hotfixes

Drupal 8.4 includes numerous hotfixes for data integrity issues related to revisions, including #2766957: Forward revisions + translation UI can result in forked draft revisions. This issue prevents data loss with multiple draft translations by restricting Drupal to only have one draft translation at a time (so multiple translators cannot have draft translations of the same content in parallel). #2860097: Only having one default revision per entity forces translations to be kept in sync is the issue to allow multiple draft translations again without data loss.

Important fixes in this release

Status of the Workflows and Content Moderation modules

The Workflows module is now stable! By itself, Workflows does not provide new functionality for the site builder, but stabilizing Workflows is an important step toward providing content moderation as a part of Drupal core.

The Content Moderation module is still considered experimental and its status for 8.4.0 is still being reviewed.

Settings Tray module renamed and now in beta

The experimental Settings Tray module's machine name has been changed from outside_in to settings_tray to match user-facing labels. If you have Settings Tray installed on your site, you must uninstall it before upgrading to 8.4.0-rc1 to avoid fatal errors. You can simply re-enable it afterward; since the Settings Tray module does not store any data or configuration, this should not affect your site.) Following this rename, Settings Tray is now considered beta stability.

All changes since 8.4.0-beta1

Download Size md5 hash
drupal-8.4.0-rc1.tar.gz 12.74 MB 28f7b802ddf81f6a5f50a1400766d913 21.19 MB 528f34f4d7e30361a2bedce12d36ea75
Last updated: 6 Sep 2017 at 21:24 UTC
Official release from tag: 
Core compatibility: 
Release type: 
Short description: 
Release candidates are not supported for production sites, but they are intended for widespread testing in preparation for the upcoming stable release.
Packaged Git sha1: