Hi Founders,
I don't want ANY of this.
If I want to edit a website I will use WordPress.
When doing Wiki I want the OLD editing experience.
I do NOT want fixed-width tables, which require me to spend effort on layout.
I do want the old data-width tables, so I can just CREATE the 1x1 table, paste the data I had prepared in Excel, and save the page.
The new experience is shit for Wiki users. Please immediately revert Confluence Cloud instances, and then provide the option to exploit new/old experiences. Or, even better, just remove the "new" experience altogether.
Same site, different pages, same content pasted from exactly the same Excel workbook.
How can I get tables to look like the bottom one (auto_suppliers) when working with the "New" Editor Experience (auto_suppliers_fullwidth)?
Is it time for a new Wiki?
I'm hugely unimpressed.
Kind regards, Robin.
Hello,
EDITED 2/2/2021 (since this seems to be still unclear):
Let me try to summarize what's been already written to everyone else asking the same question in here:
For more details, please see: How we roll out the new editor in Confluence
I hope this helps.
Justin,
Just wanted to let you and anyone else stumbling on this post that there is no way to ship data directly from 3.4.1 to 4.3.
In order to use Space XML export/import you will need to upgrade your legacy system up to 4.3. Your upgrade path is going to be 3.4.1 - > 3.5.17 -> 4.3 to ensure that you pick up the new user management piece in 3.5.x.
From there you can follow the documents linked above to do the space import and export to get your legacy data into your new instance.
Thanks Daniel,
I noticed the same information you provided in the documentation that Ramiro linked to, and am awaiting a response from the person in charge of that data space within our organization. We currently have 3.4.1 and 4.3 installed simultaneously on different resources, and I believe they would like to keep 3.4.1 as an in-tact resource for a while until 4.3 is brought up to speed as to mitigate any possible complications. I'm not sure how the licensing goes, but is it possible to duplicate our 3.4.1 installation, upgrade that as per your suggestion, and then once completed scrap our existing 4.3 install? I'm not sure if that's something that can be done with however licencing is registered, etc.
You must be a registered user to add a comment. If you've already registered, sign in. Otherwise, register and sign in.
Justin,
That is not a problem at all. Setting up a test envinronment and performing the upgrade in test is a great idea. You will be able to export your spaces unfettered.
What 4.3 instance do you want to scrap? The instance you are upgrading to 4.3 right?
You must be a registered user to add a comment. If you've already registered, sign in. Otherwise, register and sign in.
Thanks Daniel,
We have a current 4.3 install that is for the most party void of any data, so that is what we would scrap once the conversion up to 4.3 is done on a duplicate of our 3.4.1.
You must be a registered user to add a comment. If you've already registered, sign in. Otherwise, register and sign in.
Hey Justin here you can read about restoring confluence sites or restoring spaces:
And here's another thing you could use:
You must be a registered user to add a comment. If you've already registered, sign in. Otherwise, register and sign in.
Justin,
Just wanted to let you and anyone else stumbling on this post that there is no way to ship data directly from 3.4.1 to 4.3.
In order to use Space XML export/import you will need to upgrade your legacy system up to 4.3. Your upgrade path is going to be 3.4.1 - > 3.5.17 -> 4.3 to ensure that you pick up the new user management piece in 3.5.x.
From there you can follow the documents linked above to do the space import and export to get your legacy data into your new instance.
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.