digital-marketing-framework / typo3-form-fieldnames
Anyrel backend section for reviewing and filling in form field names.
Package info
github.com/digital-marketing-framework/typo3-form-fieldnames
Type:typo3-cms-extension
pkg:composer/digital-marketing-framework/typo3-form-fieldnames
Requires
- php: ^8.2
- digital-marketing-framework/typo3-core: ^4.0
- mediatis/form_fieldnames: ^4.3
- typo3/cms-core: ^12.4 || ^13.4 || ^14.3
Requires (Dev)
- ergebnis/composer-normalize: ^2.28
- friendsofphp/php-cs-fixer: ^3.27
- helmich/typo3-typoscript-lint: ^3.1.0
- phpstan/extension-installer: ^1.3.1
- phpstan/phpstan: ^2.0
- phpstan/phpstan-strict-rules: ^2.0
- rector/rector: >=2.5.2 <2.6.4
- saschaegerer/phpstan-typo3: ^2.0 || ^3.0
- seld/jsonlint: ^1.10.0
- ssch/typo3-rector: ^3.0
- symfony/yaml: ^5.3.6 || ^6.2.0 || ^7.1.4
- typo3/coding-standards: dev-main
- typo3/testing-framework: ^8.2.7 || ^9.0
Suggests
None
Provides
None
Conflicts
- typo3/class-alias-loader: < 1.1.0
Replaces
None
This package is auto-updated.
Last update: 2026-09-03 10:09:01 UTC
README
Adds a Form Field Names section to the Anyrel backend module, showing which form elements still need a field name and filling them in.
Background
mediatis/form_fieldnames adds a
required, form-unique Name to every TYPO3 form element, separate from the
translatable label. Anyrel reads that name as the stable identifier for data mapping.
When an existing project starts using Anyrel, none of its form elements have one yet,
and the form editor reports a validation error for each of them. That extension ships
a form:fieldnames CLI command to derive names from the labels; this package puts the
same thing in the backend, for people who do not work on the command line.
Requirements
- TYPO3 12.4, 13.4 or 14.x
- PHP 8.2 or newer
digital-marketing-framework/typo3-coreandmediatis/form_fieldnames
Installation
composer require digital-marketing-framework/typo3-form-fieldnames
Usage
The section appears in the Anyrel backend module as Form Field Names. It lists every form that has elements without a name, together with the name that would be generated for each, and flags problems that cannot be resolved automatically — forms in read-only storage, unparsable definitions, duplicate names set by hand, and form identifiers used by more than one form.
Nothing is written until you press a button:
- Fill in these names writes the missing names of one form
- Fill in all missing names does the same for every listed form, and only appears when more than one form is affected
An existing name is never overwritten, and a form that is already complete is not listed. Review the generated names afterwards — they are derived from the labels as a starting point, not a substitute for deciding what a field should be called.
Flush the frontend caches afterwards so pages embedding the changed forms are rebuilt.
The naming rules — snake_case, umlaut transliteration, LLL: labels resolved against
the default language, identifier fallback, numeric suffixes for collisions — are
documented in mediatis/form_fieldnames, which implements them.
Development
composer ci # all checks composer ci:static # style, types and linting only composer fix # apply rector and php-cs-fixer
License
GPL-2.0-or-later