Feature request: Using page factories for large-scale tree population



For a lot of projects, it can be helpful to establish the general 'page structure' of a site early on.

In the past, I've used fixtures for this, but I find them cumbersome. Every time you decide to switch up your model classes or fields, the fixtures remain unaware and require either a painful 'manual update' process, or a painful 'manually populate the tree locally and re-dump everything' process.

In a recent project, I decided that, since we were mostly defining a factory for every page type, we could use factories instead! I came up with the following:

from typing import Optional, Sequence

from django.template.defaultfilters import slugify
from wagtail.core.models import Page

from my_app.standardpages.factories import GeneralPageFactory

class CreatePageNode:
    Used to represent a 'Wagtail page' that must be created.

    default_factory_class = GeneralPageFactory

    def __init__(
        title: str,
        factory_class: type = None,
        children: Optional[Sequence["CreatePageNode"]] = None,
        self.title = title
        self.create_kwargs = kwargs
        self.factory_class = factory_class or self.default_factory_class
        self.children = children or []

    def create(
        self, parent: Page = None, create_subpages: bool = True, **kwargs
    ) -> None:
        create_kwargs = {**self.create_kwargs, **kwargs}
        create_kwargs.setdefault("title", self.title)
        if parent is None:
            parent = create_kwargs.get("parent") or Page.objects.first()

            page = (
                .get(slug=create_kwargs.get("slug", slugify(create_kwargs["title"])))
            created = False
        except Page.DoesNotExist:
            create_kwargs.setdefault("parent", parent)
            page = self.factory_class.create(**create_kwargs)
            created = True

        if create_subpages:
            for child in self.children:
                child.create(parent=page, create_subpages=True)

        return page, created

This can then be used to define a 'page tree to create', like so:

from .utils import CreatePageNode as p

            "About us",
                p("Accessibility Statement", specific_field_value="foo"),
                p("Collection", factory_property_value="bar"),
                p("Contact Us", slug="contact"),
                p("Corporate Support"),
                p("Frequently Asked Questions", slug="faqs"),
                    "Policies and Procedures",
                        p("Privacy Policy"),
                        p("Terms and Conditions"),
                p("Projects", ProjectIndexPageFactory),
                p("Working for us"),
            "Support us",
                p("Become a member"),
                p("Become a patron"),
            "Whats On?",
                p("Workshops", EventCategoryPageFactory, children=(
                    p("Example workshop", EventPageFactory, event_style="workshop"),
                p("Food & drink", EventCategoryPageFactory, children=(
                    p("Example cocktail evening", EventPageFactory, event_style="food"),
                p("Music", EventCategoryPageFactory, children=(
                    p("Jazz club", EventPageFactory, event_style="music", music_style="jazz"),
                    p("Rock city", EventPageFactory, event_style="music", music_style="rock"),

This can easily be incorporated into a management command that can trigger creation of all of these pages, like so:

from import BaseCommand

class Command(BaseCommand):
    def handle(self, *args, **options)

The process safely avoids creating/overwriting pages that already exist - meaning it can be rerun at a later time to add new sections (as the page types are developed)

2021-08-09 08:49:26

Add a Comment

Top 3 Comments

  easherma-truth answered on 2022-07-01 19:16:07

I think part of the issue is the sparse documentation around calling the factories (especially streamfield ones) in ways that will work. Like linking to something like body__0__carousel__items__0__label='Slide 1', in tests doesn't make a ton of sense by itself.

0 positive reactions.
  bcdickinson answered on 2022-07-01 15:55:45

Intriguing idea, but I'm not clear what would need to be built into wagtail-factories to support this use case. At first glance, a lot of your example looks like it'd be very specific to a particular project and there isn't a lot of code around just invoking the project's own factory classes.

Could you be more specific or maybe raise a PR?

0 positive reactions.
  ababic answered on 2021-08-09 09:16:05

The implementation above could easily be built upon to:

  • Allow for 'lazy' factory specification (using a string, and only importing/loading the factory class when create() is called)
  • Use settings to control the default_factory_class and data source for the management command (specified via dotted python path strings)
0 positive reactions.

Quick Hint

Where do wagtails birds live?

Where do wagtails nest? The pied wagtail likes farms, gardens, tundra, open country and inhabited areas, being as resourceful as they need to be. They can set up home right alongside people: under roofs, in walls and even in ivy hanging from houses. In winter, they are found more often on farmland.Jan 18, 2021

Repo Information

Age 5yrs
Vendor wagtail
Repo Name wagtail-factories
Primary Language Python
Default Branch main
Last Update 4 months ago

Wagtail's Code Library

Similar Issues

πŸ’Ύ wagtail Add ActivityPub support πŸ’¬ 5 closed πŸ—“οΈ 5 days ago
πŸ’Ύ wagtail Page jumps to top on "save draft" πŸ’¬ 3 open πŸ—“οΈ 1 week ago
πŸ’Ύ wagtail Eslint cleanup no plusplus rule πŸ’¬ 5 closed πŸ—“οΈ 1 week ago
πŸ’Ύ Performance: Enable text compression πŸ’¬ 3 closed πŸ—“οΈ 2 weeks ago
πŸ’Ύ Performance: serve images in next-gen formats πŸ’¬ 4 closed πŸ—“οΈ 2 weeks ago
πŸ’Ύ wagtail Local setup Error for Safari Browser πŸ’¬ 3 open πŸ—“οΈ 2 weeks ago
πŸ’Ύ wagtail Clean up eslint usage `no-prototype-builtins` πŸ’¬ 7 closed πŸ—“οΈ 3 weeks ago