Project

General

Profile

Actions

Feature #82213

closed

Since introducing the "unused content elements" feature we need a way to allow third party code to decide used/unused status

Added by Claus Due almost 7 years ago. Updated over 5 years ago.

Status:
Closed
Priority:
Should have
Assignee:
-
Category:
-
Target version:
-
Start date:
2017-08-26
Due date:
% Done:

100%

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

Description

The implementation of https://forge.typo3.org/issues/67884 unfortunately leaves no room for solutions which for one reason or the other, uses virtual column position (colPos) values. Every such colPos value is automatically considered invalid if it isn't part of the backend layout - but it is possible to add colPos selection values which are not in the backend layout. The result is that such solutions, including Flux, are negatively affected because all nested content is shown as "lost" or "unused".

It is necessary to add at least a basic way for third party code to weigh in on the decision whether a given record is unused or not. A signal can solve this perfectly.


Files

Actions

Also available in: Atom PDF