Comments

Issue summary:View changes

Updated issue summary.

Issue summary:View changes

Updated issue summary.

Issue summary:View changes

Updated issue summary.

Issue summary:View changes

update

Title:test with other modulestest with other modules & themes

Issue summary:View changes

Updated issue summary.

Issue summary:View changes

Updated issue summary.

Issue summary:View changes

Updated issue summary.

Issue summary:View changes

Updated issue summary.

Issue summary:View changes

Updated issue summary.

Issue summary:View changes

Updated issue summary.

Issue summary:View changes

Updated issue summary.

I'm not seeing any issues with Labjs, Headjs, and Librejs.

StatusFileSize
new4.53 KB

Thanks for the report :)

Following patch has been committed.

StatusFileSize
new1.98 KB

Following patch has been committed.

StatusFileSize
new1.34 KB

Following patch has been committed.

StatusFileSize
new6.76 KB

Following patch has been committed.

Nothing to report with scriptjs either.

Just a note: I'm not going to test with jquery update as I've personally never had any success with jquery update, so if someone could tackle that module it would be best.

Issue summary:View changes

Updated issue summary.

I have advagg working with jquery update. It was one of the first ones I tested.

Issue summary:View changes

striking tested modules

Issue summary:View changes

jquery cross off

I just tested LABjs and it's not compatible. The JS that gets loaded is not from AdvAgg.

StatusFileSize
new863 bytes

Created this issue for LAB.js and I've committed this patch which will check to make sure the patch has been applied to labjs on the status report page.
#1977122: AdvAgg 7.x-2.x Integration

Issue summary:View changes

Updated issue summary.

Issue summary:View changes

Updated issue summary.

Created a Stage File Proxy issue: #1977170: AdvAgg 7.x-2.x Compatibility

Issue summary:View changes

Updated issue summary.

Issue summary:View changes

Unsure about the other modules as labjs was tested as good but I found that it didn't work without patches.

Issue summary:View changes

Updated issue summary.

Issue summary:View changes

Updated issue summary.

Issue summary:View changes

Updated issue summary.

Component:JS Compression» Code
StatusFileSize
new1.14 KB

Following patch has been committed

Issue summary:View changes

Updated issue summary.

Following patch has been committed

Issue summary:View changes

Updated issue summary.

Status:Active» Fixed

Marking this issue as fixed. Will field one offs as they come in.

Status:Fixed» Closed (fixed)

Automatically closed -- issue fixed for 2 weeks with no activity.

Issue summary:View changes

Updated issue summary.

Any chance of figuring out why Mothership themes do not place nice with AdvAgg?

http://drupal.org/project/mothership - mothership_js_alter()

http://drupal.org/project/mothership - mothership_css_alter()

I've successfully gotten AdvAgg and a Mothership subtheme to play nice, EXCEPT, contextual links are NOT output. The weird part is that the ul for the contextual links is output, but the <a class="contextual-links-trigger" href="#">Configure</a> is not output rendering contextual links virtually useless. I've also checked Chrome inspector and there's no errors of any kind output so I'm at a loss...

The craziest part, and why I want to figure out a way to get this to work, is that with Mothership's options for "Compress all javascripts into one file" and "One css file!" enabled, and AdvAgg enabled the website receives between 97 and 99 score on Google PageSpeed Insights, and the load time on Pingdom is between 800ms and 900ms with less than 20 total http requests.

If the Mothership theme, and AdvAgg could play nice together then we could have some INSANE performance for Drupal all without Boost, Varnish or any other performance boosters. I'd "hate" to see what adding something like Varnish to the mix would do. Maybe a <=500ms load time, and way more potential traffic to be handled? Oh be still my heart.... :-)

Status:Closed (fixed)» Active

Marking this as Active.

I'm pretty sure Mothership's "Compress all javascripts into one file" (mothership_js_onefile) and "One css file" (mothership_css_onefile) are redundant if using AdvAgg's "Combine CSS files by using media queries checkbox". I would also bet that mothership_js_jquery_latest & mothership_js_jquerycdn can be replaced by https://drupal.org/project/jquery_update thus bringing jquery UI up to date as well.

I'll test out the mothership theme some time in the near future.

Depending on how your CSS/JS is added you might see some benefits with advagg_mod's "Optimize CSS/JavaScript Ordering" options. If you have "aggregate" "inline" "aggregate" "inline" these checkboxes should help to group the aggregates together more (to see an example of this, view the source of drupal.org, you will see the inline gaq code in-between js aggregates followed by inline js for drupal.settings).