Issue Feature Closed

#106351Provide central collection where non browsable page doktypes can be registered

Sascha Egerer 03/10/25, 14:02 updated 01/23/26, 19:04

Description

Since TYPO3 v10 it is possible to use any number of doktype with “pages.doktype” and the limitation of custom doktypes “less than 200” was lifted.

Now we have some doktypes that are not accsesible what there is no “central” knowlege about it and even no possiblity anymore to add custom doktypes.
In the core there are a bunch of places where PageRepository::DOKTYPE_SPACER, PageRepository::DOKTYPE_SYSFOLDER are checked manually.

This should be refactored to a central storage or an TCA option where a page can be defined as “non browsable”.

Reviews 1

History 6

  1. Benni Mack commented and changed assigned to Benni Mack <span data-processor="relativetime" data-value="2025-03-27T18:36:00+00:00" > 03/27/25, 18:36 </span>

    Yes. we’re going to add this soon (hopefully in v14)!

  2. Benni Mack commented and changed status Accepted Needs Feedback <span data-processor="relativetime" data-value="2026-01-23T18:53:17+00:00" > 01/23/26, 18:53 </span>

    What exactly is your definition of “non-browsable”? I built this change here: https://review.typo3.org/c/Packages/TYPO3.CMS/+/92485

  3. Sascha Egerer commented and changed status Needs Feedback Closed <span data-processor="relativetime" data-value="2026-01-23T19:04:07+00:00" > 01/23/26, 19:04 </span>

    Benni Mack wrote in #note-4:
    > What exactly is your definition of “non-browsable”? I built this change here: https://review.typo3.org/c/Packages/TYPO3.CMS/+/92485

    Looks like something as I’ve expected. I’ll close this one. Thank you!