Wordpress supporting oembed standards ?

[Arena94]

WordPress is making a good use of oembed standards.

However, things are much more complex when embedding wordpress content even for itself.

So, internally, Wordpress code do not support oembed standards ... ​http://oembed.com/

Such urls do not work

​http://mysite.tld/oembed?format=xml&url=http%3A%2F%2Fmysite.tld%2F%3Fp%3D172

​http://mysite.tld/oembed?format=json&url=http%3A%2F%2Fmysite.tld%2F%3Fp%3D172

[ocean90]

Hello @Arena94, can you elaborate a bit more on this one? Do you mean that WordPress should have a /oembed endpoint? Because that's not really a standard. It's all about the ​discovery part.

WordPress automatically adds the required link tags to the header so you should see something like this on http://mysite.tld/?p=172:

<link rel="alternate" type="application/json+oembed" href="http://mysite.tld/wp-json/oembed/1.0/embed?url=http%3A%2F%2Fmysite.tld%2F%3Fp%3D172" />
<link rel="alternate" type="text/xml+oembed" href="http://mysite.tld/wp-json/oembed/1.0/embed?url=http%3A%2F%2Fmysite.tld%2F%3Fp%3D172&#038;format=xml" />

[Arena94]

Hello,

good point,

here is what i have

<link rel="alternate" type="application/json+oembed" href="​http://127.0.0.1/wordpress/?rest_route=%2Foembed%2F1.0%2Fembed&#038;url=http%3A%2F%2F127.0.0.1%2Fwordpress%2F%3Fp%3D172" />
<link rel="alternate" type="text/xml+oembed" href="​http://127.0.0.1/wordpress/?rest_route=%2Foembed%2F1.0%2Fembed&#038;url=http%3A%2F%2F127.0.0.1%2Fwordpress%2F%3Fp%3D172&#038;format=xml" />

both links have the following result :

{"code":"rest_missing_callback_param","message":"Missing parameter(s): url","data":{"status":400,"params":url?}}

and what i should have (with a much better result)

​http://127.0.0.1/wordpress/?rest_route=/oembed/1.0/embed&url=http%3A%2F%2F127.0.0.1%2Fwordpress%2F%3Fp%3D172

​http://127.0.0.1/wordpress/?rest_route=/oembed/1.0/embed&url=http%3A%2F%2F127.0.0.1%2Fwordpress%2F%3Fp%3D172&format=xml

is it ok ?

[ocean90]

Thanks, that seems to be caused by some double escaping which converts the & into &. Clicking the link in a HTML context (src or href attribute) should work though.

[Arena94]

nice
so i close it