Project

General

Profile

Actions

Bug #15831

closed

TCA usergroup limit too smal

Added by David Worms over 18 years ago. Updated over 16 years ago.

Status:
Closed
Priority:
Should have
Assignee:
Category:
-
Target version:
-
Start date:
2006-03-15
Due date:
% Done:

0%

Estimated time:
TYPO3 Version:
4.0
PHP Version:
4
Tags:
Complexity:
Is Regression:
Sprint Focus:

Description

Here's the usecase: we had to create usergroups and assign permission to those. The problem was, we could not select more than 20 items for a list which holds many more. We created a small extension to update the TCA but since we might not be the only one to face this issue, here are the line. Please feel free to replace the value with the integer of your choice, being a bit larger than the one we have today:

from an_extension/ext_tables.php:

t3lib_div::loadTCA('be_groups');

$TCA["be_groups"]["columns"]["tables_modify"]["config"]["maxitems"] = 999;
$TCA["be_groups"]["columns"]["tables_select"]["config"]["maxitems"] = 999;
$TCA["be_groups"]["columns"]["non_exclude_fields"]["config"]["maxitems"] = 9999;

(issue imported from #M2879)


Related issues 1 (0 open1 closed)

Related to TYPO3 Core - Bug #16553: In BE Usergroup, it is not possible to select more than 20 tables(modify) at any timeClosedOliver Hader2006-09-12

Actions
Actions #1

Updated by Franz Holzinger over 18 years ago

How should such an extension to update the TCA look like?
Wouldn't it be better to find implement this using a TypoScript Configuration? This would e.g. make it possible to have different TCA settings on different pages.

Actions #2

Updated by David Worms over 18 years ago

The TCA configuration we are overwriting is found in t3lib/stddb/tbl_be.php.

The only purpose is to allow the administrator of the site to select more items when he configure backend usergroup's permissions. Since backend usergroup can only be maintained from the root page of Typo3, I don't really see a reason why we should make this configurable through an extension. Our own extension was just here to fix this behavior without having to hack the original source code. While we were configuring our backend usergroups, we just could not find a reason why those values where so low, this is why I would suggest to update the file mentioned above.

Actions #3

Updated by Sacha Vorbeck over 18 years ago

I had a similar problem today. I tried to select some additional allowed excludefields in the page-content section for a usergroup and suddenly my admin-BE-user session was terminated after saving the group. This didn`t happen when I de-selected some fields from other sections before so the total amount of the fields seems to be the problem. I yet have to try if setting "$TCA["be_groups"]["columns"]["non_exclude_fields"]["config"]["maxitems"] = 9999;" will solve the problem.

@David Worms: did you get some kind of error message or was your session also terminated?

Actions #4

Updated by David Worms over 18 years ago

No, we didn't encounter any kind of error, we were just limitited by the limited amount of selections allowed.

Actions #5

Updated by Lars Houmark over 16 years ago

The bug related with this one is fixed (4202), so I am setting this one to fixed as well.

Actions

Also available in: Atom PDF