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

Permanent Disable the "Get the latest editing experience" Pop-up

yunncsie

Hi Everyone,

My pages are currently using the Legacy editor and it's working smoothly. However, it's really annoying that every time I want to edit a page, I have to click 'Edit' and then 'Not now' to dismiss the 'Get the latest editing experience' pop-up box. I'd like to stick with the Legacy editor. Is there a way to remove the prompt forever? So that I can go directly to edit a legacy page without any hassle.

Accepted answers

Rebekka Heilmann (viadee)

Hi @yunncsie and welcome to the Community,

with these In-App Adverts it tends to be quite complicated to get them removed. Some can be removed through a support Request, others are hard-coded and cannot be deactivated at all.

I am not sure whether there is an updated timeline, but the legacy editor will likely be deactivated eventually anyway.

Your best bet however is contacting the Atlassian Support and check whether they can do something about the pop-up - that is assuming you are on a paid plan.

All comments

Rebekka Heilmann (viadee)

Hi @yunncsie and welcome to the Community,

with these In-App Adverts it tends to be quite complicated to get them removed. Some can be removed through a support Request, others are hard-coded and cannot be deactivated at all.

I am not sure whether there is an updated timeline, but the legacy editor will likely be deactivated eventually anyway.

Your best bet however is contacting the Atlassian Support and check whether they can do something about the pop-up - that is assuming you are on a paid plan.

Alex Koxaras -Relational-

Hi @yunncsie and welcome to the community,

I doubt if support can do anything for that matter, especially if they are promoting the new editor. I would expect at some point to force you to use it, and in my opinion it seems the logic thing to do. My advice is to just start using the new editor. Why prolonging the inevitable?

patric_s8eoq8

Because when you have a large amount of pages already created with the old editor, it's a mess to update - the layouts are all messed up, images are improperly scaled, etc.
It would take us weeks to migrate existing articles.

Not counting that some features of the old editor are still not working with the new one, so we would lose allll of our Dynamic image links (the reason why we never used it in the first place).

patric_s8eoq8

Came here to ask the same question but that was already answered, thanks

Very alarmed to read your comment @Rebekka Heilmann _viadee_ about the Legacy being deactivated, I thought they had backed out of this idea years ago. Is there an official date announced? This will have a cataclysmic impact on our project

Rebekka Heilmann (viadee)

Looks like there currently is no set deadline (see Understanding legacy editor element conversion in Confluence Cloud | Confluence | Atlassian Documentation and i also double checked partner updates on this) but you won't benefit from any new features and the new editor is getting more and more capabilities that make me miss the old experience less and less.

Tina-Louise Allaire

I have hundreds of Confluence pages what were created in legacy and prefer to keep them that way since It's formatting fit my needs better.

This has cause several people hours of cause they clicked on Update page on the popup not know it would mess up all their formatting.

It would take me months to fix all the formatting from converting my old legacy page (which are full 200 pages each on average when pdf printed) to the new editor and a lot of my functions would be gone.

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