Project

General

Profile

Actions

Bug #68247

closed

Story #69712: Further FormEngine development

group maxitems woes

Added by Christian Kuhn almost 9 years ago. Updated over 5 years ago.

Status:
Closed
Priority:
Should have
Assignee:
-
Category:
FormEngine aka TCEforms
Target version:
-
Start date:
2015-07-16
Due date:
% Done:

100%

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

Description

The maxitems setting for TCA group fields is somehow unclear.

tca docu states there is a default of 1 if no maxitems is set. but this only seems to fire in case there is no mm relation (?).

for "csv" relations, the maxitems=1 is active. Current behavior is that if no maxitems is set in csv relation and default 1 kicks in, the formengine still allows selecting more than one element, but datahandler throws all of them away except the first one on saving. this is a bug in formengine validation and should be fixed.

Additionally, we should find out when, where and why the maxitem default kicks in and think about if that makes sense, or if a different default should be chosen consistently (0 for "no restriction, or 9999 or similar?). This implies thought about b/w compatibility and maybe a tca migration, then.

it might be a good idea to enrich ext:styleguide with additional scenarios to nail the current and the expected situation.


Related issues 1 (0 open1 closed)

Related to TYPO3 Core - Bug #62007: Impossible to save a category with many opposite relationsRejected2014-10-02

Actions
Actions

Also available in: Atom PDF