We invite you to watch the replay of our webinar ” The urgency to migrate to Drupal 9 “. During Drupal Europe which was held from September 10 to 14, 2018, Dries Buytaert, the creator of Drupal , announced that a version “9” would be released in mid-2020. This announcement somewhat surprised the community because although the life cycle of the major version of Drupal is average for previous versions, the technical base, built on the Symfony framework, seemed to promise it a longer life expectancy compared to previous versions. previous versions. Finally, Drupal 8 is retiring in November 2021, at the same Iran Phone Number List as Drupal 7 and Symfony 3 which currently equips the solution. Even if Drupal 8 moved quickly from Symfony 2.x (8.0 to 8.2) then to Symfony 3 (from 8.3), the SensioLabs framework will no longer be maintained from this date.

Iran-Phone-Number-List

prepare-drupal-9 18 months to migrate from Drupal 8.9 Version “9” of Drupal is expected at the beginning of June 2020, at the same time as version 8.9.0, which leaves 18 months for service providers and CIOs to prepare for the migration to the new version of the solution. Under its misleading title, Drupal 9 is not a revolution but simply an “update” of the technical base marked by the transition from Symfony 3 to Symfony 4 and the removal of all obsolete elements. We will come back to this a little later … The real new features are expected from 9.1 (December 2020 ). From June 2020 to November 2021, the technical base will continue to be maintained by the community through the publication of fixes related to security issues.

Drupal 9 Is Coming Soon!

But we should probably not expect to find new features that Drupal 8 has accustomed us to in recent years. Modules produced by the community, whether they are fixes or new features, will continue to be worn by the community at least until the fateful date. Since several versions, the development team “depreciates” part of the code. This is of course to increase compatibility with Symfony 4 but also to remove features that are no longer useful. Thus, the management of advanced workflows is now integrated into the technical base just like the media management expected in 8.7 (May 2019), thus eliminating the use of certain modules from the forge that were necessary until now.

In other words, even if your site was developed according to the rules of the art, the evolution of the solution necessarily had an impact on the code produced. Thus, profound changes will be made on future versions, in particular 8.8.0 (December 2019) and 8.9.0 (June 2010), making it possible to evolve towards Symfony 4 but also on the future Symfony 5 framework, scheduled for November 2019. What impact for the Drupal repository? As with many CMS solutions, Drupal benefits from a forge (called a repository or repository) where all the modules and themes are stored in particular. drupal-9 Those who have known Drupal 6 and Drupal 7, remember the problems inherent in the “major” version upgrade.

Preparing For Drupal 9

To sum up, when you wanted to switch from Drupal 6 to Drupal 7 or from Drupal 7 to Drupal 8 , it was necessary to wait for the porting of the modules or themes that you were using – praying very hard that it (s) would come out ( in) t one day. Otherwise, there was no other option but to find an equivalent solution or to create your own custom module. Before you have a cold sweat, we want to reassure you: this situation will not happen again with Drupal 9 because the technical base, even if it evolves, remains the same. However, adjustments will surely be necessary to complete the upgrade, adjustments – probably minor – to “bring” the functionality of Symfony 3 to Symfony 4.

But unlike what happened with previous versions, the “Drupalian” community is much more seasoned. The development being much more supervised, there is little chance of finding developers a little lost on the way in which they could “upgrade” their module. What impact for Drupal 8 sites If you are already using Drupal 8 for your site, there is no need to redesign it. Acquia is talking about applying a patch, that is to say an operation equivalent to the one you would put in place to switch from one version to another minor version … But make no mistake, because even when you update your version of Drupal, and as long as you have an old version, many modules, and of course custom modules, this task becomes a little more complex and this “Upgrade” can lead to more or less worrying side effects.

Leave a Reply

Your email address will not be published. Required fields are marked *