This project is not covered by Drupal’s security advisory policy.
Allows site admins to set a list of css files/path patterns that should be unset. This means when you build themes you don't have to override so much default css. It works with public and private files.
E.g.
modules/*
profiles/*
sites/example.com/modules/og/theme/og.css
This example will remove all CSS from core modules, any css in the profiles directory and the Organic Groups css in the site directory.
This module works by modifying the page template style variable in `unset_css_preprocess_page`, which means that it probably won't work with modules such as IE Unlimited CSS Loader which uses the same technique to modify the css.
You can also set the blacklist in your `settings.php` file.
E.g.
$conf['unset_css_blacklist'] = <<<BLACKLIST
modules/*
BLACKLIST;
This will force the value of the `unset_css_blacklist` variable to be "modules/*".
Project information
- Module categories: Developer Tools
- 7 sites report using this module
- By kaleworsley on , updated
- This project is not covered by the security advisory policy.
Use at your own risk! It may have publicly disclosed vulnerabilities.
Releases
Development version: 7.x-1.x-dev updated 25 Nov 2011 at 00:54 UTC