You signed in with another tab or window. Reload to refresh your session.You signed out in another tab or window. Reload to refresh your session.You switched accounts on another tab or window. Reload to refresh your session.Dismiss alert
Copy file name to clipboardExpand all lines: docs/transform/modernize-userinterface-site-pages-model-publishing.md
+7-5Lines changed: 7 additions & 5 deletions
Original file line number
Diff line number
Diff line change
@@ -1,7 +1,7 @@
1
1
---
2
2
title: Understanding and configuring the publishing page transformation model
3
3
description: Provides detailed guidance on how to configure and use the publishing page transformation model
4
-
ms.date: 04/04/2019
4
+
ms.date: 04/17/2019
5
5
ms.prod: sharepoint
6
6
localization_priority: Normal
7
7
---
@@ -22,7 +22,7 @@ If you're using custom page layouts then it's recommended to use a custom page l
22
22
Using the `Export-PnPClientSidePageMapping` cmdlet you can:
23
23
24
24
- Export the built in mapping file (`-BuiltInPageLayoutMapping` parameter): this file will be used for the out of the box page layouts. **If you specify a custom mapping for an out of the box page layout than that mapping will take preference**
25
-
- Analyze the page layouts in the connected portal and export those as a mapping file (`-CustomPageLayoutMapping` parameter): **all** the found page layouts (so out of the box and custom) are analyzed and exported
25
+
- Analyze the page layouts in the connected portal and export those as a mapping file (`-CustomPageLayoutMapping` parameter): all the found custom page layouts are analyzed and exported. If you also want to get your OOB page layouts analyzed then use the `-AnalyzeOOBPageLayouts` parameter.
26
26
27
27
```PowerShell
28
28
# Connect to your "classic" portal
@@ -93,16 +93,16 @@ Let's analyze how a page layout mapping is configured in the page layout mapping
@@ -195,6 +195,7 @@ Each field in the classic publishing page that needs to become a visual element
195
195
-**TargetWebPart**: the type of the target web part that will visualize this field on the modern page. Supported target web parts are `SharePointPnP.Modernization.WikiTextPart`, `SharePointPnP.Modernization.WikiImagePart` and `Microsoft.SharePoint.Publishing.WebControls.SummaryLinkWebPart, Microsoft.SharePoint.Publishing, Version=16.0.0.0, Culture=neutral, PublicKeyToken=71e9bce111e9429c`.
196
196
-**Row**: the row you want to put the target web part in. Needs to be 1 or greater.
197
197
-**Column**: the column you want to put the target web part in. Needs to be 1, 2 or 3.
198
+
-**Order**: the order of the target web part in the defined row/column.
198
199
199
200
Depending the chosen TargetWebPart you'll need to provide the web part properties holding the data needed during transformation. Each property has the following properties:
200
201
@@ -210,6 +211,7 @@ If the page layout contains web part zones then these must be defined here. This
210
211
-**ZoneIndex**: the index of the zone (integer)
211
212
-**Row**: the row you want to put the web parts hosted in this zone in. Needs to be 1 or greater.
212
213
-**Column**: the column you want to put the web parts hosted in this zone in. Needs to be 1, 2 or 3.
214
+
-**Order**: order in the defined row/column for the web parts hosted in this zone
Copy file name to clipboardExpand all lines: docs/transform/modernize-userinterface-site-pages-powershell.md
+4-2Lines changed: 4 additions & 2 deletions
Original file line number
Diff line number
Diff line change
@@ -1,7 +1,7 @@
1
1
---
2
2
title: Transform classic pages to modern client-side pages using PowerShell
3
3
description: Explains how to transform classic wiki and web part pages into modern client side pages using the SharePoint PowerShell
4
-
ms.date: 04/04/2019
4
+
ms.date: 04/17/2019
5
5
ms.prod: sharepoint
6
6
localization_priority: Priority
7
7
---
@@ -42,7 +42,9 @@ LogSkipFlush (as of April 2019 release, version 3.8.1904.*) | $false | All page
42
42
DontPublish (as of April 2019 release, version 3.8.1904.*) | $false | All page types | Use the `-DontPublish` option to not publish the created modern page.
43
43
DisablePageComments (as of April 2019 release, version 3.8.1904.*) | $false | All page types | Use `-DisablePageComments` if you want to disable the commenting option on the created page
44
44
PublishingPage (as of April 2019 release, version 3.8.1904.*) | $false | Publishing pages | Set the `-PublishingPage` parameter if you're transforming a publishing page. For wiki and web part pages this parameter must be omitted or set to false.
45
-
PageLayoutMapping as of April 2019 release, version 3.8.1904.*) | | Publishing pages |Via `-PageLayoutMapping` you can specify the path the [page layout mapping file](modernize-userinterface-site-pages-model-publishing.md) that you'll use for your publishing page transformations when the publishing page is using a non out of the box page layout
45
+
PageLayoutMapping (as of April 2019 release, version 3.8.1904.*) | | Publishing pages |Via `-PageLayoutMapping` you can specify the path the [page layout mapping file](modernize-userinterface-site-pages-model-publishing.md) that you'll use for your publishing page transformations when the publishing page is using a non out of the box page layout
46
+
PublishingTargetPageName (as of May 2019 release, version 3.9.1905.*) | | Publishing pages | Use the `-PublishingTargetPageName` parameter to override the name for the modern page
47
+
SkipUrlRewriting (as of May 2019 release, version 3.9.1905.*) | | Publishing pages | During publishing page transformation URL's are rewritten to be valid in the target site collection, but using the `-SkipUrlRewriting` you can disable the URL rewriting
46
48
47
49
(`*`) Mandatory command line parameter / (`**`) Mandatory when the `-PublishingPage` parameter was set
0 commit comments