#36197 closed defect (bug) (fixed)
Update Twitter oEmbed URL
Reported by: | niallkennedy | Owned by: | ocean90 |
---|---|---|---|
Milestone: | 4.5 | Priority: | normal |
Severity: | normal | Version: | |
Component: | Embeds | Keywords: | has-patch |
Focuses: | Cc: |
Description
Twitter moved its preferred oEmbed URL for single Tweets from api.twitter.com to publish.twitter.com.
Update the oEmbed provider array to point at the new preferred endpoint, matching autodiscovery behavior. The XML response format will be removed.
Example URL:
https://twitter.com/WordPress/status/690269689855942657
Attachments (3)
Change History (14)
#2
@
9 years ago
- Milestone changed from Awaiting Review to 4.5
- Type changed from enhancement to defect (bug)
#3
@
9 years ago
- Version trunk deleted
36197.2.diff adds support for moments, which are supported by the new endpoint, see https://dev.twitter.com/web/embedded-moments/oembed.
#4
@
9 years ago
- Owner set to jorbin
- Resolution set to fixed
- Status changed from new to closed
In 36946:
#6
@
9 years ago
- Owner changed from jorbin to ocean90
- Status changed from reopened to assigned
@ocean90 Do you want to add the moments support? Is that not covered by the current autodiscovery?
#7
@
9 years ago
@jorbin Autodiscovery works only if the page includes the link tag, https://twitter.com/i/moments/650667182356082688 has none. A single tweet like https://twitter.com/sonicadvance1/status/706219050473549824 includes one though.
@niallkennedy Is this something which Twitter is planning to implement?
#8
@
9 years ago
We will return an oEmbed response from the same API URL for Moment and collection URLs today. We plan to add autodiscovery.
As twitter is deprecating the XML on May 1, I think this is a good fix to get in for 4.5