Get large thumbnail for Vimeo and Youtube in media oEmbed.

+1

#2 worked! Tested on Drupal 11.0-dev, PHP 8.3.

Good catch and a must-have fix.

By default, it pulls low resolution (480 × 360 pixels) and stores as original style.
After applying the patch, it pulls high resolution (1280 × 720 pixels) and stores as original style.

There is a patch here that failed testing. Please fix that and merge requests are preferred.

Also: It isn't clear what the screenshots in comment #6 are representing as supporting this issue being ready to commit.

Fixes are made on on 11.x (our main development branch) first, and are then back ported as needed according to our policies.

The patch also worked on my Drupal 10.3.2 (with Thunder distro).

I haven't done any testing, just added the patch in composer.json on a demo I'm working on.

sahana _n → made their first commit to this issue’s fork.

Hi,

I created an MR Please review I tested the test cases, and now the test cases are working fine.

I would greatly appreciate your suggestions for improvement. Please let me know.

Thank you!!

Left comments in MR.

Hi @smustgrave ,

Thanks for the review.

I updated the MR. The test coverage for the provider's name is already covered.
Path: core/modules/media/tests/src/Functional/ResourceFetcherTest.php

Please let me know for other concerns. I am happy to take suggestions.

Thank you!!

Test coverage should be expanded for additional changes.

While it works and gets the maxresdefault image for most YouTube Videos, it does not work every time. There is a chance that a video does not provide a maxresdefault image, just the default hqdefault. I guess that's something to do with the video size.

I added a check that the maxresdefault image is only used, when available. Otherwise, it will just return a 404.

Before the change, this would leave media entities without a thumbnail at all.

Hello,

I had the same problème on Drupal 10.3.5

Trying the patch in #2 didn't solve the problem because the http 404 error request was overriding the response.

So I did this patch that's working for my use case, maybe it needs more testing

I can confirm that patch in #19 works :)