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

Selecting a tpl w/o user intervention

jaybee

can I configure templating.cfg (or by any other method) so that,
to generate an html w/o users being asked to select a particular tpl, for the the same data type, based on, from where the dcr is clicked (the location of directory inside "data" directory)
e.g.
assume the following directory structure for same datatype,
data/dir_a/a11.dcr
data/dir_b/b11.dcr
presentation/a.tpl
presentation/b.tpl

Now to generate an html page users should not be asked to select between a.tpl & b.tpl. DCR's below directory "dir_a" should by default take a.tpl & for below "dir_b" should take b.tpl.
!thanx

Find more posts tagged with

Comments

Adam Stoller

I don't believe this functionality exists at this point (I think the path specifications in the templating.cfg file only go as far as the branch). You might want to request this through Interwoven Support if nobody else can provide a more positive response.

I think many customers have gone to the point of not having users click Generate at all, but rather, drive almost the entire process through a workflow.

--fish
(Interwoven Senior Technical Consultant)

Johnny

When I have multiple templates, i usually only register one in templating.cfg and it acts as a driver. That template can simply check the location of the DCR or what ever you need to do and then call the appropriate template to process it.

John Cuiuli

ela

Hi John,
since you're so kind to mention this solution, could you be even kinder by providing some code example? There are some similar questions in other threads, but I haven't yet seen enough details to make it work for me.

Cheers,
Eldbjørg

Johnny

The following template checks to see if the user has clicked the preview button and uses a different templating if it does.

John Cuiuli

Migrateduser

!Thanx evrybody for the feedback

ela

Hi again,
I haven't implemented this solution on production yet, because it had a low priority. But - now it's important!

I've got your code working fine. If I click 'Preview' from the DCR, I get the correct preview. If I deploy via workflow, the correct presentation tpl is used for generating the html file.

However, for every content file I need to generate a separate metadata file as well. Until now I've done this by calling a separate presentation tpl (meta.tpl) from the deployment script, using iwgen.

Do you have any suggestions on how to solve this?

Many thanks!
ela

Johnny

You would call the template from within main template.


<iw_ostream file = "${ variable }/${filename}" >
      <iw_include pt="index.tpl" mode="ptlocal">
            <![CDATA[
                    $iw_param{ 'dcrMasterList' } = \@dcrMasterList;
            ]]>
      </iw_include>
</iw_ostream>

is that what you are looking for?

John Cuiuli

ela

Hi, and thanks a lot for your quick reply!

I found a solution by using the iwpt_compile command for the meta pt!:-)

The problem was that I had to create a separate meta.html file and not as part of the main file. So, I ended up with this solution:

In the templating.cfg I have only one pt, and in that pt I use the code you've posted before, which checks whether the preview or generate was chosen, and includes the correct pt based on the choice.

The meta pt is in the same directory, but is neither included in the 'main' pt nor registered in templating.cfg. I simply changed the command in the deployment script from iwgen to iwpt_compile:

old:
system("$ext_iwgen -t $workarea/$pt -r $workarea/$dcrloc/$dcrname $workarea/$tmp/$dcrname$c_htmlext$c_metaext");

new:
system("/app/teamsite/iw-home/bin/iwpt_compile.ipl -pt $workarea/$pt -iw_pt-dcr $workarea/$dcrloc/$dcrname -iw_include-location . -ofile $workarea/$tmp/$dcrname$c_htmlext$c_metaext");

Kind regards,
Eldbjoerg

Adam Stoller

Note - if you change from using iwgen to using iwpt_compile.ipl - remember that the files generated with the latter will NOT have TeamSite Templating EA's associated with them and thus you will need to do that yourself in order to ensure that anyone who attempts to edit one of those generated pages gets redirected into editing the DCR rather than the generated output from the DCR.

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

ela

Hello fish, and thanks for the reminder!
In this case it's not a problem, because all the user defined metadata is in the dcr. The separately created meta.html won't be edited by the users.

Greetings,
Ela