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.

<?php
$conf
['unset_css_blacklist'] = <<<BLACKLIST
modules/*
BLACKLIST;
?>

This will force the value of the `unset_css_blacklist` variable to be "modules/*".

Downloads

Recommended releases

Version Downloads Date Links
7.x-1.0-alpha1 tar.gz (7.83 KB) | zip (8.51 KB) 2011-Nov-24 Notes
6.x-1.1 tar.gz (7.84 KB) | zip (8.52 KB) 2011-Nov-24 Notes

Development releases

Version Downloads Date Links
7.x-1.x-dev tar.gz (7.85 KB) | zip (8.53 KB) 2011-Dec-05 Notes
6.x-1.x-dev tar.gz (7.89 KB) | zip (8.57 KB) 2011-Nov-25 Notes

Project Information


Maintainers for Unset CSS

  • kaleworsley - 7 commits
    last: 24 weeks ago, first: 26 weeks ago

Issues for Unset CSS

To avoid duplicates, please search before submitting a new issue.
All issues
Bug reports
nobody click here