Skip to end of metadata
Go to start of metadata

You are viewing an old version of this page. View the current version.

Compare with Current View Page History

« Previous Version 9 Next »

Background

Sometime after March 31, 2024, a still unknown incompatibility between the Spring Boot Framework and the Confluence Cloud REST endpoints led to edit permissions no longer being deleted . When an edit permission can’t be deleted the “Edit Permission Inheritance” might be incomplete/not consistent. This means that child pages might contain edit permissions which they shouldn’t.

The issue has been fixed on 2024-05-08. We sincerely apologize for any inconvenience caused by this issue.

Example

An edit permission inheritance was defined on a parent-page with John and Marie having an edit permission. Later John has been removed on the parent-page. The child pages however still hold have an edit permission for John.

What you should do

You should check whether all active “Edit Permission Inheritances” are consistent. To do so please perform the following steps:

Step

Details

1

Get all active “Edit Permission Inheritances” by navigating to the following URL:

https://example.atlassian.net/wiki/search?cql=editinheritenabled%3D%22true%22

2

Navigate to each of the pages returned by the search and click on the Edit Permission Inheritance icon.

image-20240508-191240.png

3

Once the dialog opens the app searches for an incomplete inheritance. In case it detects issues a warning like this one is shown:

Inheritance seems to be inconsistent. 1 (2770927747) descendants seem suspicious.

Fix those pages

4 (UPDATED)

Please inspect those pages and

  1. Remove additional edit permission manually or

  2. Switch on the option “Remove additional edit permissions during inheritance” at least temporary and click on “Fix those pages”. ⚠️ Please note that this variant will also remove edit permissions which have been added to a child page manually.

Background: the app knows that something went wrong during inheritance on a specific page but did not keep records of what went wrong => a fully automated fix is unfortunately not possible.

We are currently evaluating options to allow an easier detection an manual fix of the affected pages. We will update this page with more details soon.

5

Move to the next page and re-start with step #2.

💡 You might use additional tabs of your browser to speed up the process.

Questions/concerns

Please feel free to open a ticket here. We sincerely apologize for any inconvenience caused by this issue.

  • No labels