Nested Templates not inheriting controls

Ok I have a Masterpage named Root, and a Nestedmasterpage off of that named Homepage.

Now in the Template designer of Root I defined a footer...

The footer is visible inside that template and pages based on that template

However pages based off of the Homepage nested master dont see the GC widget content...

I'd rather not have to hardcode the footer into the .master if possible...

Hello Steve,

If you a have master page, in your case - Root and another nested master page - Homepage, and you add some widgets in the template designer of Root  it is a normal behavior that they don't appear in the template designer for the Homepage. So my suggestion, if you don't want to hardcore this footer in the master file, is to do the following:

1. Create a template using a master page
2. Create a custom template based on the first template (see attached picture)

In this case , if you add a widget in the 'parent' template , it will be inherited in the 'custom child', but it will not be inherited in the 'child' which uses a nested master page of the parent master page.

This will be fixed though right?...

I mean the layout controls are nice, but I have a more complex homepage which would require me to break out bits into usercontrols to then put them BACK into the page...and that's just annoying when they could live in a static Nestedmaster

Hello Steve,

I not quiet sure about how you are going to implement this. Are you going to have nested physical pages or you are going to work with the UI. I prepared a short video where I created three pages

Root
Nested1 - inherits from Root
Nested2 -inherits from Nested1

In the Root I added one ContentBlock control with content - "test". I can see the content "test" in all templates that inherit from Root. For me this behavior looks normal.  Can you provide some more description about your scenario ( just a simple wireframe/schema, short video) that will help us to understand your case, so we could see if we can come up with a solution.

Kind regards,
Ivan Dimitrov
the Telerik team

Well you know what, I just did it through the UI nesting for now...

I wanted to avoid the extra layout markup in the masters, but now that I think about it, the flexability and versioning (are templates versioned?...now that I think about it) far outweigh the ability to customize by hand.

But Yeah, I had a root masterpage, added that into the templates backend.  Then in VS I added a new NESTED masterpage and choose root as the one to derive from.  Then in the SF backend I added that new nested masterpage (the physical file)

...then I added a content block widget to ROOT, but it wasn't coming through on the children.

So you're creating your nested in the UI based off a physical file, whereas mine were physical based on physical (but again, scrapped that)

Hi Steve,

It would be better if you use the way I show you if this us possible for you scenario.

1. You can edit the templates from the UI instead of Visual Studio
2. It is not necessary to hardcode some controls
3. There is history of the templates.

Greetings,
Ivan Dimitrov
the Telerik team

Hi Steve,

Edit:
History of templates is not supported. I used an old version.

Best wishes,
Ivan Dimitrov
the Telerik team