| 1 | | When doing oEmbed previews in the client, both in the media modal `embed` frame and in the TinyMCE embed preview, a `parse-embed` admin-ajax request is currently made to do the parsing. This request requires a `post_ID` parameter because the WP Embed logic caches oEmbed responses in postmeta (see #34115). There is a need for this in the media widgets to be able to obtain the `thumbnail_url` for a given oEmbed URL. Unfortunately the oEmbed preview in the media modal fails because there is no `post_ID` for context. |
| | 1 | This essentially proposes adding the functionality from noembed.com into WordPress. |
| | 2 | |
| | 3 | When doing oEmbed previews in the client, both in the media modal `embed` frame and in the TinyMCE embed preview, a `parse-embed` admin-ajax request is currently made to do the parsing. This request requires a `post_ID` parameter because the WP Embed logic caches oEmbed responses in postmeta (see #34115). There is a need for this in the media widgets to be able to obtain the `thumbnail_url` for a given oEmbed URL. Unfortunately the oEmbed preview in the media modal fails because there is no `post_ID` for context. Also, the client cannot reliably make requests to oEmbed providers directly since they inconsistently support CORS. |