14 KiB
(editing-api)=
Panel types
Built-in Fields and Choosers
Django's field types are automatically recognised and provided with an appropriate widget for input. Just define that field the normal Django way and pass the field name into
FieldPanel when defining your panels. Wagtail will take care of the rest.
Here are some Wagtail-specific types that you might include as fields in your models.
.. module:: wagtail.admin.panels
:noindex:
(field_panel)=
FieldPanel
.. class:: FieldPanel(field_name, classname=None, widget=None, heading='', disable_comments=False, permission=None)
This is the panel used for basic Django field types.
.. attribute:: FieldPanel.field_name
This is the name of the class property used in your model definition.
.. attribute:: FieldPanel.classname
This is a string of optional CSS classes given to the panel which are used in formatting and scripted interactivity.
The CSS class ``title`` can be used to give the field a larger text size, suitable for representing page titles and section headings.
.. attribute:: FieldPanel.widget (optional)
This parameter allows you to specify a :doc:`Django form widget <django:ref/forms/widgets>` to use instead of the default widget for this field type.
.. attribute:: FieldPanel.heading (optional)
This allows you to override the heading for the panel, which will otherwise be set automatically using the form field's label (taken in turn from a model field's ``verbose_name``).
.. attribute:: FieldPanel.disable_comments (optional)
This allows you to prevent a field level comment button showing for this panel if set to ``True`` (see :ref:`commenting`).
.. attribute:: FieldPanel.permission (optional)
Allows a field to be selectively shown to users with sufficient permission. Accepts a permission codename such as ``'myapp.change_blog_category'`` - if the logged-in user does not have that permission, the field will be omitted from the form. See Django's documentation on :ref:`custom permissions <django:custom-permissions>` for details on how to set permissions up; alternatively, if you want to set a field as only available to superusers, you can use any arbitrary string (such as ``'superuser'``) as the codename, since superusers automatically pass all permission tests.
StreamFieldPanel
.. class:: StreamFieldPanel(field_name, classname=None, widget=None)
Deprecated; use ``FieldPanel`` instead.
.. versionchanged:: 3.0
``StreamFieldPanel`` is no longer required for ``StreamField``.
MultiFieldPanel
.. class:: MultiFieldPanel(children, heading="", classname=None)
This panel condenses several :class:`~wagtail.admin.panels.FieldPanel` s or choosers, from a ``list`` or ``tuple``, under a single ``heading`` string.
.. attribute:: MultiFieldPanel.children
A ``list`` or ``tuple`` of child panels
.. attribute:: MultiFieldPanel.heading
A heading for the fields
InlinePanel
.. class:: InlinePanel(relation_name, panels=None, classname='', heading='', label='', help_text='', min_num=None, max_num=None)
This panel allows for the creation of a "cluster" of related objects over a join to a separate model, such as a list of related links or slides to an image carousel.
This is a powerful but complex feature which will take some space to cover, so we'll skip over it for now. For a full explanation on the usage of InlinePanel, see {ref}inline_panels.
Collapsing InlinePanels to save space
Note that you can use classname="collapsed" to load the panel collapsed under its heading in order to save space in the Wagtail admin.
FieldRowPanel
.. class:: FieldRowPanel(children, classname=None)
This panel creates a columnar layout in the editing interface, where each of the child Panels appears alongside each other rather than below.
Use of FieldRowPanel particularly helps reduce the "snow-blindness" effect of seeing so many fields on the page, for complex models. It also improves the perceived association between fields of a similar nature. For example if you created a model representing an "Event" which had a starting date and ending date, it may be intuitive to find the start and end date on the same "row".
.. attribute:: FieldRowPanel.children
A ``list`` or ``tuple`` of child panels to display on the row
.. attribute:: FieldRowPanel.classname
A class to apply to the FieldRowPanel as a whole
HelpPanel
.. class:: HelpPanel(content='', template='wagtailadmin/panels/help_panel.html', heading='', classname='')
.. attribute:: HelpPanel.content
HTML string that gets displayed in the panel.
.. attribute:: HelpPanel.template
Path to a template rendering the full panel HTML.
.. attribute:: HelpPanel.heading
A heading for the help content.
.. attribute:: HelpPanel.classname
String of CSS classes given to the panel which are used in formatting and scripted interactivity.
PageChooserPanel
.. class:: PageChooserPanel(field_name, page_type=None, can_choose_root=False)
You can explicitly link :class:`~wagtail.models.Page`-derived models together using the :class:`~wagtail.models.Page` model and ``PageChooserPanel``.
.. code-block:: python
from wagtail.models import Page
from wagtail.admin.panels import PageChooserPanel
class BookPage(Page):
related_page = models.ForeignKey(
'wagtailcore.Page',
null=True,
blank=True,
on_delete=models.SET_NULL,
related_name='+',
)
content_panels = Page.content_panels + [
PageChooserPanel('related_page', 'demo.PublisherPage'),
]
``PageChooserPanel`` takes one required argument, the field name. Optionally, specifying a page type (in the form of an ``"appname.modelname"`` string) will filter the chooser to display only pages of that type. A list or tuple of page types can also be passed in, to allow choosing a page that matches any of those page types:
.. code-block:: python
PageChooserPanel('related_page', ['demo.PublisherPage', 'demo.AuthorPage'])
Passing ``can_choose_root=True`` will allow the editor to choose the tree root as a page. Normally this would be undesirable, since the tree root is never a usable page, but in some specialised cases it may be appropriate; for example, a page with an automatic "related articles" feed could use a PageChooserPanel to select which subsection articles will be taken from, with the root corresponding to 'everywhere'.
.. versionchanged:: 3.0
``FieldPanel`` now also provides a page chooser interface for foreign keys to page models. ``PageChooserPanel`` is only required when specifying the ``page_type`` or ``can_choose_root`` parameters.
ImageChooserPanel
.. module:: wagtail.images.edit_handlers
.. class:: ImageChooserPanel(field_name)
Deprecated; use ``FieldPanel`` instead.
.. versionchanged:: 3.0
``ImageChooserPanel`` is no longer required to obtain an image chooser interface.
FormSubmissionsPanel
.. module:: wagtail.contrib.forms.panels
.. class:: FormSubmissionsPanel
This panel adds a single, read-only section in the edit interface for pages implementing the :class:`~wagtail.contrib.forms.models.AbstractForm` model.
It includes the number of total submissions for the given form and also a link to the listing of submissions.
.. code-block:: python
from wagtail.contrib.forms.models import AbstractForm
from wagtail.contrib.forms.panels import FormSubmissionsPanel
class ContactFormPage(AbstractForm):
content_panels = [
FormSubmissionsPanel(),
]
DocumentChooserPanel
.. module:: wagtail.documents.edit_handlers
.. class:: DocumentChooserPanel(field_name)
Deprecated; use ``FieldPanel`` instead.
.. versionchanged:: 3.0
``DocumentChooserPanel`` is no longer required to obtain a document chooser interface.
SnippetChooserPanel
.. module:: wagtail.snippets.edit_handlers
.. class:: SnippetChooserPanel(field_name, snippet_type=None)
Deprecated; use ``FieldPanel`` instead.
.. versionchanged:: 3.0
``SnippetChooserPanel`` is no longer required to obtain a document chooser interface.
Field Customisation
By adding CSS classes to your panel definitions or adding extra parameters to your field definitions, you can control much of how your fields will display in the Wagtail page editing interface. Wagtail's page editing interface takes much of its behaviour from Django's admin, so you may find many options for customisation covered there. (See Django model field reference).
Titles
Use classname="title" to make Page's built-in title field stand out with more vertical padding.
(collapsible)=
Collapsible
All panels are now collapsible by default.
Using classname="collapsed" will load the editor page with the panel collapsed under its heading.
content_panels = [
MultiFieldPanel(
[
FieldPanel('cover'),
FieldPanel('book_file'),
FieldPanel('publisher'),
],
heading="Collection of Book Fields",
classname="collapsed"
),
]
Placeholder Text
By default, Wagtail uses the field's label as placeholder text. To change it, pass to the FieldPanel a widget with a placeholder attribute set to your desired text. You can select widgets from Django's form widgets, or any of the Wagtail's widgets found in wagtail.admin.widgets.
For example, to customise placeholders for a Book model exposed via ModelAdmin:
# models.py
from django import forms # the default Django widgets live here
from wagtail.admin import widgets # to use Wagtail's special datetime widget
class Book(models.Model):
title = models.CharField(max_length=256)
release_date = models.DateField()
price = models.DecimalField(max_digits=5, decimal_places=2)
# you can create them separately
title_widget = forms.TextInput(
attrs = {
'placeholder': 'Enter Full Title'
}
)
# using the correct widget for your field type and desired effect
date_widget = widgets.AdminDateInput(
attrs = {
'placeholder': 'dd-mm-yyyy'
}
)
panels = [
FieldPanel('title', widget=title_widget), # then add them as a variable
FieldPanel('release_date', widget=date_widget),
FieldPanel('price', widget=forms.NumberInput(attrs={'placeholder': 'Retail price on release'})) # or directly inline
]
Required Fields
To make input or chooser selection mandatory for a field, add blank=False to its model definition.
Hiding Fields
Without a panel definition, a default form field (without label) will be used to represent your fields. If you intend to hide a field on the Wagtail page editor, define the field with editable=False.
(inline_panels)=
Inline Panels and Model Clusters
The django-modelcluster module allows for streamlined relation of extra models to a Wagtail page via a ForeignKey-like relationship called ParentalKey. Normally, your related objects "cluster" would need to be created beforehand (or asynchronously) before being linked to a Page; however, objects related to a Wagtail page via ParentalKey can be created on-the-fly and saved to a draft revision of a Page object.
Let's look at the example of adding related links to a Page-derived model. We want to be able to add as many as we like, assign an order, and do all of this without leaving the page editing screen.
from wagtail.models import Orderable, Page
from modelcluster.fields import ParentalKey
# The abstract model for related links, complete with panels
class RelatedLink(models.Model):
title = models.CharField(max_length=255)
link_external = models.URLField("External link", blank=True)
panels = [
FieldPanel('title'),
FieldPanel('link_external'),
]
class Meta:
abstract = True
# The real model which combines the abstract model, an
# Orderable helper class, and what amounts to a ForeignKey link
# to the model we want to add related links to (BookPage)
class BookPageRelatedLinks(Orderable, RelatedLink):
page = ParentalKey('demo.BookPage', on_delete=models.CASCADE, related_name='related_links')
class BookPage(Page):
# ...
content_panels = Page.content_panels + [
InlinePanel('related_links', heading="Related Links", label="Related link"),
]
The RelatedLink class is a vanilla Django abstract model. The BookPageRelatedLinks model extends it with capability for being ordered in the Wagtail interface via the Orderable class as well as adding a page property which links the model to the BookPage model we're adding the related links objects to. Finally, in the panel definitions for BookPage, we'll add an InlinePanel to provide an interface for it all. Let's look again at the parameters that InlinePanel accepts:
InlinePanel(relation_name, panels=None, heading='', label='', help_text='', min_num=None, max_num=None)
The relation_name is the related_name label given to the cluster's ParentalKey relation. You can add the panels manually or make them part of the cluster model. heading and help_text provide a heading and caption, respectively, for the Wagtail editor. label sets the text on the add button and child panels, and is used as the heading when heading is not present. Finally, min_num and max_num allow you to set the minimum/maximum number of forms that the user must submit.
For another example of using model clusters, see {ref}tagging.
For more on django-modelcluster, visit
the django-modelcluster github project page