Support for Drupal 7 is ending on 5 January 2025—it’s time to migrate to Drupal 10! Learn about the many benefits of Drupal 10 and find migration tools in our resource center.Hi,
I have run into much trouble with my AT panels everywhere websites when trying to use the performance css and js aggregators from drupal core.
The CSS and JS aggregated files act as emty files on the browser side (I mean the display is html only), though there is script in these files when I read the file downloaded from the ftp.
When I disable the performance css and js aggregators everything works fine, but I have a huge performance issue as drupal and the modules come with many css and js files. I tried to hardcode the css and js in the page.tpl.php it's a working work around for the css, but this breaks many drupal behaviors, mostly on the admin side. And the js doen't work at all once I aggregate the files manually (no more cycle, no more lightbox, etc.)
cron run, cache flush doesn't do any good
I can't think of any way to troubleshout this. ___
The CSS and JS aggregated files act as emty files on the browser side (I mean the display is html only), though there is script in these files when I read the file downloaded from the ftp.
When I disable the performance css and js aggregators everything works fine, but I have a huge performance issue as drupal and the modules come with many css and js files. I tried to hardcode the css and js in the page.tpl.php it's a working work around for the css, but this breaks many drupal behaviors, mostly on the admin side. And the js doen't work at all once I aggregate the files manually (no more cycle, no more lightbox, etc.)
cron run, cache flush don't do any good
I can't think of any way to troubleshout this.
I have also posted in this issue queue with some details about the errors : http://drupal.org/node/721400 #115 & #117
but I wonder if that is not more related to the use of both panels everywhere and an administration theme (I use AT admin) ?
I know that this concern is quite off topic here, but I bet I won't be the only one to run in that kind of problems.
Comments
Comment #1
Jerome F CreditAttribution: Jerome F commentedSorry for the double paste in the text.
I tried it on every site I did and it is the same behaviour.
When I aggregate CSS and JS, I get a blank CSS and 2 blank js files.
When I flush the cache it works once but the second time I browse the page, the aggregated file name changes, but not the path.
That's all I know so far.
Such a performance issue is a bug but I don't know if it's a panels one, a core one or mine.
Comment #2
Jeff Burnz CreditAttribution: Jeff Burnz commentedI looked at that thread and can see you have a contrib module javascript_aggregator installed:
I would turn that off or even remove it and try with Drupal core only, it could be the minification is tripping someting out, but as for the CSS I don't know, normally these things are issues with permissions or ownership.
Comment #3
Jerome F CreditAttribution: Jerome F commentedThe more I dig into it the more I get confused, but the culprit is not javascript aggregator module I disactivated it and the strange behavior stays there.
I finally realised that even before the css and js issues the page takes much to much time to render
I created an issue in panels everywhere about this topic.
http://drupal.org/node/789534
Comment #4
Jerome F CreditAttribution: Jerome F commentedIt appears that the culprit was the WSOD module. When I disabled it everything went back to normal.
Sorry for that.
I mark this fixed for further testing, If the problem comes back I'll let you know, but if it appears that was the source of all the problems I experienced even with the core css and js aggregator, that's worth knowing.