Bug #79427

Non-plugin content elements not accessible when list_type not empty

Added by Philipp Kitzberger over 2 years ago. Updated over 1 year ago.

Status:
New
Priority:
Must have
Assignee:
-
Category:
-
Target version:
-
Start date:
2017-01-23
Due date:
% Done:

0%

TYPO3 Version:
7
PHP Version:
Tags:
Complexity:
Is Regression:
No
Sprint Focus:

Description

Szenario: Admin creates a content element (CType='plugin'), chooses a valid plugin (e.g. 'powermail_pi1'), saves it and then decides it should be a CType='textmedia' instead. The so modified content element is then not accessible (editable) for editors that lack the right to edit said plugin. Even though it's a textmedia element now.

Somewhere in the access control management procedure the field 'list_type' seems to be taken into account even though it's irrelevant for non plugins.

A workaround would be to run this on the DB:

UPDATE tt_content SET list_type='' WHERE ctype != 'list' AND list_type != '';

Related issues

Related to TYPO3 Core - Bug #77312: Flexform is not rendered in content elements, when list_type is not empty New 2016-07-29
Related to TYPO3 Core - Feature #76925: Switching from one content type to another should clear fields not usable anymore New 2016-07-04

History

#1 Updated by Riccardo De Contardi almost 2 years ago

  • Related to Feature #76925: Switching from one content type to another should clear fields not usable anymore added

#2 Updated by Riccardo De Contardi over 1 year ago

It is still reproducible on 9.2.0-dev (latest master)

Also available in: Atom PDF