Drush

WF Extras is a collection of modules that provide extended functionality for WF Tools, but it doesn't make sense having it as part of the core framework.

Isolated the Nagios/Icinga functionality from drush_multi.

For the usage as Nagios/Icinga NRPE Plugin.

It just prints a message and exit with an exit status.

Commands

drush_nagios includes the following commands:

check-updates

Checks for pending updates.

Have you many users spam?
With this simple module you can delete at one time all blocked users from www.example.com / admin / people

Also available as a drush command.

Install the module as usual, go to admin / people and select the checkbox and click erase.
Also if you have blocked a user who does not want to remove the uid can enter to protect it from deletion.

If the administrator blocks a user, it does not take this when deleting all blocked.

Proper site development practices involves one ore more development environment, at least one production server, and perhaps a staging server for teams and clients to interact on code & design that is not yet in production. Each stage (development, staging, production) is called a life cycle stage. With each stage comes unique characteristics: for example debugging code is seldom present on production sites but nearly always enabled on development sites.

This project is not in a usable state.

This is a bunch of different functions that I have written for various things like:

A Drush plugin to flip CSS files. RTL to LTR and vice versa.

First bone to have the drush cssflip command work to flip css files .

For example:
If we want to switch css files for the tweme theme to rtl.

We can apply the following drush command drush csslist to get the list of all css files in the current enabled theme.

Lint your configuration.

Deletes users and all associated entities that have a selected role with a single drush command, button press or cron run.

Usually used for cleaning up test users and data from your production or staging environment.

This module is designed for high traffic sites that make heavy use of caching.

Disables the ability to clear the entire Drupal caches through the admin interface and forces the user to use the multistep version of drush cc instead of drush cc all.

Exposes a number of core caches: module-implements, bootstrap, block etc as well as all the entitycache caches to drush cc. This allows users to avoid clearing all caches when a single cache would have been appropriate.

HTTPRL Spider uses the excellent HTTP Parallel Request & Threading Library to perform an internal cache seeding spider via Drush. This is not a module, it's a command line call that can be used to effectively rebuild all Entity Cache and Boost cache files for an entire site. By default it will spider all known, front-facing entities in a site with a single call.