I have this Page with a ForeignKey districtobject:

I created a Custom image model to add Attribution to Images. I just followed the Wagtail Documentation for this: https://docs.wagtail.org/en/stable/advanced_topics/images/custom_image_model.html

I am new to wagtail. I found out how to edit the homepage and add HTML contents. But I want the content to depend on whether the user is logged in or not (e.g. if the user is not logged in, write “please log in”, otherwise, write “hello user”). I tried to write the following code, which I found somewhere on the net, in the “html” text-box in the editor:

In Wagtail, consider the following page types:

I am migrating our content from Wagtail ModelAdmin to the new *ViewSet approach. I notice that the new *ViewSet allows users to define new items via a button along the top saying “Add “

I’m creating a PageListingViewSet and would like to specify the default ordering in the table view. Previously, the ModelAdmin class (from which I’m migrating our code) allowed me to specify ordering. Likewise, the Wagtail ModelViewSet allows developers to specify ordering. However, the PageListingViewset doesn’t define or inherit from a class that allows ordering to be defined.

I was using django-improved-user with Wagtail (up to Wagtail 6.0) and things were working fairly well. With Wagtail 6.1 now, the user listing page errors out because it is trying to order the listing by first name and last name, but the default user model supplied by django improved user does not have those fields. It instead uses full name and short name. Is there a simple way to customize the user listing page to determine which columns to use and how to specify the ordering?

When creating a Wagtail 6 PageListingViewSet, we are able to add child pages via an action under the ellipsis menu:

I am working with Wagtail CMS (version 6.1) and have implemented a topic chooser view set to allow selecting and creating topics that are applied to content such as news items. These topics inherit from the Wagtail page model, enabling the creation of topic listing pages.

I am working with Wagtail CMS (version 6.1) and have implemented a PageListingViewSet to list news items, which inherit from the Wagtail page model. Everything functions correctly, but when I click the button to create a new news item, Wagtail prompts me to choose the parent page.