Home
TeamSite
templating.cfg file branch location question
smohrle
Hi there -
We are on win 2000, teamsite 6.5.
Question:
I have a main branch, say branch1, and a sub branch under this main branch called subBranch. I want to point some templates (forms) to this sub branch in the location tag on templating.cfg.
IE: <locations>
<branch vpath-regex="subBranch" />
</locations>
Problem is, when I do this, the main branch sees all the forms as well and I only want the sub branch to see the forms. I have also tried:
<locations>
<branch vpath-regex="branch1/subBranch" />
</locations>
Any help would be appreciated.
Thanks,
Sarah Mohrle
Find more posts tagged with
Comments
ccprofessional
Although not guaranteed to work you can try the following:
For the main branch, you can specify the vpath to the workarea like this:
<locations>
<branch vpath-regex="default/main/whateverpath/to/branch1/WORKAREA/wa1" />
<branch vpath-regex="default/main/whateverpath/to/branch1/WORKAREA/wa2" />
...
</locations>
For the sub-branch like this:
<locations>
<branch vpath-regex="default/main/whateverpath/to/branch1/sub-branch" />
</locations>
Ideally the branch vpath cannot specify the workarea (ie., not supported). But I have seen situations where this has been exploited - and other situations where it caused random permission problems.
No harm in trying
let us know.
Adam Stoller
Or enable the prun-missing-files option in the templating.cfg file and don't worry about the regex at all.
--fish
Senior Consultant, Quotient Inc.
http://www.quotient-inc.com
gzevin
doesn't this supposedly affect the performance? The rationale behind the 'new' category chooser was the improved functionality and only after our yells IWOV has brought the old one back...
Greg Zevin, Ph.D. Comp. Sc.
Independent Interwoven Consultant/Architect
Sydney, AU
Adam Stoller
(BTW - it was "prune" not "prun" - sorry)
This supposedly affects performance, but I've never noticed anything significant at the customer sites where I've used it.
I guess if one has LOTS of templates defined or LOTS of templates available in some branches and not others - the performance hit might become noticable - but with about 1/2 dozen templates defined and generally 2-4 templates for any given branch - the performance hit appears to be negligable, and the ease of maintenace of the templating.cfg file more than offsets it (IMO)
--fish
Senior Consultant, Quotient Inc.
http://www.quotient-inc.com
gzevin
I do agree with you. however I am still puzzled as to why the new template choosing category was brought in in the first place...
Greg Zevin, Ph.D. Comp. Sc.
Independent Interwoven Consultant/Architect
Sydney, AU
ccprofessional
I am not sure which is more efficient: prune-missing-files attribute or specifying the regex explicitly to the workarea;
I believe prune-missing-files was brought in later after customer complaints. In TS 6.0 (i may be wrong) Templating does not recognize this attribute. Templating would just show all the templates without parsing the matching rules in templating.cfg for each workarea.
Since the original question involved 6.5, I think Ghoti's approach is cleaner.
gzevin
you are just repeating what we have just said.
As for the performance, it was IWOV Engineering/Product management who have said taht the main reason behind the new parsing functionality was the improved performance. Especially for CC STD, I believe
Greg Zevin, Ph.D. Comp. Sc.
Independent Interwoven Consultant/Architect
Sydney, AU
lotsofbars.rptdesign
preview.jpg
ccprofessional
hehe.. i think you repeated what I just repeated