Add daily email for 2024-04-14
What about updating custom modules and themes?
This commit is contained in:
parent
88d5d58cf0
commit
697aeff142
26
source/_daily_emails/2024-04-14.md
Normal file
26
source/_daily_emails/2024-04-14.md
Normal file
|
@ -0,0 +1,26 @@
|
|||
---
|
||||
title: What about updating custom modules and themes?
|
||||
date: 2024-04-14
|
||||
permalink: archive/2024/04/14/what-about-updating-custom-modules-and-themes
|
||||
tags:
|
||||
- software-development
|
||||
- drupal
|
||||
- php
|
||||
cta: d7eol
|
||||
snippet: |
|
||||
But, how do you update custom modules and themes between major modern versions of Drupal?
|
||||
---
|
||||
|
||||
[Yesterday's email][yesterday] was about using Drupal Rector and the Automated Project Update bot to update contributed modules.
|
||||
|
||||
But what about custom modules within your application?
|
||||
|
||||
To do this, I use the `drupal-check` tool, which is built on PHPStan, and the Upgrade Status module.
|
||||
|
||||
They scan your custom modules and themes and report any deprecated code within your custom projects - i.e. code that will be removed in a future major version - and tell you what new code to use instead.
|
||||
|
||||
Once you've removed any deprecations, your module or theme will be ready for the next major version of Drupal.
|
||||
|
||||
This is the approach I've used to upgrade numerous websites between major modern versions of Drupal, making small updates to existing code instead of having to rewrite it from scratch.
|
||||
|
||||
[yesterday]: {{site.url}}/archive/2024/04/12/drupal-rector-and-the-project-update-bot
|
Loading…
Reference in a new issue