From 14daf4be0a9f9978d1d9fa87702ddf5bd9a8157c Mon Sep 17 00:00:00 2001 From: Matt Westcott Date: Tue, 19 Jan 2021 09:51:01 +0000 Subject: [PATCH] Remove outdated versionadded/versionchanged notes in docs --- docs/reference/contrib/settings.rst | 2 -- docs/reference/settings.rst | 4 ---- docs/reference/signals.rst | 2 -- 3 files changed, 8 deletions(-) diff --git a/docs/reference/contrib/settings.rst b/docs/reference/contrib/settings.rst index cfd47b308f..0f969d44e7 100644 --- a/docs/reference/contrib/settings.rst +++ b/docs/reference/contrib/settings.rst @@ -272,8 +272,6 @@ and two more to fetch each page): Utilising the ``page_url`` setting shortcut ------------------------------------------- -.. versionadded:: 2.10 - If, like in the previous section, your settings model references pages, and you regularly need to output the URLs of those pages in your project, you can likely use the setting model's ``page_url`` shortcut to do that more diff --git a/docs/reference/settings.rst b/docs/reference/settings.rst index 67bdbdb900..73f4066110 100644 --- a/docs/reference/settings.rst +++ b/docs/reference/settings.rst @@ -660,10 +660,6 @@ Customise the behaviour of rich text fields. By default, ``RichTextField`` and ` If a ``'default'`` editor is not specified, rich text fields that do not specify an ``editor`` argument will use the Draftail editor with the default feature set enabled. -.. versionchanged:: 2.10 - - Omitting the ``'default'`` editor now leaves the original default editor intact, so it is no longer necessary to redefine ``'default'`` when adding alternative editors. - .. _WAGTAILADMIN_GLOBAL_PAGE_EDIT_LOCK: diff --git a/docs/reference/signals.rst b/docs/reference/signals.rst index 24dc5668a4..127732b91e 100644 --- a/docs/reference/signals.rst +++ b/docs/reference/signals.rst @@ -84,8 +84,6 @@ This signal is emitted from a ``Page`` when the page is unpublished. ``pre_page_move`` and ``post_page_move`` ------------------------------------------ -.. versionadded:: 2.10 - These signals are emitted from a ``Page`` immediately before and after it is moved. Subscribe to ``pre_page_move`` if you need to know values BEFORE any database changes are applied. For example: Getting the page's previous URL, or that of its descendants.