Embeds: Add oEmbed provider support.
For the past 6 years, WordPress has operated as an oEmbed consumer, allowing users to easily embed content from other sites. By adding oEmbed provider support, this allows any oEmbed consumer to embed posts from WordPress sites.
In addition to creating an oEmbed provider, WordPress' oEmbed consumer code has been enhanced to work with any site that provides oEmbed data (as long as it matches some strict security rules), and provides a preview from within the post editor.
For security, embeds appear within a sandboxed iframe - the iframe content is a template that can be styled or replaced entirely by the theme on the provider site.
Props swissspidy, pento, melchoyce, netweb, pfefferle, johnbillion, extendwings, davidbinda, danielbachhuber, SergeyBiryukov, afercia
Fixes #32522.
Built from https://develop.svn.wordpress.org/trunk@34903
git-svn-id: http://core.svn.wordpress.org/trunk@34868 1a063a9b-81f0-0310-95a4-ce76da25c4cd
2015-10-07 12:36:25 +02:00
< ? php
/**
* WP_oEmbed_Controller class , used to provide an oEmbed endpoint .
*
* @ package WordPress
* @ subpackage Embeds
* @ since 4.4 . 0
*/
/**
* oEmbed API endpoint controller .
*
2020-11-16 12:04:12 +01:00
* Registers the REST API route and delivers the response data .
2015-10-29 23:51:24 +01:00
* The output format ( XML or JSON ) is handled by the REST API .
Embeds: Add oEmbed provider support.
For the past 6 years, WordPress has operated as an oEmbed consumer, allowing users to easily embed content from other sites. By adding oEmbed provider support, this allows any oEmbed consumer to embed posts from WordPress sites.
In addition to creating an oEmbed provider, WordPress' oEmbed consumer code has been enhanced to work with any site that provides oEmbed data (as long as it matches some strict security rules), and provides a preview from within the post editor.
For security, embeds appear within a sandboxed iframe - the iframe content is a template that can be styled or replaced entirely by the theme on the provider site.
Props swissspidy, pento, melchoyce, netweb, pfefferle, johnbillion, extendwings, davidbinda, danielbachhuber, SergeyBiryukov, afercia
Fixes #32522.
Built from https://develop.svn.wordpress.org/trunk@34903
git-svn-id: http://core.svn.wordpress.org/trunk@34868 1a063a9b-81f0-0310-95a4-ce76da25c4cd
2015-10-07 12:36:25 +02:00
*
* @ since 4.4 . 0
*/
Code Modernization: Add `AllowDynamicProperties` attribute to all (parent) classes.
Dynamic (non-explicitly declared) properties are deprecated as of PHP 8.2 and are expected to become a fatal error in PHP 9.0.
There are a number of ways to mitigate this:
* If it is an accidental typo for a declared property: fix the typo.
* For known properties: declare them on the class.
* For unknown properties: add the magic `__get()`, `__set()`, et al. methods to the class or let the class extend `stdClass` which has highly optimized versions of these magic methods built in.
* For unknown ''use'' of dynamic properties, the `#[AllowDynamicProperties]` attribute can be added to the class. The attribute will automatically be inherited by child classes.
Trac ticket #56034 is open to investigate and handle the third and fourth type of situations, however it has become clear this will need more time and will not be ready in time for WP 6.1.
To reduce “noise” in the meantime, both in the error logs of WP users moving onto PHP 8.2, in the test run logs of WP itself, in test runs of plugins and themes, as well as to prevent duplicate tickets from being opened for the same issue, this commit adds the `#[AllowDynamicProperties]` attribute to all “parent” classes in WP.
The logic used for this commit is as follows:
* If a class already has the attribute: no action needed.
* If a class does not `extend`: add the attribute.
* If a class does `extend`:
- If it extends `stdClass`: no action needed (as `stdClass` supports dynamic properties).
- If it extends a PHP native class: add the attribute.
- If it extends a class from one of WP's external dependencies: add the attribute.
* In all other cases: no action — the attribute should not be needed as child classes inherit from the parent.
Whether or not a class contains magic methods has not been taken into account, as a review of the currently existing magic methods has shown that those are generally not sturdy enough and often even set dynamic properties (which they should not). See the [https://www.youtube.com/watch?v=vDZWepDQQVE live stream from August 16, 2022] for more details.
This commit only affects classes in the `src` directory of WordPress core.
* Tests should not get this attribute, but should be fixed to not use dynamic properties instead. Patches for this are already being committed under ticket #56033.
* While a number bundled themes (2014, 2019, 2020, 2021) contain classes, they are not a part of this commit and may be updated separately.
Reference: [https://wiki.php.net/rfc/deprecate_dynamic_properties PHP RFC: Deprecate dynamic properties].
Follow-up to [53922].
Props jrf, hellofromTonya, markjaquith, peterwilsoncc, costdev, knutsp, aristath.
See #56513, #56034.
Built from https://develop.svn.wordpress.org/trunk@54133
git-svn-id: http://core.svn.wordpress.org/trunk@53692 1a063a9b-81f0-0310-95a4-ce76da25c4cd
2022-09-12 17:47:14 +02:00
#[AllowDynamicProperties]
Embeds: Add oEmbed provider support.
For the past 6 years, WordPress has operated as an oEmbed consumer, allowing users to easily embed content from other sites. By adding oEmbed provider support, this allows any oEmbed consumer to embed posts from WordPress sites.
In addition to creating an oEmbed provider, WordPress' oEmbed consumer code has been enhanced to work with any site that provides oEmbed data (as long as it matches some strict security rules), and provides a preview from within the post editor.
For security, embeds appear within a sandboxed iframe - the iframe content is a template that can be styled or replaced entirely by the theme on the provider site.
Props swissspidy, pento, melchoyce, netweb, pfefferle, johnbillion, extendwings, davidbinda, danielbachhuber, SergeyBiryukov, afercia
Fixes #32522.
Built from https://develop.svn.wordpress.org/trunk@34903
git-svn-id: http://core.svn.wordpress.org/trunk@34868 1a063a9b-81f0-0310-95a4-ce76da25c4cd
2015-10-07 12:36:25 +02:00
final class WP_oEmbed_Controller {
/**
2015-10-29 23:51:24 +01:00
* Register the oEmbed REST API route .
Embeds: Add oEmbed provider support.
For the past 6 years, WordPress has operated as an oEmbed consumer, allowing users to easily embed content from other sites. By adding oEmbed provider support, this allows any oEmbed consumer to embed posts from WordPress sites.
In addition to creating an oEmbed provider, WordPress' oEmbed consumer code has been enhanced to work with any site that provides oEmbed data (as long as it matches some strict security rules), and provides a preview from within the post editor.
For security, embeds appear within a sandboxed iframe - the iframe content is a template that can be styled or replaced entirely by the theme on the provider site.
Props swissspidy, pento, melchoyce, netweb, pfefferle, johnbillion, extendwings, davidbinda, danielbachhuber, SergeyBiryukov, afercia
Fixes #32522.
Built from https://develop.svn.wordpress.org/trunk@34903
git-svn-id: http://core.svn.wordpress.org/trunk@34868 1a063a9b-81f0-0310-95a4-ce76da25c4cd
2015-10-07 12:36:25 +02:00
*
* @ since 4.4 . 0
*/
2015-10-29 23:51:24 +01:00
public function register_routes () {
Embeds: Add oEmbed provider support.
For the past 6 years, WordPress has operated as an oEmbed consumer, allowing users to easily embed content from other sites. By adding oEmbed provider support, this allows any oEmbed consumer to embed posts from WordPress sites.
In addition to creating an oEmbed provider, WordPress' oEmbed consumer code has been enhanced to work with any site that provides oEmbed data (as long as it matches some strict security rules), and provides a preview from within the post editor.
For security, embeds appear within a sandboxed iframe - the iframe content is a template that can be styled or replaced entirely by the theme on the provider site.
Props swissspidy, pento, melchoyce, netweb, pfefferle, johnbillion, extendwings, davidbinda, danielbachhuber, SergeyBiryukov, afercia
Fixes #32522.
Built from https://develop.svn.wordpress.org/trunk@34903
git-svn-id: http://core.svn.wordpress.org/trunk@34868 1a063a9b-81f0-0310-95a4-ce76da25c4cd
2015-10-07 12:36:25 +02:00
/**
2016-05-22 20:15:28 +02:00
* Filters the maxwidth oEmbed parameter .
Embeds: Add oEmbed provider support.
For the past 6 years, WordPress has operated as an oEmbed consumer, allowing users to easily embed content from other sites. By adding oEmbed provider support, this allows any oEmbed consumer to embed posts from WordPress sites.
In addition to creating an oEmbed provider, WordPress' oEmbed consumer code has been enhanced to work with any site that provides oEmbed data (as long as it matches some strict security rules), and provides a preview from within the post editor.
For security, embeds appear within a sandboxed iframe - the iframe content is a template that can be styled or replaced entirely by the theme on the provider site.
Props swissspidy, pento, melchoyce, netweb, pfefferle, johnbillion, extendwings, davidbinda, danielbachhuber, SergeyBiryukov, afercia
Fixes #32522.
Built from https://develop.svn.wordpress.org/trunk@34903
git-svn-id: http://core.svn.wordpress.org/trunk@34868 1a063a9b-81f0-0310-95a4-ce76da25c4cd
2015-10-07 12:36:25 +02:00
*
* @ since 4.4 . 0
*
* @ param int $maxwidth Maximum allowed width . Default 600.
*/
$maxwidth = apply_filters ( 'oembed_default_width' , 600 );
2017-12-01 00:11:00 +01:00
register_rest_route (
2018-08-17 03:51:36 +02:00
'oembed/1.0' ,
'/embed' ,
array (
2017-12-01 00:11:00 +01:00
array (
2020-07-21 14:03:05 +02:00
'methods' => WP_REST_Server :: READABLE ,
'callback' => array ( $this , 'get_item' ),
'permission_callback' => '__return_true' ,
'args' => array (
2017-12-01 00:11:00 +01:00
'url' => array (
2020-05-04 00:42:06 +02:00
'description' => __ ( 'The URL of the resource for which to fetch oEmbed data.' ),
'required' => true ,
'type' => 'string' ,
'format' => 'uri' ,
2017-12-01 00:11:00 +01:00
),
'format' => array (
'default' => 'json' ,
'sanitize_callback' => 'wp_oembed_ensure_format' ,
),
'maxwidth' => array (
'default' => $maxwidth ,
'sanitize_callback' => 'absint' ,
),
2015-10-29 23:51:24 +01:00
),
),
2017-12-01 00:11:00 +01:00
)
);
2017-05-11 20:18:46 +02:00
2017-12-01 00:11:00 +01:00
register_rest_route (
2018-08-17 03:51:36 +02:00
'oembed/1.0' ,
'/proxy' ,
array (
2017-12-01 00:11:00 +01:00
array (
'methods' => WP_REST_Server :: READABLE ,
'callback' => array ( $this , 'get_proxy_item' ),
'permission_callback' => array ( $this , 'get_proxy_item_permissions_check' ),
'args' => array (
'url' => array (
2020-05-04 00:42:06 +02:00
'description' => __ ( 'The URL of the resource for which to fetch oEmbed data.' ),
'required' => true ,
'type' => 'string' ,
'format' => 'uri' ,
2017-12-01 00:11:00 +01:00
),
'format' => array (
'description' => __ ( 'The oEmbed format to use.' ),
'type' => 'string' ,
'default' => 'json' ,
'enum' => array (
'json' ,
'xml' ,
),
),
'maxwidth' => array (
'description' => __ ( 'The maximum width of the embed frame in pixels.' ),
'type' => 'integer' ,
'default' => $maxwidth ,
'sanitize_callback' => 'absint' ,
),
'maxheight' => array (
'description' => __ ( 'The maximum height of the embed frame in pixels.' ),
'type' => 'integer' ,
'sanitize_callback' => 'absint' ,
),
'discover' => array (
General: Remove “whitelist” and “blacklist” in favor of more clear and inclusive language.
“The WordPress open source community cares about diversity. We strive to maintain a welcoming environment where everyone can feel included.”
With this commit, all occurrences of “whitelist” and “blacklist” (with the single exception of the `$new_whitelist_options` global variable) are removed. A new ticket has been opened to explore renaming the `$new_whitelist_options` variable (#50434).
Changing to more specific names or rewording sentences containing these terms not only makes the code more inclusive, but also helps provide clarity. These terms are often ambiguous. What is being blocked or allowed is not always immediately clear. This can make it more difficult for non-native English speakers to read through the codebase.
Words matter. If one contributor feels more welcome because these terms are removed, this was worth the effort.
Props strangerstudios, jorbin, desrosj, joemcgill, timothyblynjacobs, ocean90, ayeshrajans, davidbaumwald, earnjam.
See #48900, #50434.
Fixes #50413.
Built from https://develop.svn.wordpress.org/trunk@48121
git-svn-id: http://core.svn.wordpress.org/trunk@47890 1a063a9b-81f0-0310-95a4-ce76da25c4cd
2020-06-22 19:26:13 +02:00
'description' => __ ( 'Whether to perform an oEmbed discovery request for unsanctioned providers.' ),
2017-12-01 00:11:00 +01:00
'type' => 'boolean' ,
'default' => true ,
2017-05-11 20:18:46 +02:00
),
),
),
2017-12-01 00:11:00 +01:00
)
);
Embeds: Add oEmbed provider support.
For the past 6 years, WordPress has operated as an oEmbed consumer, allowing users to easily embed content from other sites. By adding oEmbed provider support, this allows any oEmbed consumer to embed posts from WordPress sites.
In addition to creating an oEmbed provider, WordPress' oEmbed consumer code has been enhanced to work with any site that provides oEmbed data (as long as it matches some strict security rules), and provides a preview from within the post editor.
For security, embeds appear within a sandboxed iframe - the iframe content is a template that can be styled or replaced entirely by the theme on the provider site.
Props swissspidy, pento, melchoyce, netweb, pfefferle, johnbillion, extendwings, davidbinda, danielbachhuber, SergeyBiryukov, afercia
Fixes #32522.
Built from https://develop.svn.wordpress.org/trunk@34903
git-svn-id: http://core.svn.wordpress.org/trunk@34868 1a063a9b-81f0-0310-95a4-ce76da25c4cd
2015-10-07 12:36:25 +02:00
}
/**
2017-05-11 20:18:46 +02:00
* Callback for the embed API endpoint .
2015-10-29 23:51:24 +01:00
*
* Returns the JSON object for the post .
Embeds: Add oEmbed provider support.
For the past 6 years, WordPress has operated as an oEmbed consumer, allowing users to easily embed content from other sites. By adding oEmbed provider support, this allows any oEmbed consumer to embed posts from WordPress sites.
In addition to creating an oEmbed provider, WordPress' oEmbed consumer code has been enhanced to work with any site that provides oEmbed data (as long as it matches some strict security rules), and provides a preview from within the post editor.
For security, embeds appear within a sandboxed iframe - the iframe content is a template that can be styled or replaced entirely by the theme on the provider site.
Props swissspidy, pento, melchoyce, netweb, pfefferle, johnbillion, extendwings, davidbinda, danielbachhuber, SergeyBiryukov, afercia
Fixes #32522.
Built from https://develop.svn.wordpress.org/trunk@34903
git-svn-id: http://core.svn.wordpress.org/trunk@34868 1a063a9b-81f0-0310-95a4-ce76da25c4cd
2015-10-07 12:36:25 +02:00
*
* @ since 4.4 . 0
*
2015-10-29 23:51:24 +01:00
* @ param WP_REST_Request $request Full data about the request .
2019-11-11 03:43:03 +01:00
* @ return array | WP_Error oEmbed response data or WP_Error on failure .
Embeds: Add oEmbed provider support.
For the past 6 years, WordPress has operated as an oEmbed consumer, allowing users to easily embed content from other sites. By adding oEmbed provider support, this allows any oEmbed consumer to embed posts from WordPress sites.
In addition to creating an oEmbed provider, WordPress' oEmbed consumer code has been enhanced to work with any site that provides oEmbed data (as long as it matches some strict security rules), and provides a preview from within the post editor.
For security, embeds appear within a sandboxed iframe - the iframe content is a template that can be styled or replaced entirely by the theme on the provider site.
Props swissspidy, pento, melchoyce, netweb, pfefferle, johnbillion, extendwings, davidbinda, danielbachhuber, SergeyBiryukov, afercia
Fixes #32522.
Built from https://develop.svn.wordpress.org/trunk@34903
git-svn-id: http://core.svn.wordpress.org/trunk@34868 1a063a9b-81f0-0310-95a4-ce76da25c4cd
2015-10-07 12:36:25 +02:00
*/
2015-10-29 23:51:24 +01:00
public function get_item ( $request ) {
Embeds: Add oEmbed provider support.
For the past 6 years, WordPress has operated as an oEmbed consumer, allowing users to easily embed content from other sites. By adding oEmbed provider support, this allows any oEmbed consumer to embed posts from WordPress sites.
In addition to creating an oEmbed provider, WordPress' oEmbed consumer code has been enhanced to work with any site that provides oEmbed data (as long as it matches some strict security rules), and provides a preview from within the post editor.
For security, embeds appear within a sandboxed iframe - the iframe content is a template that can be styled or replaced entirely by the theme on the provider site.
Props swissspidy, pento, melchoyce, netweb, pfefferle, johnbillion, extendwings, davidbinda, danielbachhuber, SergeyBiryukov, afercia
Fixes #32522.
Built from https://develop.svn.wordpress.org/trunk@34903
git-svn-id: http://core.svn.wordpress.org/trunk@34868 1a063a9b-81f0-0310-95a4-ce76da25c4cd
2015-10-07 12:36:25 +02:00
$post_id = url_to_postid ( $request [ 'url' ] );
/**
2016-05-22 20:15:28 +02:00
* Filters the determined post ID .
Embeds: Add oEmbed provider support.
For the past 6 years, WordPress has operated as an oEmbed consumer, allowing users to easily embed content from other sites. By adding oEmbed provider support, this allows any oEmbed consumer to embed posts from WordPress sites.
In addition to creating an oEmbed provider, WordPress' oEmbed consumer code has been enhanced to work with any site that provides oEmbed data (as long as it matches some strict security rules), and provides a preview from within the post editor.
For security, embeds appear within a sandboxed iframe - the iframe content is a template that can be styled or replaced entirely by the theme on the provider site.
Props swissspidy, pento, melchoyce, netweb, pfefferle, johnbillion, extendwings, davidbinda, danielbachhuber, SergeyBiryukov, afercia
Fixes #32522.
Built from https://develop.svn.wordpress.org/trunk@34903
git-svn-id: http://core.svn.wordpress.org/trunk@34868 1a063a9b-81f0-0310-95a4-ce76da25c4cd
2015-10-07 12:36:25 +02:00
*
* @ since 4.4 . 0
*
* @ param int $post_id The post ID .
2015-10-31 16:38:25 +01:00
* @ param string $url The requested URL .
Embeds: Add oEmbed provider support.
For the past 6 years, WordPress has operated as an oEmbed consumer, allowing users to easily embed content from other sites. By adding oEmbed provider support, this allows any oEmbed consumer to embed posts from WordPress sites.
In addition to creating an oEmbed provider, WordPress' oEmbed consumer code has been enhanced to work with any site that provides oEmbed data (as long as it matches some strict security rules), and provides a preview from within the post editor.
For security, embeds appear within a sandboxed iframe - the iframe content is a template that can be styled or replaced entirely by the theme on the provider site.
Props swissspidy, pento, melchoyce, netweb, pfefferle, johnbillion, extendwings, davidbinda, danielbachhuber, SergeyBiryukov, afercia
Fixes #32522.
Built from https://develop.svn.wordpress.org/trunk@34903
git-svn-id: http://core.svn.wordpress.org/trunk@34868 1a063a9b-81f0-0310-95a4-ce76da25c4cd
2015-10-07 12:36:25 +02:00
*/
$post_id = apply_filters ( 'oembed_request_post_id' , $post_id , $request [ 'url' ] );
$data = get_oembed_response_data ( $post_id , $request [ 'maxwidth' ] );
2015-10-29 23:51:24 +01:00
if ( ! $data ) {
return new WP_Error ( 'oembed_invalid_url' , get_status_header_desc ( 404 ), array ( 'status' => 404 ) );
Embeds: Add oEmbed provider support.
For the past 6 years, WordPress has operated as an oEmbed consumer, allowing users to easily embed content from other sites. By adding oEmbed provider support, this allows any oEmbed consumer to embed posts from WordPress sites.
In addition to creating an oEmbed provider, WordPress' oEmbed consumer code has been enhanced to work with any site that provides oEmbed data (as long as it matches some strict security rules), and provides a preview from within the post editor.
For security, embeds appear within a sandboxed iframe - the iframe content is a template that can be styled or replaced entirely by the theme on the provider site.
Props swissspidy, pento, melchoyce, netweb, pfefferle, johnbillion, extendwings, davidbinda, danielbachhuber, SergeyBiryukov, afercia
Fixes #32522.
Built from https://develop.svn.wordpress.org/trunk@34903
git-svn-id: http://core.svn.wordpress.org/trunk@34868 1a063a9b-81f0-0310-95a4-ce76da25c4cd
2015-10-07 12:36:25 +02:00
}
2015-10-29 23:51:24 +01:00
return $data ;
Embeds: Add oEmbed provider support.
For the past 6 years, WordPress has operated as an oEmbed consumer, allowing users to easily embed content from other sites. By adding oEmbed provider support, this allows any oEmbed consumer to embed posts from WordPress sites.
In addition to creating an oEmbed provider, WordPress' oEmbed consumer code has been enhanced to work with any site that provides oEmbed data (as long as it matches some strict security rules), and provides a preview from within the post editor.
For security, embeds appear within a sandboxed iframe - the iframe content is a template that can be styled or replaced entirely by the theme on the provider site.
Props swissspidy, pento, melchoyce, netweb, pfefferle, johnbillion, extendwings, davidbinda, danielbachhuber, SergeyBiryukov, afercia
Fixes #32522.
Built from https://develop.svn.wordpress.org/trunk@34903
git-svn-id: http://core.svn.wordpress.org/trunk@34868 1a063a9b-81f0-0310-95a4-ce76da25c4cd
2015-10-07 12:36:25 +02:00
}
2017-05-11 20:18:46 +02:00
/**
* Checks if current user can make a proxy oEmbed request .
*
* @ since 4.8 . 0
*
* @ return true | WP_Error True if the request has read access , WP_Error object otherwise .
*/
public function get_proxy_item_permissions_check () {
if ( ! current_user_can ( 'edit_posts' ) ) {
return new WP_Error ( 'rest_forbidden' , __ ( 'Sorry, you are not allowed to make proxied oEmbed requests.' ), array ( 'status' => rest_authorization_required_code () ) );
}
return true ;
}
/**
* Callback for the proxy API endpoint .
*
* Returns the JSON object for the proxied item .
*
* @ since 4.8 . 0
*
* @ see WP_oEmbed :: get_html ()
2024-03-06 06:05:12 +01:00
* @ global WP_Embed $wp_embed WordPress Embed object .
2022-11-13 14:51:20 +01:00
* @ global WP_Scripts $wp_scripts
2021-06-15 12:24:57 +02:00
*
2017-05-11 20:18:46 +02:00
* @ param WP_REST_Request $request Full data about the request .
2017-07-14 18:05:43 +02:00
* @ return object | WP_Error oEmbed response data or WP_Error on failure .
2017-05-11 20:18:46 +02:00
*/
public function get_proxy_item ( $request ) {
2022-11-13 14:51:20 +01:00
global $wp_embed , $wp_scripts ;
2021-06-15 12:24:57 +02:00
2017-05-11 20:18:46 +02:00
$args = $request -> get_params ();
// Serve oEmbed data from cache if set.
2017-07-13 00:51:40 +02:00
unset ( $args [ '_wpnonce' ] );
2017-05-11 20:18:46 +02:00
$cache_key = 'oembed_' . md5 ( serialize ( $args ) );
2017-12-01 00:11:00 +01:00
$data = get_transient ( $cache_key );
2017-05-11 20:18:46 +02:00
if ( ! empty ( $data ) ) {
return $data ;
}
$url = $request [ 'url' ];
unset ( $args [ 'url' ] );
2017-07-14 18:05:43 +02:00
// Copy maxwidth/maxheight to width/height since WP_oEmbed::fetch() uses these arg names.
if ( isset ( $args [ 'maxwidth' ] ) ) {
$args [ 'width' ] = $args [ 'maxwidth' ];
}
if ( isset ( $args [ 'maxheight' ] ) ) {
$args [ 'height' ] = $args [ 'maxheight' ];
}
2018-12-14 04:20:37 +01:00
// Short-circuit process for URLs belonging to the current site.
$data = get_oembed_response_data_for_url ( $url , $args );
if ( $data ) {
return $data ;
}
2017-05-11 20:18:46 +02:00
$data = _wp_oembed_get_object () -> get_data ( $url , $args );
if ( false === $data ) {
2020-06-23 08:08:08 +02:00
// Try using a classic embed, instead.
/* @var WP_Embed $wp_embed */
$html = $wp_embed -> get_embed_handler_html ( $args , $url );
if ( $html ) {
// Check if any scripts were enqueued by the shortcode, and include them in the response.
$enqueued_scripts = array ();
foreach ( $wp_scripts -> queue as $script ) {
$enqueued_scripts [] = $wp_scripts -> registered [ $script ] -> src ;
}
return ( object ) array (
'provider_name' => __ ( 'Embed Handler' ),
'html' => $html ,
'scripts' => $enqueued_scripts ,
);
}
2017-05-11 20:18:46 +02:00
return new WP_Error ( 'oembed_invalid_url' , get_status_header_desc ( 404 ), array ( 'status' => 404 ) );
}
2019-07-19 06:32:57 +02:00
/** This filter is documented in wp-includes/class-wp-oembed.php */
2018-12-14 04:20:37 +01:00
$data -> html = apply_filters ( 'oembed_result' , _wp_oembed_get_object () -> data2html ( ( object ) $data , $url ), $url , $args );
2017-05-11 20:18:46 +02:00
/**
* Filters the oEmbed TTL value ( time to live ) .
*
* Similar to the { @ see 'oembed_ttl' } filter , but for the REST API
* oEmbed proxy endpoint .
*
* @ since 4.8 . 0
*
* @ param int $time Time to live ( in seconds ) .
* @ param string $url The attempted embed URL .
* @ param array $args An array of embed request arguments .
*/
$ttl = apply_filters ( 'rest_oembed_ttl' , DAY_IN_SECONDS , $url , $args );
set_transient ( $cache_key , $data , $ttl );
return $data ;
}
Embeds: Add oEmbed provider support.
For the past 6 years, WordPress has operated as an oEmbed consumer, allowing users to easily embed content from other sites. By adding oEmbed provider support, this allows any oEmbed consumer to embed posts from WordPress sites.
In addition to creating an oEmbed provider, WordPress' oEmbed consumer code has been enhanced to work with any site that provides oEmbed data (as long as it matches some strict security rules), and provides a preview from within the post editor.
For security, embeds appear within a sandboxed iframe - the iframe content is a template that can be styled or replaced entirely by the theme on the provider site.
Props swissspidy, pento, melchoyce, netweb, pfefferle, johnbillion, extendwings, davidbinda, danielbachhuber, SergeyBiryukov, afercia
Fixes #32522.
Built from https://develop.svn.wordpress.org/trunk@34903
git-svn-id: http://core.svn.wordpress.org/trunk@34868 1a063a9b-81f0-0310-95a4-ce76da25c4cd
2015-10-07 12:36:25 +02:00
}