When the time comes and all of your code is ready, you’ll be able to upgrade to Drupal 9 with minimum hassle. While doing this work, be sure and stay up to date with the latest Drupal 8 minor releases. The work you do not only helps your own organization but potentially countless others. There are a lot of ways to help out to speed up the overall process. If you are done with all of your custom code and low-hanging fruit, dedicate some time inside the issue queues of contrib modules your website depends on. Keep your contrib module inventory up to date during your transition period. By the time you get to them later, it may be a trivial update. This allows time for some of the more difficult contrib work to be completed by the module maintainers and the wider community. This is where you want to start.įocus on your custom modules and the easy contrib updates first. That represents the lowest level of effort. There is no substitute for rolling up your sleeves and getting to work.įor contrib modules, the latest releases will often support both Drupal 8 and Drupal 9, so they can go ahead and be updated. Start adding some of the tickets you created into your sprints or general workload. Updating modules and codeįixing your custom codebase is all work you are going to have to do sooner or later. Many projects won’t require any changes, but it is best to check early so you are not surprised.Īdd any flags as tickets to your ticketing system. The Upgrade Status module should flag these for you. Make sure your templates are not using functions in Twig templates that are not supported in version 2. Twig has its own deprecations moving from Twig 1 to Twig 2. If you use any contrib base or sub-themes, keep them on your list to track and treat them as modules. Group 6: D9 release is not yet available.Group 5: D9 major or minor release available, forked modules.Group 4: D9 major dev release available, not forked.Group 3: D9 minor dev release available, not forked.Group 2: D9 major tagged release available.Group 1: D9 minor tagged release available.Will this contrib module even have a D9 release? Is there a different module that will take its place?.Which modules are we currently forking/patching that may need more hand-holding to get to their D9 release?.For modules with a D9 release, are they minor updates or major updates?.Which have a D9 release, and which does not?.Organize the contrib modules on which you are dependent into groups that represent levels of effort. Now is also a great time to check the contrib space and see if you even need these custom modules anymore. Some things will need minor changes, like a different function call. A VS Code extension is also available.įor each module that has a Drupal 9 compatibility issue, create a ticket in your ticketing system. The benefit of adding it to your CI workflow is to make sure you aren’t introducing any new incompatibilities. This will show you where the work is to get your custom codebase compatible with Drupal 9. Get drupal-check installed and running on a development environment or as part of your CI workflow. Organize the sheet to easily filter your contrib and custom modules because the work process will differ for each category. To get this information into a spreadsheet, install this patch for the module. This will give you a good baseline of the information you want to track. To get started, we suggest installing the Upgrade Status module. Create a list in whatever format will work best for your team. You need to look at three things: custom modules, contrib modules, and themes. This deprecated code can range in impact depending on what you are using and what APIs you have taken advantage of. The Drupal 9 codebase is very similar to the Drupal 8.9 codebase, but it removes the code marked as deprecated. The larger your codebase, the more you need to take into account. When moving to Drupal 9 from Drupal 8 (which reaches end-of-life on November 2, 2021), planning is required. Upgrading to Drupal 9 from Drupal 8 provides the first test of these promises. No more major investments in expensive migrations to maintain feature parity. No more rewriting business logic just to keep things working. With Drupal’s new versioning and release planning came the promise of easy upgrades between major versions.
0 Comments
Leave a Reply. |