Download drupal-8.3.0.tar.gztar.gz 12.08 MB
MD5: 1dcce599eddba07eb00e8879937525c3
SHA-1: 59b4a546871d62a6f863db7cbe3db65ac1fb3956
SHA-256: 0cd22d72b5eba604d2b455f97a13b8c551bd1056d857fb45db3a851ce8b09980
Download drupal-8.3.0.zipzip 19.93 MB
MD5: 67b9a07a1a2bab72ff0d0be670daf104
SHA-1: 1b02815c045b8a10cca47dcd66920c6340638179
SHA-256: 1371e3b703d657883c733d15a81f418bafe024da522629717a6ed7c0cc13f0b5

Release info

Created by: cilefen
Created on: 6 Apr 2017 at 00:33 UTC
Last updated: 6 May 2017 at 19:21 UTC
Core compatibility: 8.x
Release type: Bug fixes, New features is brought to you in part by the generous support of sponsors like:

Release notes

Update: Drupal 8.3.1 is available and fixes a security vulnerability. After updating to Drupal 8.2.8 for the security fix and then reading the release notes below, you should update directly to 8.3.1 instead of 8.3.0.

This is a minor version (feature release) of Drupal 8 and is ready for use on production sites. See the CHANGELOG.txt for a summary of changes and improvements since the last minor release. Learn more about Drupal 8 and the Drupal 8 release cycle.

If you encounter errors when updating to this release, see the known issues listed below. If you use Drush, update to Drush 8.1.10 prior to using it to update Drupal. There are known issues updating to Drupal 8.3.0 using older versions of Drush.

This minor release provides new improvements and functionality without breaking backward compatibility (BC) for public APIs except where noted below. Note that 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.

See the Drupal core change records for additional information on API changes. Translators should take note of a handful of minor string changes since the last release.

Backwards compatibility break to correct Serialization module output

#2751325: All serialized values are strings, should be integers/booleans when appropriate corrects a bug that would output all scalar values as strings rather than the correct data type in serialized output, including REST responses. This fix may require some client application updates if the application relies on these values being strings.

An opt-in backwards compatibility mode is configurable at the site level, but not enabled by default. Read the change record for more information on this change and on configuring the backwards compatibility mode.

Important bug fixes since 8.2.x

The following important bugs have been resolved since the final 8.2.x bugfix release:

New stable features

The BigPipe module has become stable in 8.3.0. This module provides an advanced implementation of Facebook's BigPipe page rendering strategy, leading to greatly improved perceived performance for pages with dynamic, personalized, or uncacheable content. See the BigPipe handbook page.

Improved authoring features

Improved site building and administrative features

Improved web services features

Drupal 8.3.0 significantly improves REST and API-first support with the following new features, API and developer experience improvements, and bug fixes.

Improved performance and scalability

Testing improvements

Experimental modules

The modules listed in this section are considered experimental for this release. Experimental modules are provided with Drupal core for testing purposes, but are not yet fully supported.

New experimental modules

Workflows (alpha stability)
This module abstracts the transitions and states system from Content Moderation into a separate component so that it can be reused by modules that implement non-publishing workflows (such as for users or products) as well as content publishing workflows. The module also includes support for default workflow states and transitions.
Layout Discovery (alpha stability)
Provides an API for modules or themes to register layouts as well as five common default layouts. By providing this API in core, we help make it possible for core and contributed layout solutions to be compatible with each other. The following contributed modules already have development versions that support the new API:

See the layout roadmap for the next steps for this module.

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. See the entity display layout roadmap for the next steps for this module.

Updated experimental modules

Migrate (beta stability)
As of 8.3.0, the Migrate API now has beta stability, meaning that no future backwards-incompatible API changes are anticipated, so developers can leverage these APIs in custom migrations. Migrate will be considered completely stable after the issues tagged Migrate critical are resolved, to ensure the base API fully supports critical functionality.
Migrate Drupal and Migrate Drupal UI (alpha stability)
Content Moderation (alpha stability)

Content Moderation allows content workflow states such as Draft, Archived, and Published, and now depends on the new experimental Workflows module (described above) to supply workflows and transitions for these states. See the Workflows change record for more information.

Important: If you previously installed Content Moderation in 8.2.x, you must uninstall it before upgrading to 8.3.0 or you will encounter fatal errors. You will need to reconfigure and reapply your workflows and transitions with the new module after upgrading and re-enabling Content Moderation, so be sure to back them up beforehand. (No upgrade path is supplied since the module is still alpha stability.)

Content Moderation includes many additional improvements in this release:

See the Content Moderation roadmap for the next steps for this module. Both Workflow and Content Moderation must reach beta stability within six months for Content Moderation to remain in core.

Settings Tray (alpha stability)
This is a prototype of Dries's proposed Outside-In usability enhancements. It allows configuring page elements such as blocks and menus from the frontend of your site. See the roadmap of outstanding issues, which includes both planned improvements and known accessibility and interaction bugs. The module is more polished in this release, but still considered alpha stability. It needs to become stable within the next six months to remain in core.
DateTime Range (alpha stability)
The DateTime Range module provides a field type that allows end dates. This is important for contributed modules like the Calendar module to work with Drupal 8 core. The DateTime Range module plan is mostly complete and DateTime Range is expected to be beta stability soon, with only a couple of usability issues remaining. This module needs to become stable within the next six months to remain in core.
Place Block (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. The Place Block module needs to reach stability within the next six months to remain in core.
Inline Form Errors (alpha stability)
This provides a proof-of-concept for showing form errors inline for improved accessibility. Since the last minor release, Inline Form Errors has improved significantly, including usability and accessibility fixes as well as underlying fixes to the form system. The Inline Form Errors experimental module's functionality is now automatically disabled while editing a field with Quick Edit because its method of displaying errors was not compatible with Quick Edit's. (There is a followup to allow any form to opt out of Inline Form Errors.) See the outstanding issues for Inline Form Errors for additional issues that remain before Inline Form Errors can become stable.

Package management improvements

Other API improvements

Modules requiring Drupal 8.3.0 or later can take advantage of these additional API improvements:

Third-party library updates

In addition to the vendor updates and coding standards changes described below, PHP CodeSniffer and Drupal Coder have been added as development requirements: #2744463: Add phpcs/coder to dev requirements. (As a reminder, dev dependencies should never be added to production or Internet-facing sites. See Drupal 8 will no longer include dev dependencies in release packages for more information.)

Changed coding standards

Drupal 8.3.0 has adopted the following coding standards changes:

Known issues

We've received reports of the following issues with this release:

  1. Sites that have the HAL module enabled and are upgrading from 8.1.x have encountered #2867444:
    Configuration schema errors whilst updating to 8.3.0
    . Possible workarounds include updating to 8.2.7 first and then to 8.3.0, or (for sites using Drush) updating to Drush 8.1.10. (Note that 8.1.x has been end-of-life since September 2016, so we generally do not provide full support for updates that skip minor releases.)
  2. Some users have reported #2867253: Upgrade to 8.3.0: Call to a member function get() on array in CacheCollector.php. If you encounter this error, please provide a list of installed contributed modules and any other information about your site on the linked issue.
  3. There is a small BC break in statistics_get() when it is used with an invalid node ID. #2867493: Error: Call to a member function getTotalCount() on boolean in statistics_get() provides a fix for this issue.
  4. #2853509: Don't render status messages if there are no messages introduced a regression that was noted in #2875947: CSS files not loaded on AJAX calls.

Drupal 8 currently has a number of known issues related to incorrect tracking of file usage, which can result in files being unexpectedly deleted from a site. Site owners experiencing unexplained file loss should consider setting "Delete orphaned files" to "Never" on /admin/config/media/file-system until these issues are resolved, and note the following issues:

Search the issue queue for all known issues.

All changes since 8.3.0-rc2


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