Does not support nested macros which means Redirection macros cannot be placed in a nested container (such as inside an expand macro, etc.).Redirection application in cloud have the following limitations: Support of nested macros which means Redirection macros can easily be nested and integrated with other Confluence native macros or any third-party macros.
Monthly subscriptions are the default option, however, discounted annual subscriptions are available upon request to our Atlassian Sales team. Migrate to Redirection for Confluence using steps at Migration PathĪvailable through both Atlassian Marketplace and ServiceRocket Marketplace.Īvailable through Atlassian Marketplace only. Find details of each migratable macro below and the differences in terms of behavior once migrated to Cloud.You may see an "unknown macro" where the macros were originally positioned in the documents Migration for the following Linking macro works out of the boxįor macros that are migrated but are unsupported, the following applies: Look out for icons highlighting how the data will be migrated.Only some macros in are available in Cloud.Current status as at May 2021: Likely To Implement.Currently, Linking macro cannot be used with Scaffolding macro.Due to the above, other macro integration is difficult.Does not support nested macros, which means Linking macros cannot be placed in a nested container (such as inside an expand macro, etc).To learn more about the page conversion process, go to Converting pages to the new editor.Linking macros in cloud have the following limitations: You'll also have the chance to restore a page to its previous, legacy editor version after conversion. We want you to feel comfortable with the process. You'll also have the option to preview any page before converting it. When the page conversion functionality is available in your Confluence instance, you can pick and choose which pages get converted and when. Our goal is to allow you to convert your pages from the legacy editor to the new editor without data loss and with little to no changes to the look and feel of the content. Since there are some differences in the capabilities available in the legacy editor and those in the new editor, we want to make it abundantly clear what will happen to your content when you convert a page. We won’t be converting your pages for you because we know that you know your content best and can decide when it’s the best time to convert your content.
CONFLUENCE ROADMAP PLANNER WIDTH FULL
If you have a Confluence instance full of pages created using the legacy editor, you have the option to convert those pages to the new editor. All new features and enhancements are made to the the new editor.
0 kommentar(er)
