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

Question on templating.cfg tags

sowju

Hi All,

I have a doubt on templating.cfg

Do we have any tag for validating generated filename from templating.cfg same as directory regex tag for template as below :

template name="*.tpl" extension="html" fullpage="t"
locations
branch vpath-regex=".*" preview-dir="/"
directory dir-regex="http/[^/]+" /
/branch
/locations
/template

Please let me know how to implement regex to validate generated filename from templating.cfg file

Find more posts tagged with

Comments

curiousmaverick

I don't think that is possible. But still, you may check the corresponding DTD.

Adam Stoller

Hi All,

I have a doubt on templating.cfg

Do we have any tag for validating generated filename from templating.cfg same as directory regex tag for template as below :

template name="*.tpl" extension="html" fullpage="t"
locations
branch vpath-regex=".*" preview-dir="/"
directory dir-regex="http/[^/]+" /
/branch
/locations
/template

Please let me know how to implement regex to validate generated filename from templating.cfg file

Nope - you need to take care of that either within FormAPI or a wrapper process performed by a workflow.

Also - despite what a lot of people think the first time they look at it, the templating.cfg file will not initialize the location for saving the DCR to a specified path - it will just case FormsPublisher to complain if your entered path/name does not conform to the regex supplied (I prefer to use FormAPI and information contained in one or more fields within the DCT to programatically name the DCR)