|
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 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
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 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. :/
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. Month of talking and no result?
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....
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, Will they be reimported properly?
Yes, Import has never been a problem.
|
|||||||||||||||||||||||||||||||||||||||||||||||||||||||||||||||||||||||||||||||
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