Page tree
Skip to end of metadata
Go to start of metadata

This element defines the properties of an oEmbed service which is to be used with EditLive!. These attributes map to the configuration according to the oEmbed specification.

EditLive! evaluates service elements in the order they appear within the configuration file, allowing for fallback providers to be used.

Configuration Element Tree Structure

<editLive>
<mediaSettings>
<multimedia>
<services>
<service>

<editLive>
  ...
  <mediaSettings>
    ...
    <multimedia>
      ...
      <services>
        ...
        <!--service configuration settings-->
        <service />

        ...
      </services>
    </multimedia>
  </mediaSettings>
  ...
</editLive>

Required Attributes

name

The name of the oEmbed service.

endpoint

The API endpoint of the oEmbed service. EditLive! supports both XML and JSON API endpoints.

scheme

The scheme to match URLs against that should use this endpoint. Wildcards are supported.

Example

The following example demonstrates how to configure multiple oEmbed services for use with EditLive!. In this case the first service is YouTube, with a fallback to embed.ly for all other URLs.

<editLive>
  ...
  <mediaSettings>
    ...
    <multimedia>
      <services>
        ...
        <service name="YouTube" endpoint="http://www.youtube.com/oembed" scheme="http://*.youtube.com/*" />
		<service name="Embed.ly" endpoint="http://api.embed.ly/1/oembed?key=<your key here>" scheme="*" />
        ...
      </servies>
    </multimedia>
  </mediaSettings>
  ...
</editLive>

Note

Some endpoints (such as embed.ly) require API keys specific to your application, and often the free account limits are very low (for example embed.ly only supports 5000 requests a month on free accounts).

API keys can be specified along with the endpoint URL, as shown in the example above.

Remarks

The <service> element can appear multiple times within the <services> element.

  • No labels