![]() ![]() Upgrade to Drush 10 and install it with composer if it’s not already: composer require - dev drush / drush.At time of writing it has the most consistent compatibility with contrib modules. Depending on your situation, I’d suggest the following addendums to this list: I recommend starting with the environment requirements in the official docs which lists Apache/Nginx, PHP, Database, and Drush. Also, it’s much easier to QA several small PRs than one enormous one. Given how many different systems you’re going to mess with it’s really easy to get stuck in various composer or git knots and end up having to redo a lot of work. It’s tempting to do all of these things in one fell swoop, but I recommend against that. The main things you’ll need to consider are local environment requirements, live environment requirements, deprecated contrib/custom code, and composer changes. Make a plan, take it slowįirst, you need to figure out what changes need to be made to the site for D9 compatibility and then build a plan around those requirements. This blog post isn’t a complete guide on how to upgrade to D9 it’s supplemental to the existing documentation found here. If you’ve found yourself in the middle of one such upgrade then you’ve come to the right place. ![]() While that usually is the case, some sites have their own set of hacks, oddities, and technical debt that make the upgrade process a lot more arduous. One of the major selling points of Drupal 9 is that the upgrade is really easy: fix your deprecated code, update your contrib modules, run some composer magic, and you’re done. ![]()
0 Comments
Leave a Reply. |
AuthorWrite something about yourself. No need to be fancy, just an overview. ArchivesCategories |