How to revert to legacy editor
Asked by sumapathy:

I moved to the new editor, following the nudge. But after moving to new editor, i realized that editing is too slow. When I type a word the letters appear in slow motion on the page. This totally beats the purpose. Now I am looking to move back to the old editor \& unable to find the option.

The help says it possible. But does not state how


Answers:
author: Brant Schroeder
body: You can [contact support](https://support.atlassian.com/contact) to have the old editor enabled on your instance.

See the comment on [CONFCLOUD-65695](https://jira.atlassian.com/browse/CONFCLOUD-65695) for more details:
> Hi all,
>
> Thanks for all the feedback on this ticket. Given the amount of requests we've started to explore what a potential quick win may look like to re-introduce this. That being said, we still can't guarantee a time frame for this - we will make sure to update this ticket as we know more on our end.
>
> In the meantime, if you have the legacy template available - which most of you should have - you can keep using that to create new pages and still keep using this feature. If you don't have that template,[you can reach out to support](https://support.atlassian.com/contact) and we'll be happy to enable it for you.
>
> Thanks,  
> Avinoam

comments: author: sumapathy
body: Well. I do have legacy template. I can create a new page with legacy template and it opens old editor. No issues.

But I had opened an old page, which had lot of content. Wanted to try the new editor and moved to new editor. I am not able to work on this page. (please note this is not a page. it is a living document which I need to actively work on). I can not delete and create a new page with old template - cause this is a page that is tracked.

And I am trying to type on this and it is dead slow. I see what ever I type appear in slow motion on the new editor.

I need to conver this back to new editor. Else my productivity and core work is affected. I hope am making my "user perspective" clear here.


author: sumapathy
body: Excuse me if am coming across quite harsh.   
The core use case of confluence is to create content using an editor. If that editor is too slow isnt that an issue to even roll it out

Well even if it is released, shouldnt there be a appropriate roll back plan when the core feature is affected ?


author: Brant Schroeder
body: I am just a community member trying to help other community members out. Please submit a support ticket and see if Atlassian can rectify this issue for you.


author: sumapathy
body: Thanks. I was under the impression that the responses was from product support.

Thanks for helping out


author: Martin Rogers
body: You are kidding. A response from support?


author: S?rgio Paulino
body: I have the same issue, how could I revert back to legacy editor on a confluence page?


author: Adriane Hunt
body: Thanks! We did reach out to Support and now have the Legacy Editor template avialable to us.


author: PetesPiece19
body: I also vastly prefer the Legacy editor. It's been a while since I've used it, but try this:

1. Open Confluence and at the top of the page, select **Templates**.

2. On the **Templates** page, choose the **Legacy editor page** to create a new page using that editor.

Optionally:

1. Open Confluence and at the top of the page, select **Create**.

2. In the right side bar, select **Templates** , then search for **Legacy editor page**, and select that page.

This enables me to use that editor.

I am not an expert, nor do I work for Atlassian. Your instance of Confluence may vary, with different fields/features etc. but this works for me even today. I won't be providing more information than this, but I do hope it helps someone find that editor.

Best of luck.

comments: author: dennis_moul
body: I don't have a Legacy editor page in my list of 130 templates, but I've found that instead of creating a new page, if I copy an old page that was created with the legacy editor and then edit that page (removing all the previous content), it continues to use the sane legacy editor instead of the "we wanted to build neat things rather than what users actually need" new editor.


Tags: cloud