Wikipakk tree issues

[Alin-Dumitrescu]

Hello,

I am evaluating wikipakk for a confluence site migrated to SharePoint with WikiTracs. It seems during the migration the hierarchy of the pages was not preserved - all pages are now listed in a flat list - what am I doing wrong?

Thanks, Alin

[heinrich-ulbricht]

@Alin-Dumitrescu This should work out of the box, so I think you are doing everything right.

Which version of WikiPakk are you using? From AppSource or GitHub, and which version number? There is a small question mark beneath the page tree that opens a dialog showing the version. Make sure it's the (as of now) latest version v2.2.2.

For the SharePoint page tree to show the Confluence page hierarchy certain metadata is needed. WikiTraccs should carry this metadata over when migrating pages from Confluence to Sharepoint.

Let's check if this metadata is present.

In SharePoint, please open the migration target site - that's the site WikiTraccs is migrating the Confluence pages to. Choose Site Contents and open the Site Pages library. There should be pages in there that have been migrated already.

Add the following existing columns to the current view of the Site Pages library (if they are not already shown):

• Confluence: Id (WikiTraccs)
• Confluence: Parent Id (WikiTraccs)
• Confluence: Sibling Order (WikiTraccs)

This should look like this:

Those IDs are Confluence page IDs, parent and child, plus the order from the Confluence page tree.

Are there values in those columns for migrated pages? If no, we have to look at the migration and why those values didn't carry over. If yes, we have to look at what WikiPakk does not like about them.

Feel free to post screenshots of the Site Pages Library view, WikiPakk showing the flat "hierarchy", or the JavaScript console filtered for "WikiPakk" messages. If they contain information not for the public eye, blur them where necessary or send them to contact - at - wikitransformationproject.com, referencing this issue here. Thank you!

[Alin-Dumitrescu]

Hi Heinrich,

I do see the information listed below and it looks correct. If you want to schedule a meeting to review this in more details, just let me know

@.***

The tree is flat, all items have the expand symbol ( > ) and if I click on the expand symbol, it will try to retrieve pages and eventually disappear. @.***

Thank you, Alin Dumitrescu Azure DevOps Consultant

[heinrich-ulbricht]

Having a quick call sounds like a good suggestion because this is difficult to diagnose without seeing it. You can use the booking page to choose a time that hopefully fits your schedule. Thanks!

[Alin-Dumitrescu]

I am on the PST time (GMT-8). I see there is a 7:00 AM my time available on Tue June 6th. Any chance there is a spot at the same time or later sooner?

Thank you, Alin Dumitrescu Azure DevOps Consultant

[heinrich-ulbricht]

@Alin-Dumitrescu Ah timezones :D I added two later options Thursday and Tuesday - how about that?

[Alin-Dumitrescu]

Thu would be great – but I don’t see the options on Thursday - only Tuesday…

Thank you, Alin Dumitrescu Azure DevOps Consultant

[heinrich-ulbricht]

Strange, do you see this:

Still need to figure out time slots that are equally acceptable in PST and CEST ^^ we'll get there.

[Alin-Dumitrescu]

I got that time and was able to schedule at 12:00 PM thank you. Talk to you soon!

Thank you, Alin Dumitrescu

[heinrich-ulbricht]

Further analysis showed that page metadata for some SharePoint pages was missing. The page tree thus had no information of the parent child relationship of those pages, displaying them at the root. This is expected behavior.

The solution in this case was to delete and remigrate the affected pages.

Closing this issue. Feel free to open a new one if there are other issues.