- ๐จ๐ฆCanada nickdickinsonwilde Victoria, BC (T'So-uke lands)
Patch solution seems default good. However... that would be a breaking change. I would support this if it was behind a settings flag for existing sites.
- ๐บ๐ธUnited States caspervoogt
For some reason, I have found that at least in one case for me, it helped to add .field-field-media-oembed-video as one of the FitVids video containers on /admin/config/media/fitvids, even though I did have a valid container already defined. That works for me, no need for a patch or extra CSS.
- ๐ฆ๐บAustralia imclean Tasmania
I'm not sure this patch is necessary. Add the oembed URL (e.g.
https://www.example.com/media/oembed
) to "Additional video providers" to get fitvids to recognise it. - ๐ฆ๐บAustralia imclean Tasmania
I'm also using this patch #2966656-34: Negotiate max width/height of oEmbed assets more intelligently โ .
- ๐ฎ๐ณIndia Jeya sundhar Coimbatore
sundhar โ made their first commit to this issueโs fork.
- ๐ช๐ธSpain qpro Spain
#18 ๐ Not applying to oEmbed videos Needs work works for me, thanks, it save my day, although it's a workaround that could lead to some problems, for example when changing beetween environments with diferent domain ( dev.example.com/beta.example.com/example.com)
- ๐ฆ๐บAustralia imclean Tasmania
@qpro, just add the URLs for all the environments, the field accepts multiple values.