Issue Details (XML | Word | Printable)

Key: CONF-7283
Type: Bug Bug
Status: Resolved Resolved
Resolution: Fixed
Priority: Critical Critical
Assignee: Jens Schumacher [Atlassian]
Reporter: Michael Thorpe
Votes: 4
Watchers: 3
Operations

If you were logged in you would be able to see more operations.
Confluence

Space export does not export restricted pages.

Created: 07/Nov/06 05:54 AM   Updated: 07/Aug/08 02:54 AM
Component/s: Export Page / Space
Affects Version/s: 1.4.4
Fix Version/s: 2.7.1

Time Tracking:
Not Specified

File Attachments: None
Image Attachments:

1. screenshot-1.jpg
(15 kB)
Environment: Tomcat 5.5. Red Hat Linux 2. JDK 1.5.7
Issue Links:
Reference
 

Participants: Dave Loeng [Atlassian], Don Brown [Atlassian], Don Willis [Atlassian], Jens Schumacher [Atlassian], Max Vit, Michael Thorpe and Oleksii Gnatkevych
Since last comment: 36 weeks, 5 days ago
Internal Complexity: 5
Resolution Date: 15/Jan/08 12:41 AM
Internal Value: 8
Labels:


 Description  « Hide
I am attempting to upgrade Confluence 1.4.4 to 2.2.9.

We have a large confluence installation with > 100,000 pages.

I cannot do a complete backup/or restore so I have been attempting to export individual Spaces. However any page which has been restricted ( plus any children of that page ) is not exported.

I have checked the export file and the page has not been exported into the file.

It seems possible that the export honours the permissioning model and disregards the fact that I am the administrator.



 All   Comments   Work Log   Change History      Sort Order: Ascending order - Click to sort in descending order
Don Willis [Atlassian] added a comment - 09/Nov/06 01:13 AM
No doubt the restricted pages can't be exported so that users can't gain access to those pages just by exporting the space. But it seems fairly reasonable that an admin user could override those restrictions, given that they could just export the entire space anyway.

I suggest you open a support request at http://support.atlassian.com so that we can help advise on your upgrade. For example, you could use method 1 described here:
http://confluence.atlassian.com/display/DOC/Upgrading+Confluence


Michael Thorpe added a comment - 09/Nov/06 06:02 AM
Don

Thanks for your feedback.

Now I know I am being dumb here but I thought that this was the Confluence Support Site!!! I have done as you suggested and opened an issue @ support.atlassian.com. What is the difference between these two sites?

Also

I have attached a screen shot of the message on the Upgrade page that you referred to which states that method 2 MUST be used to upgrade from 1.x to 2.x.

Regards

Michael


Don Willis [Atlassian] added a comment - 09/Nov/06 05:43 PM
Hi Mike,

jira.atlassian.com is for reporting bugs or making requests for new features in our products.

support.atlassian.com is for getting help with a specific instance of our product.

So you were right to create a bug here about export not working the way you think it should work (although I've changed it to an "improvement", since many would argue that it works correctly now).

However, for for us to help you with your specific problem of upgrading your confluence installation, you create a support request.

One of the big differences between the sites, is that the issues you create at s.a.c are by default visible only to you and Atlassian, so that you can discuss the details of your system and upload logs without publishing them to the world.

Cheers,
Don


Michael Thorpe added a comment - 10/Nov/06 03:27 AM
Don

I will make any further comments on the issue opened on the Support site - unless there is anything that may be useful to the rest of the world.

Michael


Don Brown [Atlassian] added a comment - 18/Oct/07 07:23 PM
This is a problem for Confluence Hosted as well. Since we are doing the export as an administrator, we should be able to export all pages. It causes a lot of headache for us right now as we have to take off all restrictions, migrate the space, then ask the user to re-enable the restrictions; not to mention, it makes us look rather incompetent. :/

Jens Schumacher [Atlassian] added a comment - 19/Oct/07 03:28 PM
I just got of a call with a customer who would like to migrate his hosted space to a Standalone version. Unfortunately they used page permissions heavily and are now unable to migrate their content.

This will hit us more and more so we should fix it as soon as possible.


Oleksii Gnatkevych added a comment - 26/Nov/07 03:28 AM
Month of talking and no result?

Max Vit added a comment - 26/Nov/07 08:46 PM
Why provide page permission restrictions if that will prevent a space to be exported properly by an administrator? What I am hearing here is that spaces can't be confidently exported unless you remove all locks and then re-enable the restrictions. We have a test instance and a production instance of confluence; we spent a lot of effort in preparing spaces with restrictions on the test instance only to find out we couldn't transfer this to the production instance....

Dave Loeng [Atlassian] added a comment - 10/Jan/08 10:43 PM
Fixed in 2.7.1.

Export space will now give space admins and confluence admins the option to export all content in a space (including pages that they cannot see due to page level restrictions).

Cheers,
Dave


Oleksii Gnatkevych added a comment - 15/Jan/08 02:47 AM
Will they be reimported properly?

Jens Schumacher [Atlassian] added a comment - 24/Jan/08 06:22 PM
Yes, Import has never been a problem.