Ticket #592 (closed feature: invalid)

Opened 7 years ago

Last modified 5 years ago

Oembed service implementation

Reported by: dave Owned by: Dave
Priority: minor Milestone: 4.9
Component: EmbeddedPlayback Severity: New Ticket
Keywords: oembed Cc:
Who will test this: And


For consideration.

Based on reference from

oEmbed is an open format for allowing an embedded representation of a URL on third party sites. The simple API allows a website to display embedded content (such as photos or videos) when a user posts a link to that resource, without having to parse the resource directly.

Wordpress already implements a client side for this, allowing users to simply post a url to a resource, and automatically have that service provide the data to embed in their post or page.

There is already django-oembed, ruby-oembed, jquery-oembed, drupal-oembed, Typo3 Extension etc that allow developers to create sites that use oembed to parse URL's and automatically embed content in their sites.

This would allow other sites to simply post a link to a plumi resource, and have that resource automatically embed the data for them, no need to copy and paste the embed code.

It is a simple JSON / XML response to a request of a service.

Also refer :


Change History

comment:1 Changed 7 years ago by anna

  • Milestone set to 4.2 Beta (Features and Refactoring)

comment:2 Changed 7 years ago by and

  • Owner set to Dave

comment:3 Changed 7 years ago by and

  • Milestone changed from 4.3 Beta to 4.7 Beta

comment:4 Changed 5 years ago by anna

  • Status changed from new to closed
  • Resolution set to invalid
  • Severity set to New Ticket

Add a comment

Modify Ticket

as closed
The resolution will be deleted. Next status will be 'reopened'

E-mail address and user name can be saved in the Preferences.

Note: See TracTickets for help on using tickets.