TYPO3 Core

I tested in Typo3 8.7.6. I can't override the template paths like Christoph. In Version 8.7.4 / 8.7.5 it works as expected.

We seem to have this too in 8.7.6

Unfortunately not fixed in 8.7.7

I can also confirm the issue described by Christian from 8.7.6 to 8.7.8.

This is still an issue in 8.7.9, afaik caused by
https://github.com/TYPO3/TYPO3.CMS/commit/cdd6dca4c9dbc0a5563f8beb68aed2dde2d061cf#diff-e29c9d272acd4119f0a7f907625256c7

I have the same problem . I'm use typo3 version 8.7.18 .

Example . I have news extension and next for example I create new extension where I extend news for example so_my_news . And now we have setup for Layout, Template like here

10 => EXT: so_my_news/Resources/Private/Layouts

100 =>EXT:news/Resources/Private/Layouts/

and now you have

1 => string '/var/www/html/web/typo3conf/ext/news/Resources/Private/Layouts/'

2 => string '/var/www/html/web/typo3conf/ext/so_my_news/Resources/Private/Layouts/'

how you see the order is not the same . You can check this : typo3/cms/typo3/sysext/fluid/Classes/View/TemplatePaths function setLayoutRootPaths

Affects also 9.3. Problem still existing there.

We just experiences a similar problem in TYPO3 version 9.5.8:

Our extension was named like „our_extension“. So we did the typoscript setup inside the extension like

plugin.tx_our_extension {
    view {
        partialRootPaths {
            0 = EXT: our_extension/Resources/Private/Partials/
            1 = {$plugin.tx_our_extension.view.partialRootPath}
        }
    }
}

and tried to overwrite it in another extension like

plugin.tx_our_extension {
    view {
        partialRootPaths {
            10 = EXT: another_extension/Resources/Private/Partials/
        }
    }
}

It didn’t work until we changed „plugin.tx_our_extension“ to „plugin.tx_ourextension“. Just without the underscore:

plugin.tx_ourextension {
    view {
        partialRootPaths {
            10 = EXT: another_extension/Resources/Private/Partials/
        }
    }
}

Is this somehow related? #87737

Hi,
I think I'm facing a similiar issue. I can't override template/partial/layout root paths if I have following setup:
I include typoscript of a extern extension - let's call it extern_extension - via static template. It has defined partialRootPaths like this:

plugin.tx_externextension {
    view {
        partialRootPaths {
            0 = EXT: our_extension/Resources/Private/Partials/
            1 = {$plugin.tx_externextension.view.partialRootPath}
        }
    }
}

I also include my own typoscript template from my sitepackage via static template. In the sitepackage I try to set the constant plugin.tx_externextension.view.partialRootPath in the constants in my sitepackage. But: I don't do it in Configuration/TypoScript/constants.typoscript directly, but in an extra file which is included in my constants.typoscript via @import / <INCLUDE_TYPOSCRIPT>.

With this setup, I can see my added partialRootPaths in the backend in the typoscript object browser, but in FE they are not taken into account. Same problem if I don't use the constant, but do it in setup (but also in an extra file which gets included from my setup.typoscript).

Solution for me was to either, put my overrides directly in setup.typoscript or constants.typoscript OR to not import the typoscript settings from the extern extension via static template, but use @import in the same file I do the overrides. Both solutions aren't really good in my opinion.

This sounds related too: https://forge.typo3.org/issues/93544
And this one: https://forge.typo3.org/issues/95588

I'm having trouble ordering the root paths too. Running TYPO3 10.4 with PHP 7.4 .

Inside of my controller action I'm debugging "$this->resolveView()" and looking for:
baseRenderingContext -> templatePaths -> partialRootPaths

I have configured three items but only two are shown there. It seems like douplicate parths are removed But lets look at the resulting array:

$partialRootPaths = [
  0 = '/var/www/.../typo3conf/ext/foo/Resources/Private/Partials/'
  2 = '/var/www/.../typo3conf/ext/bar/Resources/Private/Extensions/Foo/Partials/'
]

If I look at the TypoScript object browser, it shows me the desired/configured paths and order (see below).
Also if I remove all elements except the one from EXT:bar, the path for EXT:foo is still present and I'm unable to get the array completely empty.

plugin.tx_foo {
  view {
    partialRootPaths {
      0 = {$plugin.tx_foo.view.partialRootPath}
      1 = EXT:bar/Resources/Private/Extensions/Foo/Partials/
      2 = EXT:foo/Resources/Private/Partials/
    }
  }
}

fooPage = PAGE
fooPage {
  typeNum = 1642686437
  10 = USER_INT
  10 {
    userFunc = TYPO3\CMS\Extbase\Core\Bootstrap->run
    extensionName = Foo
    pluginName = Foo
    vendorName = RANDOHG
  }
}

This is still applicable to 10.4, 11.5, and presumably 12.5 as well.

The rabbit-hole goes deep.

1. Back in 2015, somebody introduces a method sanitizePath to the class TemplatePaths, see here https://github.com/TYPO3/Fluid/commit/fbf343bb25739e2151d8b100be27eb44a36841bc
   The change is supposed to ensure that paths are absolute and can be concatenated with File-Paths easily (by having a trailing slash).
   BUT, the commit also adds a call to array_unique, which means that each path can only be contained once in the resulting array.
2. During initialization of the Extbase MVC view, the following code is executed:
   1. setViewConfiguration, which correctly sets the array from the TypoScript view settings
      https://github.com/TYPO3/typo3/blob/08c6c69db86497572e639df5bd0c7b7079c63c31/typo3/sysext/extbase/Classes/Mvc/Controller/ActionController.php#L541
      This calls the setXRootPaths methods, which sanitize (unique-ify) the arrays.
   2. Directly after that, TemplatePaths::fillDefaultsByPackageName is called as well
      https://github.com/TYPO3/typo3/blob/08c6c69db86497572e639df5bd0c7b7079c63c31/typo3/sysext/extbase/Classes/Mvc/Controller/ActionController.php#L527-L529
   3. This calls TemplatePaths::getContextSpecificViewConfiguration, and here is where the trouble starts
      https://github.com/TYPO3/typo3/blob/08c6c69db86497572e639df5bd0c7b7079c63c31/typo3/sysext/fluid/Classes/View/TemplatePaths.php#L64-L108
      That function sets the extension resource paths with index 0 as the "default" base paths.
      If the paths were already configured, which they already were, the base paths and the configured paths are merged. So far, so good.
      Except, this merged array is then passed to setXRootPaths again. Which removes any duplicate paths.
3. Effectively, if you configured the extension path with your TypoScript at any other index but 0, it will get moved to index 0.
4. Even if you left the extension paths out of the TS config, the paths will get added at index 0.

EDIT:

The workaround to have an extension which has another extension's resource paths as the fallback is to re-order the template paths in your controller action or initializeView method "by hand".
That is obviously dumb and this should work out of the box with just TypoScript.

I have made a reproduction for 10.4.37, 11.5.30, and 12.4.5, which are currently available via public composer (not ELTS):
https://github.com/fwg/typo3-bugs/tree/forge/81099

The bit that should work but doesn't is here: https://github.com/fwg/typo3-bugs/blob/forge/81099/src/bugs_ext/ext_localconf.php#L24-L29

@Simon Praetorius the patch for typo3fluid/fluid does fix the issue – I think it's better though if the core is fixed.
(The patch does not cleanly apply via composer-patches but it still works.)

This is a patch for typo3/cms-fluid that also fixes the issue:
https://github.com/fwg/typo3/commit/3717ca7bcdfc1e293258827b6705878f20185638

Now to make it a core contribution...

Patch set 2 for branch main of project Packages/TYPO3.CMS has been pushed to the review server.
It is available at https://review.typo3.org/c/Packages/TYPO3.CMS/+/80658

Patch set 3 for branch main of project Packages/TYPO3.CMS has been pushed to the review server.
It is available at https://review.typo3.org/c/Packages/TYPO3.CMS/+/80658

Patch set 1 for branch 12.4 of project Packages/TYPO3.CMS has been pushed to the review server.
It is available at https://review.typo3.org/c/Packages/TYPO3.CMS/+/80834

Patch set 1 for branch 11.5 of project Packages/TYPO3.CMS has been pushed to the review server.
It is available at https://review.typo3.org/c/Packages/TYPO3.CMS/+/80835