Support for Drupal 7 is ending on 5 January 2025—it’s time to migrate to Drupal 10! Learn about the many benefits of Drupal 10 and find migration tools in our resource center.Google has forced(*) a cookie consenting page when a request is sent to https://www.youtube.com/watch?v=### without a consent cookie. So the current method of getting video meta data no longer works.
The response is a 303 code "See Other" with redirection to https://consent.youtube.com/m.
| Comment | File | Size | Author |
|---|---|---|---|
| #5 | youtube-302.patch | 628 bytes | jcisio |
Comments
Comment #2
jcisio CreditAttribution: jcisio as a volunteer and at Axess Open Web Services commentedComment #3
jcisio CreditAttribution: jcisio as a volunteer and at Axess Open Web Services commentedWe could use NoEmbed (
https://noembed.com/embed?url=https://www.youtube.com/watch?v=###) but we don't have much info. Maybe just force to use the API key now?Comment #4
jcisio CreditAttribution: jcisio as a volunteer and at Axess Open Web Services commentedOK I think we can simply change the url to
https://www.youtube.com/oembed?url=https://www.youtube.com/watch?v=###and let the tags/width/height go...Comment #5
jcisio CreditAttribution: jcisio at Axess Open Web Services for Public Sénat commentedBy playing around, it turns out that the GDPR blocking screen is displayed only when the
User-Agentis sent.Comment #6
jcisio CreditAttribution: jcisio as a volunteer and at Axess Open Web Services commentedComment #8
jcisio CreditAttribution: jcisio as a volunteer and at Axess Open Web Services commentedComment #10
bwaindwain CreditAttribution: bwaindwain as a volunteer commentedSome of our users were reporting "Invalid YouTube video identifier." when trying to create youtube video atoms. Turns out it only affected sites on our non-US servers. This patch fixes it.
Thanks @jcisio