#40758 closed defect (bug) (invalid)
Wordpress supporting oembed standards ?
Reported by: |
|
Owned by: | |
---|---|---|---|
Milestone: | Priority: | normal | |
Severity: | normal | Version: | |
Component: | Embeds | Keywords: | |
Focuses: | Cc: |
Description
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
Change History (5)
#2
@
6 years ago
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&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&url=http%3A%2F%2F127.0.0.1%2Fwordpress%2F%3Fp%3D172&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)
is it ok ?
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
: