The Drupal community launches new functionalities with its version of the core 8.6.0

10 September 2018
Drupal 8.6
This week, we tested the first stable version of the version 8.6. What new functionalities can we see in 8.6? Here is our overview of what is included.

1. AUSY PRojects

We had the opportunity to install the 8.6.0 version on all of our projects currently in development and maintenance without setbacks, which proves that Drupal 8 has reached maturity.

2. new functionalities or updates in 8.6

The Drupal community released an important update with Drupal 8.6.0, which offers significant improvements.


It is the first version of Drupal 8 that offers a full migration path from Drupal 7 to Drupal 8. Many modifications have been necessary for migrating the APIs in order to make that possible.

Multilingual migrations are as of now deactivated unless the corresponding new experimental module is activated.

The migration of temporary files has been cancelled for the Drupal 7 migrations. This should not have an impact on standard migration since temporary files are, by nature, ephemeral and should not be migrated.

Multiple methods on MigrateFieldInterface have been modified in order to make it more self-documentable. The contrib and custom modules may need to update their sources. Method duplication will make it possible for modules to function simultaneously with 8.5.x and 8.6.x.


The Views integration Datetime Range fields should extend the Views integration for regular Datetime fields. In the previous versions of Drupal 8, the date range fields were not identical to the other datetime fields. Since the previous filter had different operations from those available for the datetime fields, an update hook transforms the operations into a new format. The update hook will list updated views. Creators/developers/site administrators must verify these views in order to check that the filtering operation is appropriate.


The configuration installation programme now installs optional configuration when there is recursive dependence in relation to other optional configurations installed at the same time. This modification does not require modification on the part of the module authors or site owners, but the site owners must take note that from now on, supplementary configurations can be installed on their import or export sites.



Until Drupal 8.5, the reference type field to a taxonomy term was not standardised. It was stocked in a separate database table. Its Views integration was fragile and the Migrate support was blocked for the taxonomy terms. All that has been resolved by making the field a standard entity reference field. Updates may be necessary for the modules that directly query the taxonomy_term_hierarchy table.


The taxonomy terms now have a published field in order to permit workflow moderation. In the majority of cases, the field will be automatically installed. However, if your site or module already has a taxonomy field with this name, read the modification record in order to know how to update your site.


The configuration of the editorial workflow has been moved from content moderation into the standard profile. This means that installation profiles and distributions based on this configuration must add it to their own profiles, because they will no longer be automatically installed with Content Moderation.


The HAL and JSON normalisers are now responsible for map and field property types.

It is now possible to download files via REST API. There is a new resource plug-in called REST File Upload that, once activated, makes it possible to download a file of any size and to create a File entity that can be referenced from a file, image or multimedia field.

The specialised entity reference fields with supplementary properties, such as width and height properties of the image field, are now also present in the release of REST API.


The authors of the contrib modules must take note that certain depreciation warnings are no longer ignored by API in core testing, which means that automated tests which trigger these warnings fail until the obsolete code is replaced.

The Drupal 8 tests had to check compatibility with the old versions of PHPUnit. As of now, PHPUnit 6 will be used for PHP 7.0+ tests. Site owners using PHPUnit 4 on a PHP 7 platform will see the following message appear:

PHPUnit testing framework version 6 or greater is required when running on PHP 7.0 or greater. Run the command ‘composer-run-script drupal-phpunit-upgrade’ in order to fix this.


The media entity provides a “base” entity for media. This entity can refer to all kinds of multimedia objects (local files, YouTube, videos, tweets, Instagram photos, etc.). The media entity provides a relationship between Drupal and the media resource. You can thus refer to a resource or use this entity in any other Drupal entity.

Eventually, this indispensable module will provide a stable API for this new version of Drupal 8, permitting a strong contribution of annex modules. This module will not be visible in the back office until the user interface is improved.

3. Support

Drupal 8 will officially stop supporting PHP 5.5 and 5.6 on 7 March 2019, in less than a year. In order to inform site owners as much as possible, the users will see a warning during installation and on the STATUS report page if the host uses a version of PHP that predates 7.0. We advise you to use a host with PHP 7.1 or greater, in order to ensure that you have enough time to resolve all problems that might affect your Drupal site or other applications (See the PHP requirements page for Drupal 8 for more information on the recommended versions of PHP.).

Developers must consult the modification records of Drupal 8.6.x in order to obtain information on the API additions and internal compatibility breaks.


The latest Drupal update added important functionalities for managing environments as well as applications. This update confirms Drupal’s status as the essential CMS for web projects.

If you wish to know more about our expertise, visit our Drupal page or contact us via the form to get more information.



Let's discuss your projects together.