The field level options
minitems
and
maxitems
limit how many rows the
wizard accepts. They are named and behave like their counterparts on the native TCA
types
inline
,
select
and
group
. Both default to
0
, which
means "no limit".
maxitems
counts rows. Once it is reached, the "Create new record after
this record" button of every row is disabled. Records that already exceed the limit
are still rendered - they are flagged instead of silently truncated, so no data is
lost when a limit is lowered later on.
minitems
counts filled rows. The wizard always keeps one row on screen,
so a single untouched row counts as zero items.
Violations mark the field with the FormEngine error class. This blocks saving and
raises the standard "fields missing" modal, the same way native TCA types do. Like
those types, the limits are not enforced by the DataHandler.
Warning
minitems
must not exceed
maxitems
, and both must be non-negative
integers. Anything else throws an
\LIA\LiaMulticolumnwizard\Exceptions\Backend\InvalidOptionValueException
while rendering the form.
Field length options
Columns of type
text
and
textarea
accept
max
and
min
-
named after the native TCA options for
input
and
text
- to limit the
number of characters.
max
renders as
maxlength
, so the browser stops further input.
text
columns default to
255
;
textarea
columns stay uncapped
unless
max
is set.
min
renders as
minlength
and is additionally checked in JavaScript,
because FormEngine submits the form itself and the browser therefore never runs its
own
minlength
validation. Empty fields are never flagged - use
minitems
to require rows.
Reference index
A multiColumnWizard field stores its rows as a JSON string, which the
typolink
soft reference parser cannot read. Links maintained in the wizard are therefore invisible
to
sys_refindex
by default: TYPO3 does not warn that a page is still referenced
when it is deleted, and the info module does not list the reference.
The parser key
multiColumnWizardTypolink
closes that gap. It walks the rows, hands
every value of a
link
column to the typolink parser and merges the results, so the
links are indexed like the ones of a native link field.
Run
typo3 referenceindex:update
afterwards to index the existing records. All link
types the typolink parser supports are covered, page and record links included.
Note
The link columns are read from
columnFields
of the field, unioned with the
columnsOverrides
of every record type - the reference index works on the raw
record and does not resolve the type. A column name used as a link in one record type
and as something else in another is consequently parsed as a link everywhere.
Set up the DatabaseFileds in your database tables:
In order to use the link feature you need to also create a field of type link in the current TCA and reference it in the multicolumnwizard link
field in the linkUseField attribute. This field will be automatically hidden by Javascript.
Here you can also use your own function to generate the selection options. The function must return an array, otherwise you will receive an exception.
Enter the complete class name as the first parameter. The second parameter is the function name followed by an array with all the parameters required to execute your function.
ViewHelpers
Rendered
Fri, 04 Sep 2026 14:25:56 +0000
This is a complete reference of all available Fluid ViewHelpers. This documentation is generated from PHP Source code.