Early Bird Registration for DrupalCon Portland 2024 is open! Register by 23:59 PST on 31 March 2024, to get $100 off your ticket.
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'
Comment | File | Size | Author |
---|---|---|---|
#15 | undefined_index_error-1818636-14.patch | 1.84 KB | iamcarrico |
#11 | undefined_index_error-1818636-11.patch | 1.86 KB | iamcarrico |
#10 | undefined_index_error-1818636-10.patch | 977 bytes | iamcarrico |
Comments
Comment #1
mixhael CreditAttribution: mixhael commentedAnyone? This error really keeps bugging me
Comment #2
lolmaus CreditAttribution: lolmaus commentedI'm having this issue too.
Comment #3
Snugug CreditAttribution: Snugug commentedAre 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.Comment #4
lolmaus CreditAttribution: lolmaus commentedAurora 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.
Comment #5
mixhael CreditAttribution: mixhael commentedYes, 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
Comment #6
mixhael CreditAttribution: mixhael commentedI actually noticed this error is also displayed for anonymous users...
Comment #7
Snugug CreditAttribution: Snugug commentedCheck out 7-2.2. It appears as if this is no longer an issue, but want to 2x check with you guys.
Comment #8
mixhael CreditAttribution: mixhael commentedIt seems to be fixed, however I know have a superfish incompatibility issue:
Is this aurora related and should I open a new ticket for this?
Comment #9
mixhael CreditAttribution: mixhael commentedActually, the issue doesn't seem to be solved and introduces more problems:
Comment #10
iamcarrico CreditAttribution: iamcarrico commentedOkay---
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.
Comment #11
iamcarrico CreditAttribution: iamcarrico commentedThis 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.
Comment #13
Snugug CreditAttribution: Snugug commented#11: undefined_index_error-1818636-11.patch queued for re-testing.
Comment #15
iamcarrico CreditAttribution: iamcarrico commentedThere was a conflict with recent changes--- fixed it.
Comment #17
iamcarrico CreditAttribution: iamcarrico commentedAlthough--- I am not entirely certain this will work with the new changes-- I am reviewing them now.
Comment #18
iamcarrico CreditAttribution: iamcarrico commentedThe issue has been found and fixed in the current dev branch.
Comment #19
mixhael CreditAttribution: mixhael commentedI guess this does not include a fix for the file_get_contents problem, right?
Comment #20
iamcarrico CreditAttribution: iamcarrico commentedIt 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.
Comment #21
mixhael CreditAttribution: mixhael commentedJust updated, first message I saw:
:(
Comment #22
iamcarrico CreditAttribution: iamcarrico commentedDid 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
Comment #23
lolmaus CreditAttribution: lolmaus commentedI also saw the error from #21. But after updating cache as suggested in #22 i don't see it anymore.
Comment #24
lolmaus CreditAttribution: lolmaus commentedNoo! I still see the error!
It just appears not on every page.
Also, it's different from #21:
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!
Comment #25
Snugug CreditAttribution: Snugug commentedThe 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.
Comment #26
Snugug CreditAttribution: Snugug commentedlolmaus, your error is new, one I haven't come across. Screen shot your sub theme settings page and your JavaScript console.
Comment #27
iamcarrico CreditAttribution: iamcarrico commented@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.
Comment #28
lolmaus CreditAttribution: lolmaus commentedThank 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.
Comment #29
iamcarrico CreditAttribution: iamcarrico commentedClosing this issue--- should be fixed.