Migrate TYPO3 FlexForm data columns

Question

Database records with FlexForm columns don't auto-upgrade when new fields are added in the flexform. When adding a new select field in a plugin configuration (or a flux content element), I can't rely on the field having the default value in all content elements - because the values of newly added fields are only stored in the database when editing the content elements. This makes code larger because I have to account for not-yet-existing values.

Example: A "color" select field with a default value that we just output into a class attribute:

<a class="{settings.color}">...</a>

Putting a check/switch in there makes the code much more verbose and unreadable.

What would be a good way to adjust the database records of existing (plugin) content elements when flexforms change?

The lowlevel cleanup:flexforms command only removes values for non-existing fields AFAIK.

Not sure if this works for all types, but I found in the code: The command cleanup:flexforms uses FlexFromTools-> cleanFlexFormXML which writes back missing values: github.com/TYPO3/typo3/blob/… — Tobias Gaertner
– Tobias Gaertner, Commented Sep 8 at 8:27
No, just tried it: When adding a new select and number field to plugin flexform, cleanup:flexforms does not add those to the database. Only when removing fields from flexform - those fields get removed from database. — cweiske
– cweiske, Commented Sep 8 at 11:33

Tobias Gaertner · Accepted Answer · 2025-09-09 06:35:52Z

0

I personally would never rely on any free xml data comming from a flexform field, but always work with strong defaults while handling those data. E.g. in a switch-case use the default-case for the expected default.

answered Sep 9 at 6:35

Tobias Gaertner

1,18412 silver badges31 bronze badges

Sign up to request clarification or add additional context in comments.

2 Comments

cweiske Sep 10 at 4:19

We're doing this, and this is causing problems because of unnecessary code. Think e.g. of a "color" field with a default value that you just output into a class attribute: <a class="{settings.color}">...</a> - putting a switch in there makes the code much more verbose.

Tobias Gaertner Sep 10 at 15:15

I can think of something like '<a class="{f:if(condition:'{settings.color}, then: '{settings.color', else: 'default-color-class''}' or even simpler '<a class="default-color {settings.color}">...'

Collectives™ on Stack Overflow

Migrate TYPO3 FlexForm data columns

1 Answer 1

2 Comments

Your Answer

Hot Network Questions

Collectives™ on Stack Overflow

1 Answer 1

2 Comments

Your Answer

Sign up or log in

Post as a guest

Related