![]() ![]() Once reviewed, we don’t recommend jumping directly to 8.9 unless you are on a version *prior* to 8.6.1. Make a note of each change that may impact your particular site install and correct any discrepancies that may arise. Changes include the fact that Drupal now requires PHP 7.3 or greater, the addition of new core modules (such as Workflows, Media Library, and JSON: API), changes to the way path aliases are handled, and the introduction of a new set of Composer packages and a default project template. To address this, we strongly recommend first reviewing the release notes of each minor version (i.e., Drupal 8.4.0, 8.5.0, etc.) and note the changes introduced by each version. This can be problematic because each Drupal feature release introduces different overall requirements and various changes under the hood that can require database updates and other special handling. The first major stumbling block many upgrades hit is when the site has lagged significantly behind the Drupal update schedule and is currently on a version of Drupal older than 8.8. If your site’s code is working on Drupal 8.9 and clean of any deprecations, it should work with Drupal 9 since they share the same public APIs. Drupal 8.9 is the long-term support version of Drupal 8 and is the ideal starting place for a D9 upgrade. The first step of the Drupal 9 preparedness project should be to ensure that you are running the latest version of Drupal 8 (8.9.13 at the time of this writing). More commonly, sites will lag on updates, and your reports will show several updates that need to be applied. If your site is well-maintained, this step will be easy: The Upgrade Check report will be mainly Green, and you are well on your way to being ready for D9. While Third And Grove’s support process consists of this as part of our regular support contracts, it’s a fact of life that many teams struggle with prioritizing these updates over more critical work to meet actual business goals. Routine site maintenance should always include installing and testing updates to the latest versions of Drupal Core and installed contributed modules. While it can’t fix everything, it can significantly speed up the process. This module uses the Rector PHP refactoring library to automatically generate patches to fix the deprecations in your code. If your site has a significant amount of custom code, you also want to install Upgrade Rector. ![]() You can run against a subset of your site’s modules if necessary and export the results after running the checks. If your codebase is larger, the checks can take a little bit of time to run, particularly when run locally. Instead, install it as a dev requirement and run it locally or on your development or local environment. Upgrade Status can be run with Drush or from within your Drupal site, but it’s not a good idea to run this on production. Any installed libraries for deprecation status, required changes to our info.yml files, and other possible compatibility issues.Custom code to identify deprecations and required changes.Contributed modules to see if they are Drupal 9 ready, have a compatible upgrade, or have a patch available to make them compatible. ![]() ![]() Global requirements to ensure our environment is configured correctly and has all of the prerequisites installed to run Drupal 9.Fortunately, the Upgrade Status module gives you almost everything you need by checking: Because the first challenge is finding and fixing all of the deprecated code and identifying modules that need updating, you will need a tool to help you. The first step of any project is making sure you have the proper tools to proceed, and Drupal upgrades are no different. That being said, there are still important considerations to keep in mind when preparing and executing your upgrade to Drupal 9. Now that Drupal 9 has been released, we’ve had the opportunity to work through the upgrade process from Drupal 8 and found that it is indeed a significantly lower lift than doing re-implementations while moving to Drupal 8. The update promised to improve compatibilities between versions, introduce gradual deprecation of old APIs alongside new features, and strongly suggested that the days of performing full-site rebuilds to move between major versions of Drupal were in the past. One highly anticipated change was the move to a new structured release cycle. The advent of Drupal 8 brought about many new features and improvements. ![]()
0 Comments
Leave a Reply. |
AuthorWrite something about yourself. No need to be fancy, just an overview. ArchivesCategories |