css aggregation incompatible with Pressflow?

[adixon]

I've just upgraded a site from 3.1.6 to 3.2.2. It's using Pressflow instead of Drupal, which shouldn't make a difference but appears to in this case.

The short version is that it looks funny, and the only way I've been able to fix it is to turn off css aggregation (it goes funny when I turn it on again). In comparing your demo with my site, a key difference is that Pressflow has the full domain of the css aggregated file, whereas your demo (and drupal), just has the path.

So i think the problem comes down to how you're doing the css aggregation is somehow not compatible with Pressflow [Pressflow is also trying to be compatible with the CDN module, so that may be another source of how it's different from regular Drupal]

This is all using the Garland theme, so it's not a theme issue, I don't think.

Anyone have a similar experience? Anyone have a look at the css treatment in CiviCRM to see if it's not quite kosher?

[Donald Lobo]

http://forum.civicrm.org/index.php/topic,15207.msg65582.html#msg65582

lobo

[adixon]

Exactly right (line 2348 of /css/civicrm.css), thank you.