ConvertTo-PnPClientSidePage maps wrong content about modernization HOT 5 CLOSED

Hi @rjcg916,

Thanks for your feedback. Can you specify in more detail with what is wrong for you?

The feed web part is mapped to the news web part as there's no modern version of the feed. If you use the ReplaceHomePageWithDefault switch then the home page should be changed to the default home page of a modern team site.

from modernization.

I dug into this more and believe I found the root cause.

On my site, I have a SitePages library along with other Wiki libraries. When I try to convert my SitePages/Home.aspx page, the content from "Home.aspx" on one of the Wikis appeared in the SitePages/Migrated_Home.aspx page. I tried renaming pages across the libraries to make "Home.aspx" unique, but the command appears to always look in the first library it fines.

from modernization.

Good point, the tool currently defaults to the first wiki page library it finds. It essentially does not take in account that one can have multiple wiki page libraries. When you use the .Net approach you can target any library, but the PS implementation currently does not allow that. I'll create.

I've created #12 for this.

from modernization.

Are you OK with closing this question now that we've a bug open to fix this?

from modernization.

Did some more investigation and realized that you cannot create modern site pages in other wiki page libraries, only the site pages library allows modern site pages. The logic in the PowerShell cmdlet has been updated for that (see #12). We're looking into allowing multiple page libraries in the future, at that point the needed support will be added.

from modernization.