Create
cancel
Showing results for 
Search instead for 
Did you mean: 
Sign up Log in
Celebration

Earn badges and make progress

You're on your way to the next level! Join the Kudos program to earn points and save your progress.

Deleted user Avatar
Deleted user

Level 1: Seed

25 / 150 points

Next: Root

Avatar

1 badge earned

Collect

Participate in fun challenges

Challenges come and go, but your rewards stay with you. Do more to earn more!

Challenges
Coins

Gift kudos to your peers

What goes around comes around! Share the love by gifting kudos to your peers.

Recognition
Ribbon

Rise up in the ranks

Keep earning points to reach the top of the leaderboard. It resets every quarter so you always have a chance!

Leaderboard

Come for the products,
stay for the community

The Atlassian Community can help you and your team get more value out of Atlassian products and practices.

Atlassian Community about banner
4,465,501
Community Members
 
Community Events
176
Community Groups

After import space, all pages have ghost restrictions from unexacting in import parent. $permission.

Source: Confluence Server 7.5.0

Space originally be a part of bigger space with parent restrictions.

All restrictions was removed via built-in script runner function.

 

Destination: Confluence Data Center 7.4.4

Imported space without any errors. All work fine for admin user.

User cannot see the content below home page. No restrictions are shows on space admin / restrictions.

 

We look also on page information:

Error on page information

Page PermissionsRestrictions from parent pages:

  • Page: *** – Only $permission.userSubject.name can view this page.

 

I've made some script runner script to get all descendent from main page, and after that for every page I get parent and setting this information again via PageManager. It fixed the problem, but we search better solution for that, or fix in the xml file.

 

Other observation:

When we reorder the pages, reordered pages start to work without missing ghosty restictions.

2 answers

1 accepted

0 votes
Answer accepted

Re-index and clearing the cache helps!

Cache clearing and reindexing did not help for me, but 'Repair ancestors table' did:

 

https://confluence.atlassian.com/doc/rebuilding-the-ancestor-table-153948.html

Suggest an answer

Log in or Sign up to answer
DEPLOYMENT TYPE
SERVER
VERSION
7.4.4
TAGS

Atlassian Community Events