Guide Throws Light on Fully Disabling Deprecated Drupal Core Modules

Staff Reporter

Luciano Cossich published a LinkedIn article detailing how to fully disable a deprecated Drupal core module that remained active after an upgrade.

In the post, titled "Disabling That Pesky Deprecated Drupal Core Module That You Didn't Uninstall When You Upgraded Because You Didn't Know Better," Cossich explains the challenges he faced when trying to remove the unused Help module from his personal website. After discovering leftover configuration data causing errors, he documented a manual cleanup process.

The article walks readers through inspecting and editing Drupal’s configuration files, removing obsolete entries from core.extension.yml, user.role.content_editor.yml, and deleting related block configuration files. Cossich also describes using Drush commands to identify, back up, and safely remove lingering configurations tied to the deprecated module.

When standard uninstallation attempts failed, Cossich recommends a full uninstall-reinstall cycle to completely clear leftover menu items and configuration records. The article emphasizes the importance of clearing caches and re-exporting configuration files to prevent future issues.

Source Reference

Title

Disabling that pesky deprecated Drupal core module that you didn't uninstall when you upgraded because you didn't know better

Byline

Luciano Cossich Sales

Date of Publication

19 April 2025

Guide

Drupal Core

Code

Drupal Update

Disclosure: This content is produced with the assistance of AI.

Disclaimer: The opinions expressed in this story do not necessarily represent that of TheDropTimes. We regularly share third-party blog posts that feature Drupal in good faith. TDT recommends Reader's discretion while consuming such content, as the veracity/authenticity of the story depends on the blogger and their motives.

Note: The vision of this web portal is to help promote news and stories around the Drupal community and promote and celebrate the people and organizations in the community. We strive to create and distribute our content based on these content policy. If you see any omission/variation on this please reach out to us at #thedroptimes channel on Drupal Slack and we will try to address the issue as best we can.