You signed in with another tab or window. Reload to refresh your session.You signed out in another tab or window. Reload to refresh your session.You switched accounts on another tab or window. Reload to refresh your session.Dismiss alert
I've searched for any related issues and avoided creating a duplicate issue.
Please give us a description of what happened.
When the option "YouTube embeds: make pages load faster by only loading the YouTube player when the user clicks play" is enabled, videos simply disappear on AMP pages.
I'm using the official AMP plugin, but apparently it also happens with other AMP plugins:
Please describe what you expected to happen and why.
There's no need to replace the YouTube player in AMP pages, since AMP already has it's own lazyload solution. Yoast should just skip AMP for this feature.
How can we reproduce this behavior?
Enable the lazyload option in Yoast Video
Open a AMP post with a embeded YouTube video
That's all.
Technical info
If relevant, which editor is affected (or editors):
Classic Editor
Gutenberg
Classic Editor plugin
Which browser is affected (or browsers):
Chrome
Firefox
Safari
Other
Used versions
WordPress version: 6.0
Yoast SEO version: 14.5
Gutenberg plugin version:
Classic Editor plugin version:
Relevant plugins in case of a bug: AMP (official version) 2.2.4
Tested with theme:
The text was updated successfully, but these errors were encountered:
Please give us a description of what happened.
When the option "YouTube embeds: make pages load faster by only loading the YouTube player when the user clicks play" is enabled, videos simply disappear on AMP pages.
I'm using the official AMP plugin, but apparently it also happens with other AMP plugins:
This is the exact same bug that i'm experiencing.
Please describe what you expected to happen and why.
There's no need to replace the YouTube player in AMP pages, since AMP already has it's own lazyload solution. Yoast should just skip AMP for this feature.
How can we reproduce this behavior?
Technical info
Used versions
The text was updated successfully, but these errors were encountered: