Project

General

Profile

Actions

Bug #86909

closed

tt_content examples in "Page" module does not respect CTypes added via TSconfig

Added by Soren Malling about 6 years ago. Updated over 5 years ago.

Status:
Closed
Priority:
Should have
Assignee:
-
Category:
Backend User Interface
Target version:
-
Start date:
2018-11-11
Due date:
% Done:

100%

Estimated time:
TYPO3 Version:
9
PHP Version:
7.2
Tags:
autosite, sites
Complexity:
Is Regression:
Sprint Focus:

Description

Case

I've added a number of items to the tt_content field CType directly via Page TSconfig.

When I add a content element which is added via TSconfig, the backend print "INVALID VALUE (webability_[contentname])". This is due to the $CType_labels property being used for rendering is not taking what is added via TSconfig in to concern.

Proposed solution

I suggest that we streamline this access of content types, so changes made via tsconfig or any other condition is taken into account and returns a single point of getting these values.

Perhaps a more API-wise solution. A "Content Element Registry" of a kind.

Comments are welcome, I will love to put time into it.

This is finding and suggestion based on the work of EXT:autosite where TSconfig is playing a big part in keeping each pagetree/site clean.


Files

Actions

Also available in: Atom PDF