Issue Bug Closed

#81758Fluid paths chain depends on order within the PAGE-object

Julian Hofmann 06/30/17, 13:35 updated 10/02/18, 10:58

Description

Changing the paths chain of templates for a plugin inserted via TypoScript has strange behaviour:
which chain configuration is active, depends on the order in the PAGE-object.

*Example with EXT:indexed_seach:*
We insert the plugin as normal content element and we’d like to insert a small searchbox via TS using other templates:

page = PAGE
page.5 = USER
page.5 {
  userFunc = TYPO3\CMS\Extbase\Core\Bootstrap->run
  vendorName = TYPO3\CMS
  extensionName = IndexedSearch
  pluginName = Pi2
  switchableControllerActions {
    Search {
      1 = form
      2 = search
    }
  }

  view =< plugin.tx_indexedsearch.view
  view.templateRootPaths.20 = myTemplatePath/Special/Templates/
  settings =< plugin.tx_indexedsearch.settings
}
page.20 < styles.content.get

+Result:+
Both plugins will be rendered using the templates from the TS object (“myTemplatePath/Special/Templates/”).

*Example 2:*
Just change the order:

page = PAGE
# Now the content first
page.1 < styles.content.get
page.5 = USER
page.5 {
   #...
}

+Result:+
Both plugins will be rendered using the templates from the global plugin configuration.

Reviews 0

No change resolves or names this issue in its commit message, and no comment links one.