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; } } }

Calling a PT from other section

Nikhil

Hi ,

We have the following structure ...

templatedata/PressPack/PressReleases/
data/
datacapture.cfg
presentation/
a.tpl
b.tpl
c.tpl
and

templatedata/PressPack/Spotlight/
data/
datacapture.cfg
presentation/
a.tpl

I want to generate a page using DCRs from these two section with a single template called "a.tpl"
The two templates under both these sections needs to be same.

My question is ...Can we refer to the same template a.tpl of PressReleases section.
How can i call a template which is residing in some other section?
Here ,from "Spotlight" section I want to call a templete named "a.tpl" residing in "PressReleases" section .

Please suggest if theres a way to have only one template.

Thanks.

Find more posts tagged with

Comments

Adam Stoller

The TeamSite / Templating GUI options for Generate (iwgen) and Regenerate (iwregen) won't allow you to do this.

The script iwpt_compile.ipl allows you much greater flexibility in this regard (look in http://localhost/iw/help/tst/pt for more information on iwpt_compile.ipl - the side effect is that you will have to use this same command to regenerate the pages if any of the component pieces change (DCR/PT) and the resultant file will not (without additional coding) have any TeamSite Extended Attributes on it to indicate that it was generated from any DCRs or PTs.

--fish
(Interwoven Senior Technical Consultant)

Migrateduser

If you're going to generate output from the command line using iwpt_compile.ipl, you can have .tpls anywhere--iwpt_compile.ipl doesn't care.

If you're going to use the TST GUI to generate, then you need a seperate .tpl in each location, BUT: you can use the <iw_include> tag to include common content. Your two a.tpl's can be just empty shells, containing only <iw_include pt='path_to_the_real_pt_file' /> as their only content. The real PT can then be located anywhere.

bw

Bob Walden [bob.walden@interwoven.com]
Interwoven Education Group
IM: Yahoo, MSN bob_walden

Eric_Knutson.JPG