You signed in with another tab or window. Reload to refresh your session.You signed out in another tab or window. Reload to refresh your session.You switched accounts on another tab or window. Reload to refresh your session.Dismiss alert
The PageListingViewSet documentation on Custom page listings in Wagtail 6.1 is very nice, that allows nice listings of specific model pages.
However, it is not clear to me if it's possible to use the method to customize the standard lists of content accessed from the page tree? And if so, how to do that?
In my case I'd like to add a column and a filter to all pages, just as in a custom listing.
Many thanks!
The text was updated successfully, but these errors were encountered:
Thanks for the suggestion @krzysztofjeziorny! Customising the main explorer view through PageListingViewSet isn't currently supported, so this isn't just a documentation issue - have updated the issue title accordingly.
A large part of the difficulty here is that the listing is always generated by querying the base Page model (since we don't know in advance which page types will exist in the currently viewed section - even if a subpage_types rule is in place, there might be other pages still remaining from before that rule was added), and so we can't filter on fields defined on more specific page types.
I think we could handle that by associating PageListingViewSet subclasses with particular parent page models - so, for example, you could define an EventPageListingViewSet based on an EventPage model that adds a column / filter on the event's date field, and configure that to be used whenever you're viewing children of an EventIndexPage.
The
PageListingViewSet
documentation on Custom page listings in Wagtail 6.1 is very nice, that allows nice listings of specific model pages.However, it is not clear to me if it's possible to use the method to customize the standard lists of content accessed from the page tree? And if so, how to do that?
In my case I'd like to add a column and a filter to all pages, just as in a custom listing.
Many thanks!
The text was updated successfully, but these errors were encountered: