I'm using the FCKEditor in conjunction with IMCE. When using Internet Explorer the popup file browser window has degraded due to the too many CSS files in IE issue. I have Unlimited CSS enabled and working for everything else, but when I look at the source code for this file browser page I see that the css files have not been modified by the module.

I noted that in issue #445138 (http://drupal.org/node/445138) you suggested adding in the call to preprocess from unlimited_css in any module that might be preprocessing the page after this module. The only one that I could find would be my own theme preprocess_page function. So I called it there:

   // Hook into unlimited_css.module
   if (module_exists('unlimited_css')) {
     unlimited_css_preprocess_page($vars);
   }

But that still doesn't work. I would be grateful for any assistance or ideas.

Comments

Durrok’s picture

Subscribing... same issue.

protoplasm’s picture

This was a great module for me as well until I was apprised of this issue with Internet Explorer by one of our moderators. We use WYSIWYG & Tinymce on 6.19 with a weighty list of modules. All other browsers work fine with IMCE and your module. I've had to disable the module because of this issue which is major for us and reenable CSS optimization (which cleared up the problem handily). IE strikes, once again.

donquixote’s picture

reenable CSS optimization

which you should always do on production sites. And if you do that, you can leave unlimited_css enabled.

IE strikes, once again.

It would be useful to find out why this happens.
Can you get the latest -dev, and:
- Check $vars['styles'] and $vars['styles_unlimited_css'] in hook_preprocess_page?
- Check your html source for the styles included? Any files missing? Wrong order?
- Check if the iframe has its own stylesheets, or uses the styles from the parent page? (i don't remember how this works)
- Tell me which parts of the page look broken?

protoplasm’s picture

I was using the module for the purpose that I didn't want to enable css optimization in IE. The website completely broke without css optimization in IE and your module fixed that. On the development server it was difficult to tweak and write css in IE with those optimized file names showing in firebug. If I get the chance, I'll look into further.

donquixote’s picture

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