Download drupal-8.4.0-rc2.tar.gztar.gz 12.76 MB
MD5: 50730355dd1a82d988e484c2b4eff422
SHA-1: c1a850bd660bbc717008b5bc806207b08b1ec2c8
SHA-256: 3007c096db2a320101bc0bc34f6b06887246cd51c782b7edbd8fa09533b68479
Download drupal-8.4.0-rc2.zipzip 21.25 MB
MD5: c7d43354145662cd581e089d51049ea0
SHA-1: c16bd946511755dfa379a7b595d13722e91ea7c9
SHA-256: 2aba2f2040210fd8ea33297d24e2a2363afc2d73eb8da041010b09c512e2b9ab

Release info

Created by: catch
Created on: 20 Sep 2017 at 12:48 UTC
Last updated: 18 Oct 2017 at 16:11 UTC
Core compatibility: 8.x
Release type: Bug fixes

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, 8.4.0-beta1, and 8.4.0-rc1 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.

Changes since 8.4.0-rc1:


The selected release is the release that will be used for automated testing. Optional projects are only used for testing.


No required projects


No optional projects