TYPO3 Core

Can someone explain what does not work here? I tested these two configurations and they work fine:

Scenario 1¶

page.40 = FLUIDTEMPLATE
page.40 {
  templateName = Test
  layoutRootPaths {
    10 = EXT:myext/Resources/Private/Layouts
  }
  partialRootPaths {
    10 = EXT:myext/Resources/Private/Partials
  }
  templateRootPaths {
    10 = EXT:myext/Resources/Private/Templates
  }
}

Scenario 2¶

page.40 = FLUIDTEMPLATE
page.40 {
  template = FILE
  template.file = EXT:myext/Resources/Private/Templates/Test.html
  layoutRootPath = EXT:myext/Resources/Private/Layouts
  partialRootPath = EXT:myext/Resources/Private/Partials
}

Oh, wow. Did anyone of you actually read until the end? I posted nothing about any FLUIDTEMPLATE, did I? Whereas the link which I did post, leads to a page where example PHP code is shown, which is exactly what I do in my code. In PHP (not TS) I try to use this StandaloneView to render an email template. As there are base templates in a certain base folder A which may have been "overwritten" by an extension and a folder B. (because I dont actually want to "overwrite" the path, but instead provide an additional one while leaving the base path there, so not each template, partial and layout file needs to be copied into path B)

This (of course) has been configured in the TS setup of the extension, hence the TS reference in my description. Now (again): this does not work. If you take a closer look on what I wrote, there are method names and even the possible fix for this issue is described. Just take a look into the two different implementations of resolving the path names in those view classes and the penny will drop...

@Patrick Broens: I consider it not only misleading but even just bad behaviour when one view does resolve the path names correctly wheres the other one does not. Of course it is possible to let every extension author use the exact same code to solve this in their own extensions but I guess putting it in one central place (extbase) is the better solution in such a case. Do you agree?

Hi,

i created a small test extension and i don't get the point. You will see in the extension that if you set a template for the StandaloneView and you define the LayoutRootPath and the PartialRootPath everything works fine.
If you don`t do that the view expects that your partials and layouts as a subfolder of the absolute template path.

You can checkout the extension on github.

https://github.com/markusguenther/mg_standaloneview

If i am wrong and just dont understand you please tell me that ;)

@Markus Günther: Yes, I see what you did and that's what I already wrote in the comment to Patrick (I consider it not only misleading but even just bad behaviour when one view does resolve the path names correctly wheres the other one does not. Of course it is possible to let every extension author use the exact same code to solve this in their own extensions but I guess putting it in one central place (extbase) is the better solution in such a case. Do you agree?) The behavior was not really "wrong" but inconsistent and unhandy, that's what I wanted to mention here.

@Anja Leichsenring: THANK YOU!!! :-)