I created a subtheme with compass create and did some modifications in the .info file, added some templates and modified page.tpl.php

Now I get this error: Notice: Undefined index: async in aurora_group_js() (line 435 of /domains/awene.com/dev/sites/all/themes/aurora/includes/scripts.inc).

No clue where to look for to debug it.

Also, and not sure if this is related. The modernizr debug info shows up despite having it set to '0'

Support from Acquia helps fund testing for Drupal Acquia logo

Comments

mixhael’s picture

Anyone? This error really keeps bugging me

lolmaus’s picture

I'm having this issue too.

Snugug’s picture

Are you both on Aurora 2.1? Do you both have JS Compression enabled? Mixhael, a good place to start to debug it would be line 435 of aurora/includes/scripts.inc. I believe I know the issue, although I thought I had gotten it solved for 2.1. I don't have time to dig in/push out a fix until this weekend, but rest assured nothing is broken; that's a notice, not an error.

lolmaus’s picture

Aurora 2.1. The issue persists regardless of the "Aggregate JavaScript files" setting.

It might be worth mentioning that i receive this error message for a registered user. It does not appear for anon and user 1.

mixhael’s picture

Yes, as far as I see nothing is broken, but it kind of bothers me this error is displayed every page I visit :)

If you have a quick fix: please let me know!

Heads up for Aurora by the way, love it

mixhael’s picture

I actually noticed this error is also displayed for anonymous users...

Snugug’s picture

Check out 7-2.2. It appears as if this is no longer an issue, but want to 2x check with you guys.

mixhael’s picture

It seems to be fixed, however I know have a superfish incompatibility issue:

Warning: file_get_contents(jQuery(function(){ jQuery('#superfish-1').supersubs({minWidth: 12, maxWidth: 27, extraWidth: 1}).superfish({ pathClass: 'active-trail', animation: {opacity:'show'}, speed: 'fast', autoArrows: false, dropShadows: true}); });) [function.file-get-contents]: failed to open stream: No such file or directory in aurora_build_js_cache() (line 689 of /domains/awene.com/dev/sites/all/themes/aurora/includes/scripts.inc

Is this aurora related and should I open a new ticket for this?

mixhael’s picture

Actually, the issue doesn't seem to be solved and introduces more problems:

Notice: Undefined index: force header in aurora_get_js() (line 54 of /domains/awene.com/dev/sites/all/themes/aurora/includes/scripts.inc).
Notice: Undefined index: async in aurora_group_js() (line 454 of /domains/awene.com/dev/sites/all/themes/aurora/includes/scripts.inc).
Warning: file_get_contents(jQuery(function(){ jQuery('#superfish-1').supersubs({minWidth: 12, maxWidth: 27, extraWidth: 1}).superfish({ pathClass: 'active-trail', animation: {opacity:'show'}, speed: 'fast', autoArrows: false, dropShadows: true}); });) [function.file-get-contents]: failed to open stream: No such file or directory in aurora_build_js_cache() (line 689 of /domains/awene.com/dev/sites/all/themes/aurora/includes/scripts.inc).
Notice: Undefined index: force header in aurora_get_js() (line 54 of /domains/awene.com/dev/sites/all/themes/aurora/includes/scripts.inc

iamcarrico’s picture

Version: 7.x-2.1 » 7.x-2.2
Assigned: Unassigned » iamcarrico
Category: support » bug
Status: Active » Needs work
FileSize
977 bytes

Okay---

The patch here will solve the "Undefined Index" issues-- I am working on why the file_get_contents error happens.

In theory, since it is inline, it shouldnt try and pull the content, but it is. I think this has to do with the way we are grouping the JS. I will take a bit longer of a look this afternoon.

iamcarrico’s picture

Assigned: iamcarrico » Unassigned
Status: Needs work » Needs review
FileSize
1.86 KB

This should be a working patch-- I want to test it a bit more to ensure it is %100 working, and will work with @snugug to ensure it will fit in the future plans.

Status: Needs review » Needs work

The last submitted patch, undefined_index_error-1818636-11.patch, failed testing.

Snugug’s picture

Status: Needs work » Needs review

Status: Needs review » Needs work

The last submitted patch, undefined_index_error-1818636-11.patch, failed testing.

iamcarrico’s picture

Status: Needs work » Needs review
FileSize
1.84 KB

There was a conflict with recent changes--- fixed it.

Status: Needs review » Needs work

The last submitted patch, undefined_index_error-1818636-14.patch, failed testing.

iamcarrico’s picture

Status: Needs work » Needs review

Although--- I am not entirely certain this will work with the new changes-- I am reviewing them now.

iamcarrico’s picture

Version: 7.x-2.2 » 7.x-2.x-dev
Status: Needs review » Fixed

The issue has been found and fixed in the current dev branch.

mixhael’s picture

I guess this does not include a fix for the file_get_contents problem, right?

iamcarrico’s picture

It does actually----

The issue was the the inline script was not being grouped properly, so inline scripts were being treated like files. With the groupings fixed, so is that error. Let me know if it still persists at all.

mixhael’s picture

Status: Fixed » Active

Just updated, first message I saw:

Notice: Undefined index: force header in aurora_get_js() (line 54 of /domains/awene.com/dev/sites/all/themes/aurora/includes/scripts.inc).
Notice: Undefined index: async in aurora_group_js() (line 454 of /domains/awene.com/dev/sites/all/themes/aurora/includes/scripts.inc).
Notice: Undefined index: force header in aurora_get_js() (line 54 of /domains/awene.com/dev/sites/all/themes/aurora/includes/scripts.inc).

:(

iamcarrico’s picture

Did you make sure all the caches were cleared? Because of the position in the preprocessors, the errors displayed on a page will be from 1-2 page loads ago. Hit me up on IRC if you still have an issue ChinggizKhan

lolmaus’s picture

I also saw the error from #21. But after updating cache as suggested in #22 i don't see it anymore.

lolmaus’s picture

Noo! I still see the error!

It just appears not on every page.

Also, it's different from #21:

Notice: Undefined index: every_page in drupal_sort_css_js() (line 3120 of /var/aegir/platforms/drupal-7.17/includes/common.inc).
Notice: Undefined index: every_page in drupal_sort_css_js() (line 3120 of /var/aegir/platforms/drupal-7.17/includes/common.inc).
Notice: Undefined index: every_page in drupal_sort_css_js() (line 3123 of /var/aegir/platforms/drupal-7.17/includes/common.inc).
Warning: uasort(): Array was modified by the user comparison function in aurora_get_js_old() (line 114 of /var/aegir/platforms/drupal-7.17/sites/all/themes/aurora/includes/scripts.inc).
Notice: Undefined index: type in aurora_get_js_old() (line 143 of /var/aegir/platforms/drupal-7.17/sites/all/themes/aurora/includes/scripts.inc).

I've got jQuery Update module installed.

Worse of all, standard Drupal JS won't work! I. e. date calendar won't popup, multiple values field has weights instead of drag-and-drop, etc.

At the same time, custom jQuery JS defined via subtheme's info file does work.

Please help, that site has to go live this week!

Snugug’s picture

The following steps should solve this issue:

Update to 7.x-2.6
Uninstall jQuery Update
Under Theme Settings, in the JavaScript section, choose a jQuery CDN and an updated version of jQuery
If you are moving JavaScript to the footer, it's entirely possible that inline JavaScript is breaking so check "keep libraries in the header"
If you are not using browser wrappings for your JavaScript, under Experimental, make sure that Custom JS handling is turned off. If you are, then I believe we've tracked down and fixed these issues in 7.x-2.6 but if not, for the time being find another way to do that and uncheck the Custom JS anyway.

With Custom JS unchecked, you are literally using Drupal's standard JS handling with allowances made for changing scope a la move to footer.

Snugug’s picture

lolmaus, your error is new, one I haven't come across. Screen shot your sub theme settings page and your JavaScript console.

iamcarrico’s picture

@lolmaus --- Can you open a new issue if Snugug's instructions in #25 do not solve it? If I see a new issue, I will start to work on it promptly.

lolmaus’s picture

Thank you Snugug, #25 + disabling footer JS totally fixed my issue, it works as expected now!

I'm sorry for hijacking the issue after having messed with theme settings. But #25 might be helpful to other inattentive drupaleros. :)

I had given Aurora another try and it seems i'm just too novice to benefit from it: i don't use any of its advanced settings and i don't do complicated JS. So gonna use Boron further, but i already got one Aurora-powered project.

Snugug and ChinggizKhan, thank you for being so responsive. Snugug, i'm also checking out your SASS tools. Hope i'll become skilled enough to leverage Toolkit and other useful stuff.

iamcarrico’s picture

Status: Active » Closed (fixed)

Closing this issue--- should be fixed.