Pagetree Facets (TYPO3 v13+)
New in version 2.5.0
Integration with konradmichalik/typo3-pagetree-facets was introduced in version 2.5.
If the optional konradmichalik/typo3-pagetree-facets extension is installed and enablePagetreeFacetsIntegration is enabled, a Content Planner facet appears in the page tree filter modal.
The Content Planner facet in the page tree filter modal, with a
status: criterion selected and "Pages only" left at its default
Table of Contents
Tokens
| Token | Values | Notes |
|---|---|---|
status: | status uid(s), comma-separated for OR, none | Only statuses allowed for the current user (see Permissions) are offered or matched; a disallowed uid resolves to no match, silently. |
assignee: | me, a backend user uid, none | none means unassigned. |
comments: | open, resolved, todo, mine, none | todo only appears when commentTodos is enabled. |
Values within one token combine with OR (status:); separate tokens
combine with AND (status:), same as every other facet in
this filter modal.
Other Registered Records
Other registered records (such as content elements if enabled via
enableContentElementSupport, and
any additional records registered via Extension)
can carry their own status, assignee and comments. However, the page tree
filter only ever returns pages. All three tokens therefore match a page whose
other registered records meet the criteria as well as pages that match
directly, unless the modal's "Pages only" checkbox is ticked, which
restricts every token to page-level matches only. Unticked (the default) is
the broader match.
Files and folders (enableFilelistSupport) are excluded from this matching, even though they can also carry a status, assignee and comments: they live in the file storage tree, not the page tree, and have no page they could resolve to (see "Out of scope" below).
Note
This checkbox defaults to unticked deliberately, not ticked: the filter modal treats any ticked checkbox across every facet as an active filter criterion for its chip bar and "N active filters" indicator, with no way to express "only matters together with another field in this facet" - a ticked-by-default checkbox would therefore show as a permanent, always- active chip on every use of the filter modal, regardless of whether any status, assignee or comment criterion is selected at all.
Note
This checkbox only has an effect once at least one status, assignee or comment criterion is also selected in this facet — it modifies how those tokens match, rather than being a filter criterion of its own. With nothing else selected, the filter modal's underlying framework never calls this facet at all, so ticking the checkbox alone has nothing to persist and appears to reset the next time the modal opens.
Out of scope
- Slug-based
status:tokens (uid-only for now) - Filtering the file storage tree