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 in TS

nagendra

We believe TS keeps an unlimited number of versions. Could we specify a limit on the number of versions which can be set? Is it a TS configurable param?

Or, is there any other way to control/limit versioning?

Thanks,

Find more posts tagged with

Comments

iw_store

I don't think any such param or limitation exists, as long as you change your asset in workarea and submit every one intends to have a separate version of it. If any such facility exists at some point of time you will start loosing versions of that asset. Hence I feel IW has not provided such facility, as different versions of an asset is important in CMS until that asset has existance. Smiley Happy

Sailesh

We believe TS keeps an unlimited number of versions. Could we specify a limit on the number of versions which can be set? Is it a TS configurable param?

Or, is there any other way to control/limit versioning?

Thanks,

Whats your exact requirement? Why you want to limit number of version? What will happen to changes done after a reaching it limit of the version number?

kaalraa

We believe TS keeps an unlimited number of versions. Could we specify a limit on the number of versions which can be set? Is it a TS configurable param?
Or, is there any other way to control/limit versioning?
Thanks,

If you think... your versions have increased and you dont want them... simply delete the editions... versions would be omitted on its own.

Frederik

Or, is there any other way to control/limit versioning?

As others said, you can't limit the # of versions per file.

What you can do, is delete old (named/published) editions. That will delete the versions of files which are found in those editions and nowhere else.

So if you have ed_0000 till ed_0999 and you delete ed_0000 till ed_0500, you'll delete all the file versions used in ed_0000 till ed_0500 which aren't existing in ed_0501 till ed_0999, nor in any workarea. Never delete your INITIAL edition though.

It may not be exactly what you asked, but if the underlying need is to limit disk space by removing less relevant, old, content, it may do.

patrickm

Yes the only way to control editions is to remove those older ones. Edition deletion is server intensive, so pay attention to background batch processes associated with each edition delete. iwfreeze -j can be used to pause these if they affect server performance.

jkm

Yes the only way to control editions is to remove those older ones. Edition deletion is server intensive, so pay attention to background batch processes associated with each edition delete. iwfreeze -j can be used to pause these if they affect server performance.

interesting information..I never noticed this before, when does this impact the server most.. when high number of files are changed in the edition?? I assume when the screen refresh in TS, the deletion process should be completed or it keeps on running in the background ?

Adam Stoller

interesting information..I never noticed this before, when does this impact the server most.. when high number of files are changed in the edition?? I assume when the screen refresh in TS, the deletion process should be completed or it keeps on running in the background ?

In general, unless there are significant amount of changes between editions (hundreds or more - a guess) the impact of deleting any single edition should be relatively minor.

However, yes, the deletion process continues in the background as the process runs asynchronously.

If you have access to a shell on the server - you can run iwstat -c to see what's happening.

Deleting branches is generally a much heavier weight process than editions - because editions are essentially just a list of pointers to specific versions of files and only those versions that are no longer referenced by any TeamSite area (workarea, staging, editions) are subject to "garbage collection" - whereas deletion of a branch represents a deletion of all versions of all files associated with that branch.

jkm

Thanks Adam for this information...
I tried this with iwstat -c but it was very minor and difficult to notice. We may be able to notice this when number of changes are really high as part of the edition as you have said earlier.