I wonder if you mean this: add_filter( ‘oembed_dataparse’, function( $return, $data, $url ) { // Target only ‘video’ type: if( is_object( $data ) && property_exists( $data, ‘type’ ) && ‘video’ === $data->type ) { // do stuff } return $return; }, 10, 3 ); where we target the video type response from the oEmbed service, … Read more
It doesn’t have to do with the theme. Flickr oEmbed is returning an image file which name ends with _n.jpg, and effectively it has a width of 320px. The bigger version ends with _b.jpg The filter hook that we need to use is embed_oembed_html. The following manipulates the result of the returning html to increase … Read more
Instagram has changed its embed code from being just an iframe to a bunch of HTML and a JS script. Very inelegant, but nothing we can do. This setup, of course, fails when called through AJAX since the JS file that’s part of the HTML does not run. Thankfully there is another official way to … Read more
Your XML root element was ‘OEmbed’, not ‘oembed’, as given in the spec. XML element names are case-sensitive, per the XML spec.
Using the following in your functions.php file should do the trick: /** * Configure default oEmbed video sizes */ function base_oembed_defaults($embed_size) { if( is_single() ) { $embed_size[‘width’] = 580; $embed_size[‘height’] = 435; } return $embed_size; } add_filter(’embed_defaults’, ‘base_oembed_defaults’); Add as many WordPress conditional statements as you like to match the desired aspect ratio for each … Read more
Probably impractical. When you do not control the content you can not know if it will be embedable at the time of viewing. Easiest example of why it might be hard in the context of youtube/vimeo is videos that can become restricted, either private or geo restricted. In that case the content is still embedable … Read more
Note that the WPCS standards for PHPCS are not “official”. I am one of the maintainers, and all that we can do is to do our best to match the standards that WordPress suggests. In this case, I’m unsure how you would escape the output from wp_oembed_get(). The function may indeed need to be escaped … Read more
The output of the oEmbed call is filtered through oembed_result and then cached in the database. Every time the content is displayed, the output is filtered again through embed_oembed_html. So you can add a filter in either of these places that checks for width and height attributes and removes them. Of course, since the code … Read more
if you could make it to something like this: <div class=”videoWrapper”> <iframe width=”600″ height=”338″ src=”https://www.youtube.com/embed/f5CcOq8UzkI?feature=oembed” frameborder=”0″ allowfullscreen=””></iframe> </div> then responsive css for that would be like this: .videoWrapper { position: relative; padding-bottom: 56.25%; /* 16:9 */ padding-top: 25px; height: 0; } .videoWrapper iframe { position: absolute; top: 0; left: 0; width: 100%; height: 100%; } … Read more
I think the best thing to do in this case is to wrap your oEmbed content with a div before they are rendered and then show an alternate image with the CSS background-image property. If the video loads, then the oEmbed content will cover the background image. You can add the wrapper using the embed_oembed_html … Read more