When I activate the metatag module, my typekit settings essentially turn off. I have a feeling it's because of the order of the code? Any ideas?
The typekit script code is still showing in the source code correctly...

Comments

mosesdog’s picture

Update: the error looks like this:
NetworkError: 403 Forbidden - https://use.typekit.com/...

DamienMcKenna’s picture

Does the problem persist if you disable Metatag again?

mosesdog’s picture

Typekit fonts come back after disabling Metatag.

DamienMcKenna’s picture

Priority: Normal » Major

Bummer. If nobody else can come up with a patch, I'll see if I can try to dig into this soon.

Bumping this to Major because it breaks some site functionality from another module.

mosesdog’s picture

I appreciate it! I'll look into it a little deeper as well, or as much as I am able.
The module is great otherwise.

DamienMcKenna’s picture

Priority: Major » Normal
Status: Active » Postponed (maintainer needs more info)

I looked at the Typekit module - I have no idea how the Metatag module could interfere with it. Do you see any JavaScript errors on the page, either when Metatag is enabled or not? Metatag includes two JS files - one is loaded on the admin/config/search/metatags page, the other on entity & default configuration forms, but otherwise there isn't anything that should be interfering with Typekit.

mosesdog’s picture

The only error that I'm seeing is the Network error for typekit - no other javascript errors. Nothing in my logs either. Really weird.
Thanks for looking into it, not a big deal if we can't solve it.

DamienMcKenna’s picture

Version: 7.x-1.5 » 7.x-1.x-dev

Does the problem persist with recent versions?