#108126Inconsistent doktype usage/type
Description
There is an overall issue existing regarding the doktype field.
I could not find the actual commit, but the pages doktype field has been removed from ext_tables.sql as it is auto generated by the ctrl -> type TCA functionality.
This now causes the doktype field to be an VARCHAR instead of an INT like before.
One of the side effects is, that the record controller throws an exception here:
https://github.com/TYPO3/typo3/blob/main/typo3/sysext/backend/Classes/Controller/NewRecordController.php#L583
To test: run a databas update to change the doktype field to varchar and create a record via list module on a random page.
With integer as field, this error does not occur.
Another effect ist the following TypoScript condition which does not work anymore:
`traverse(page, “doktype”) in [1,2]]`
The doktype is a string now, thus the values would have to be wrapped.
Those are only 2 cases I could find
Possible solution:
1. readding the doktype field to ext_tables.sql
2. casting all points where doktype is evaulated and expected as integer (e.g. in the NewRecordController)
Reviews 0
No change resolves or names this issue in its commit message, and no comment links one.
History 4
-
Henrik Elsner changed subject
Inconsistent doktype usageInconsistent doktype usage/type <span data-processor="relativetime" data-value="2025-11-14T11:28:09+00:00" > 11/14/25, 11:28 </span> -
Garvin Hicking commented and changed category status
NewNeeds Feedback <span data-processor="relativetime" data-value="2026-01-27T12:24:21+00:00" > 01/27/26, 12:24 </span>The pages.doktype should still be created as “int”, that’s how it is for me in v13 and main/v14.
Maybe extension TCAs that enhance the doktype specify a non-integer value and caused the automatism to be set to VARCHAR. Can you check your TCA please, also of involved extensions?
-
Garvin Hicking commented and changed status
Needs FeedbackClosed <span data-processor="relativetime" data-value="2026-04-14T19:01:53+00:00" > 04/14/26, 19:01 </span>Closed due to lack of feedback
We had the same issue, but could not find any reason for it.
After changing the field type in mysql manually the problem was resolved, but the database analyser, still wanted to change it back to varchar.
But after installing the recyler extension, this too was solved.
And it remained so even after deinstalling the extension.
My guess is, that it wasn’t the recycler that solved the issue, but simply installing a new extension and therefore dumping the deepest php cache.
But i can’t confirm either because the problem couldn’t be recreated.
We are on TYPO3 v13.4.21 and this is the only installation with the same version, that has this error on our side, the older and newer ones are correctly configured with int as field type.