Project

General

Profile

Actions

Bug #72689

closed

6.2.17 broke editing of content elements

Added by Florian Seirer almost 9 years ago. Updated over 8 years ago.

Status:
Rejected
Priority:
Must have
Assignee:
-
Category:
-
Target version:
-
Start date:
2016-01-14
Due date:
% Done:

0%

Estimated time:
TYPO3 Version:
6.2
PHP Version:
5.4
Tags:
Complexity:
Is Regression:
No
Sprint Focus:

Description

After upgrading from 6.2.15 to 6.2.17, editors can no longer edit some (!) of their content elements.
Upon opening the element, they get the following message instead of the editing forms:

Reason: ERROR: authMode "explicitAllow" failed for field "list_type" with value "0" evaluated

I compared a not-editable content element with an editable one and found out that, while they both are of the same type (text), the editable CE hast list_type=0, while the non-editable CE has list_type=NULL.


Related issues 1 (0 open1 closed)

Related to TYPO3 Core - Bug #32209: Be user with explicit deny can edit the content plugin fieldsClosed2011-11-30

Actions
Actions #1

Updated by Florian Seirer almost 9 years ago

In one of our TYPO3 installations about 80% (!) of CEs were not editable.
Reverting back to 6.2.15 resolved the problem, at least temporarily.

Actions #2

Updated by Morton Jonuschat almost 9 years ago

  • Status changed from New to Rejected

TYPO3 6.2.16 implemented stricter checking of authentication for editing content elements in commit 83e0ef9f

If you can't fix your permissions for the affected editors you can override the TCA configuration to disable strict enforcement.

Actions #3

Updated by Florian Seirer almost 9 years ago

The TCA override works, thanks.

But the editor is unsuccessfully trying to edit a text element, not a list element (plugin).
So what has the value of list_type to do with that?

Actions #4

Updated by Florian Seirer almost 9 years ago

Anyways, if sombody else is having the same problem:

update tt_content set list_type='' where list_type='0';
solved the issue for me, even without touching the TCA config.

Must have been some legacy thing...

Actions #5

Updated by Daniel Alder over 8 years ago

Florian Seirer wrote:

Anyways, if sombody else is having the same problem:
[...] solved the issue for me, even without touching the TCA config.

Must have been some legacy thing...

same issue here. changing the field "list_type" to empty string as described by florian worked for me too.

Actions #6

Updated by A. Sales over 8 years ago

Hello Daniel,
Where and/or which file do I write (update tt_content set list_type='' where list_type='0';)
in?
Thanks, Anthony

Actions #7

Updated by Florian Seirer over 8 years ago

You need a direct connection to the DB.
The extension phpmyadmin should work just fine for that, or desktop software like MySQL Workbench.

Don't forget to create a backup before. ;-)

Actions #8

Updated by A. Sales over 8 years ago

Thanks for the advise, I will try it.

Actions

Also available in: Atom PDF