Unsupported operand types: null + array #533
Comments
|
Can you have a look, if there is any TCA field without the |
nhovratov
added a commit
that referenced
this issue
Feb 2, 2023
TYPO3 v12 introduced the new TCA type="file". This is great and so Mask removed the default TCA type="inline" and foreign_table="sys_file_reference" for it. The problem: Standard file fields with no option set have their config array removed completely. This happens in TcaFieldDefinition in the method removeBlankOptions. After the next save in the backend builder, Mask assumes this field is a core field and sets coreField=1. This is game over and needs to be fixed manually after. To circumvent this problem, the fields "maxitems" and "minitems" are kept in the config, eventhough they are empty and are added for every file field, if not defined. Fixes: #533
nhovratov
added a commit
that referenced
this issue
Feb 2, 2023
TYPO3 v12 introduced the new TCA type="file". This is great and so Mask removed the default TCA type="inline" and foreign_table="sys_file_reference" for it. The problem: Standard file fields with no option set have their config array removed completely. This happens in TcaFieldDefinition in the method removeBlankOptions. After the next save in the backend builder, Mask assumes this field is a core field and sets coreField=1. This is game over and needs to be fixed manually after. To circumvent this problem, the fields "maxitems" and "minitems" are kept in the config, eventhough they are empty and are added for every file field, if not defined. Fixes: #533
nhovratov
added a commit
that referenced
this issue
Feb 2, 2023
TYPO3 v12 introduced the new TCA type="file". This is great and so Mask removed the default TCA type="inline" and foreign_table="sys_file_reference" for it. The problem: Standard file fields with no option set have their config array removed completely. This happens in TcaFieldDefinition in the method removeBlankOptions. After the next save in the backend builder, Mask assumes this field is a core field and sets coreField=1. This is game over and needs to be fixed manually after. To circumvent this problem, the fields "maxitems" and "minitems" are kept in the config, eventhough they are empty and are added for every file field, if not defined. Fixes: #533
Sign up for free
to join this conversation on GitHub.
Already have an account?
Sign in to comment
Hi,
after Updating to Typo3 V11 (from 8 to 9 to 10) we got an "Unsupported operand types: null + array" when opening a Mask-Element. Typo3 throws
Core: Exception handler (WEB): Uncaught TYPO3 Exception: Unsupported operand types: null + array | TypeError thrown in file /usr/local/www/apache24/noexec/.../typo3_src-11.5.22/typo3/sysext/backend/Classes/Form/Container/SingleFieldContainer.php in line 185. Requested URL: https://..../typo3/record/edit?token=--AnonymizedToken--&edit%5Btt_content%5D%5B180%5D=edit&returnUrl=%2Ftypo3%2Fmodule%2Fweb%2Flayout%3Ftoken%3D--AnonymizedToken--%26id%3D54%26%23element-tt_content-180If I look at the code it seems to be, that typo3 needs some TCA-Information. How can we fix this problem?
The text was updated successfully, but these errors were encountered: