-
Notifications
You must be signed in to change notification settings - Fork 23
New issue
Have a question about this project? # for a free GitHub account to open an issue and contact its maintainers and the community.
By clicking “#”, you agree to our terms of service and privacy statement. We’ll occasionally send you account related emails.
Already on GitHub? # to your account
Using palettes in TCA with select inside is not working #332
Comments
@PLACEBOBRO This won't work this way. First: A Basic is not a Palette. This means if the Basic is not in use, it won't generate any TCA at all. Second: You can't go "one level down" with Content Blocks. Everything defined in Content Blocks should only be used in there. If you need low level TCA, you have to define the fields and palettes in pure TCA and re-define it in Content Blocks. My tip: Define your Container as a Content Block and simply use your Basic with the Palette like normal. See guide here: b13/container#546 (comment) |
Thank you for your fast answer. Then I missunderstood how some things work haha. |
I have to reopen the issue.
The palette_header configuration is the same as above |
Please come to Slack if you need support. GitHub is not the right place. |
I encountered an issue with basics and "normal" TCA.
I created a palette in the Basics folder with the following configuration:
Here my TCA:
if I use the palette in a normal content block element, there is no issue.
However, if I want to add the palette via normal TCA to a content element which isn't created with content blocks (in this case to a container) this is not working. I get the following error because of the select inside the Basic:
All other fields are rendered correctly (e.g. Text)
I also found out, that using e.g. a checkbox with renderType: checkboxToggle, a normal checkbox is rendered, due to the fact, that maybe checkbox has a default renderType set and select doesn't?
TYPO3 13.4.2
content-blocks v. 1.1.4
PHP 8.3
The text was updated successfully, but these errors were encountered: