I installed unlimited css on my development website when I first ran into the ie problem and it solved it right away. Thank you!
Now I've copied the site over to a production environment. I've been putting in fewer modules on the production site to keep it leaner, and just now installed unlimited css when I ran into the ie problem again.

The odd thing is that it isn't working on the production site, but it is working on the development site. There aren't any modules on the production site that aren't in the development site, in fact there are many fewer.

The page source on my dev site uses the @import calls, while on the production site it is still links.

I've cleared the cache in Drupal and also in my browser.

admin/settings/performance is identical on both installations, and I've cleared the cache. I also included 

  function ves_v2_preprocess_page(&$vars, $hook) {
    unlimited_css_preprocess_page($vars);
  }

in my template.php (ves_v2) file.

Any ideas where else I should look?

Is it possible that the order of enabling modules may make a difference?

Comments

ademarco’s picture

ademarco commented
Status: Active » Postponed (maintainer needs more info)

A new version of the module is out (6.x-1.2), could you check if you still have this issue? Thanks.

donquixote’s picture

donquixote commented

Please check #912374: Other modules can override $vars['styles'] after unlimited_css_preprocess_page() has run..
And, what means "it isn't working" ? If you see link tags, this can be intended. unlimited_css will only put @import when you hit the magic number.

donquixote’s picture

donquixote commented
Status: Postponed (maintainer needs more info) » Closed (cannot reproduce)

Hi,
sorry for letting this sleep for a long time.
Is this still an issue with the current version?

I close this, as not much feedback has been provided, and this is likely no longer the case in the recent version.