Project

General

Profile

Actions

Feature #106351

open

Provide central collection where non browsable page doktypes can be registered

Added by Sascha Egerer 5 days ago.

Status:
New
Priority:
Should have
Assignee:
-
Category:
-
Target version:
-
Start date:
2025-03-10
Due date:
% Done:

0%

Estimated time:
PHP Version:
Tags:
Complexity:
medium
Sprint Focus:

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".


Related issues 1 (1 open0 closed)

Related to TYPO3 Core - Bug #106349: Non browsable pages should not be slug candidatesUnder ReviewSascha Egerer2025-03-10

Actions
Actions

Also available in: Atom PDF