From 9d6937c792ab43d62c07cd7b0c4a0a60130eebba Mon Sep 17 00:00:00 2001
From: adeveloper <kumaravel@live.com>
Date: Mon, 29 Jun 2015 17:07:14 -0400
Subject: [PATCH] DefaultContentManager.cs

The new version should always be contentItemRecord.Versions.Max(x => x.Number) + 1; not latestVersion.Number + 1;

I have a scenario where user can delete the draft content. In this scenario, I set the published version to have Latest=true and the draft version to have Latest=false. Now if I have to create again a new draft out of the published content, I end up having two versions of the same content items with the same version number.
---
 src/Orchard/ContentManagement/DefaultContentManager.cs | 10 ++++++----
 1 file changed, 6 insertions(+), 4 deletions(-)

diff --git a/src/Orchard/ContentManagement/DefaultContentManager.cs b/src/Orchard/ContentManagement/DefaultContentManager.cs
index a94278d7a..31603d9da 100644
--- a/src/Orchard/ContentManagement/DefaultContentManager.cs
+++ b/src/Orchard/ContentManagement/DefaultContentManager.cs
@@ -481,11 +481,13 @@ namespace Orchard.ContentManagement {
 
             if (latestVersion != null) {
                 latestVersion.Latest = false;
-                buildingItemVersionRecord.Number = latestVersion.Number + 1;
-            }
-            else {
-                buildingItemVersionRecord.Number = contentItemRecord.Versions.Max(x => x.Number) + 1;
+                //buildingItemVersionRecord.Number = latestVersion.Number + 1;
             }
+            //else {
+            //    buildingItemVersionRecord.Number = contentItemRecord.Versions.Max(x => x.Number) + 1;
+            //}
+            ////The new version should always be the next highest available number.
+            buildingItemVersionRecord.Number = contentItemRecord.Versions.Max(x => x.Number) + 1;
 
             contentItemRecord.Versions.Add(buildingItemVersionRecord);
             _contentItemVersionRepository.Create(buildingItemVersionRecord);