1) Create a subtheme of ninesixty

2) Override framework/debug.css with an empty file/entry in subtheme.info

3) Get php warnings:

Notice: Undefined index: every_page in drupal_sort_css_js() (line 3136 of ...\includes\common.inc).
Notice: Undefined index: every_page in drupal_sort_css_js() (line 3139 of ...\includes\common.inc).
Notice: Undefined index: every_page in drupal_sort_css_js() (line 3136 of ...\includes\common.inc).
Notice: Undefined index: every_page in drupal_sort_css_js() (line 3139 of ...\common.inc).
Warning: uasort(): Array was modified by the user comparison function in drupal_get_css() (line 3060 of ...\includes\common.inc).
Notice: Undefined index: type in drupal_get_css() (line 3077 of ...\common.inc).
Warning: ksort() expects parameter 1 to be array, null given in drupal_group_css() (line 3203 of ...\includes\common.inc).
Notice: Undefined index: type in drupal_group_css() (line 3215 of ...\includes\common.inc).
Notice: Undefined index: data in drupal_pre_render_styles() (line 3434 of ...\includes\common.inc).

As far as I can tell, these are caused by ninesixty_css_alter adding an extra entry in the $css array when $framework contains a css file not in $css.

Comments

wylbur’s picture

wylbur commented

We are grappling with this right now, did you come to any solution for this? I'll post anything we come up with.

kevincrafts’s picture

kevincrafts commented

I added the following code to a sub theme and it fixed the warnings (note that it is unsetting the ninesixty css files, not the sub theme):

function hook_css_alter(&$vars) {
    unset($vars['sites/all/themes/ninesixty/styles/framework/reset.css']);
    unset($vars['sites/all/themes/ninesixty/styles/framework/960.css']);
    unset($vars['sites/all/themes/ninesixty/styles/framework/text.css']);
    unset($vars['sites/all/themes/ninesixty/styles/framework/debug.css']);
 }
kevincrafts’s picture

kevincrafts commented
Issue summary: View changes
Status: Active » Needs review