embeds.rst 10 KB

123456789101112131415161718192021222324252627282930313233343536373839404142434445464748495051525354555657585960616263646566676869707172737475767778798081828384858687888990919293949596979899100101102103104105106107108109110111112113114115116117118119120121122123124125126127128129130131132133134135136137138139140141142143144145146147148149150151152153154155156157158159160161162163164165166167168169170171172173174175176177178179180181182183184185186187188189190191192193194195196197198199200201202203204205206207208209210211212213214215216217218219220221222223224225226227228229230231232233234235236237238239240241242243244245246247248249250251252253254255256257258259260261262263264265266267268269270271272273274275276277278279280281282283284285286287288289290291292293294295296297298299300301302303304305306307308309310311312313314315316317318319320321322323324325326327328329330331332333334335336337338339340341342343344345346347348349350351352353354355356357358359360361362363364365366
  1. .. _embedded_content:
  2. ================
  3. Embedded content
  4. ================
  5. Wagtail supports generating embed code from URLs to content on external
  6. providers such as Youtube or Twitter. By default, Wagtail will fetch the embed
  7. code directly from the relevant provider's site using the oEmbed protocol.
  8. Wagtail has a built-in list of the most common providers and this list can be
  9. changed :ref:`with a setting <customising_embed_providers>`. Wagtail also supports
  10. fetching embed code using `Embedly`_ and :ref:`custom embed finders <custom_embed_finders>`.
  11. Embedding content on your site
  12. ==============================
  13. Wagtail's embeds module should work straight out of the box for most providers.
  14. You can use any of the following methods to call the module:
  15. Rich text
  16. ---------
  17. Wagtail's default rich text editor has a "media" icon that allows embeds to be
  18. placed into rich text. You don't have to do anything to enable this; just make
  19. sure the rich text field's content is being passed through the ``|richtext``
  20. filter in the template as this is what calls the embeds module to fetch and
  21. nest the embed code.
  22. ``EmbedBlock`` StreamField block type
  23. -------------------------------------
  24. The :class:`~wagtail.embeds.block.EmbedBlock` block type allows embeds
  25. to be placed into a ``StreamField``.
  26. For example:
  27. .. code-block:: python
  28. from wagtail.embeds.blocks import EmbedBlock
  29. class MyStreamField(blocks.StreamBlock):
  30. ...
  31. embed = EmbedBlock()
  32. ``{% embed %}`` tag
  33. -------------------
  34. Syntax: ``{% embed <url> [max_width=<max width>] %}``
  35. You can nest embeds into a template by passing the URL and an optional
  36. ``max_width`` argument to the ``{% embed %}`` tag.
  37. The ``max_width`` argument is sent to the provider when fetching the embed code.
  38. .. code-block:: html+Django
  39. {% load wagtailembeds_tags %}
  40. {# Embed a YouTube video #}
  41. {% embed 'https://www.youtube.com/watch?v=SJXMTtvCxRo' %}
  42. {# This tag can also take the URL from a variable #}
  43. {% embed page.video_url %}
  44. From Python
  45. -----------
  46. You can also call the internal ``get_embed`` function that takes a URL string
  47. and returns an ``Embed`` object (see model documentation below). This also
  48. takes a ``max_width`` keyword argument that is sent to the provider when
  49. fetching the embed code.
  50. .. code-block:: python
  51. from wagtail.embeds.embeds import get_embed
  52. from wagtail.embeds.exceptions import EmbedException
  53. try:
  54. embed = get_embed('https://www.youtube.com/watch?v=SJXMTtvCxRo')
  55. print(embed.html)
  56. except EmbedException:
  57. # Cannot find embed
  58. pass
  59. .. _configuring_embed_finders:
  60. Configuring embed "finders"
  61. ===========================
  62. Embed finders are the modules within Wagtail that are responsible for producing
  63. embed code from a URL.
  64. Embed finders are configured using the ``WAGTAILEMBEDS_FINDERS`` setting. This
  65. is a list of finder configurations that are each run in order until one of them
  66. successfully returns an embed:
  67. The default configuration is:
  68. .. code-block:: python
  69. WAGTAILEMBEDS_FINDERS = [
  70. {
  71. 'class': 'wagtail.embeds.finders.oembed'
  72. }
  73. ]
  74. .. _oEmbed:
  75. oEmbed (default)
  76. ----------------
  77. The default embed finder fetches the embed code directly from the content
  78. provider using the oEmbed protocol. Wagtail has a built-in list of providers
  79. which are all enabled by default. You can find that provider list at the
  80. following link:
  81. https://github.com/wagtail/wagtail/blob/master/wagtail/embeds/oembed_providers.py
  82. .. _customising_embed_providers:
  83. Customising the provider list
  84. ~~~~~~~~~~~~~~~~~~~~~~~~~~~~~
  85. You can limit which providers may be used by specifying the list of providers
  86. in the finder configuration.
  87. For example, this configuration will only allow content to be nested from Vimeo
  88. and Youtube. It also adds a custom provider:
  89. .. code-block:: python
  90. from wagtail.embeds.oembed_providers import youtube, vimeo
  91. # Add a custom provider
  92. # Your custom provider must support oEmbed for this to work. You should be
  93. # able to find these details in the provider's documentation.
  94. # - 'endpoint' is the URL of the oEmbed endpoint that Wagtail will call
  95. # - 'urls' specifies which patterns
  96. my_custom_provider = {
  97. 'endpoint': 'https://customvideosite.com/oembed',
  98. 'urls': [
  99. '^http(?:s)?://(?:www\\.)?customvideosite\\.com/[^#?/]+/videos/.+$',
  100. ]
  101. }
  102. WAGTAILEMBEDS_FINDERS = [
  103. {
  104. 'class': 'wagtail.embeds.finders.oembed',
  105. 'providers': [youtube, vimeo, my_custom_provider],
  106. }
  107. ]
  108. Customising an individual provider
  109. ~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~
  110. Multiple finders can be chained together. This can be used for customising the
  111. configuration for one provider without affecting the others.
  112. For example, this is how you can instruct Youtube to return videos in HTTPS
  113. (which must be done explicitly for YouTube):
  114. .. code-block:: python
  115. from wagtail.embeds.oembed_providers import youtube
  116. WAGTAILEMBEDS_FINDERS = [
  117. # Fetches YouTube videos but puts ``?scheme=https`` in the GET parameters
  118. # when calling YouTube's oEmbed endpoint
  119. {
  120. 'class': 'wagtail.embeds.finders.oembed',
  121. 'providers': [youtube],
  122. 'options': {'scheme': 'https'}
  123. },
  124. # Handles all other oEmbed providers the default way
  125. {
  126. 'class': 'wagtail.embeds.finders.oembed',
  127. }
  128. ]
  129. .. topic:: How Wagtail uses multiple finders
  130. If multiple providers can handle a URL (for example, a YouTube video was
  131. requested using the configuration above), the topmost finder is chosen to
  132. perform the request.
  133. Wagtail will not try to run any other finder, even if the chosen one didn't
  134. return an embed.
  135. .. _Embedly:
  136. Embed.ly
  137. --------
  138. `Embed.ly <https://embed.ly>`_ is a paid-for service that can also provide
  139. embeds for sites that do not implement the oEmbed protocol.
  140. They also provide some helpful features such as giving embeds a consistent look
  141. and a common video playback API which is useful if your site allows videos to
  142. be hosted on different providers and you need to implement custom controls for
  143. them.
  144. Wagtail has built in support for fetching embeds from Embed.ly. To use it,
  145. first pip install the ``Embedly`` `python package <https://pypi.org/project/Embedly/>`_.
  146. Now add an embed finder to your ``WAGTAILEMBEDS_FINDERS`` setting that uses the
  147. ``wagtail.embeds.finders.oembed`` class and pass it your API key:
  148. .. code-block:: python
  149. WAGTAILEMBEDS_FINDERS = [
  150. {
  151. 'class': 'wagtail.embeds.finders.embedly',
  152. 'key': 'YOUR EMBED.LY KEY HERE'
  153. }
  154. ]
  155. .. _custom_embed_finders:
  156. Custom embed finder classes
  157. ---------------------------
  158. For complete control, you can create a custom finder class.
  159. Here's a stub finder class that could be used as a skeleton; please read the
  160. docstrings for details of what each method does:
  161. .. code-block:: python
  162. from wagtail.embeds.finders.base import EmbedFinder
  163. class ExampleFinder(EmbedFinder):
  164. def __init__(self, **options):
  165. pass
  166. def accept(self, url):
  167. """
  168. Returns True if this finder knows how to fetch an embed for the URL.
  169. This should not have any side effects (no requests to external servers)
  170. """
  171. pass
  172. def find_embed(self, url, max_width=None):
  173. """
  174. Takes a URL and max width and returns a dictionary of information about the
  175. content to be used for embedding it on the site.
  176. This is the part that may make requests to external APIs.
  177. """
  178. # TODO: Perform the request
  179. return {
  180. 'title': "Title of the content",
  181. 'author_name': "Author name",
  182. 'provider_name': "Provider name (eg. YouTube, Vimeo, etc)",
  183. 'type': "Either 'photo', 'video', 'link' or 'rich'",
  184. 'thumbnail_url': "URL to thumbnail image",
  185. 'width': width_in_pixels,
  186. 'height': height_in_pixels,
  187. 'html': "<h2>The Embed HTML</h2>",
  188. }
  189. Once you've implemented all of those methods, you just need to add it to your
  190. ``WAGTAILEMBEDS_FINDERS`` setting:
  191. .. code-block:: python
  192. WAGTAILEMBEDS_FINDERS = [
  193. {
  194. 'class': 'path.to.your.finder.class.here',
  195. # Any other options will be passed as kwargs to the __init__ method
  196. }
  197. ]
  198. The ``Embed`` model
  199. ===================
  200. .. class:: wagtail.embeds.models.Embed
  201. Embeds are fetched only once and stored in the database so subsequent requests
  202. for an individual embed do not hit the embed finders again.
  203. .. attribute:: url
  204. (text)
  205. The URL of the original content of this embed.
  206. .. attribute:: max_width
  207. (integer, nullable)
  208. The max width that was requested.
  209. .. attribute:: type
  210. (text)
  211. The type of the embed. This can be either 'video', 'photo', 'link' or 'rich'.
  212. .. attribute:: html
  213. (text)
  214. The HTML content of the embed that should be placed on the page
  215. .. attribute:: title
  216. (text)
  217. The title of the content that is being embedded.
  218. .. attribute:: author_name
  219. (text)
  220. The author name of the content that is being embedded.
  221. .. attribute:: provider_name
  222. (text)
  223. The provider name of the content that is being embedded.
  224. For example: YouTube, Vimeo
  225. .. attribute:: thumbnail_url
  226. (text)
  227. a URL to a thumbnail image of the content that is being embedded.
  228. .. attribute:: width
  229. (integer, nullable)
  230. The width of the embed (images and videos only).
  231. .. attribute:: height
  232. (integer, nullable)
  233. The height of the embed (images and videos only).
  234. .. attribute:: last_updated
  235. (datetime)
  236. The Date/time when this embed was last fetched.
  237. Deleting embeds
  238. ---------------
  239. As long as your embeds configuration is not broken, deleting items in the
  240. ``Embed`` model should be perfectly safe to do. Wagtail will automatically
  241. repopulate the records that are being used on the site.
  242. You may want to do this if you've changed from oEmbed to Embedly or vice-versa
  243. as the embed code they generate may be slightly different and lead to
  244. inconsistency on your site.