Issues with Hamburger Menu and Missing Image

Hey Alex,

It looks like you have a malformed script tag, like so:

Code:

Log In or Sign Up to view this code.

The ="async" on the end is being incorrectly added as a second part to the data-src attribute. When the CookieYes plugin tries to process this, it isn't handling the malformed attribute and this is causing a JavaScript error which is preventing other scripts running on the page. I believe this is what is stopping the menu from working (when I accept cookies, CookieYes doesn't process the tag and the menu works). I think it might likewise be preventing the slider from animating in the slide with your image.

I'm can't tell exactly the source of the error. It's possible that the google tag manager tag is malformed to begin with, in which case looking at and correcting how the tag is added (specifically removing the ="async" part) should fix it.

But it's also possible that lightspeed is corrupting the script tag when it modifies it to defer the script. If that's the case you might need to either disable lightspeed, add an exception so that it doesn't process this script tag, or contact the lightspeed developers for advice on how to fix the issue.

Finally, while I don't think CookieYes is causing the malformed tag, it is ultimately triggering the JavaScript error. So again, disabling this plugin or contacting the developers for a workaround to handle such tags might resolve the issue.

Hope that helps!

 

Sure, I totally understand.

Hopefully Divi support have been able to shed some light on it. If not, here are a couple more observations.

First, the "google_gtag.js" exclusion should just be "google_gtagjs" (no period). I can still see LiteSpeed processing the script tag (albeit intermittently), so I think the exclusions aren't currently working. It might be worth disabling LiteSpeed entirely and testing to see if that sorts the issue.

Second, I think I now know how the tag is getting corrupted. Whatever is adding the tag in the first place seems to be setting the following attribute:

async="async"

However, the async attribute is normally just indicated by the presence (or absense) of the attribute name, i.e:

async

When LiteSpeed applies its own deferral mechanism to the script tag, I think it is trying to remove the existing async attribute, but only actually getting write of the name, leaving:

="async"

Which is making the script tag malformed.

The fix, then would be any of: correcting the tag itself, preventing LiteSpeed from processing the tag, or ensuring that CookieYes or similar plugins aren't tripping over the malformed tag.