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

cool_rash

Hi

In our project templating.cfg has grown beyond estimation. As I understand it effects the performance in a big way. I remember reading in forum some ways suggested by members to solve it, and now I am not able to get the posts. So let me know the following

1. If templating.cfg grows how it effects the performance.
2. The ways to solve the same. Can we split templating.cfg

Thanks

Find more posts tagged with

Comments

romil_rose

Yes, you can split the templating.cfg. Take a look at KB Article: 58163 on support site.

Screenshot at 2013-10-23 10:47:33.png

ISCBorisB

Yes, you can split the templating.cfg. Take a look at KB Article: 58163 on support site.

Please note that there may be a serious problem with the XML Entities Method described in this Article, for the
TS 6.5.x anyway. Note also that I never tried that in 6.7, perhaps it has been resolved

All DCR - related functions seem fine (New Form, Editing, FormAPI etc). However, traditional presentation
template generation fails in both GUI and iwgen modes with the following Error Message: "Preview And Generate
Error: Not a valid extension. Valid extension for xyz.tpl is:". Legacy Case #00731765, IWOV confirmed a defect,
I'm not aware of any resolution though

romil_rose

Hi Boris,
As per KB Article 62866, they have fix it in 6.7.2. But I myself have never tried it though.

ISCBorisB

Hi Boris,
As per KB Article 62866, they have fix it in 6.7.2. But I myself have never tried it though.

Thanks Romil, I've missed this one!

cool_rash

Thanks to all for the insight given...