#24242 closed enhancement (fixed)
Rdio and Spotify oEmbed Support
Reported by: | ryan | Owned by: | ryan |
---|---|---|---|
Milestone: | 3.6 | Priority: | normal |
Severity: | normal | Version: | |
Component: | Embeds | Keywords: | |
Focuses: | Cc: |
Description (last modified by )
With the addition of an Audio Post Format UI, rounding out our default oEmbed provider list with Rdio and Spotify support seems useful.
Attachments (3)
Change History (13)
#2
@
12 years ago
Tested out ryan's patch and I noticed that for long rdio.com URLs, the regex uses the old hashed URLs. Rdio currently serves non-hashed URLs such as http://www.rdio.com/artist/Kanye_West/album/Graduation/track/Can%27t_Tell_Me_Nothing/ . I tried removing the #/ and it looks like it works with both hashed and unhashed Rdio song URLs.
#4
@
12 years ago
- Owner set to ryan
- Resolution set to fixed
- Status changed from new to closed
In 24160:
#5
@
12 years ago
- Description modified (diff)
- Resolution fixed deleted
- Status changed from closed to reopened
- Summary changed from Rdio oEmbed Support to Rdio and Spotify oEmbed Support
24 hours ago, Spotify didn't have an oEmbed endpoint. They do now — https://twitter.com/nicklas2k/status/330094611202723840. Nice!
Note: See
TracTickets for help on using
tickets.
Those regexes have been on wordpress.com for a long while.