Current version of the modern image web part does support setting a link on the image and use of text overlay. Implement to support img tag wrapped inside an a tag + support caption via figcaption element

I'm having an issue applying the PNP template.
I'm a global admin, I have an app store, I have the latest files,
Any ideas?

Message : {"error":{"code":"-2147024891, System.UnauthorizedAccessException","message":{"lang":"en-US","value":"Access denied. You do not have permission to perform this action or access this resource."}}}
Stacktrace : at OfficeDevPnP.Core.ALM.AppManager.d__39.MoveNext()
--- End of stack trace from previous location where exception was thrown ---
at System.Runtime.ExceptionServices.ExceptionDispatchInfo.Throw()
at System.Runtime.CompilerServices.TaskAwaiter.HandleNonSuccessAndDebuggerNotification(Task task)
at OfficeDevPnP.Core.ALM.AppManager.d__5.MoveNext()
--- End of stack trace from previous location where exception was thrown ---
at System.Runtime.ExceptionServices.ExceptionDispatchInfo.Throw()
at System.Runtime.CompilerServices.TaskAwaiter.HandleNonSuccessAndDebuggerNotification(Task task)
at OfficeDevPnP.Core.ALM.AppManager.Add(Byte[] file, String filename, Boolean overwrite, AppCatalogScope scope, Int32 timeoutSeconds)
at OfficeDevPnP.Core.Framework.Provisioning.ObjectHandlers.Utilities.TenantHelper.ProcessApps(Tenant tenant, ProvisioningTenant provisioningTenant, FileConnectorBase connector, TokenParser parser,
PnPMonitoredScope scope, ProvisioningTemplateApplyingInformation applyingInformation, ProvisioningMessagesDelegate messagesDelegate)
at OfficeDevPnP.Core.Framework.Provisioning.ObjectHandlers.ObjectHierarchyTenant.ProvisionObjects(Tenant tenant, ProvisioningHierarchy hierarchy, String sequenceId, TokenParser parser,
ProvisioningTemplateApplyingInformation applyingInformation)
at OfficeDevPnP.Core.Framework.Provisioning.ObjectHandlers.SiteToTemplateConversion.ApplyProvisioningHierarchy(Tenant tenant, ProvisioningHierarchy hierarchy, String sequenceId,
ProvisioningTemplateApplyingInformation provisioningInfo)
at SharePointPnP.PowerShell.Commands.Provisioning.Tenant.ApplyTenantTemplate.ExecuteCmdlet()
at SharePointPnP.PowerShell.Commands.PnPCmdlet.ProcessRecord()
ScriptLineNumber : 1

Hi,

I just noticed that the "ConvertTo-PnPClientSidePage" cmdlet doesn't migrate content coming from "content editor" webparts.

Is there a way to map those contents to "Text" webparts in the modern experience?

Thanks.

Our site has a custom column we use to sort pages. The column is validated against a list of known values. Transformed pages don't carry over their parent page's value from this column.

I have installed and enabled the Page transformation UI on a site from the modernization center. I got the message "Modernization functionality added to site" message. Yet , when I browse to the site the 'Create Modern Version' command is not visible in the Wiki Page ribbon. It is visible on a webpart page ribbon.
Kindly Advise , how to debug the issue.

A call of this form:
ConvertTo-PnPClientSidePage -Identity $page.FieldValues["FileLeafRef"] -Overwrite
generates a page not found error when the $page (WikiPage) is of the form "How To Use This Library.aspx".

The cmdlet currently assumes the page always lives in the first wiki page library it finds, which might not be the case if you've created additional libraries

I am fallowing https://docs.microsoft.com/en-us/sharepoint/dev/transform/modernize-userinterface-site-pages-powershell
and getting error :

ConvertTo-PnPClientSidePage : Exception has been thrown by the target of an invocation.
At line:21 char:1

• ConvertTo-PnPClientSidePage -Identity $page.FieldValues["FileLeafRef" ...

•   + CategoryInfo          : WriteError: (:) [ConvertTo-PnPClientSidePage], TargetInvocationException
    + FullyQualifiedErrorId : EXCEPTION,SharePointPnP.PowerShell.Commands.ClientSidePages.ConvertToClientSidePage
  
  

Build in debug measurements to drive performance optimization / check number of server roundtrips and optimize where possible

I keep getting issues in Step 2 after setting up the Azure apps. Any suggestions? I have double checked and gone through all the steps multiple times. Help would be greatly appreciated.
https://drive.google.com/file/d/1MPCWUsOxsYkepjtBRyOlFHWrnC0AgA73/view?usp=sharing

Support publishing page transformation. Ideas:

• Use 'pagelayout' mapping template to determine which fields become content and which will be metadata and what layout to be used
• Generate mapping template based upon analyzing a page layout
• Provide 'built-in' mappings for OOB page layouts
• Provide capability to create target page into another site collection (what about depending assets in this case?)

Embed JS on the page that shows a banner on classic pages pointing to the created modern version of that page. This will help users discover the modern versions when these are for example generated by IT using PowerShell or .Net.

Check the samples in https://github.com/SharePoint/PnP/tree/master/Samples/Core.JavaScriptCustomization to get started.

See #27.

Hi,
Some pages in my Site Pages library give me the above error message others work fine. Looking at the page metadata I cant figure out what the difference is.

What causes this message?

Transforming the page succeeds, but leaves the transformed page as "Migrated_" without renaming the original to "Previous_".

Stack Trace:
at Microsoft.SharePoint.Client.ClientRequest.ProcessResponseStream(Stream responseStream)
at Microsoft.SharePoint.Client.ClientRequest.ProcessResponse()
at Microsoft.SharePoint.Client.ClientRequest.d__6.MoveNext()
--- End of stack trace from previous location where exception was thrown ---
at System.Runtime.CompilerServices.TaskAwaiter.ThrowForNonSuccess(Task task)
at System.Runtime.CompilerServices.TaskAwaiter.HandleNonSuccessAndDebuggerNotification(Task task)
at Microsoft.SharePoint.Client.ClientRequest.d__0.MoveNext()
--- End of stack trace from previous location where exception was thrown ---
at System.Runtime.CompilerServices.TaskAwaiter.ThrowForNonSuccess(Task task)
at System.Runtime.CompilerServices.TaskAwaiter.HandleNonSuccessAndDebuggerNotification(Task task)
at Microsoft.SharePoint.Client.ClientRuntimeContext.d__0.MoveNext()
--- End of stack trace from previous location where exception was thrown ---
at System.Runtime.CompilerServices.TaskAwaiter.ThrowForNonSuccess(Task task)
at System.Runtime.CompilerServices.TaskAwaiter.HandleNonSuccessAndDebuggerNotification(Task task)
at Microsoft.SharePoint.Client.ClientContext.d__4.MoveNext()
--- End of stack trace from previous location where exception was thrown ---
at System.Runtime.CompilerServices.TaskAwaiter.ThrowForNonSuccess(Task task)
at System.Runtime.CompilerServices.TaskAwaiter.HandleNonSuccessAndDebuggerNotification(Task task)
at Microsoft.SharePoint.Client.ClientContextExtensions.d__7.MoveNext()
--- End of stack trace from previous location where exception was thrown ---
at System.Runtime.CompilerServices.TaskAwaiter.ThrowForNonSuccess(Task task)
at System.Runtime.CompilerServices.TaskAwaiter.HandleNonSuccessAndDebuggerNotification(Task task)
at Microsoft.SharePoint.Client.ClientContextExtensions.ExecuteQueryRetry(ClientRuntimeContext clientContext, Int32 retryCount, Int32 delay, String userAgent)
at SharePointPnP.Modernization.Framework.Transform.PageTransformator.SwapPages(PageTransformationInformation pageTransformationInformation)
at SharePointPnP.Modernization.Framework.Transform.PageTransformator.Transform(PageTransformationInformation pageTransformationInformation)
at SharepointModernisation.Program.Main(String[] args) in C:\Users\Gianni\Source\Repos\SharepointModernisation\Program.cs:line 66

Dear Bert,
Would it be possible to offer an on-prem version for SP2019?

Best regards
Nicolas

I receive this error message in the modernization center when i try to create a modern version:
Busy generating a modern version of Homepage.aspx...
Error: SyntaxError: Unexpected end of JSON input

There seems to be some files missing fro the solution/projects.

This issue showed, need to find the root cause and if needed provide a fix.

Script to upload the latest Azure Function app from a zip file. Is needed for upgrade towards the beta release.

In step 2 of the deployment I get "Insufficient privileges to complete the operation" when running the Apply-PnPTenantTemplate command. Do you need to be a Global Tenant Admin to run this step or should I be able to run this as a SharePoint Administrator?

Using /sites/modernizationcenter is not always possible:

• url could be taken
• tenant could be configured to create it's site collection under /teams instead of /sites

See #18

Applying a PnP Provisioning template to all site collections is time-consuming, using the Add-PnPCustomAction cmdlet will be much faster. This script should also allow removing the UI integration.

I am trying to convert a classic page to modern page by using the ribbon button on the page library, after clicking the button, it redirected to the modernization center page and after awhile there are error message in the page as below :

Busy generating a modern version of Home.aspx...
Error: Tenant xxx.com is not whitelisted for this transformation service endpoint.

where I can setup the whitelist ? how to resolve this ? thanks !

Hello @jansenbe
There are issue in migrating the classic page to modern using .Net based SharePoint PnP Modernization framework.

I get below error. It is random, sometimes i get this error and sometime not. Tried 'Include(WelcomePage)'.Nothing works. Any suggestion please

Error Description:
The property or field 'WelcomePage' has not been initialized. It has not been requested or the request has not been executed. It may need to be explicitly requested.

Do we have any mapping solution to convert contact webpart to modern people webpart in office 365.

Thanks
ParvathySN

Preview version only supports English, add support for Dutch and then describe for community how to add additional languages

Title says it all. Overwrite is enabled, TargetPageTakesSourcePageName is enabled. The modern version ends up in the root of the library, even when the original page was in a folder.

Transforming a page in a subsite using the page transformation UI results in the modernization proxy page being called with an invalid SiteUrl parameter (e.g. modernize.aspx?SiteUrl=/sites/contosoelectronicsdrones&ListId={bb2f8a1b-c0a8-4720-8b5f-60db0c743be3}&ItemId=2 is passed while the site is /sites/contosoelectronicsdrones/marketing)

Hi,
I am following the article from https://developer.microsoft.com/en-us/sharepoint/blogs/modernize-your-sharepoint-pages/ and trying to use the cmdlet -

ConvertTo-PnPClientSidePage : Page 'test2.aspx' does not exist

When using the cmdlet I get the following error?
`ConvertTo-PnPClientSidePage : Page 'test2.aspx' does not exist
At line:1 char:1

• ConvertTo-PnPClientSidePage -Identity test2.aspx -AddPageAcceptBanner

•   + CategoryInfo          : WriteError: (:) [ConvertTo-PnPClientSidePage], Exception
    + FullyQualifiedErrorId : EXCEPTION,SharePointPnP.PowerShell.Commands.ClientSidePages.ConvertToClientSidePage`
  
  

This page is a wikipage that does exist on the site.

Create a basic script that allows one to fetch site collections based upon a filter and then run the script that enables/disables the page transformation UI in those site collections

This commands maps Home.aspx wiki page to a Migrated_Home.aspx with wrong content.

These should be seen as wiki page and simply result in an empty modern site page. Investigate/fix why they're recognized as aspx pages.

Title says it all. Looks like it's trying to replace a token in the URI for the new page? This happens on many pages on the site I'm working with.

Outer exception (top level of this hidden, it's just Main() in program.cs on my end):
at System.RuntimeMethodHandle.InvokeMethod(Object target, Object[] arguments, Signature sig, Boolean constructor)
at System.Reflection.RuntimeMethodInfo.UnsafeInvokeInternal(Object obj, Object[] parameters, Object[] arguments)
at System.Reflection.RuntimeMethodInfo.Invoke(Object obj, BindingFlags invokeAttr, Binder binder, Object[] parameters, CultureInfo culture)
at SharePointPnP.Modernization.Framework.Functions.FunctionProcessor.ExecuteMethod(Object functionClassInstance, FunctionDefinition functionDefinition, MethodInfo methodInfo)
at SharePointPnP.Modernization.Framework.Functions.FunctionProcessor.Process(WebPart& webPartData, WebPartEntity webPart)
at SharePointPnP.Modernization.Framework.Transform.ContentTransformator.Transform(List`1 webParts)
at SharePointPnP.Modernization.Framework.Transform.PageTransformator.Transform(PageTransformationInformation pageTransformationInformation)

Inner Exception:
at System.String.ReplaceInternal(String oldValue, String newValue)
at System.String.Replace(String oldValue, String newValue)
at SharePointPnP.Modernization.Framework.Functions.BuiltIn.ListAddWebRelativeUrl(Guid listId)

On clicking 'Create Modern Version' button on a web part page , receiving the following error.
Not all parameters are configured, can't execute. Please run the setup steps.
AzureAD application ID:
AzureAD function host:
Page transformation endpoint:
However , if I rerun the setup , it says APP is already installed.

I've followed the steps to update my webmappings manifest (noticed that the line numbers being referred to are wrong

Using the ConvertTo-PnPClientSidePage cmdlet is giving me this error.

Any ideas as to why this might be happening?

I have followed the deployment guide using (pnp powershell). After I enabled the "the page transformation UI on the site collections", the "create modern version" is gray out.

Please advise

I have webpart page with Script Editor webpart

When transforming the webpart page to modern page it displays below message
'Busy generating a modern version of WebPartPage4.aspx...
Error: Object reference not set to an instance of an object.'