Problem
| Info |
|---|
Parent The parent page destination field is not populating properly correctly on the Copy Page Tree page |
...
Cause
We have determined that for relatively large spaces the Atlassian API our app uses for relatively large spaces does not return results , but rather times out. In other words, our app asks Confluence for a list of pages in the space, but Confluence does not respond with an answer. Thus, we've definitively determined that to be it is a bug in the Atlassian Confluence API. However, Atlassian has now deprecated that API and offered a newer REST API which means , so we have to rewrite large parts of the app. And Atlassian no longer supports the API we are using. At the time of When creating the app, we used that API because it was the only one available. We have identified that Confluence sometimes times out on the destination drop-down. This seems to be a proxy issue or bug with the JSON-RPC api API, which is not paginated.
Workaround
Copy the page tree to a "temp space" or
...
under a hundred pages so the "parent destination field" populates.
After the copy, you can navigate to the top of the new
...
page tree
...
and use the Confluence "Move" page feature to move the new page tree to
...
its ultimate destination.
Related articles
| Filter by label (Content by label) | ||||||||||||||||
|---|---|---|---|---|---|---|---|---|---|---|---|---|---|---|---|---|
|
...
|
...
| hidden | true |
|---|
...