Subpage configuration is used instead of Page configuration with fluidpages 3.6.0

[kitzberger]

We've got a similar situation like in #239 but with inheritance of variables instead of fields.

Here's our templates. I stripped the parts that I thought were irrelevant.

Template of current page:

    <f:section name="Configuration">
        <flux:form id="topicpage">
            <flux:grid>
                <flux:grid.row>
                    <flux:grid.column colPos="0" name="colPos0">
                        <flux:form.variable name="deniedContentTypes" value="teaser_item, slider_item" />
                        <flux:form.variable name="Fluidcontent" value="{deniedContentTypes: 'Vendor.extension_name:SliderContainer.html'}" />
                    </flux:grid.column>
                </flux:grid.row>

Template of all subpages:

    <f:section name="Configuration">
        <flux:form id="contentpage">
            <flux:grid>
                <flux:grid.row>
                    <flux:grid.column colPos="0" name="colPos0">
                        <flux:form.variable name="deniedContentTypes" value="teaser_item, slider_item" />
                        <flux:form.variable name="Fluidcontent" value="{deniedContentTypes: 'Vendor.extension_name:TeaserContainer.html, Vendor.extension_name:SliderContainer.html'}" />
                    </flux:grid.column>
                </flux:grid.row>

On the current page it is not possible to choose the "TeaserContainer" type from the content element wizard since it's not listed there at all. It's possible though to just create any other type and then alter the type to "TeaserContainer" since all types are listed in the "tx_fed_fcefile" dropdown when editing a content element, regardless of any deniedContentTypes statements in any of the used templates.

[kitzberger]

Any progress/feedback on this one?

[kitzberger]

@NamelessCoder : I debugged this one once again and am now convinced that there isn't any bug regarding fetching the wrong template. I was misled by the fact that my current pages parent and child page had the same tx_fed_page_controller_action.

Nonetheless the issue itself remains. Only the description changed. Am I correct that there's currently no way of stopping the inheritance of variables? I think there should be one, just like it's possible to stop the inheritance of fields. Right?