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

Limiting template to a WORKAREA

vsleung

Does anyone know how to limit a template to a specific workarea? Any help will be appreciated! Thanks!

Find more posts tagged with

Comments

nipper

You have a single branch with 3 workareas, but only want the DCT to work in one of the 3 ? Can the DCRs be visible in all other workareas ?

Then you can accomplish this with permissions and submit.cfg.

Otherwise it is really bad design.

vsleung

You have a single branch with 3 workareas, but only want the DCT to work in one of the 3 ? Can the DCRs be visible in all other workareas ?

Then you can accomplish this with permissions and submit.cfg.

Otherwise it is really bad design.

Yes..I only want the template to be visible in one of the workarea. So, I should limit that with permissions and submit.cfg and not with templating.cfg?

nipper

How many branches do you have on the system ?

How many workareas do you have on the branch that you want this template visable ?

If that answer is 1 of many, then submit.cfg and permissions will make the templates visible but not editable.

If you do not want ot see anything of that template (i.e. not even see templatedata) in other workareas on the same branch, then you have a bad design

gzevin

If you do not want ot see anything of that template (i.e. not even see templatedata) in other workareas on the same branch, then you have a bad design

I will argue with you on that Smiley Wink

because there are cases when one needs to have a category/data type to be visible just from one/few workareas (e.g., navigation and other components).

Architecturally, this is still the same web site, so I would not recommend to have a sub-branch. Therefore, the option is to simply copy only relevant categories/data types to relevant workareas. And never do Get Latest on templatedata ...

BTW, this is exactly why IWOV has re-introduced that functionality by that 'prune' option in templating.cfg, after having removed it in 6.0

nipper

I will argue with you on that

the option is to simply copy only relevant categories/data types to relevant workareas. And never do Get Latest on templatedata ...

Like I said, that is a bad design. I have seen way too many installs get put in a really bad state by doing something like this.