You are here

Home » API reference » Unused Modules 6

README.txt in Unused Modules 6 

Over time your website gets unwieldy so it needs cleaning up.
Though it's simple to find what modules are enabled/disabled, it's rather
difficult to find out if this is true for a project.

This is a helper / development module that lists unused modules / projects that
can be safely deleted.
This makes your repository cleaner and your website faster.

Naming / nomenclature
* Project: a project that has its own namespace and can be downloaded from
Drupal.org. Say "Views".
* Module: a project can contain multiple modules. Say "views" and "views_ui".

Examples
* Module "views_ui" is disabled and module "views" is enabled. The project
"views" is not safe to delete.
* Module "admin_menu" is disabled and module "admin_menu_toolbar" is also
disabled. The project "admin_menu" is safe to delete.

Notes / caveats
* Core modules are not listed, never delete them!
* If a module occurs multiple times it is listed only once and always in the
most specific location. This is because the method to track modules is a Drupal
function that returns modules that can be enabled. That function favours
specific (/sites/your-site) over generic (/sites/all).
See https://www.drupal.org/node/176046 .
* Always make a full backup of your database and codebase before deleting modules!
* Always uninstall modules before deleting them.
* Double / triple check results!!!

Usage
Install and go to: /admin/config/development/unused_modules

Sorry, its a heavy page load.

File

README.txt
View source 
  1. Over time your website gets unwieldy so it needs cleaning up.

  2. Though it's simple to find what modules are enabled/disabled, it's rather

  3. difficult to find out if this is true for a project.

  4. 

  5. This is a helper / development module that lists unused modules / projects that

  6. can be safely deleted.

  7. This makes your repository cleaner and your website faster.

  8. 

  9. Naming / nomenclature

  10. * Project: a project that has its own namespace and can be downloaded from

  11. Drupal.org. Say "Views".

  12. * Module: a project can contain multiple modules. Say "views" and "views_ui".

  13. 

  14. Examples

  15. * Module "views_ui" is disabled and module "views" is enabled. The project

  16. "views" is not safe to delete.

  17. * Module "admin_menu" is disabled and module "admin_menu_toolbar" is also

  18. disabled. The project "admin_menu" is safe to delete.

  19. 

  20. Notes / caveats

  21. * Core modules are not listed, never delete them!

  22. * If a module occurs multiple times it is listed only once and always in the

  23. most specific location. This is because the method to track modules is a Drupal

  24. function that returns modules that can be enabled. That function favours

  25. specific (/sites/your-site) over generic (/sites/all).

  26. See https://www.drupal.org/node/176046 .

  27. * Always make a full backup of your database and codebase before deleting modules!

  28. * Always uninstall modules before deleting them.

  29. * Double / triple check results!!!

  30. 

  31. Usage

  32. Install and go to: /admin/config/development/unused_modules

  33. 

  34. Sorry, its a heavy page load.