ConvertTo-PnPPage | transformed page embedded urls issue
Nobody has claimed this yet.
- Dominant language
- C#
- Stars
- 259
- Forks
- 161
- Avg merge
- 10h 33m
- Merged PRs (30d)
- 1
Description
I'm converting SP2013 publishing pages to SPO with the following cmdlet:
ConvertTo-PnPPage -Identity $pageTitle -PublishingPage -CopyPageMetadata -SkipHiddenWebParts -TargetConnection $connSPO -TargetWebUrl $TargetSPOSite -Overwrite -LogType File -LogFolder "C:\PnP Logs" -LogVerbose -LogSkipFlush
Everything works fine but the urls (inside the transformed pages) pointing to other pages: the problem is that those urls have the "/sites/" managed path twice, e.g. https://tenant.sharepoint.com/sites/sites/siteabc/sitepages/sitepage.aspx
In the source SP2013 pages the links are set as relative ones, e.g. /onpremsite/pages/sitepage.aspx by using the insert link button from the ribbon and choosing "from SharePoint".
Page content type is "Enterprise Wiki Page", page layout "Basic page".
PnP.PowerShell version 2.1.1.
OS: Win 10
Contributor guide
No contributing guide indexed for this repository
First steps
- Read the whole issue, then the project's contributing guide.
- Comment on the issue to say you are picking it up — it saves two people doing the same work.
- Fork the repository and make your change on a branch.
- Open a pull request that references the issue number.
Research direction
Reproduce the ConvertTo-PnPPage command against an SP2013 publishing page containing relative links to other pages, then inspect the transformed page URLs. Done means links in the converted page contain the /sites/ managed path only once; the payload does not identify a source file or test.
Written by the indexing model from the issue text.
Assessment
- Tech stack
- csharp, powershell
- Domain
- tooling
- Issue type
- Bug
- Difficulty
- 4/5
- Estimated time
- 3-5 days
- Activity status
- Stale
- Clarity
- Mostly clear
- Newbie friendliness
- 38/100