nav[aria-label="Primary Navigation"] { padding: 0; & ul { list-style: none; width: 100%; display: flex; flex-direction: row; justify-content: start; align-items: start; gap: 30px; padding: 0; & li { margin: 0; } & ul li { list-style: none; } } }

Roll back to old editor?

Robin Roos_citpea

Hi Founders,

Regarding : https://community.atlassian.com/t5/Confluence-questions/Why-are-the-toolbar-formatting-options-for-Overviews-and-Pages/qaq-p/1072778

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.

Accepted answers

Dario B

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:

Most of the instances still have the old editor enabled. You just have to choose the legacy editor page template:
In case you don't have the legacy editor template then:
- If you are site admin and you are on a standard plan you can create a support request in order to ask to have the old editor enabled: https://support.atlassian.com/contact
- If you are on a free plan you can create a new thread here in the community asking to have the old editor enabled for you and we will open a support request on your behalf.

For more details, please see: How we roll out the new editor in Confluence

I hope this helps.

All comments

Shannon S

Hello Robin,

Welcome to the Atlassian Community and thank you so much for bringing this up to us. I wanted to let you know that I separated your comment from the older thread as it deserves its own topic. In addition, the previous thread was a bit old and I wanted to make sure your thread was seen. I hope that's alright with you.

Regarding the new editor, it is not possible to revert to the old editor, I wanted to discuss the feature you mentioned as well as some other options.

Tables in the editor can be set to 3 widths:

Full width
Wide
Center

You can change between these widths by clicking on the blue arrows to the right of your table when you hover over it with your cursor. Unfortunately, at this time, center is the smallest you are able to set tables in the new editor.

There's a feature request created below that you can vote on in order to show that this feature is important to you and is something you'd like to see in the new editor:

CONFCLOUD-61917 Responsive column widths in tables

Using the Excel Macro you could embed the spreadsheet as it is in Excel, although the display of this macro is not adjustable.

In general, we are working on upcoming features for tables amongst other things, as you can see in the Confluence Cloud Editor Roadmap.

Any feedback you have regarding the editor can be shared in one of the following ways:

Click Send Feedback under Help Us Improve in the left-hand avatar menu on your instance. This will be seen directly by the development team.
Join the public conversation at Try out the new editing experience. This will be seen by the project managers for the new editor.
Set aside 30 minutes of time 1:1 with the head project manager. You can do so by adding an appointment to his calendar.

Thank you again for this feedback, and for help in making the editor what Confluence users want to see.

Regards,

Shannon

Roland_Peer

This means I have to manually adapt my tables (and I have many of them).

You guys are burning through the goodwill I have for Confluence very quickly. I know you need your new layout so it looks neat for the next decade but it's annoying to constantly being told to vote for something I have been using for years. I can put up with not finding existing features anymore (I had to endure this with MS Office Ribbon as well and in the end it turned out okay). But they didn't remove features!

Shannon S

Roland,

Thank you for providing that feedback on the new editor! Please be sure to share that feedback as well with the product manager directly, using the resources I've shared above. Let me know if you have any trouble!

Regards,

Shannon

Son Le_7dmv57

Hi @Shannon S

How can I back to old editor version?

Thank you!

Bec Honey

Hi Shannon, I don't understand how you can refer people to a ticket - as if you're doing something, then we see this?: allow images inline.jpg

I'm confused... How many times, and in how many places must we report what we want back?

You've already closed the duplicate ticket associated to it. Surely anything to do with images, inline, resizing etc should be looked at as a high priority since its affecting how older pages look now they're converted?

Shannon S

Hi Bec,

I'm really sorry, I can certainly see how that's misleading. I'd like to clarify that further for you.

A feature request does not necessarily require a certain number of votes before we work on it. There's more information in our policy on implementing new features about what leads a requested feature to be implemented, but there are lot more factors:

When we plan a release, we use many factors to help decide which suggestions to implement, including:

Customer feedback - there are many ways we listen for your feedback:
- formal customer interviews and other research activities
- events like Atlassian Summit, developer conferences, and road shows
- in-product feedback from evaluation and EAP (early access program) releases
- comments and votes on issues in https://jira.atlassian.com/, our public issue tracker
- questions and posts on Atlassian Community.
Support team insights - our support team know which issues are the most challenging, and most common for customers.
Solution partner insights - our solution partners help us better understand real-world customer deployments, especially for customers at scale.
Product analytics - analytics are used from Cloud customers and opted-in Server customers, which helps us understand how existing features are being used.
Product strategy - our long-term strategic vision for the product.

We have been actively including new features that are requested, but there are many still need to be prioritized. The Confluence Cloud Editor roadmap will show you more about which features have been already prioritized in our upcoming roadmap. If a request is not yet in the roadmap, then we haven't been able to prioritize it yet and are still in the information gathering stage. That's the case with this feature request.

Regarding the duplicate case, it closed because it's a duplicate of an existing open feature request. We want to make sure that people are following the request that contain updates about the feature. The duplicate requests won't be updated so we close those to avoid any confusion.

What you can do to help this process along is to provide your input on the ticket itself, via the feedback option on your Cloud site, or directly to the product manager.

Take care,

Shannon

David_Gray

The new editor is awful. Why should Atlassian make an arbitrary decision to restrict how their users leverage the tool? I have lost lots of features that allowed me design clearer, more attractive pages and to clean up pages with issues.

Specifics I have run into just today:

1. When I paste in a document, I no longer can show a preview of the contents.

2. I am trying to convert some Word documentation to Confluence pages. When I paste in a table from word, I'm getting a dark blue background with black text - almost unreadable. I could just convert the text to white - until now.

3. I would like to indent portions of the document for readability and context. Can't do that.

4. Sometimes it is helpful to add a yellow background to call attention to key points. Now my best option is change the text color. Couldn't you have left that function in place?

5. Sometimes in a numbered list of items, it is useful to add an image or table in line with the list. I can't do that any more.

If you wanted to offer a product that was a bare-bones wiki, why not make that an alternative to the old experience and see how many of your users choose that option.

Apparently, Atlassian believes they know what I want better than I do. This is really just unbelievable.

Tim Wrathall

I'm not so concerned about new/missing feature, I'm more concerned about the general performance of the new editor. For the past week the user experience when I edit a page has been nothing short of terrible.

As an example, there is a noticeable delay when I enter text into a table cell, and when it displays on the screen. It's quite frustrating when you're trying to take notes in a workshop, and you need immediate playback to the audience. I'm using the latest version of Chrome to edit. Both Safari and Edge are not options.

When in editing mode, it looks like Confluence detects a network dropout, then quickly reconnects. I tried to edit on multiple different networks, but still the same issue.

Advice, thoughts, and workaround all greatly appreciated.

Soltész András

Yep, it is an unmitigated catastrophe. You switch to a new component when it is at feature parity with the old one. Not a second before.

The exact same as with the new JIRA boards that nobody wanted and lost valuable features (like being able to see closed tickets).

The new editor doesn't seem to have basic features like search and replace.

I have no idea why Atlassian is doing this but it will not serve them well. They are hamoraging goodwill and mindshare.

Michał Gleba

JUST ROLL BACK TO THE OLD EDITOR !!!

No questions about it.

The new one is piece of shit and shouldn't be rolled out to the public use anymore.

Following @Bec Honey : How many times, and in how many places must we report what we want back ?

Dario B

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:

Most of the instances still have the old editor enabled. You just have to choose the legacy editor page template:
In case you don't have the legacy editor template then:
- If you are site admin and you are on a standard plan you can create a support request in order to ask to have the old editor enabled: https://support.atlassian.com/contact
- If you are on a free plan you can create a new thread here in the community asking to have the old editor enabled for you and we will open a support request on your behalf.

For more details, please see: How we roll out the new editor in Confluence

I hope this helps.

Leo Hsu_t4q3f6

Great, much appreciated that you've considered the negative feedback surrounding the new editor! Thanks for enabling a roll back to the old editor, I'll reach out to support to have this done as soon as possible.

Leo Hsu_t4q3f6

Hi @Dario B I reached out to Atlassian Support and was told that the window to roll back to the old editor had passed. Could you please help? Thanks!

Dario B

Hi @Leo Hsu ,

EDITED: I have found your support ticket and I left an internal note for the engineer handling it. Let me know in case of any problem.

Have a nice weekend,
Dario

Alexandr_Reznic

"Allow me to elaborate on what I was trying to say there. There are many features that existed in the old editor, but have since been removed or temporarily delayed in the new editor. "

Allow me to elaborate on this cynical answer. When a vendor intentionally starts DOWNGRADING the product while continuously raising the pricing, he will inevitably face the market consequences.

Atlassian seems to be on the brink of chain reaction in which existing clients will start migrating to cheaper and more predictible platforms while new ones will avoid rolling in because of the inherent risks.

Think about it, guys, before it's too late.

Leo Hsu_t4q3f6

I was able to roll back to the old editor after contacting Atlassian Support, referencing this particular community thread. We're all much happier now, hopefully you'll be able to do the same!

Korina Skhinas

When is the Companion app going to be compatible with the new editor? This rollout completely disabled our collaboration workflow on editing files.

https://confluence.atlassian.com/confcloud/edit-files-724765124.html

Please help!

Jake_f9d5sb

There is no way to contact Atlassian if you have a free cloud account. This means the people with that account type can not use the suggested remedy to contact support and ask them to switch it back for you. I guess if you don't give them money you're sol. I did find a possible solution and I posted it here just bit ago tonight.

Best Regards

Jake

Jake_f9d5sb

I just found a hack that works. It turns out there is a "Copy" option in the drop down list in the upper right corner of every page.

Screenshot_2020-04-26 Blank Page Template (with expanded editor features) - jfines - Confluence.png

Make a copy of your personal page (or any template page that has the additional editor features in it) and delete everything in the body of the page except the title. Delete all the macros and the sections, everything in that copy. Then name is something like Blank Page Template (with expanded editor features) and save. It will become a child page to whatever space or page you are when you save it. Now you can make a "Copy" of that page and move it to where you want and it will have all the editor features in it.

I'm sure there is a better way and even with this there is probably a couple more steps that would make it even better. I'm not saying it's the most elegant solution, but it is one solution and it's easy (even for someone like me that don't know much about this here thing).

hth

Jake

Dario B

@Jake If you have a free account you can create a thread here in the community (saying that you want the old editor enabled) and we can open a support request on your behalf.

unknown

This is IMHO sub-optimal solved, specially stating here "You'll also have the chance to restore a page to its previous, legacy editor version after conversion" - but without stating that this needs to be done via the support and without a simple roll-back function.

Based on the feedback, this is not very user friendly nor customer orientated.

Simona Pappacena

Hi Founders,

I try to create a new page or a task or every thing else but is impossible: the (new) editor is gray and all is not modificable.

No collaboration is possible without that funtions.

it works fine only if you import a word page or if you use the web app

I need support (we need)

thanks you

Dario B

Hi @Simona Pappacena ,

As written in the accepted answer for this thread, support can re-enable the old editor if needed, but we first need to know a bit more about the issue you are facing.

I am not sure what you mean when you say:

the (new) editor is gray and all is not modificable.

No collaboration is possible without that funtions.

it works fine only if you import a word page or if you use the web app

Can you kindly provide more details?

Specifically:

How do you access Confluence? What do you mean exactly when you say that it only works if you use the web app?
What happens when you try to create a new page?
Does it make any difference if you try to create a new page in a new space or in an existing one?
Can you provide a screenshot of the editor being all greyed out?

Finally, for the future, please notice that adding a reply to an old thread already marked as solved is decreasing your chances to get an answer. Create a new thread instead.

Cheers,
Dario

Russell Wagner_qqts2k

Confluence has gone from having the most intuitive and easy-to-use table editor I've ever used to something unimaginably bad, confusing, and annoying. A crying shame. Why do software companies always have to change things that no one wants changed?

Michał Gleba

I fully agree with you. The same is with the searching tool while you're creating links and many other "new ideas" going into absolutely wrong direction.

This is good example how to break something working well: the change just for change even the change becomes thing worst instead of better.

I don't know if it's present in other languages: in Poland we sometimes say "better is enemy of good". The new confluence editor fit to it fully. ;-(

Soltész András

I find that mysterious myself. The old editor was more than capable, there was no need to change.

I guess there are underlying technikal reasons but the error was still huge.

Ship a new product when it is ready to replace the old one. Not a second before. Definitely not a half-baked shite with half the features of the old one.

Simona Pappacena

Hi @Dario B ,

Thank you for support,

I'm happy to tell you that I added to Confluence Jira Core

and this addition probably solved the issue.

Now the new editor works and I can create or modify any tipe of item (blank page, blog posts, etc) both in Confluence and in Jira.

cheers

Simona

Mark Farnan

Just stumbled on this problem and thread myself. What an awful decision to remove functionality that many people relied on. Who signed off on that? Goodwill is hard to gain and easy to lose. I wonder what they're going to remove next? Let me check what other solutions are out there that are adding capabilities rather than removing them.

Dam Nguyen

I don't know why the new version is created and why it isn't deleted now by the team, totally awful, I'm stuck with the page after edited content and cannot save now, just click "Publish" with no hope, the editor from hell !!!!

Andrew_vv9bta

Enough, the new editor has new functionality which is an improvement in many ways while there is some work to go for getting feature parity on some critical elements. Dynamic table sizing is much improved as well as table editing and usability.

Go look at a website that doesn't use dynamic design elements, it is clunky and very dated looking. Confluence needs to bring back some levels of control like centering and defining overall table widgth and especially bringing back image re-sizing controls. But enough with the immature responses to new technology and features, have some empathy for a team that is trying to make improvement over time.

Russell Wagner_qqts2k

The missing elements I miss are the very intuitive and easy to use buttons for adding and removing rows and columns to a table, as well as setting rows and columns as headers. Confluence used to have the absolute most user-friendly table editor I've ever used, but now it is among the hardest to use and least intuitive I know.

Michał Gleba

@Andrew S I'm very sorry - there's no place for trying and having empathy while it's getting worse and we have to pay for it. Have a look at other comments regarding people's experiences with the new editor.

Example from @Russell Wagner : "Confluence used to have the absolute most user-friendly table editor I've ever used, but now it is among the hardest to use and least intuitive I know." We love old table management, there's no need to change it. Another similar example is with inserting links: the old way is absolutely fantastic, the new one absolutely unuseful. There are many other examples...

Could you please start hear some feedback from the market / users ? I believe the new editor uses some amazing technology, but it is unuseful at all.

Andrew S

FYI you mentioned me, not the Andrew that replied above.

Joe Eugene_6rcpdm

+1 same issue

How can i switch back to old editor?

Dario B

Hi @Joe Eugene ,

Welcome to the Atlassian Community!

Let me try to summarize what's been already written to everyone else asking the same question in here:

Most of the instances still have the old editor enabled. You just have to choose the legacy editor page template:
In case you don't have the legacy editor template then:
- If you are site admin and you are on a standard plan you can create a support request in order to ask to have the old editor enabled: https://support.atlassian.com/contact
- If you are on a free plan you can create a thread here in the community asking to have the old editor enabled for you and we will open a support request on your behalf.

I hope this helps.

Cheers,
Dario

ryanbeck

When can we expect basic features such as jira task creation with more than Title and Description fields available?

Joe Bloggs

Atlassian got this terribly wrong. Having to copy pages from "template" just to be able to keep the proper old editor is quite inconvenient.

Dario B

Hi @Joe Bloggs ,

As already mentioned multiple times in this thread, you don't need to use any workaround to be able to use the old editor. Indeed, if you scroll a few rows up you can read:

Let me try to summarize what's been already written to everyone else asking the same question in here:

Most of the instances still have the old editor enabled. You just have to choose the legacy editor page template:

In case you don't have the legacy editor template then:
If you are site admin and you are on a standard plan you can create a support request in order to ask to have the old editor enabled: https://support.atlassian.com/contact

If you are on a free plan you can create a thread here in the community asking to have the old editor enabled for you and we will open a support request on your behalf.

karan_70pfur

Hi @Dario B ,

could you please enable legacy editor for my instance.

https://prod-3.atlassian.net/

cheers,

Karan

Dario B

Hello @karan ,

I have created JST-634601 on your behalf in order to have TinyMCE re-enabled on https://prod-3.atlassian.net/.

Cheers,
Dario

Christa_pp78gg

Hi @Dario B - Could you please enable the legacy editor for https://veridianinfo.atlassian.net.

Thanks,

Christa

Dario B

Hello @Christa ,

Welcome to the Atlassian Community!

I have created JST-638649 on your behalf in order to have TinyMCE enabled on your instance. Please follow-up in there.

Cheers,
Dario

Joe Eugene_6rcpdm

Atlassian

Please stop messing with Legacy Editor confluence editor. Many people have complained about the new editor with 100% width tables.

Please put *Legacy Editor* back in my confluence!

Thanks

Joe

Dario B

Hello @Joe Eugene ,

I can see you already have a support ticket open with us (JST-639882). Please follow-up in there, that's the right place to get the old editor (re-)enabled.

Cheers,
Dario

kevin.danaher

How can I have the legacy page set as the default template when people hit the create button in my space? There are various features of the old editor that we commonly used and this change is just making a mess of our space.