Verification *Type the characters you see in the picture; if you can't read them, submit the form and a new image will be generated. Not case sensitive. Switch to audio verification.

Home page

Submitted by Anonymous (not verified) on Vin, 2018-01-19 05:01

Description:

Release notes

This is a alpha release for the next feature release of Drupal 8. Alphas are good testing targets for developers and site builders who are comfortable reporting (and where possible, fixing) their own bugs. Alpha releases are not recommended for non-technical users, nor for production websites. More information on alpha releases.

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.

Important update information

Site update and module owners planning to update to this release should take note of the following important issues:

Drupal 8 will officially drop support for PHP 5.5 and 5.6 in one year, on March 7, 2019. In order to give site owners as much notice as possible, users will now see a warning on installation and on the status report page if the host is running a version of PHP older than 7.0. We recommend you plan to update to a host with PHP 7.1 or higher soon, to ensure you have sufficient time to resolve any issues that may impact your Drupal site or other applications. (See the Drupal 8 PHP requirements page for more information on recommended PHP versions.)

A bug in Symfony 3.4 causes parsing to fail on certain YAML files that contain comments. Drupal core is working around this issue, but custom services.yaml files or other custom YAML formats may need to implement their own fixes until the issue is fixed upstream in Symfony (hopefully before Drupal 8.5.0). See the Symfony 3.4 change record for details.

In order to provide secure REST support for file uploads, viewing public files now requires the "access content" permission. This may require changes to automated tests, but should not affect most sites (since "access content" will already typically be granted). Ensure that the "access content" permission is granted to the relevant roles if you have unusual, custom file handling. File download permission is not affected.

Previously, multi-value base fields in views used incorrect field names, which caused numerous bugs for views data, REST support, etc. and also led to duplicate entries in the Views UI. In 8.5.0, the correct field name is used. Most views should be automatically updated for this change by running update.php, but in rare cases this might break existing custom views. In contrib and custom modules that extend views, overridden base field handlers may need to be updated to use the new (correct) name.

Important: If you have not already upgraded to 8.4.0, read the Drupal 8.4.0 release notes before upgrading to 8.5.0. Drupal 8.4 includes major version updates for Symfony, jQuery, and jQuery UI and is no longer compatible with older versions of Drush.

Earlier development versions of Drupal 8.5.x were potentially vulnerable to a timing attack for viewing REST in rare cases. It is unlikely that this could be exploited; however, if your site is running Drupal 8.5.x-dev and uses REST you should update to 8.5.0-alpha 1 immediately. Drupal 8.4.4 and earlier are not affected, nor are sites that do not enable REST support.

A bug in the 8.5.x upgrade path caused updates to fail with an error with certain configuration. This issue is resolved in 8.5.0-alpha1 and should not affect sites that update directly to 8.5.0-alpha1 or later.

Issue #2808217 by Wim Leers, tedbow, YesCT, dawehner, xjm, Berdir, damiankloip, slucero: To be able to view Vocabulary config entities via REST, one should not have to grant the 'administer taxonomy' permission

Issue #2927766 by Wim Leers: Update ResponseGeneratorTest to use the BrowserTestBase base class instead of the deprecated RESTTestBase

Issue #2449143 by damiankloip, tedbow, Wim Leers, dawehner, Pavan B S, Tybor, effulgentsia, larowlan: REST views specify HTML as a possible request format, so if there is a "regular" HTML view on the same path, it will serve JSON

Issue #2912298 by chr.fritsch, phenaproxima: Make media name available on manage display

Alphas are good testing targets for developers and site builders who are comfortable reporting (and where possible, fixing) their own bugs. Alpha releases are not recommended for non-technical users, nor for production websites.