Actions
Story #94430
closedpages.doktypes higher than 200 do not work properly as frontend pages
Status:
Closed
Priority:
Should have
Assignee:
-
Category:
Backend API
Target version:
-
Start date:
2021-08-11
Due date:
% Done:
100%
Estimated time:
(Total: 0.00 h)
TYPO3 Version:
10
PHP Version:
7.4
Tags:
Sprint Focus:
Description
The documentation states that pre TYPO3 10.4, pages that were supposed to be used as frontend pages, needed to have a doktype
below 200. Since 10.4 this restriction would no longer apply:
In 10.4.17 custom page types with a doktype
higher than 200 (I tried 301 and 302) do actually render in the frontend. Some things do not work though:
- Page Type Shortcut:
A shortcut to a page with adoktype > 200
does not work in Shortcut Mode First subpage of selected/current page. Subpages of the current page with adoktype > 200
will not be considered and thus not called in the frontend, even if they clearly are the first subpage of the shortcut.
- Link Browser
Pages with doktypes > 200 will be muted in the page tree, just as Sysfolders. Thus you cannot set links to pages with doktype > 200 or content elements on these pages.
- View button in doceader
When editing a content element on a page with doktype > 200 the view button will not render this page in the frontent. In my case it rendered the root page instead withdoktype = 4
I eventually changed my custom PAGES_TYPES
to a number below 200 and the described problems disappeared.
Actions