anthonyfletchers

Hi – I am implementing the FB Pixel code via GTM and the app id is not recognised by Yoast. If I try using https://graph.facebook.com/<APP_ID&gt; then I receive the following response:

{
“error”: {
“message”: “An access token is required to request this resource.”,
“type”: “OAuthException”,
“code”: 104,
“fbtrace_id”: “AqsKQs0BoBJEQKBTZBp7rKn”
}
}

I can’t see a way past this and our analytics have basically stopped working. Does anyone have an idea how I can:

a) Get an access token,
b) Get the Pixel code to work using Yoast.

Is the only solution to bypass Yoast altogether and to roll our own?

Many thanks in advcance,

Anthony

This is a great idea, and I’m experiencing the same issues with Breeze not being able to load CSS async or to defer it. It is the only thing left for me to do in terms of optimisations.

I noticed a similar request posted over two years ago but there has been no movement thus far.

Maybe it’s time to move on this one? Almost all of the other cache plugins work in this way and Breeze will only be better with this functionality.

Hi,
I noticed this post and have a similar issue.

I installed the plugin and assigned it to a CPT (called FAQ, for frequently asked questions). Now when I go to my FAQs page, it shows the *archive* and not the actual page.

Similarly, with other CPTs on the system for which I have *not* activated this plugin but if I click on any of the links to view the CPT it shows a 404 page instead.

I’ve tried clearing permalinks, etc.. but that has had no effect. Archive pages and 404s are everywhere now.

Any ideas how I can remove the effects that this plugin has had on my project?

Many thanks ??