We read every piece of feedback, and take your input very seriously.
To see all available qualifiers, see our documentation.
Have a question about this project? Sign up for a free GitHub account to open an issue and contact its maintainers and the community.
By clicking “Sign up for GitHub”, you agree to our terms of service and privacy statement. We’ll occasionally send you account related emails.
Already on GitHub? Sign in to your account
<amp-pixel
The stats tracking code should still be there.
It's not there.
Reported in 1210111-zen
The text was updated successfully, but these errors were encountered:
This is because the AMP plugin was updated to back off of adding JP support in 6.2: ampproject/amp-wp@c280a51
Jetpack is checking for amp_is_canonical : 1bd4eaa#diff-f26e9ed01c2ca4e906e59c7c15b45ab1R69
amp_is_canonical
That function, though, is to check if themes are declaring their own AMP support, thus short-circuiting the default templates: https://github.com/Automattic/amp-wp/blob/6e6275b84bba131010a90dbea4d325986728057b/amp.php#L274
EDIT: #9625 looks like it should have addressed this, so might be something else. No joy nevertheless for a pixel in amp.
Sorry, something went wrong.
I think I may have come across a site experiencing behaviour related to this in #1208872-zen.
Tracking code is present on non-AMP pages, but missing on AMP pages, which is causing stats from Twitter to not report correctly in Calypso.
gravityrail
Successfully merging a pull request may close this issue.
Steps to reproduce the issue
<amp-pixel
What I expected
The stats tracking code should still be there.
What happened instead
It's not there.
Reported in 1210111-zen
The text was updated successfully, but these errors were encountered: