Issue Feature Resolved

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

Christoph Schwob 08/13/21, 19:09 updated 09/04/26, 06:40

Description

No description.

Reviews 1

Files 2

History 916

  1. Christoph Schwob changed subject Show minItems and maxItems for TCA FAL Fields in Backend Show minItems and maxItems config values for TCA FAL Fields in Backend <span data-processor="relativetime" data-value="2021-08-13T19:09:19+00:00" > 08/13/21, 19:09 </span>

  2. Tymoteusz Motylewski commented and changed status New Needs Feedback <span data-processor="relativetime" data-value="2021-08-14T11:48:01+00:00" > 08/14/21, 11:48 </span>

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

  3. Christoph Schwob commented <span data-processor="relativetime" data-value="2021-08-14T12:34:41+00:00" > 08/14/21, 12:34 </span>

    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.

  4. Henrik Ziegenhain commented and changed attached bad-ux-2.png attached bad-ux-1.png <span data-processor="relativetime" data-value="2023-04-06T04:24:33+00:00" > 04/06/23, 04:24 </span>

    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.

  5. Gerrit Code Review pushed patch set 1 for main to change 95367 status Needs Feedback Under Review <span data-processor="relativetime" data-value="2026-08-19T07:54:36+00:00" > 08/19/26, 07:54 </span>

  6. Josua Vogel commented and changed status Under Review Resolved done 0 % 100 % <span data-processor="relativetime" data-value="2026-09-04T06:40:11+00:00" > 09/04/26, 06:40 </span>

    Applied in changeset commit:7f695ce1175be9527aa82b85339331f58451257f.