looking for on configuration setting in templating.cfg

Can any body help me on this issue?

We have two presentation template in presentation folder and also mapped in templating .cfg , these two teamplates are used for two different purpose one for only preview and another for only generation of output page .
Can it is possible that when user click on preview button he should not get choices for selecting presentation template? I mean to say no option should come for user for selecting presenation template.I want to do this from GUI of teamsite

And i am looking for any configuration or setting in configuration file for this.

Find more posts tagged with

Comments

kaalraa

Can any body help me on this issue?

We have two presentation template in presentation folder and also mapped in templating .cfg , these two teamplates are used for two different purpose one for only preview and another for only generation of output page .
Can it is possible that when user click on preview button he should not get choices for selecting presentation template? I mean to say no option should come for user for selecting presenation template.I want to do this from GUI of teamsite

And i am looking for any configuration or setting in configuration file for this.

Not possible to work from TS GUI. However can work with your own custom scripts by capturing the button; preview or generate.

Also just curious to know the concept as why you need two presentations; one for preview and other for generate??

Frederik

What we have implemented in this case, is one TPL. As first thing, it detects whether it's called via PREVIEW or GENERATE.

    # Distinguish generate / prewiew, cfr http://devnet.interwoven.com/site.fcgi/techlib/002411
    my $is_preview = (iwpt_get_flag_param('-oprefix') ne '');

Then, depending on that, it does different things...

If you wish to seperate logic from content processing, you can have the actual presentation transformation in a 2nd (preview.tpl) and 3rd TPL (generate.tpl) that aren't configured in templating.cfg. You can run them from the 1st TPL with iw_include

[HTML][/HTML]

jiten

Thanks Kaalraa

we need two presentation template because for preview we want to see our content the way it should appear on web means complete look and feel of page With some static content like header footer ,navigation

second one for generatig that specific part of page that we want to manage
means we are including this generated page in particuler html page

that's why we do not want to give option to user to select presentation tpl
because if he will select generated tpl he can see only a part of page in preview

Adam Stoller

Thanks Kaalraa

we need two presentation template because for preview we want to see our content the way it should appear on web means complete look and feel of page With some static content like header footer ,navigation

second one for generatig that specific part of page that we want to manage
means we are including this generated page in particuler html page

that's why we do not want to give option to user to select presentation tpl
because if he will select generated tpl he can see only a part of page in preview

As Frederik indicated - it might be better if you configure one PT and have it use conditional logic witin the PT to do what you want - either completely internally to that PT or by inclusion of one or another "component" PT. If you write your PTs in perl - it becomes fairly simple to write the header and footer bits as subroutines that only get called if the user is performing a Preview operation.