Issue with Page Index after migration to XWiki: All the pages with no child-page became Terminal pages automatically

Help / Discuss
, , ,
1

Dear XWiki community,

I am not able to manage the access rights for some child pages under a parent page. The only option that I see when clicking on the three dots next to the child-page name is “Manage parent page” (“Übergeordnete Seite verwalten” in the image attached).

I think there was some issue with the Page Index when we migrated the pages and child-pages from simplewiki to XWiki in October 2025. This has happened to all the pages and child-pages that were migrated. However, all the child-pages that were created after the migration are connected correctly to the parent page.

There is an incosistency when viewing the page tree from different areas. E.g., when i see it from the homepage, I see all the child-pages, but when I check it while creating a new page or moving a page, it does not show the child pages that were created before migration.

Now, I need help with solving this issue. Is there any scalable way to reindex all the pages correctly again, because we have several parent pages like this which are affected?

Thank you for you help in advance :folded_hands:

Regards,
Anurag

homepage-view
homepage-view564×531 31.1 KB

manage-parent-page-option
manage-parent-page-option1140×213 16.4 KB

page-creation-view
page-creation-view700×328 19.5 KB

2

Hi @anegi,

Besides the Manage parent page, there is also another useful feature located in the Edit drowpdown section named Access Rights which allows you to manage the permissions of the current page.

3

One reason you see the 2 different document trees is that, in the first one, the hierarchy navigation displays all the pages while the second one, the creation menu, will only list the available pages that can be the parent of new pages (non-terminal pages).
Could you confirm that the 4 pages displayed as children of AHUB, in the creation form, are the only ones that are non-terminal pages? See more about Relations between Pages about page types.

4

Hi @acotiuga ,

Thank you for your reply. I am logged in as the Admin for XWiki and both the views are from same admin user. Unfortunately, I do not see a dropdown under Edit as I am not an advanced user and therefore I cannot create a Terminal Page either, as per my understanding.

Is there a way to check if the pages are Terminal or non-Terminal being a Simple User (Admin)?

However, as an adminshouldn’t I be able to manage the access rights for the pages even if the pages are Terminal pages?

5

You can change the user type from Simple to Advanced from your user profile preferences: https://www.xwiki.org/xwiki/bin/view/documentation/xs/user/user/edit-profile/edit-profile-preferences/.

6

Hi @acotiuga , thank you. So I was able to change my editing rights to ‘Advanced User’ and I checked for the pages. The four pages that I can see in ‘Create Page’ section are non-terminal pages (WebHomein page reference) and the others are Terminal pages (no WebHome in page reference).

7

So, all the pages that had no child page before the migration have become Terminal pages automatically. Please correct me if I’m wrong!
How can we bulk change them to non-terminal pages again?

8

I don’t think there’s an easy way, except through scripting. Maybe using the Nested Pages Migrator (but I don’t know its state as of 2026).

OTOH it’s easy to rename a page to be non-terminal. Note that you only need to make a page non-terminal if you intend to create children pages.

If you need a script, something like the following might work (generated by Gemini). You’ll need PR rights probably.

{{velocity}}
## --- CONFIGURATION ---
#set ($targetSpace = "TargetSpace") ## Change this to your space name
#set ($dryRun = true)                ## Set to false to execute
## ---------------------

#if ($dryRun)
  {{info}}**Dry Run Mode:** No changes will be applied. Set `$dryRun = false` to execute.{{/info}}
#end

### Batch Converting Terminal Pages in: $targetSpace

## 1. Query for terminal pages (those not named 'WebHome')
#set ($query = $services.query.xwql("where doc.space like :spaceName and doc.name <> 'WebHome'"))
#set ($query = $query.bindValue("spaceName", "${targetSpace}%"))
#set ($results = $query.execute())

#if ($results.size() == 0)
  {{warning}}No terminal pages found in space: $targetSpace{{/warning}}
#else
  |=Source Page|=Action|=Status
  #foreach ($docFullName in $results)
    #set ($sourceRef = $services.model.resolveDocument($docFullName))

    |$docFullName|Convert to Nested|
    #if (!$dryRun)
      ## 2. Execute conversion: (Reference, UpdateLinks)
      #set ($job = $services.refactoring.convertToNestedDocument($sourceRef, true))

      ## Wait for the job to finish to update the status in the table
      #set ($discard = $job.join())

      #set ($status = $job.getStatus().getState())
      #if ($status == 'FINISHED')
         (% style="color:green" %)Success(%%)
      #else
         (% style="color:red" %)Failed ($status)(%%)
      #end
    #else
      (% style="color:orange" %)Pending (Dry Run)(%%)
    #end
  #end
#end
{{/velocity}}
9

Did you use any existing tool or script to perform the migration? Some tools allow configuring how pages are created in the new XWiki structure, which can influence whether pages end up as terminal or non-terminal.

Right now, it’s possible to rename all those terminal pages and convert them into non-terminal ones. The simplest approach is to rename each page manually and un-check the “Rename as terminal” option.

If the number of pages is large, manual renaming becomes impractical. In that case, a script is the best solution to perform bulk renames efficiently.
Here is how you can convert a terminal document to a nested (non-terminal) document:
https://extensions.xwiki.org/xwiki/bin/view/Extension/Refactoring%20Module#HConvertaTerminalDocumenttoaNestedDocument

10

Thank you @acotiuga and @vmassol for your kind support. Luckily we did not have way too many Terminal pages. We were able to uncheck the ‘Termin page’ box for all the affected pages in ~15 minutes. Everything works now!