You're on your way to the next level! Join the Kudos program to earn points and save your progress.
Level 1: Seed
25 / 150 points
1 badge earned
Challenges come and go, but your rewards stay with you. Do more to earn more!
What goes around comes around! Share the love by gifting kudos to your peers.
Keep earning points to reach the top of the leaderboard. It resets every quarter so you always have a chance!
Join now to unlock these features and more
My name is Steven Bao, and I’m a Product Manager on the Confluence Cloud team. We’ve been working on the capability to bulk convert legacy editor content to the new editor and are excited to announce that we are in process of rolling out!
If you are a recent migrator from server/DC, you may have noticed that your migrated content stayed in the legacy editor. Today, you are able to convert pages from the legacy editor to the new editor, but only on a single page basis. With this functionality you will be able to bulk convert eligible content (some content, such as nesting is not supported in the new editor) from the legacy editor to the new editor on a space or site basis.
You must be a space admin to enable this at a space level. Navigate to:
Space Settings → Manage Space → Convert Pages
Toggle on “Convert Pages Automatically”
You must be a site admin to enable this at a site level. Navigate to:
Site Administration → Further Configuration
Check “Convert Pages Automatically”
When this setting is enabled, all eligible pages in the space/site will display using the new render in view mode, as well as the new editor in edit mode. Users will receive a notification of this conversion the first time they land on a page that was bulk converted.
Users will be able to revert the change from the dropdown menu in the top right hand corner if the page has not been published (in both view and edit). If the page has been published, they will need to revert from page history.
This change is also able to be reverted at the space or site level, but will not revert pages that have been published since bulk conversion.
Eligibility mainly depends on if the page does not contain nested bodied macros, as they are incompatible with the new editor. There are also some minor changes during conversion to certain macros described here: https://support.atlassian.com/confluence-cloud/docs/convert-pages-to-the-new-editor/
At this time, we will also be excluding conversion of pages created in cloud using the legacy template or pages that were converted to the fabric editor but reverted as we do not want to convert pages that are desired to be in the legacy editor at this point.
We’d love for you and your teams to try this functionality out and and let us know what you think in the comments below.
If you don't yet see this option today, you'll see it coming to your instance within the next few weeks. As a reminder, you must be a space admin to enable this on a space level, or a site admin to enable this on a site level.