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

templating.cfg first timer. This is probably really easy to fix.

bettineski

Hello.

This is my first time working with the templating.cfg (our head developer left).

While I have no problem with the coding, I'm not real solid on how to get a new tempatedata area setup.

Here's the full path to the templatedata folder:

//apwcms/default/main/************/CONTENT/WORKAREA/root/templatedata/Regulatory_Affairs/Price_Summaries

[html]

[/html]

Of course I'm getting the usual error:

"Unable to create a new form of type Regulatory_Affairs/Price_Summaries under the branch //apwcms/default/main/WWW.PORTLANDGENERAL.COM/CONTENT. This form was not configured for this branch or you do not have permission to access it."

Does anyone see anything obvious in my .cfg file that I need to fix?

Thanks!

Find more posts tagged with

Comments

nipper

The catagory name should not be Content but it shoudl be Regulatory_Affairs

bettineski

In the templating.cfg I have another category called "Regulatory_Affairs" that is it's own branch.

[html]

... etc...
[/html]

Here's one of the data types inside that Category:

[html]

[/html]

Is there some way of adding my Price_Summaries as a data-type in that Category?

I've tried it, but I get the "parsing" error.

I can't tell if there's an error in my datacapture.cfg code, or if I've got templating.cfg configured wrong.

What's the best practice in this situation?

Oh, and thank you so much for the quick reply.

CRB

also keep in mind that it is case sensitive, make sure you spell the folder names correctly.

nipper

Move the new section to the Regulatory_Affairs section. Remove the branch restriction (just make it /default/main). Once you get it working you can set up a regex for all the branches you need.

bettineski

Move the new section to the Regulatory_Affairs section. Remove the branch restriction (just make it /default/main). Once you get it working you can set up a regex for all the branches you need.

Awesome. Now it looks like it's just a problem with the datacapture.cfg, which is exactly what I expected to see Smiley Happy

Thank you for the help!

Adam Stoller

Make things easier on yourself - edit the templating.cfg file so that the container element looks like this:

<templating prune-missing-files="t">

Then change all the branch vpath-regex's to look like this:

<branch vpath-regex=".*" />

This will make it so that if the DCT (and its associated data/ and presentation/ directories) are in the current workarea - they're available for usage. If they're not - they're not presented as choices.

If you happen to have two categories of the same name (with different data-types) in different branches - the above should do the right thing.

If you happen to have two categories of the same name with some overlap in data-types in different branches - as long as those data-types are defined identically (i.e.: both are of the same type ["iwov" or "xml"], the presentation template(s) are named identically, and they produce the same output file extension) - the above should do the right thing.

If you have significant differences from the above - then alter the name(s) of one or the other data-type and/or category - and the above should do the right thing.