templating.cfg

[html]

[/html]
I have 2 branches under capital_com - capital1 and capital2.
with this branch path, new data-type shd be available under capital1 and capital2 both, right ?

But when I add data-type "newshape" to templating.cfg with this branch path, its available under capital1 only. When I click on new form entry under path /capital1/workarea/area1/templatedata/shapes/newshape, newshape is available as an option.
Now, when I click on new form entry under path /capital2/workarea/area1/templatedata/shapes/newshape , newshape is not available as an option.

Why is it so ? How to make sure newshape is available as an option under both capital1 and capital2 ? Does something need to be changes in templating.cfg ?

thanks.

Find more posts tagged with

Comments

nipper

do you have this path created /templatedata/whatever/newshape/... on both branches ? In the very beginning of the templating.cfg is a parameter for prune (typically set to yes).

If that is set to yes and you do a new form, then TS looks for the proper folders before it offers this template as a choice.

Adam Stoller

do you have this path created /templatedata/whatever/newshape/... on both branches ? In the very beginning of the templating.cfg is a parameter for prune (typically set to yes).

If that is set to yes and you do a new form, then TS looks for the proper folders before it offers this template as a choice.

To be more precise - it is an attribute of the outer-most element of the templating.cfg file and the name is prune-missing-files which is set to "false" by default, and typically (at least in my case) gets explicitly set to "true" so that I don't have to worry about regex's in the templating.cfg file to determine which each template type should be available.

More information can be found in the product documentation.

spayal

[html]

[/html]

This is the outermost attribute of templating.cfg file.

Whats prune in this ? I never had to modify prune brfore.

First time I am coming to know this parameter "prune".

Can you pls show with an example where this prune parameter is and how does it affect display of choices ?

thanks

ISCBorisB

[html]

[/html]

This is the outermost attribute of templating.cfg file.

Whats prune in this ? I never had to modify prune brfore.

First time I am coming to know this parameter "prune".

Can you pls show with an example where this prune parameter is and how does it affect display of choices ?

thanks

[html][/html]Default is "false" thus you do not have it set.
So, let me reiterate

do you have this path created /templatedata/whatever/newshape/... on both branches?

spayal

Thanks for explaining about prune-missing-files. So its set to default, which is false.

I dont know what do you mean by "do you have this path created on both the branches..."

If you are asking about templating.cfg file (As vpath is created here, if thats what you mean) then in my first post I have posted tye sample code. vpathis created upto capital_com. cpaital1 and capital2 are sub branches of capital_com. So I guess if vpath is created upto capital_com then whatever data type is added for capital_com branch, will be available as an option for all the workareas under capital1 and capital2 (Pls correct me if Im wrong).

If you are asking something else, pls ask more clearly (its clear enough for those who know. I am confused) may be stating file name and location.

Thanks.

Adam Stoller

Thanks for explaining about prune-missing-files. So its set to default, which is false.

I dont know what do you mean by "do you have this path created on both the branches..."

If you are asking about templating.cfg file (As vpath is created here, if thats what you mean) then in my first post I have posted tye sample code. vpathis created upto capital_com. cpaital1 and capital2 are sub branches of capital_com. So I guess if vpath is created upto capital_com then whatever data type is added for capital_com branch, will be available as an option for all the workareas under capital1 and capital2 (Pls correct me if Im wrong).

If you are asking something else, pls ask more clearly (its clear enough for those who know. I am confused) may be stating file name and location.

Thanks.

The default behavior (without prune-missing-files enabled) is that you have to explicitly tell templating.cfg, via a regex, which branch(es) should have a particular category/data-type enabled for it:

<category name="intranet">
    <locations>
      <branch vpath-regex="/default/main/(some|pattern|here)/.*" />
    </locations>
   ...

So if you have

" /> </locations> ...Then as long as you have the proper category/data-type/datacapture.cfg (and data/) setup - it doesn't matter what branch or workarea it's in - it will be available. If it isn't setup in a particular branch, it won't show up as an option.Theoretically the default (without prune-missing-files) is more efficient (from the application / processing / CPU perspective) - but it requires more maintenance and administration.The alternative requires less maintenance and administration, and thus far I've yet to see any performance problems with it.

nipper

This is very basic stuff. If you do not know it, take training.

For a form to work, it must be defined in the templating.cfg AND the appropriate folder structure must be created.
/templatedata/NAME1/NAME2/ with data and presentation folders and a file called datacapture.cfg. NAME1 and NAME2 corresponde to the category and type in the templating.cfg. If things don't match it won't work.

spayal

in templating.cfg, prune-missing-files is default i.e. false and for category vpath is set with wild card regex.
[html]

........
[/html]

With this coding, it works for the other branches but how come is it not working for this branch ? This "stocks" category is in about 10 branches.

How to get the new datatypes working for capital1 and capital2 branches ?

Thanks.

nipper

if you are not going to read the previous answers, then why will anyone post more ?

Go tell your boss that you need to get training or they should hire someone who knows how to use this tool.

spayal

Point is I have tried the options that you have suggested and its not working as yet.

Another thing , which I noticed recently is that even if I took out the data types that which were added in templating.cfg (i.e reverted back to the earlier version of templating.cfg) , still those data types appear as options when I create new form from captal1 branch.

In the vpath of data-type, vpath is marked until capital branch and capital1 and capital2 branches are sub branches of capital
[html]
............

[/html]

So how come its available in one branch and not in other ?

what can this be due to ?

lineplot.zip

spayal

May be answers to following question will help clarify my confusion.

1) [html]

[/html]

In this case data-type book will be available in moneymagazine branch.

2) [html]

[/html]
In this case , where will data-type book be available ? will it be available in media only ?

3) [html]

[/html]
Will it be available under all the branches in media now ?

4) [html]
[/html]
what if locations tag is not provided at all ? where will this data-type be available ?

pls explain.

Amit_LnT

answer to your questions..
1. data type is available under moneymagazine branch and sub branches.
2. not media only. Under all the other workareas (of sub branches too), if the proper folder structure for datacapture.cfg is followed.
3. same as above
4. if location is not specified, it will be shown in the list of data type for every available branch. I supposed, you must be having a dev box. Pls try out these things first and get yourself clear.
Also, throughout the whole thread, you did not specify that you have created the same folder structure
(content type name /data type name/data/datacapture.cfg)
for data type under each branch - capital1 and capital2.
And if created, do you get any error when you click on New form Entry ??

nirali

This is complicated.

spayal

1) [html]

[/html]

if data-type is to be made available in moneymagazine branch and all the branches under it, dont we need to use wildcard regex for it ?
"....../moneymagazine/.*" ? Or is it valid with or without wildcard regex ?

2) [html]

[/html]
Its the same confusion like wildcard regex. If data-type can be made available without using wild card regex, then why do we need to use wild card regex ?

3) [html]

[/html]
Will it be available under all the branches in media now ? If it can be done just as "...../store1/main/media" then why use wildcard regex ?

Yes, we have got uniform structure under capital1 and capital2 for all the branches.

Issue with me is some data-types added recently works fine under capital1 but does not work under capital2 and data-type is added as specified in question 1

Any ideas, why will this happen ?

Again on another server, this data-type is working fine under both the capital1 and capital2 branches.

When I click on new form entry, I dont get any error.

Thanks