Hopiu/wagtail
1
0
Fork 0
mirror of https://github.com/Hopiu/wagtail.git synced 2026-05-03 04:54:45 +00:00
Code Issues Projects Releases Packages Wiki Activity Actions

Removed all versionchanged older than 0.7

Browse source
This commit is contained in:
Karl Hobley 2015-04-09 17:05:26 +01:00
parent 8d162d0a86
commit 0e67d5b3ca
3 changed files with 0 additions and 18 deletions
Show stats Download patch file Download diff file Expand all files Collapse all files

3
docs/images/using_in_templates.rst
View file

@ -3,9 +3,6 @@
Using images in templates
=========================
.. versionchanged:: 0.4
The 'image_tags' tags library was renamed to 'wagtailimages_tags'
The ``image`` tag inserts an XHTML-compatible ``img`` element into the page, setting its ``src``, ``width``, ``height`` and ``alt``. See also :ref:`image_tag_alt`.
The syntax for the tag is thus::

6
docs/pages/writing_templates.rst
View file

@ -117,9 +117,6 @@ See :ref:`image_tag` for full documentation.
Rich text (filter)
~~~~~~~~~~~~~~~~~~
.. versionchanged:: 0.4
The 'rich_text' tags library was renamed to 'wagtailcore_tags'
This filter takes a chunk of HTML content and renders it as safe HTML in the page. Importantly it also expands internal shorthand references to embedded images and links made in the Wagtail editor into fully-baked HTML ready for display.
Only fields using ``RichTextField`` need this applied in the template.
@ -162,9 +159,6 @@ Wagtail embeds and images are included at their full width, which may overflow t
Internal links (tag)
~~~~~~~~~~~~~~~~~~~~
.. versionchanged:: 0.4
The 'pageurl' tags library was renamed to 'wagtailcore_tags'
pageurl
--------

9
docs/search/indexing.rst
View file

@ -60,15 +60,6 @@ The search may not return any results while this command is running, so avoid ru
Indexing extra fields
=====================
.. versionchanged:: 0.4
The ``indexed_fields`` configuration format was replaced with ``search_fields``
.. versionchanged:: 0.6
The ``wagtail.wagtailsearch.indexed`` module was renamed to ``wagtail.wagtailsearch.index``
.. warning::
Indexing extra fields is only supported with ElasticSearch as your backend. If you're using the database backend, any other fields you define via ``search_fields`` will be ignored.