opdavies/oliverdavies.uk
1
0
Fork 0
Code Issues 1 Pull requests Projects 1 Releases Packages Wiki Activity Actions

Move all files to sculpin/

Browse source
This commit is contained in:
Oliver Davies 2025-10-01 00:01:33 +01:00
parent c5d71803a5
commit 0f61b4e9ee
1514 changed files with 0 additions and 0 deletions
Download patch file Download diff file Expand all files Collapse all files

26
source/_posts/2024-04-14.md
View file

@ -1,26 +0,0 @@
---
title: What about updating custom modules and themes?
date: 2024-04-14
permalink: daily/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}}/daily/2024/04/12/drupal-rector-and-the-project-update-bot