From 3b26ddc1622e6aab5eadd9a942d183da39918b72 Mon Sep 17 00:00:00 2001 From: Karl Hobley Date: Mon, 1 Jun 2015 16:03:59 +0100 Subject: [PATCH] Fixed module names for a few classes --- docs/reference/pages/editing_api.rst | 6 +++--- 1 file changed, 3 insertions(+), 3 deletions(-) diff --git a/docs/reference/pages/editing_api.rst b/docs/reference/pages/editing_api.rst index 1f72a15476..6401d3b7df 100644 --- a/docs/reference/pages/editing_api.rst +++ b/docs/reference/pages/editing_api.rst @@ -171,7 +171,7 @@ PageChooserPanel ImageChooserPanel ----------------- -.. class:: ImageChooserPanel(field_name) +.. class:: wagtail.wagtailimages.edit_handlers.ImageChooserPanel(field_name) Wagtail includes a unified image library, which you can access in your models through the :class:`~wagtail.wagtailimages.models.Image` model and the ``ImageChooserPanel`` chooser. Here's how: @@ -203,7 +203,7 @@ ImageChooserPanel DocumentChooserPanel -------------------- -.. class:: DocumentChooserPanel(field_name) +.. class:: wagtail.wagtaildocs.edit_handlers.DocumentChooserPanel(field_name) For files in other formats, Wagtail provides a generic file store through the :class:`~wagtail.wagtaildocs.models.Document` model: @@ -231,7 +231,7 @@ DocumentChooserPanel SnippetChooserPanel ------------------- -.. class:: SnippetChooserPanel(field_name, model) +.. class:: wagtail.wagtailsnippets.edit_handlers.SnippetChooserPanel(field_name, model) Snippets are vanilla Django models you create yourself without a Wagtail-provided base class. So using them as a field in a page requires specifying your own ``appname.modelname``. A chooser, ``SnippetChooserPanel``, is provided which takes the field name and snippet class.