Andrew Fletcher published: 3 August 2022 1 minute read
Replicate
Replicate the bug in your local environment.
Check
Check - do you have the latest version of the contrib module? In case the issue has already been identified and resolved.
A quick check of the issue list for the contrib module.
Nothing.
Document notes
Read through the log files to understand where the bug is located. Devel module is a must for a backend dev to help resolve issues like this one. Ensure Symfony var-dumper or Kint is running. Data is gold here and a time saver.
Armed with data, you will have a great idea of what has gone wrong - so time to fix the bug.
Test. Test. Test.
All working... Create a patch so any future updates don't have the same issue. Also, let the contrib module authors know about the issue via normal git processes.
Related articles
Andrew Fletcher
•
04 Apr 2025
Managing .gitignore changes
When working with Git, the .gitignore file plays a critical role in controlling which files and folders are tracked by version control. Yet, many developers are unsure when changes to .gitignore take effect and how to manage files that are already being tracked. This uncertainty can lead to...
Andrew Fletcher
•
26 Mar 2025
How to fix the ‘Undefined function t’ error in Drupal 10 or 11 code
Upgrading to Drupal 10.4+ you might have noticed a warning in their code editor stating “Undefined function ‘t’”. While Drupal’s `t()` function remains valid in procedural code, some language analysis tools — such as Intelephense — do not automatically recognise Drupal’s global functions. This...
Andrew Fletcher
•
17 Mar 2025
Upgrading to PHP 8.4 challenges with Drupal contrib modules
The upgrade from PHP 8.3.14 to PHP 8.4.4 presents challenges for Drupal 10.4 websites, particularly when dealing with contributed modules. While Drupal core operates seamlessly, various contrib modules have not yet been updated to accommodate changes introduced in PHP 8.4.x. This has resulted in...