SharePoint 2013 aspx pages version manipulation

Wednesday, February 17, 2016

SharePoint 2013 aspx pages version manipulation

If you have better idea about versioning in SharePoint 2013 and you might be working with aspx pages that could be used for designing contact us page, information page or product page and any kind of aspx page using SharePoint 2013. Complex situations come where you are concurrently working with different version of those pages.
It’s simple if you are familiar with layout pages you need to create a simple aspx page and select layout and that’s it, you are ready to go. Below example of aspx page is a contact page where you have created different versions and one of them is a published version and you also make changes in the existing one and that become draft version and you check in that aspx version where your content deployment job is already setup so you can only publish this draft version and then unpublished it or somehow remove that draft or manipulate all these versions.
We come across with a problem when we were working on the same page and created different versions of aspx page, below screen shot is displaying various versions of aspx page 17.0 where by mistake or you want to you want to make changes on the production version so  new content should be displayed and save it so SharePoint has created another draft version for you- or you made small change on published version so then it becomes draft version and you would probably see the screen below for your change that you made to 17.0 version and becomes 17.1 version.
So the version that has unpublished option as described in the picture below technically is the version on production server but if you look at the version so there is 17.1 version is there because you have made some changes in it and SharePoint has created another draft for you of the production version.  

So you would see one “unpublished” option in your SharePoint 2013 version history page and you would see only “view” and “restore” option for the page which is converted into draft. And you would see “view” “restore” and “delete” option for those versions that is there with draft status.
SharePoint 2013 aspx version managaement
SharePoint 2013 version history
So technically our published version is 17.1 because we made small change in content so then SharePoint converted and produced a 17.1 as draft but if you check the screen 17.0 is published version.

If you click on view option then you can delete this item version from that dialog box and edit content type of that page and restore it from there. As a rule of thumb – this area is for version to delete individually, unpublished and restores any version of any type – it could be document, aspx page excel sheet etc.
SharePoint 2013 document version or aspx page version with unpublished option
SharePoint 2013 document version or aspx pages version
These screens shot captured from Microsoft own product SharePoint server 2013 illustrated here for learning purpose only.

Whereas if you want to see other version of that aspx page so you would see unpublished version too and with other version like 16.0 or 15.0 you would probably see delete option to delete that version of page and view option to view that version of page and you would probably see restore to restore that version of aspx pages.
SharePoint 2013 aspx page version management with delete option
SharePoint 2013 aspx page version management with delete option
On the other hand you can easily manage other version of that aspx page where you can delete and restore the same version of aspx page in SharePoint 2013.
If you want to try this out so to be on safe side – you can easily delete one version and restore it from recycle bin folder where all deleted items are kept so fear not and go and delete any draft version of aspx page  and restore it from recycle bin folder- it’s that simple.
SharePoint 2013 provides the same tendency of SharePoint2013 document versions that it provides with pages, list item, and presentation version and excel sheet version.
Now we are sure you understand how easily you can manipulate complex version scenario of aspx pages in SharePoint 2013 and your issue has been resolve.
Please leave comments if you have any other issue related to that SharePoint document version, aspx page versions.

No comments: