I've noticed the following bug recently: if you require Drush to disable cck(content module) it nicely prompts you with the actions to be performed. However even if answer is no(don't do it) drush goes ahead and does it anyway.

pokadan@interestsphere.com [~/public_html]# drush disable content -l http://drupalmashup.interestsphere.com
The following modules will be disabled: content, content_permissions, content_taxonomy, content_taxonomy_autocomplete, content_taxonomy_options, content_taxonomy_tree, fieldgroup, nodereference, number, optionwidgets, text, userreference
Do you really want to continue? (y/n): n
drush: Aborting.
Drush command could not be completed.                                [error]

Which is a shame because if you issue the enable command it is unable to perform that:

pokadan@interestsphere.com [~/public_html]# drush enable content -l http://drupalmashup.interestsphere.com
Content is already enabled.                                          [error]
There were no modules that could be enabled.                         [ok]
An error occurred at function : drush_pm_enable                      [error]

I'm running drush in a unix type environment.

Comments

pokadan’s picture

Issue tags: +drush

Please help..

moshe weitzman’s picture

Assigned: Unassigned » owen barton

might be a dupe

owen barton’s picture

Component: Code » PM (dl, en, up ...)
Status: Active » Fixed

Confirmed this no longer happens with Drush 3.x

Status: Fixed » Closed (fixed)
Issue tags: -drush

Automatically closed -- issue fixed for 2 weeks with no activity.