How to use Drush to quickly disable & re-enable all non-core modules

generate list

drush statusmodules -p | sed -e 's/\<block //g' -e 's/\<filter //g' -e 's/\<node //g' -e 's/\<system //g' -e 's/\<user //g' > modulelist.txt

disable

drush disable `cat modulelist.txt`

enable

drush enable `cat modulelist.txt`

enjoy

btw, to put your site in maintenance mode:

drush eval 'variable_set('site_offline', 1)'

and to put it back on line

drush eval 'variable_set('site_offline', 0)'

not sure what needs doing here.

maybe put a note in the docs?

:subscribe:

Such a rare event. Please add drush integration to the module that does this (I forget the name).

See http://drupal.org/project/contrib_toggle (which looks to be discontinued for reasons noted on the module's page).

I couldn't get the methods in #1 to work. I believe it may because drush itself has changed.

You can drush pm-enable a list of modules separated by spaces, but with about 290 non-core modules this is more difficult than just checking things off. It would be nice if there was a method to extract the code names for the enabled non-core modules on the current site (maybe I missed something?). Not seeing a command to do that, I went to the update.php page, selected & copied my listing, removed the ' module:' with a replace command in a word processor and then replaced paragraph formatting with a space and that gave me a space separated list of most of my modules I wanted to enable. It worked for most. I got a couple of errors where it didn't work, but it did save me lots of time and enabled most of the files for me.

After almost 4 years, I decided yesterday to learn drush and boy-oh-boy it is a time saver for updating modules. Again, the only problem is finding the code names for the modules. Since I work off the update status page to upgrade my module versions, I kind of wish that 'they' would print out the code names for the file directly on that page.

Anyways, hats off to the developer(s) of drush. What an amazing tool!

http://2bits.com/articles/server-indigestion-the-drupal-contributed-modu...

Thanks for your reply. "mysql> select name from system where type = 'module' and status = 1 order by name"... Fantastic.

(The article is also on server bloat. It's a tribute to drupal that even with all the modules (I'm including the modules within modules in my count) and thousands of pages, pictures, and users--the site is reasonably responsive. The bloat does need to go).

Thanks again!

See:
#440962: a way to list enabled modules so that this output can be fed to a disable command - like in drush_mm module
#888480: drush pm-list: way to exclude rather than include a package

Links at post 13 by xjm explain getting a list of all the enabled modules.
drush pm-list --pipe --type=module --status=enabled

Again this works fine for getting all enabled modules including Core-required modules. Going by the recommended way of upgrading, it would be good to disable all non-Core-required modules.
drush pm-list --type=module --package="Other"
can be used to get a list of all package types. But this is painful to list different types.
It would be good if drush has a feature to not include certain packages. I am not sure if such a thing already exists.

So as of now, am using this script to disable all non-Core-required modules (slight change in the scripts above).
#] drush pm-list --type=module --status=enabled | awk '/\(/ && /\)/ && ! /[Cc]ore.*-.*[Rr]equired/' | sed 's/.*(\(.*\)).*/\1/' > ModulesWoutCore
#] drush pm-disable `cat ModulesWoutCore`

Enable back when rest of upgrade is complete.
#] drush pm-enable `cat ModulesWoutCore`

HIH for ppl who are looking for this.

Re: #14, I proposed an option for this (without all the awk craziness) in #888480: drush pm-list: way to exclude rather than include a package (patch available there), but it was marked "won't fix." If you'd like a simpler way of excluding packages, I'd say follow up on that issue.

Here is my version without awk (also i really don't like backticks...) and it generates a sorted list, which is nicer for checking the list before firing the disable part:

drush pm-list --type=module --status=enabled | sed '/\((.*)\)/!d;/[Cc]ore.*-.*[Rr]equired/d;s/.*(\(.*\)).*/\1/' | sort > noncoremod.txt
drush pm-disable $(cat noncoremod.txt)
drush pm-enable $(cat noncoremod.txt)

Great! Thanks - this will probably save me a lot of headaches.

Might be good to note that this also disables the Core Optional modules...

This would only disable everything not included in core (which is what is needed for Drupal Upgrades).

drush pm-list --type=module --status=enabled | sed '/\((.*)\)/!d;/[Cc]ore.*-.*[Oo]ptional/d;s/.*(\(.*\)).*/\1/' | sort > noncoremod.txt

Note that you will get a notice that says some modules are "a required module and can't be disabled." This should be fine.

Disable non-core in one line with:

drush pml --no-core --type=module --status=enabled --pipe | xargs drush -y dis

I've tried #16 and #18 on a Drupal 6 install with drush_version=4.5 and those worked for me!
Thanx!

#19 works like a charm

#19 worked great although I would definitely send the module list to a file first.

drush pml --no-core --type=module --status=enabled --pipe > modules.txt
xargs -a modules.txt drush -y dis
xargs -a modules.txt drush -y en

Mac Lion's xargs (as does BSD's) lacks the --arg-file (-a) parameter. This worked for me on Mac:

(first command as is)
cat modules.txt | xargs drush -y dis #since you can batch uninstall no problems
cat modules.txt | xargs -L 1 drush -y en #may choke without the "one line at a time" command

If you run the drush disable command one at a time, (-L 1) you could prevent dependent modules, later in the list, from uninstalling. It seems passing module list as a batch is both quicker and more effective.