You signed in with another tab or window. Reload to refresh your session.You signed out in another tab or window. Reload to refresh your session.You switched accounts on another tab or window. Reload to refresh your session.Dismiss alert
Currently when pasting a link that doesn't support oEmbed embedding, an error is shown, and the option to convert to a normal link is proposed
What is your proposed solution?
I like the way Medium handles this. It fetches the OpenGraph tags and makes a nice card.
Right now the embed block calls the oEmbed endpoint (/wp-json/oembed/1.0/proxy). It would make sense to call another API endpoint (for example /wp-json/opengraph/1.0/proxy) when this fails, which would return the relevant OpenGraph tags (title, description, image) needed to build the card.
The text was updated successfully, but these errors were encountered:
The core already has an API for parsing the site metadata. Currently, it's used to generate URL details popups. We can probably adopt that into an embed provider.
What problem does this address?
Currently when pasting a link that doesn't support oEmbed embedding, an error is shown, and the option to convert to a normal link is proposed
What is your proposed solution?
I like the way Medium handles this. It fetches the OpenGraph tags and makes a nice card.
Right now the embed block calls the oEmbed endpoint (
/wp-json/oembed/1.0/proxy
). It would make sense to call another API endpoint (for example/wp-json/opengraph/1.0/proxy
) when this fails, which would return the relevant OpenGraph tags (title, description, image) needed to build the card.The text was updated successfully, but these errors were encountered: