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

versioning

spayal

When I make changes to templating.cfg in GUI, new version is being cereated.
and upon uploading this new file this new version comes in effect. If I want to go back to earlier version, I click on properties tab and click on versions and I get to see different versions. I can choose earlier version and click on revert and that version will come in use, is this right ?

The version which is in use does not have revert button on it, right ?

thanks

Find more posts tagged with

Comments

Sailesh

When I make changes to templating.cfg in GUI, new version is being cereated.
and upon uploading this new file this new version comes in effect. If I want to go back to earlier version, I click on properties tab and click on versions and I get to see different versions. I can choose earlier version and click on revert and that version will come in use, is this right ?

The version which is in use does not have revert button on it, right ?

thanks

How can you revert to current version, you can only revert to an earlier version. Once reverted you need to submit that version again for the effects.

Adam Stoller

When I make changes to templating.cfg in GUI, new version is being cereated.
and upon uploading this new file this new version comes in effect. If I want to go back to earlier version, I click on properties tab and click on versions and I get to see different versions. I can choose earlier version and click on revert and that version will come in use, is this right ?

The version which is in use does not have revert button on it, right ?

thanks

Uhm, unless you've created a custom "admin" branch that manages the configuration files that normally reside on the local disk - (or if I've managed to miss some dramatic change somewhere) - there is no means of modifying the templating.cfg file in the GUI. That file is located in IWHOME/local/config/

Are you perhaps talking about changes to a FormsPublisher DCT (datacapture.cfg)?

spayal

yes, custom admin branch is created which manages the configuration files.

This custome admin file is not created by me and I have a question on how to link configuration files with this branch.

I guess I have to share configuration files on server. From the local folder, I can map to these shared folders on the server using tool. But from a teamsite GUI, how can I link to these configuration files ?

Pls explain with primary details.

Thanks

nipper

This is implementation specific. Ask whoever set it up, or whoever they trained.

If neither are available, you better hope the next option works, which is submit the file (tempalting.cfg) from TeamSite.

If the changes are not active you need someone who knows how TeamSite works to look at what was implemented and show you what it does. This cannot be done without close examination of the system.