nav[aria-label="Primary Navigation"] { padding: 0; & ul { list-style: none; width: 100%; display: flex; flex-direction: row; justify-content: start; align-items: start; gap: 30px; padding: 0; & li { margin: 0; } & ul li { list-style: none; } } }

TS6.1: Standard Interface

System

Hello,

We have many branches using the same category name and I don't succeed in configuring templating.cfg to show only the relivant workareas & templates in the CC Standard interface.

Imagine there are the two following branches, they both have 3 templates (template3 is there in the two branches) and they both use a category called "cat". Also branch11 is a child of branch1 in the directory tree :

/default/main/branch1/WORKAREA/work/templatedata/cat/template1
/default/main/branch1/WORKAREA/work/templatedata/cat/template2
/default/main/branch1/WORKAREA/work/templatedata/cat/template3

/default/main/branch1/branch11/WORKAREA/work/templatedata/cat/template3
/default/main/branch1/branch11/WORKAREA/work/templatedata/cat/template4
/default/main/branch1/branch11/WORKAREA/work/templatedata/cat/template5

Now how should templating.cfg be configured to show only the good workareas & templates in the Standard Interface ???
At the moment I have made this very basic configuration which of course doesn't work fine :

<templating>
<category name="cat">
<locations>
<branch vpath-regex="/default/main/branch1" />
<branch vpath-regex="/default/main/branch1/branch11" />
</locations>
<data-type name="template1" dcr-type="iwov"></data-type>
<data-type name="template2" dcr-type="iwov"></data-type>
<data-type name="template3" dcr-type="iwov"></data-type>
<data-type name="template4" dcr-type="iwov"></data-type>
<data-type name="template5" dcr-type="iwov"></data-type>
</category>
</templating>

Anyone can help ?

Find more posts tagged with

Comments

lidkh

Hi Pierre-Yves,

You should try the following:

<templating>
<category name="cat">
<locations>
<branch vpath-regex="branch1/.*"/>
</locations>
<data-type name="template1" dcr-type="iwov">
<presentation>
<template name="template1.tpl" extension="html">
<locations>
<branch vpath-regex="branch1" preview-dir="/">
<directory dir-regex=".*"/>
</branch>
</locations>
</template>
</presentation>
</data-type>
<data-type name="template2" dcr-type="iwov">
<presentation>
<template name="template2.tpl" extension="html">
<locations>
<branch vpath-regex="branch1" preview-dir="/">
<directory dir-regex=".*"/>
</branch>
</locations>
</template>
</presentation>
</data-type>
<data-type name="template3" dcr-type="iwov">
<presentation>
<template name="template2.tpl" extension="html">
<locations>
<branch vpath-regex="branch1/.*" preview-dir="/">
<directory dir-regex=".*"/>
</branch>
</locations>
</template>
</presentation>
</data-type>
<data-type name="template4" dcr-type="iwov">
<presentation>
<template name="template4.tpl" extension="html">
<locations>
<branch vpath-regex="branch1/branch11" preview-dir="/">
<directory dir-regex=".*"/>
</branch>
</locations>
</template>
</presentation>
</data-type>
....
</category>

Cheers,
Khalid

Adam Stoller

... or alternatively (if you have SP1 installed) change the beginning of your templating.cfg file to look like this:<templating prune-missing-files="t">This will allow you to avoid having to put all those regex's in your templating.cfg as it will essentially restore the pre-6.0 behavior of templating (I believe it looks for the templatedata/category/data-type directory rather than the templatedata/category/data-type/datacapture.cfg file - which I believe is being fixed in the next SP[?])

Interwoven's claim is that the lack of checking the file system was a performance improvement - but I think that unless you have a LOT of templates defined for any given branch, the hit for checking the file system is pretty minimal and it makes the templating.cfg file a lot easier to maintain.

--fish
Senior Consultant, Quotient Inc.
http://www.quotient-inc.com

Migrateduser

Are you sure that syntax is correct? I'm running 6.1SP1 and when I make that change to templating.cfg it fails to parse the file (which seems pretty weird anyway - one would expect it would just ignore extra attributes).

Adam Stoller

TS 6.1 SP1 Release notes (ts.610.sp1.rn.pdf) page 16.

It worked for my current customer. Are you sure you installed SP1? Are you sure you typed it correctly? You *might* have to do a simple 'iwreset' (no flags)?

--fish
Senior Consultant, Quotient Inc.
http://www.quotient-inc.com