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 about file version in CMS

Haiyan

Hi,

My understanding of teamsite versioning is if I revert a file back to a previous version, any version created after will be lost. What if I my current file version is version 10, I want to revert to version 8 for some temporary purpose, and I still want to be able to go back to version 10 after I am done with my temporary work. Will that be possible?

Thanks,
-Haiyan

Find more posts tagged with

Comments

Adam Stoller

Hi,

My understanding of teamsite versioning is if I revert a file back to a previous version, any version created after will be lost. What if I my current file version is version 10, I want to revert to version 8 for some temporary purpose, and I still want to be able to go back to version 10 after I am done with my temporary work. Will that be possible?

Thanks,
-Haiyan

Your understanding is wrong. The best way to see this is in CCPro:

The one thing that you would lose is any non-submitted changes in the workarea.

Bhargav Coca

I am reiterating what Adam said with your example

Make sure you submit Version 10 before reverting (This is crucial so as to not loose version 10 changes).

Now go to version and revert that file to Version 8. I am not sure what you gonna do to this reverted file if you make changes and submit its gonna be version 11.

So when you are reverting back revert version 10 back (The version 8 now became version 11).

HTH

Thanks

Rick Poulin

Make sure you submit Version 10 before reverting (This is crucial so as to not loose version 10 changes). Now go to version and revert that file to Version 8. I am not sure what you gonna do to this reverted file if you make changes and submit its gonna be version 11. So when you are reverting back revert version 10 back (The version 8 now became version 11).

Increasing specificity of the above in case anybody gets to a point where this matters..

Say your current version is 9+ (modifications since version 9). Reverting to version 8 right now means that version 9+ gets erased and replaced with the *contents and attributes* of version 8. The version of the current file is still 9+, and what used to be 9+ is now gone forever. A comment on the file's version history will indicate that version 9+ was created based on version 8.

Say your current version is 9+ and you now submit it. This copy becomes version 10. Now revert to version 8. The *contents and attributes* of version 8 now get copied as version 10+. If you 'undo changes', your revert never happened. If you submit, this becomes version 11. Either way, version 10+ gets that same 'created from version 8' comment.

In both examples, previous *submitted* versions remain unchanged in your version history, but you do lose any unsubmitted modifications.