Known Issues and Limitations

The issues on this page affect the page tree in WikiPakk 2.18.

Page Tree Editor access for readers

The Page Tree Editor is for authors. Users with only Read access to the hierarchy can still see its drag-and-drop controls. If a reader tries to move a page, SharePoint rejects the change. The editor can show Access is denied. The saved hierarchy stays unchanged.

Place the editor on a page for users who can change the hierarchy. Use Children Display or the Page Tree panel for readers.

Pages in Site Pages folders

A regular SharePoint page in a Site Pages subfolder can be missing from the page tree if WikiPakk has not saved its position in the tree. This also applies to uploaded HTML pages. A news post in a folder can be missing from the News year and month branches.

This can happen when you:

• Open a folder in Site Pages, select Create or upload > Site Page, and publish the page.
• Use Duplicate on a page that is already in a folder.
• Use Upload HTML page from a folder view.
• Put an existing page or news post in a folder when it has no saved position in the tree.
• Create pages in folders with a script that does not save their tree relationships.

You can still open the file in Site Pages or find it with the tree’s title search. It can be missing from both the tree view and the Page Tree Editor. Reloading does not fix it.

WikiPakk stores the tree parent separately from the file’s folder. A page in a subfolder can appear at the tree root:

File location                 Saved tree placement
Site Pages                    Page tree
`-- Projects                  `-- Project Guide
    `-- Project Guide.aspx

Workaround

Use an account that can change the page hierarchy.

1. Open Page Tree and search for the page title.
2. Open the result’s three-dot menu.
3. Select Move to tree root.
4. Clear the search. Reload the page if needed, then check the tree.

This saves the page’s position in the tree without moving its file. You can then move its tree entry below another page. For a news post, this does not repair its automatic placement under News.

For pages created by a script, add or update a hierarchy-list row for each page. Set its parent to another page ID, or use 0 for a root. See Scripting the Page Hierarchy.

In tests, New > Page from an open page created the file in the library root. WikiPakk saved its parent. Pages in folders with saved tree positions also appeared in the tree. WikiPakk uses valid migration hierarchy data to place migrated pages.

Links after a folder rename

An open tree can keep an old page address after someone renames its physical folder in another tab. Clicking that entry can show 404 NOT FOUND, although the page still exists. The page ID and its saved tree parent stay the same.

Workaround: Reload the page that hosts the tree, then open Page Tree again. This loads the new file address.

Copied migrated pages

When SharePoint copies a migrated page, it can also copy its WikiTraccs metadata. The original and the copy then contain the same Confluence page ID. WikiPakk uses dates, the file name, and other page metadata to tell them apart.

If WikiPakk identifies the copy correctly, the copy does not use the original’s Confluence parent and child relationships. Its content remains available in SharePoint.

A copy can show the original’s children

WikiPakk can mistake a copy for the original when their dates or other metadata are too similar. The original and the copy can then show the same child pages.

Recommended workaround: Clear the Confluence metadata values from the copied page’s fields. This removes its link to the original Confluence hierarchy. Keep duplicate detection enabled.

Before moving, hiding or deleting a subtree, check the page list in the corresponding dialog. Cancel if it includes pages that should stay with the original branch.

For new pages, create a regular SharePoint page and copy the content into it.

An original can be identified as a copy

Unusual migration dates can cause WikiPakk to mistake an original page for a copy. WikiPakk then ignores that page’s Confluence hierarchy. The tree can show only top-level pages even though the pages and their migration fields exist.

The configuration guide explains how to check this case and when to disable duplicate detection. Use that workaround only for original pages that WikiPakk mistakes for copies.