Project

General

Profile

Actions

Feature #94886

open

Epic #93528: Backlog of UX ideas for Editors

Show minItems and maxItems config values for TCA FAL Fields in Backend

Added by Christoph Schwob over 3 years ago. Updated over 1 year ago.

Status:
Needs Feedback
Priority:
Should have
Assignee:
-
Category:
Backend User Interface
Start date:
2021-08-13
Due date:
% Done:

0%

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

Files

bad-ux-2.png (21.4 KB) bad-ux-2.png TCA Configuration Henrik Ziegenhain, 2023-04-06 04:23
bad-ux-1.png (38.3 KB) bad-ux-1.png Bad User Experience when Items are missing Henrik Ziegenhain, 2023-04-06 04:23

Related issues 1 (0 open1 closed)

Related to TYPO3 Core - Bug #89275: IRRE fields marked as error, even when they are not requiredClosed2019-09-25

Actions
Actions #1

Updated by Christoph Schwob over 3 years ago

  • Subject changed from Show minItems and maxItems for TCA FAL Fields in Backend to Show minItems and maxItems config values for TCA FAL Fields in Backend
Actions #2

Updated by Tymoteusz Motylewski over 3 years ago

  • Status changed from New to Needs Feedback

please add more description. a proof of concept would be nice

Actions #3

Updated by Christoph Schwob over 3 years ago

first idea was a small badge like on textfields with information about how many chars left.

but I'm open for ideas and feedback. At the moment this issue is more a note to think about it and collect ideas as an concrete task to do.

Actions #4

Updated by Riccardo De Contardi over 3 years ago

  • Parent task set to #93528
Actions #5

Updated by Benni Mack about 3 years ago

  • Target version changed from 11 LTS to Candidate for Major Version

Updated by Henrik Ziegenhain over 1 year ago

Imho this is more a bug than a feature.

Currently this missing badge leads to a very bad user experience in Backend

Think of the following situation:
  • TCA types `inline` or `file`
  • minitems > 1
  • User inserts first item

At this point at least one item is still missing to fulfil the requirement.
The field is marked with "has errors / mandatory", which would be indeed correct. But the user does not know why there are errors. Imho there an bade/indicator as descriped above is missing.

The second issue here is, all fields of the child items are marked as "has errors / mandatory" now, which is completly wrong.

Imho this would be a really great enhancement for v12 LTS, but I donĀ“t have any ideas how to solve this.
I only could provide some insights - as this is an issue for us since years - and testing.

Actions #7

Updated by Henrik Ziegenhain over 1 year ago

  • Related to Bug #89275: IRRE fields marked as error, even when they are not required added
Actions

Also available in: Atom PDF