Found in: 1.21.0
How to reproduce:
- Set up a SharePoint site, and add a Page as draft only
- Run PnP.Framework provisioning to extract a template from that page (or site)
- Apply the template to another SharePoint site
- Examine the version history of new page => It is already published
Why this is an issue:
If copying a site with news, it is likely that the news needs to be updated for the new site. So, if any news pages already has a published version, that version will instantly be visible to visitors to the site.
Problem found:
In pnpframework\src\lib\PnP.Framework\Provisioning\ObjectHandlers\Utilities\ClientSidePageContentsHelper.cs, at line 109 the Published property of the extractedPage object is set to true. This will control if page will be created as a Published page later when applying the template to a SharePoint site.
Found in: 1.21.0
How to reproduce:
Why this is an issue:
If copying a site with news, it is likely that the news needs to be updated for the new site. So, if any news pages already has a published version, that version will instantly be visible to visitors to the site.
Problem found:
In pnpframework\src\lib\PnP.Framework\Provisioning\ObjectHandlers\Utilities\ClientSidePageContentsHelper.cs, at line 109 the Published property of the extractedPage object is set to true. This will control if page will be created as a Published page later when applying the template to a SharePoint site.