From 9dd4d6c6c4f595c2a099f184139111bfe8543f40 Mon Sep 17 00:00:00 2001 From: =?UTF-8?q?S=C3=A6var=20=C3=96fj=C3=B6r=C3=B0=20Magn=C3=BAsson?= Date: Tue, 21 Jun 2022 08:13:58 +0000 Subject: [PATCH] Update documentation for the serve method override so that it does not mention a specific demo site. (#8714) --- docs/reference/pages/model_recipes.rst | 2 +- 1 file changed, 1 insertion(+), 1 deletion(-) diff --git a/docs/reference/pages/model_recipes.rst b/docs/reference/pages/model_recipes.rst index 18f396e8d3..1ba1cb5e05 100644 --- a/docs/reference/pages/model_recipes.rst +++ b/docs/reference/pages/model_recipes.rst @@ -9,7 +9,7 @@ Overriding the :meth:`~wagtail.models.Page.serve` Method Wagtail defaults to serving :class:`~wagtail.models.Page`-derived models by passing a reference to the page object to a Django HTML template matching the model's name, but suppose you wanted to serve something other than HTML? You can override the :meth:`~wagtail.models.Page.serve` method provided by the :class:`~wagtail.models.Page` class and handle the Django request and response more directly. -Consider this example from the Wagtail demo site's ``models.py``, which serves an ``EventPage`` object as an iCal file if the ``format`` variable is set in the request: +Consider this example of an ``EventPage`` object which is served as an iCal file if the ``format`` variable is set in the request: .. code-block:: python