Site structure
Version 6.x > Site structure > Scope of DocType View modes: 
User avatar
Member
Member
Snarrak - 1/9/2012 2:50:04 AM
   
Scope of DocType
Hi everyone,

One of the tabs of a Page Template is the 'Scope'-tab. I can select in which part of my website the template is showed.

Is this also possible for a DocType?
And maybe even possible to allow it only beneath a specific template?

Regards,
Jorik

User avatar
Kentico Consulting
Kentico Consulting
kentico_borisp - 1/9/2012 3:45:40 AM
   
RE:Scope of DocType
Hello,

The document types are global objects, not site specific. That's why they don't have any site specific settings and I don't have any information on implementing this feature in the future. So no, the document types don't have a scope defined by default. The only restriction for document types is to allow them to be placed under a specific document type. So for example, you can create a custom "container" document type and allow some other "child" document type to be placed only under this "container" document type. Now, you can manage, where your "child" document can be placed by creating the "container" document type only in the desired sub tree. So the restrictions are document type based, not template based. The children and parents of a document type can be managed in SiteManager / Development / Document types / <your doc type> / Child types.

Best regards,
Boris Pocatko

User avatar
Member
Member
Snarrak - 1/9/2012 4:10:22 AM
   
RE:Scope of DocType
Hi Boris,

I know about the parent- and childtype properties, but in this case there all Pages (menu-items).
Too bad... but wasn't that important, just some ease.

Thanks anyway.
Regards,
Jorik

User avatar
Kentico Consulting
Kentico Consulting
kentico_borisp - 1/9/2012 5:30:45 AM
   
RE:Scope of DocType
Hello,

You can also implement this custom functionality by yourself. For example, creating a custom field to the template item and save there the scopes to the given template. You would need to change the UI a bit, so these settings are reflected. A more convenient approach would be to create a new requirement on our Uservoice page and maybe it gets implemented in one of the upcoming versions.

Best regards,
Boris Pocatko