mirrors/wagtail
mirrors/wagtail
0
0
Fork 0
mirror of https://github.com/wagtail/wagtail.git synced 2024-11-29 01:22:07 +01:00
Code Issues Releases Wiki Activity

Fix / remove broken documentation links

Browse Source
This commit is contained in:
Matt Westcott 2022-03-02 11:48:06 +00:00
parent d4899f5a51
commit c6f3b9982c
4 changed files with 3 additions and 5 deletions
Show Stats Download Patch File Download Diff File Expand all files Collapse all files

2
docs/reference/jinja2.rst
View File

@ -101,7 +101,7 @@ Returns the Site object corresponding to the current request.
{{ wagtail_site().site_name }} {{ wagtail_site().site_name }}
See :ref:`wagtile_site` for more information See :ref:`wagtail_site_tag` for more information
``wagtailuserbar()`` ``wagtailuserbar()``
~~~~~~~~~~~~~~~~~~~~ ~~~~~~~~~~~~~~~~~~~~

2
docs/releases/1.10.rst
View File

@ -18,8 +18,6 @@ full-text search functionality. This means that if you use PostgreSQL to manage
your database, you can now get a good quality search engine without needing your database, you can now get a good quality search engine without needing
to install Elasticsearch. to install Elasticsearch.
To get started, see :ref:`postgres_search`.
This feature was developed at the Arnhem sprint by Bertrand Bordage, Jaap Roes, This feature was developed at the Arnhem sprint by Bertrand Bordage, Jaap Roes,
Arne de Laat and Ramon de Jezus. Arne de Laat and Ramon de Jezus.

2
docs/releases/1.12.rst
View File

@ -74,7 +74,7 @@ The configuration settings ``WAGTAILEMBEDS_EMBED_FINDER`` and ``WAGTAILEMBEDS_EM
Registering custom hallo.js plugins directly is deprecated Registering custom hallo.js plugins directly is deprecated
~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~ ~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~
The ability to enable / disable ``hallo.js`` plugins by calling ``registerHalloPlugin`` or modifying the ``halloPlugins`` list has been deprecated, and will be removed in Wagtail 1.14. The recommended way of customising the hallo.js editor is now through :ref:`rich text features <rich_text_features>`. For details of how to define a hallo.js plugin as a rich text feature, see :doc:`../extending/extending_hallo`. The ability to enable / disable ``hallo.js`` plugins by calling ``registerHalloPlugin`` or modifying the ``halloPlugins`` list has been deprecated, and will be removed in Wagtail 1.14. The recommended way of customising the hallo.js editor is now through :ref:`rich text features <rich_text_features>`.
Custom ``get_admin_display_title`` methods should use ``draft_title`` Custom ``get_admin_display_title`` methods should use ``draft_title``

2
docs/releases/2.0.rst
View File

@ -267,7 +267,7 @@ legacy versions of the API until everyone has migrated to an officially supporte
``construct_whitelister_element_rules`` hook is deprecated ``construct_whitelister_element_rules`` hook is deprecated
~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~ ~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~
The ``construct_whitelister_element_rules`` hook, used to specify additional HTML elements to be permitted in rich text, is deprecated. The recommended way of whitelisting elements is now to use rich text features - see :ref:`whitelisting_rich_text_elements`. For example, a whitelist rule that was previously defined as: The ``construct_whitelister_element_rules`` hook, used to specify additional HTML elements to be permitted in rich text, is deprecated. The recommended way of whitelisting elements is now to use rich text features. For example, a whitelist rule that was previously defined as:
.. code-block:: python .. code-block:: python