allowedRecordTypes is not overwriting allowedContentTypes

[Denneee]

Describe the bug
I have a backend layout that restricts content using the new setting allowedContentTypes.
I’m trying to create a nested content element (an accordion), but when I save it, I get an error saying that the CType is not allowed. I seam to not be able to overwrite the backend layout setting allowedContentTypes with allowedRecordTypes.

To Reproduce
Steps to reproduce the behavior:

1. Create a backend layout and a page that is using this backend layout

mod.web_layout.BackendLayouts.default {
  title = Default
  config {
    backend_layout {
      colCount = 1
      rowCount = 1
      rows {
        0 {
          columns {
            1 {
              name = Main
              colPos = 0
              identifier = main
              allowedContentTypes := addToList(fv_accordion)
              allowedContentTypes := addToList(div)
              allowedContentTypes := addToList(shortcut)
            }
          }
        }
      }
    }
  }
}

2. Create the Content Element

Config.yaml

name: fv/accordion
typeName: fv_accordion
group: fv
prefixFields: true
prefixType: vendor
vendorPrefix: tx_basis
fields:
  - identifier: accordion_item
    type: Collection
    minitems: 1
    fields:
      - identifier: headline
        type: Text
        required: true
      - identifier: content
        type: Collection
        foreign_sortby: sorting
        foreign_table: tt_content
        shareAcrossFields: true
        shareAcrossTables: true
        allowedRecordTypes:
          - text
          - div

backend-preview.html

<f:layout name="Preview"/>
<f:section name="Header">
</f:section>

<f:section name="Content">
    <f:for each="{data.accordion_item}" as="item">
            <h3>{item.headline}</h3>
            <f:render partial="PageLayout/Grid" arguments="{data: item, identifier: 'content'}"/>
        </f:for>
</f:section>

3. Got to the created page and insert the content element
4. Try to create a content from type text
5. Save the Content Element
6. See Error: This action could not be completed; please contact your administrator. Technical details: 1: The record "tt_content:174" with CType "text" in colPos "0" couldn't be saved due to disallowed value(s).
7. When I delete the allowedContentTypes in the backend layout or change the colPos to something different then 0, everything is working as expected.

Expected behavior
I can save the content and see the related content element in the backend preview. The setting allowedRecordTypes is overwriting the setting allowedContentTypes for this element correctly.

TYPO3 Version
v14.2
also in v13.4 with content_defender extension/syntax

Content Blocks Version:
2.2

[nhovratov]

We probably need to use the ManipulateBackendLayoutColPosConfigurationForPageEvent for this.

[nhovratov]

Released in 2.4.1

[Denneee]

Thank you @nhovratov
I can save the element now and i can see only my allowed Records. But sadly the backend preview is still showing that the elements are not allowed

[nhovratov]

Could you share a screenshot?

[Denneee]

I take back my previous statement: unfortunately, saving still doesn't work. I had another function included that modified the colPos value to 999 (my current workaround). With that function in place, saving at least worked.

The code is the same as I initially provided, in case there's an issue on my side that I overlooked.

[nhovratov]

@Denneee Okay, I see. I only implemented 1 level, but as you have a 2 levels deep Collection, it didn't work for you. I will try now a recursive approach. This will need a check for infinite loop as well.

[Denneee]

Thanks alot!

[nhovratov]

@Denneee Please try version 2.4.3. It should do the trick!

[Denneee]

Good morning @nhovratov
I tried it now with 1 level and 2 level deep Collections. Both are not working on me and on save I get still the same error:

"the record "tt_content:NEW6a1d3aaae29a7114972379" with CType "text" in colPos "0" couldn't be saved due to disallowed value(s)."

I tried to use different colPos Values, that will allow me to save it, because there i dont use the "allowedContentTypes"-Restrictions, but in the Backend Preview i will still get the error that the element is not allowed in this column.

My only current fix is to change my BackendLayout to use the colPos 1 instead of 0.
Maybe its just the new EventListener in TYPO3 that is not working 100% correctly.

[nhovratov]

@Denneee Ah, it could be because you are referring to Core Content Elements "text" and "div" instead of real Content Block Elements. I'll check again, whether it's possible to make them work, too.