Hot answers tagged versioning
The Content and Structure worked fine for me. Moving individual documents from one library to another captures all versions. Assuming, of course, versioning is configured the same on both libraries. That bit me the first time - the destination had Major, but the source had Major/Minor. Once the destination was switched to Major/Minor, documents came over ...
Using some CAML tools pointed at a local library with versioning enabled, I was able to get back the field ows__UIVersionString of a file. It correctly shows the version is 9.0 which is reflected in the UI. <Where> <Eq> <FieldRef Name='ID' /> <Value Type='Counter'>1</Value> </Eq> ...
Next time you make changes to your CSS file, create your own rev/version tag where the CSS file is being referenced (probably your Master Page). This way the browser will break the cached CSS and re-retrieve thinking it's a new file. ex. <link href="/styles/style.css?rev=03_27_2014_v1" type="text/css" rel="stylesheet" />
Only top voted, non community-wiki answers of a minimum length are eligible