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
+59-19Lines changed: 59 additions & 19 deletions
Display the source diff
Display the rich diff
Original file line number
Diff line number
Diff line change
@@ -178,24 +178,6 @@ For each field that you want to take over you'll need to add a Field element spe
178
178
> - Functions support is not available for taxonomy fields
179
179
> - Page property web part configuration was introduced in the June 2019 release
180
180
181
-
#### Page preview image options
182
-
183
-
When a page has a page header image that image will also be used as a page preview image. If you however want to control the page preview image then you can populate the `BannerImageUrl` field using either the `ToPreviewImageUrl` function or by specifying a hard coded value as shown in below samples.
184
-
185
-
```XML
186
-
<!-- When you do have a publishing image field that will need to be set as preview image -->
<!-- When you do have a hard coded preview image already available on the target site. Note that the source field name (PublishingContactEmail in below sample) must exist, although it's not used here -->
> Controlling the page preview image was introduced with the May 2019 release.
198
-
199
181
### WebParts element
200
182
201
183
Each field in the classic publishing page that needs to become a visual element on the target page (like a web part or text) must defined in the web parts section:
@@ -303,4 +285,62 @@ Now that the assembly has been defined you can use your functions and selectors
If you however publish this page the modification data will change again. If you want to keep the modification date and publish you can add these 2 additional fields:
When a page has a page header image that image will also be used as a page preview image. If you however want to control the page preview image then you can populate the `BannerImageUrl` field using either the `ToPreviewImageUrl` function or by specifying a hard coded value as shown in below samples.
333
+
334
+
```XML
335
+
<!-- When you do have a publishing image field that will need to be set as preview image -->
<!-- When you do have a hard coded preview image already available on the target site. Note that the source field name (PublishingContactEmail in below sample) must exist, although it's not used here -->
Copy file name to clipboardExpand all lines: docs/transform/modernize-userinterface-site-pages-powershell.md
+2-2Lines changed: 2 additions & 2 deletions
Display the source diff
Display the rich diff
Original file line number
Diff line number
Diff line change
@@ -57,7 +57,7 @@ SkipUrlRewriting (as of May 2019 release, version 3.9.1905.*) | | Publishing pa
57
57
58
58
Above shown sample shows in-place page transformation, for transforming publishing pages you need a slightly different syntax. Below sample shows how to modernize the mypage.aspx page and create a modern version of it in a communication site. During this transformation the page transformation will either use the built-in page layout mapping if the page is using an out of the box page layout or it will generate a page layout mapping on the fly for custom page layouts:
0 commit comments