I have had an update from Microsoft on this issue, apparently the wording is wrong.
It will retain the number of major versions entered, but the number for minor versions is not to limit the number of minor versions, but to limit the number of major versions that have minor versions (Does that make sense?).
For example, if I set major versions to 10 and minor versions to 2, it will show me 10 major versions of which 10 and 9 will have minor versions still available.
The problem here is that I can still create 100 minor versions so this is not helping me limit the amount of versions my users keep and keep my storage costs down
n a document library under “Versioning Settings” you can choose to set the number of major and minor versions to retain.
This does not work! You are still able to create more than the number of versions specified in both major and minor
I have spoken to Microsoft and they have confirmed this to be a “design limitation”. Has anyone ever got someone at Microsoft to say “bug”?
I’ll keep you updated if I get a fix for this.
Can someone help me please, I have the following problem.
I developed a custom site definition solution in Visual Studio 2005 using the following process detailed in my post earlier.
I had no problems in my development environment and added the solution into our UAT environment using STSADM and deployed through Central Administration.
The template was successfully deployed and able to provision sites based on that template.
After a cycle of UAT some changes and bugs came back which I fixed in my solution and tested in the development environment no problems.
I took the wsp files and used the UPGRADESOLUTION operation in STSADM. I tested the provisioning of a new site and it worked, but when I checked an existing site that had been provisioned from the site definition the homepage just displayed a 404 – file not found.
I am still able to view the settings of the site if I access the _layouts pages. I have tried resetting the site to the site definition in the Site Settings with no luck.
I have opened the site in SharePoint Designer and can see all the files including the default.aspx site that cannot be found, but if I try to open it comes back with a soap error saying the file does not exist.
Nothing is entered in the event logs or SharePoint logs.
Please help I am desperate, we are meant to be going live in 2 weeks and am not very confident if I am unable to upgrade an existing site definitions through a solution. 😦