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

populating the branch_list from an external file

Sharty

Hi all,

just a quick question for everybody:

Is it possible to populate the <branch_list> within the available_templates.cfg from an external file?

We would like to maintain the branch_list from the TeamSite GUI and it would be nice, if we could set up a file and populate the branch_list from that file.

We are using TS 6.1 on Solaris here.

Cheers, Jens

Edited by Sharty on 08/19/04 08:16 AM (server time).

Find more posts tagged with

Comments

Dwayne

I don't believe that there's a supported way to do this. There's nothing in the DTD about an external source, anyway.

If you don't care about the supported part, then you could edit available_templates.ipl which is a Perl fragment used to parse available_templates.cfg and build a list of possible WFT choices. You could edit that file to provide whatever functionality you like.

Before the days of available_templates.cfg (which I think came into being with TS 5.0) that was the official method for adding WFT support to TeamSite. The available_templates.cfg method is less flexible, but a lot safer.

--

Current project: TS 5.5.2/6.1 W2K

Adam Stoller

It's not possible to do this with respect to the actual setup - but you could *generate* the available_templates.cfg file and in that respect you could do what you want.

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

Edited by ghoti on 08/19/04 08:24 AM (server time).

Sharty

thanks for the quick answers.

I was already looking at the available_templates.ipl, but because this is unsupported, we won't do that in this installation.

we will go ahead and maintain the complete available_templates.cfg in a config workarea together with all the opther config files to be able to build a history.

Cheers, Jens

Dwayne

I usually create one or more branches to manage these sorts of files, and then set up an OpenDeploy config file to move them into their "real" location.

Just make sure you don't have "Do Deletes" turned on.

My normal practice is to set this up on a "DEV" box, and then have two sets of deployments. One deploys from STAGING to the live location on the DEV box. Once everything is tested, I deploy to the production box - sometimes to an equivalent workarea on that Production box, sometimes directly to the live location on the production box, depending on my customer's requirements.

--

Current project: TS 5.5.2/6.1 W2K