You signed in with another tab or window. Reload to refresh your session.You signed out in another tab or window. Reload to refresh your session.You switched accounts on another tab or window. Reload to refresh your session.Dismiss alert
The validator option errorMessage can be used to provide a custom
string as error message for validation failures of the RegularExpressionValidator. In order to streamline error message
translation keys with all other validators, the validator option errorMessage has been marked as deprecated in TYPO3 v13 and will be
removed with TYPO3 v14.
Impact
Using the validator option errorMessage of the RegularExpressionValidator will trigger a PHP deprecation warning.
Affected installations
TYPO3 installations using the validator option errorMessage of the RegularExpressionValidator.
Migration
The new validator option message must be used to provide a custom and
translatable error message for failed validation.
Deprecation: #102326 - RegularExpressionValidator validator option "errorMessage"
https://docs.typo3.org/c/typo3/cms-core/main/en-us/Changelog/13.2/Deprecation-102326-RegularExpressionValidatorValidatorOptionErrorMessage.html
Deprecation: #102326 - RegularExpressionValidator validator option "errorMessage"
See 102326
Description
The validator option
errorMessage
can be used to provide a customstring as error message for validation failures of the
RegularExpressionValidator
. In order to streamline error messagetranslation keys with all other validators, the validator option
errorMessage
has been marked as deprecated in TYPO3 v13 and will beremoved with TYPO3 v14.
Impact
Using the validator option
errorMessage
of theRegularExpressionValidator
will trigger a PHP deprecation warning.Affected installations
TYPO3 installations using the validator option
errorMessage
of theRegularExpressionValidator
.Migration
The new validator option
message
must be used to provide a custom andtranslatable error message for failed validation.
Before:
After:
Backend, NotScanned, ext:extbase
The text was updated successfully, but these errors were encountered: