From 697aeff142336194f5e1d290e6cd99a982a44a40 Mon Sep 17 00:00:00 2001 From: Oliver Davies Date: Wed, 17 Apr 2024 17:57:17 +0100 Subject: [PATCH] Add daily email for 2024-04-14 What about updating custom modules and themes? --- source/_daily_emails/2024-04-14.md | 26 ++++++++++++++++++++++++++ 1 file changed, 26 insertions(+) create mode 100644 source/_daily_emails/2024-04-14.md diff --git a/source/_daily_emails/2024-04-14.md b/source/_daily_emails/2024-04-14.md new file mode 100644 index 000000000..c903593ed --- /dev/null +++ b/source/_daily_emails/2024-04-14.md @@ -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