#106730Type 0 is not recognized in backend TCA for records
Description
Since TYPO3 version 13.4.10 it seems that record types having the key 0 do not show the appropriate TCA input masks anymore.
This error also happens with 13.4.11. In 13.4.9 everything works as expected.
For example the news extension uses type=0 for standard news. But now the backend automatically shows the TCA mask for the type=1 (internal news), even if the type selection is correctly set to 0 (hence displaying the field “internalurl” but not “bodytext”).
Can you please check the problem?
Thank you!
Reviews 0
No change resolves or names this issue in its commit message, and no comment links one.
History 8
-
Georg Ringer commented and changed status
NewClosed <span data-processor="relativetime" data-value="2025-05-19T17:33:15+00:00" > 05/19/25, 17:33 </span> -
Georg Ringer changed Duplicates #106697 <span data-processor="relativetime" data-value="2025-05-19T17:33:22+00:00" > 05/19/25, 17:33 </span>
-
Matthias Buchegger commented and changed PHP Version 8.4 <span data-processor="relativetime" data-value="2025-05-20T19:33:08+00:00" > 05/20/25, 19:33 </span>
Not fixed in 13.4.12 as announced. Still have the issue, that settings of type 0 are ignored in TCA.
cosmoblonde GmbH wrote:
> Since TYPO3 version 13.4.10 it seems that record types having the key 0 do not show the appropriate TCA input masks anymore.
> This error also happens with 13.4.11. In 13.4.9 everything works as expected.
>
> For example the news extension uses type=0 for standard news. But now the backend automatically shows the TCA mask for the type=1 (internal news), even if the type selection is correctly set to 0 (hence displaying the field “internalurl” but not “bodytext”).
>
> Can you please check the problem?
> Thank you! -
cosmoblonde GmbH commented <span data-processor="relativetime" data-value="2025-05-20T20:14:33+00:00" > 05/20/25, 20:14 </span>
For our project, the fix of todays release 13.4.12 works.
Tested for news records.@Matthias Buchegger: I assume you have the problem in an extension that is not news? Is the type = 0 defined as string or integer?
-
Matthias Buchegger commented <span data-processor="relativetime" data-value="2025-05-22T15:43:13+00:00" > 05/22/25, 15:43 </span>
cosmoblonde GmbH wrote in #note-4:
> For our project, the fix of todays release 13.4.12 works.
> Tested for news records.
>
> @Matthias Buchegger: I assume you have the problem in an extension that is not news? Is the type = 0 defined as string or integer?It’s the exactly same like in the news ext.
the defined type field has integer values (I use selects or toggles).
the types are defined as strings. but I tested that to change it in integers and that doesn’t work either.everything worked fine in 13.4.10.
-
Garvin Hicking commented <span data-processor="relativetime" data-value="2025-05-23T06:27:23+00:00" > 05/23/25, 06:27 </span>
mbucheggermb_online – could you post your exact TCA config (and if existing the ext_tables.sql part for the field). Could be an issue of how the db field is stored. -
Matthias Buchegger commented <span data-processor="relativetime" data-value="2025-05-23T14:01:18+00:00" > 05/23/25, 14:01 </span>
Garvin Hicking wrote in #note-6:
>mbucheggermb_online – could you post your exact TCA config (and if existing the ext_tables.sql part for the field). Could be an issue of how the db field is stored.Of Course…
That’s the TCA
https://jmp.sh/cvwHHQBnext_tables.sql
CREATE TABLE tx_publicrelations_domain_model_content ( uid int(11) NOT NULL auto_increment, pid int(11) DEFAULT '0' NOT NULL, mailing int(11) unsigned DEFAULT '0', invitation int(11) unsigned DEFAULT '0', role tinytext, type int(11) unsigned DEFAULT '0' NOT NULL, ...We just updated from typo3 v11 to v13, but nobody in the team recognized any issue in 13.4.10 and after the update to 13.4.11 we recognized that “bug”. Due to the fact it was recognized by others as well I thought it should be done with the update to 13.4.12, but it’s still the same. Was not sure if there’s a caching issue with files, but I deleted everything from all the other versions, so there’s no way to use old files.
I did a workaround with setting a value 100 in the whole extension, but that’s not very clean. It’s just the 0 that’s not recognized, everything else is working well.
-
Garvin Hicking commented <span data-processor="relativetime" data-value="2025-05-23T15:51:05+00:00" > 05/23/25, 15:51 </span>
please try to swt the “type” field in your ext_tables.sql to varchar. Or remove the definition to let the TCA SQL automatism kick in, that could help?
closing as duplicate of #106697, will be released soon