Embedded Razor Templates

Question

are there any limitations with embedded razor templates. The issue:

<span>Level0</span>
@importRazor("/webdav/020-D%20Design%20Master/Building%20Blocks/System/Template%20Building%20Blocks/Razor%20TBBs/Component%20Layouts/Intro/Test%20Level1.cshtml")

And child Level 1 has

<span>Level1</span>
@importRazor("/webdav/020-D%20Design%20Master/Building%20Blocks/System/Template%20Building%20Blocks/Razor%20TBBs/Component%20Layouts/Intro/Test%20Level2.cshtml")

And child Level2 has

<span>Level2</span>
@importRazor("/webdav/020-D%20Design%20Master/Building%20Blocks/System/Template%20Building%20Blocks/Razor%20TBBs/Component%20Layouts/Intro/Test%20Level3.cshtml")

And Level3 has

<span>Level3</span>

So the final output should be:

Level0
Level1
Level2
Level3

but currently, I am seeing output as Level0 only. Is this expected?

Answer 1

When a template is compiled by the razor mediator, any embedded templates are resolved and the text is embedded before compilation occurs. The resulting assembly is cached, and that's the last time the embedded templates will be looked at until the embedding template is for whatever reason compiled again.

The trick is to make a small, otherwise irrelevant change in the embedding template. For example, change the title. (I usually change it back immediately - the point is to update the timestamp of the last save.) This will ensure that the cached version is now out of date, and the whole process of resolving embedded templates will happen again.

The other way to clear the cache is to restart the publisher service. I'd usually recommend that in development, the quickest/easiest way is the first method, while in production, your best bet is to restart the publisher after the content porter import.

Answer 2

It seems to be the issue with TBB that are generating output to placed in broker DB.

If you are using DD4T TBB for publishing then there is parameter LinkLevel, which identifies how much deep it should traverse through to render the output.

The default value of LinkLevel is 1.

Looking at the output, it seems that you have not specified the LinkLevel parameter.

Given below is the syntax for adding LinkLevel parameter

<TemplateInvocation>
    <Template xlink:href="tcm:x-xxxx-2048" xmlns:xlink="http://www.w3.org/1999/xlink" xlink:title="Title" />
    <TemplateParameters>
      <Parameters xmlns="DD4T.Templates.Schemas.DynamicDeliveryParameters">
<LinkLevels>6</LinkLevels>
</Parameters>
    </TemplateParameters>
  </TemplateInvocation>

Here, I have given LinkLevel as 6 that means it will go down until 6 levels.