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; } } }

Switch back to Legacy Editor

Sat Singh

Hi everyone,

I know a few people have been frustrated with the new editor and want to switch back to the legacy editor?

Is this just a matter of contacting Support and getting them to switch it back over in the backend?

If so can I raise a ticket to do this?

Thanks in Advance !

Sat

Accepted answers

Diego_88dj6o

Hello there @Sat Singh ! You are correct, this is a matter of raising a support ticket and requesting this change.

Please, keep in mind that doing this will not enable the Legacy Editor as default option for content creation. Also, no new features are being implemented for the Legacy Editor and bug fixing for it is also limited.

You can check more information on the request of the legacy editor here:

Change to your content is in your hands

With all this in mind, I went ahead and raised a ticket on your behalf with our support team. Keep your eyes peeled for an email about it!

Let us hear from you!

All comments

Brant Schroeder

Unfortunately, no. It is not simply a case of the "editor" changing. Atlassian is replacing the legacy XMHTL Confluence Storage Format with the new JSON-based Atlassian Document Format, which will be used across all its different products. You actually want Atlassian to provide better feature parity between the old and new.

Sat Singh

So does that mean it's actually not possible to switch the whole space to the legacy?

I assume all the spaces that people have created in the legacy XMHTL will still be compatible?

It seems like this chap was able to : https://community.atlassian.com/t5/Confluence-questions/Requesting-legacy-editor/qaq-p/1496244

Brant Schroeder

@Sat Singh

You listed on this post that you are on a free plan. I have escalated to Atlassian so they can help address your issue. If you are not on a free plan then you should submit an issue to support.

Sat Singh

Awesome thanks Brant!

Diego_88dj6o

Hello there @Sat Singh ! You are correct, this is a matter of raising a support ticket and requesting this change.

You can check more information on the request of the legacy editor here:

Change to your content is in your hands

With all this in mind, I went ahead and raised a ticket on your behalf with our support team. Keep your eyes peeled for an email about it!

Let us hear from you!

Jeanne Howe_56oel8

Please be sure to vote for this issue. As Admins, we should have the option for setting the default editor - Legacy or new Fabric.

default to "Legacy editor page" template when creating new pages in Confluence

My users much prefer the Legacy editor but have to select it every time they go to create a page. We should have the option to set the default editor for the instance, and the users should then have the ability to set their personal default at the profile level.

Anant Jain

Deleted.

I realized later that this issue refers to Confluence and not JIRA

Ahmet Kilic - T2T

Take a look at the page history you had a legacy editor on.

Welcome!

It looks like you're new here. Sign in or register to get started.

Quick Links

Find more posts tagged with

confluence

cloud

confluence-cloud

atl-rvw