You're on your way to the next level! Join the Kudos program to earn points and save your progress.
Level 1: Seed
25 / 150 points
Next: Root
1 badge earned
Challenges come and go, but your rewards stay with you. Do more to earn more!
What goes around comes around! Share the love by gifting kudos to your peers.
Keep earning points to reach the top of the leaderboard. It resets every quarter so you always have a chance!
Join now to unlock these features and more
The Atlassian Community can help you and your team get more value out of Atlassian products and practices.
Hi,
Using our Confluence onDemand, I am unable to move or re-order any pages except those in my personal space. I'm an administrator, so I do have view and add permissions on everything.
I've attempted this numerous times using drag&drop on the tree view via Browse -> Pages, as well as trying to move individual documents with tools -> move. In both cases the operation seems to be accepted but the page is never moved. No error messages are displayed.
Applying the workaround listed in the issue below solved the issue for us.
I found that the issue was trying to move a restricted view page to an area that's not restricted. I temporarily removed the view restrictions on the page and it moved to the new space and new location without an issue.
You must be a registered user to add a comment. If you've already registered, sign in. Otherwise, register and sign in.
Hello Mark,
This really looks like a permission issue, are you attempting to move the pages to a different space? In that case you may additional need permissions to do that, please note the following:
Notes about permissions:
To move a page, you need the following permissions:
- 'Add' permission on the page you are moving, and
- 'View' permission on the page's parent page. So if you are moving the page to a different parent, you need 'View' permission on the new parent.
To move a page into a different space, you also need:
- 'Delete' permission on the space you are moving from, and
- 'Add' permission on the space you are moving to.
Please add additional context to this thread if the above pondering does not solve the issue.
You must be a registered user to add a comment. If you've already registered, sign in. Otherwise, register and sign in.
Hi Mark,
It might be possible that the ancestor table is corrupted. You can rebuild it by going to <Confluence-url>/permissions/pagepermsadmin.action >> Rebuild.
Hope this helps.
Kind Regards,
Jing Hwa
You must be a registered user to add a comment. If you've already registered, sign in. Otherwise, register and sign in.
The available help articles (including the steps noted above) were unclear and did not resolve the issue for us. The issue was exacerbated by a deleted page in the tree on a versioned page.
The following steps were executed and finally fixed the issue.
- Disabled default logo (as referenced in the workaround)
- Rebuilt the ancestor
- Bounced the application
- Tailed server logs to ensure the application is error free, since the fixes were database related
Note: The last two items were executed in addition to what Atlassian recommended.
You must be a registered user to add a comment. If you've already registered, sign in. Otherwise, register and sign in.
Hi Mark,
Glad that you have found the workaround for now :). In the meantime I have reported this bug here:
https://jira.atlassian.com/browse/CONF-30068
All the best.
You must be a registered user to add a comment. If you've already registered, sign in. Otherwise, register and sign in.
Thank you, but that didn't seem to have any affect. The URL I had to use was <Confluence-url>/admin/permissions/pagepermsadmin.action as the one you posted wasn't found.
You must be a registered user to add a comment. If you've already registered, sign in. Otherwise, register and sign in.
The available help articles (including the steps noted above) were unclear and did not resolve the issue for us. The issue was exacerbated by a deleted page in the tree on a versioned page.
The following steps were executed and finally fixed the issue.
- Disabled default logo (as referenced in the workaround)
- Rebuilt the ancestor
- Bounced the application
- Tailed server logs to ensure the application is error free, since the fixes were database related
Note: The last two items were executed in addition to what Atlassian recommended.
You must be a registered user to add a comment. If you've already registered, sign in. Otherwise, register and sign in.
You must be a registered user to add a comment. If you've already registered, sign in. Otherwise, register and sign in.