With custom features modules it's easily possible to end up with a dependency between a non-developer module and a developer module. It's also feasible to assume that some contrib modules incorrectly place a dependency on dev modules. With this in mind, and on the basis that some site builders may click the menu entry without first checking or configuring the list of dev modules, I think we need to introduce a confirmation screen, something like this:

The following modules will be disabled:

  • Devel
  • Views UI
  • etc

Additionally, the following dependent modules will also be disabled:

  • Random contrib module
  • Random features module
  • etc

Would you like to continue?
[Yes] [No]

Support from Acquia helps fund testing for Drupal Acquia logo

Comments

Angry Dan’s picture

Status: Active » Needs review
FileSize
6.64 KB

See attached patch for a solution to this problem.

Dave Reid’s picture

Issue summary: View changes
Status: Needs review » Closed (won't fix)

The 'disable development modules' functionality has been removed as of #2392519: Remove 'Disable Development modules'.