Closed (fixed)
Project:
Aurora
Version:
7.x-2.0
Component:
Code
Priority:
Normal
Category:
Feature request
Assigned:
Unassigned
Reporter:
Created:
10 Oct 2012 at 20:18 UTC
Updated:
4 Nov 2012 at 00:55 UTC
Jump to comment: Most recent file
Comments
Comment #1
iamcarrico commentedIt will also have a patch that comes with it for the compass-aurora side, so that the settings are added in the .info file.
Comment #2
Snugug commentedThanks for this. I'll take a look at this, might need a little bit of tweaking to make these options all AJAX-y and awesome like the rest of the theme settings page, but otherwise generally looks good. Going to test.
As for the compass-aurora side, a pull request is better than a patch here.
Comment #3
iamcarrico commentedBut of course.
Comment #4
Snugug commentedAwesomesauce. TYM
Comment #5
iamcarrico commentedI forgot to make the diff include the new jQuery files. New patch.
Comment #7
iamcarrico commentedFixed the error
Comment #8
iamcarrico commentedLet me know if it does actually apply for you. It does in my environment
Comment #10
Snugug commented#7: add_in_jquery_update_support-7.patch queued for re-testing.
Comment #12
Snugug commentedWhile I can get this to apply (it has a whitespace issue when it applies, but it will apply cleanly), because of Force Header, the scope for the backup for the CDN is wrong, and when adding Force Header => True with it, it comes in before the external call, which is an issue. Because of how tightly coupled Drupal and jQuery are, jQuery, jQuery.once, Drupal.js, and Settings all need to be loaded in the head still. Anyway, this is a problem because this then breaks all the things, so there's still some work that needs to be done, possibly in scripts.inc to fix the group weight issues.
Comment #13
iamcarrico commentedI see what you mean, I have gone over how the code in scripts.inc goes, and I think I see how it could work better. I will need to do a bit more testing before I can comment on how to get jQuery to be organized better. I know in the past, the only (main) issue we had was when a WYSIWYG was enabled, having code be in the footer caused more issues.
I will look into it this weekend.
Comment #14
iamcarrico commentedCommitted.