Copy Page Tree - Cloud conflicting page titles for private pages
To avoid page title conflicts, the Copy Page Tree app must make pages unique in the destination space.
When copying within a single space, when the destination space IS the origin space, hidden pages in the copied page tree can cause trouble. A hidden page has restrictions that prevent the copying user from seeing the page. They don’t know it is in the tree they are copying.
If you use Search/Replace for the page titles, do not add a unique prefix to the title, and copy within a single space, you can run into trouble for a hidden page. If the hidden page has some title that is not matched by your Search/Replace, then the title will remain unchanged during the copy, and it will fail:
Unexpected response code: 400:
com.atlassian.confluenc.api.service.exceptions.BadRequestException:
The copied pages have conflicting titles. e.g. My Private Draft.
Please specify a page title prefix to avoid conflict.When you are in this situation, an admin (not just a site admin) must use the Space Settings tool to view Permissions. Then, go to Restricted Pages, where you can see an entry for the problem page. The title of the problem page is in the error message, like My Private Draft in the above example.
The admin can click on the lock icon for the hidden page to access a summary for the page:
From the page summary, the admin user can “View Page History,” view the current version, and delete the problem page. That is the brute-force fix. A better way is to contact the user who created their page and have them rename it to fit in with your Search/Replace scheme or delete it themselves.
A user who can set page restrictions can cause trouble in a space. This is only one example of the problem that private pages can cause. That is why Confluence does not, by default, grant this ability to most users. You should carefully consider this ability before granting it to all your users in a space.