See what uninstalling a module deletes, before you do it.
Uninstalling a module deletes more than the module. With the Context module, every context created after installing it is stored under the module's name, so uninstalling Context deletes all of them, and the Uninstall page never says so. Uninstall Impact lists, for your site, everything an uninstall would delete or change. It never changes anything itself.
What it lists
- Modules uninstalled with it: installed modules that depend on it.
- What blocks the uninstall: for example, content of a type it provides.
- Everything built with it: every item of a configuration type it provides, with labels.
- Other configuration that uses it: which items fix themselves (a role loses permissions) and which are deleted (a workflow, a whole view).
- Content types, fields and database tables dropped, with item and row counts.
- Its own settings.
Each section is a dry run of the same core code the real uninstall uses.
Where
- Reports » Uninstall impact
- A What uninstalling deletes link next to every module on the Uninstall page
drush uninstall-impact MODULE[,MODULE...], also as JSON or CSV for CI
Why it matters for government and regulated sites
An uninstall that drops tables holding records under a retention schedule is a records-management incident. Seeing the row counts first prevents it and avoids a restore from backup.
Related
Drupal Cleanup: its config import policy only lets an import uninstall modules you list on purpose.
Requirements
Drupal 10.3 or 11. No other modules.
More Modules
- NIST for Gov: Reports that check a Drupal site against NIST SP 800-53 Rev. 5 controls, starting with API keys, passwords and tokens stored in plain text.
Related sites
Project information
- Project categories: Developer tools
- Created by trigve hagen on , updated
Stable releases for this project are covered by the security advisory policy.
There are currently no supported stable releases.
