[TASK] Add TCA "required" config option for TYPO3v12+ #2228
Conversation
This file contains bidirectional Unicode text that may be interpreted or compiled differently than what appears below. To review, open the file in an editor that reveals hidden Unicode characters.
Learn more about bidirectional Unicode characters
|
I added a second commit to remove deprecated TCA configuration in TYPO3v12, so that no TCA migration notices are shown anymore. |
cweiske
force-pushed
the
tca-require
branch
2 times, most recently
from
687a0b7 to
697c96b
Compare
|
I've also adjusted the creation of flux form field configuration now. |
"eval=required" is not used anymore in TYPO3v12+, as described in the TCA migration message: > The TCA field 'title' of table 'content_types' defines "required" > in its "eval" list. > This is not evaluated anymore and should be replaced > by `'required' => true`. To keep backwards compatibility with TYPO3v10 and 11, "eval=required" is kept. Changelog entries: https://docs.typo3.org/c/typo3/cms-core/main/en-us/Changelog/12.0/Deprecation-97035-RequiredOptionInEvalKeyword.html https://docs.typo3.org/c/typo3/cms-core/main/en-us/Changelog/12.0/Feature-97035-UtilizeRequiredDirectlyInTCAFieldConfiguration.html
to prevent the following deprecation notices: 1. eval=required > The TCA field 'title' of table 'content_types' defines "required" > in its "eval" list. > This is not evaluated anymore and should be replaced > by 'required' => true. Changelog https://docs.typo3.org/c/typo3/cms-core/main/en-us/Changelog/12.0/Deprecation-97035-RequiredOptionInEvalKeyword.html https://docs.typo3.org/c/typo3/cms-core/main/en-us/Changelog/12.0/Feature-97035-UtilizeRequiredDirectlyInTCAFieldConfiguration.html 2. cruser_id > The TCA property ['ctrl']['cruser_id'] of table 'content_types' > is not evaluated anymore and has therefore been removed. > Please adjust your TCA accordingly. Changelog: https://docs.typo3.org/c/typo3/cms-core/main/en-us/Changelog/12.0/Breaking-98024-TCA-option-cruserid-removed.html
TYPO3v12 uses a new config option for required form fields instead of eval="required". Using <flux:field.input> with a required="1" property causes TYPO3 to log a deprecation notice: > TYPO3 Deprecation Notice: > FlexFormTools did an on-the-fly migration of a flex form data structure. > This is deprecated and will be removed. > Merge the following changes into the flex form definition > "settings.field": > The TCA field 'dummyField' of table 'dummyTable' defines "required" > in its "eval" list. > This is not evaluated anymore and should be replaced > by `'required' => true`. in > vendor/typo3/cms-core/Classes/Configuration/FlexForm/FlexFormTools.php > line 1127 This patch introduces a new code path for TYPO3v12+: "required" is not added to the "eval" configuration, but as a separate config array key. Changelog entries: https://docs.typo3.org/c/typo3/cms-core/main/en-us/Changelog/12.0/Deprecation-97035-RequiredOptionInEvalKeyword.html https://docs.typo3.org/c/typo3/cms-core/main/en-us/Changelog/12.0/Feature-97035-UtilizeRequiredDirectlyInTCAFieldConfiguration.html
|
Can I do something to help getting this merged? |
Sign up for free
to join this conversation on GitHub.
Already have an account?
Sign in to comment
Add this suggestion to a batch that can be applied as a single commit.
This suggestion is invalid because no changes were made to the code.
Suggestions cannot be applied while the pull request is closed.
Suggestions cannot be applied while viewing a subset of changes.
Only one suggestion per line can be applied in a batch.
Add this suggestion to a batch that can be applied as a single commit.
Applying suggestions on deleted lines is not supported.
You must change the existing code in this line in order to create a valid suggestion.
Outdated suggestions cannot be applied.
This suggestion has been applied or marked resolved.
Suggestions cannot be applied from pending reviews.
Suggestions cannot be applied on multi-line comments.
Suggestions cannot be applied while the pull request is queued to merge.
Suggestion cannot be applied right now. Please check back later.
"eval=required" is not used anymore in TYPO3v12+, as described in the TCA migration message:
To keep backwards compatibility with TYPO3v10 and 11, "eval=required" is kept.
Changelog entries:
https://docs.typo3.org/c/typo3/cms-core/main/en-us/Changelog/12.0/Deprecation-97035-RequiredOptionInEvalKeyword.html
https://docs.typo3.org/c/typo3/cms-core/main/en-us/Changelog/12.0/Feature-97035-UtilizeRequiredDirectlyInTCAFieldConfiguration.html
This change is necessary for the flux own content_types table, as well as configuration generated for flux form fields.