[BUG] Add-PnPFileToSiteTemplate can't deal with Umlaute
Nobody has claimed this yet.
- Dominant language
- C#
- Stars
- 259
- Forks
- 161
- Avg merge
- 10h 33m
- Merged PRs (30d)
- 1
Description
Issue description
The command Add-PnPFileToSiteTemplate can't deal with Umlaute. Instead of just importing the file including an Umlaut, it will create a subfolder.
E.g. when I have a structure in my source as follows:
/SharedDocuments/Ankündigung.docx
it will create the following structure in the template:
/SharedDocuments/Ank%/Ankündigung.docx
Command used
Add-PnPFileToSiteTemplate -Path example.xml -SourceUrl "https://example.sharepoint.com/sites/example/SharedDocuments/Ankündigung.docx"
Expected behavior
For the command Add-PnPFileToSiteTemplate to keep the original location of the exported file and not create "random" subfolders.
What is the version of the Cmdlet module you are running?
v1.12.0
Which operating system/environment are you running PnP PowerShell on?
- Windows
- Linux
- MacOS
- Azure Cloud Shell
- Azure Functions
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
Start by reproducing Add-PnPFileToSiteTemplate with the provided Ankündigung.docx source path and trace how the command converts the URL into the template location. Done means the exported file retains its original /SharedDocuments location without creating an Ank% subfolder; add or run a regression test for the umlaut path if the relevant test entry point is found.
Written by the indexing model from the issue text.
Assessment
- Tech stack
- csharp, powershell
- Domain
- cli
- Issue type
- Bug
- Difficulty
- 3/5
- Estimated time
- 1-2 days
- Activity status
- Stale
- Clarity
- Mostly clear
- Newbie friendliness
- 35/100