Versions Compared

Old Version 7

changes.mady.by.user Chris Matkaris

Saved on

compared with

New Version 8

changes.mady.by.user Madzy Soetman

Saved on

Key

  • This line was added.
  • This line was removed.
  • Formatting was changed.

Note that this page covers how to migrate only Refined Toolkit from Server/Data Center to Cloud. Click here if you are also migrating Refined for Confluence.

...

Info

Macros on Cloud might look and work a bit differently - click the links to read the documentation.

Server and
Data Center

Cloud

UI Button

UI Button

  • Supported settings: Title, URL, Tooltip, Size, and Color

  • Unsupported settings: Icon, Display, Open in a new window

  • It’s not possible to set custom color profiles on Cloud

  • URLs are static. If they link to local pages and blog posts in Server/DC, you need to manually change the link to the new URL in Cloud

UI ChildrenUI Children

Child Pages

  • Supported setting: Page

  • Unsupported settings: Display, Columns, Sort children by, Reverse sort

UI Children Cards

Turns into a UI Children Child Pages macro with the cards display mode

UI Expand(s)

UI Expand (sContainer)

  • Supports the same settings as on Server/DC

UI Image

Images are migrated if you have Refined Toolkit Cloud, but they are not editable. To add images in Cloud, simply insert them in the Confluence Editor.

UI Step(s)

UI Step (sContainer)

  • Unsupported setting: Size

UI Tab(s)

UI Tab (sContainer)

  • Supports the same settings as on Server/DC

UI Text Box

Turns into a UI Panel

  • Supported setting: Type

  • Unsupported settings: Text size, Show icon

  • It’s not possible to set custom color profiles on Cloud.

-

UI Activity Stream

-

UI Page Tree

- 

News

-

Content Layout Editor

Preparation guide

When you migrate to Cloud, you edit your pages in Confluence Cloud’s legacy editor. This editor is similar to the one you are used to from Server/DC. While Atlassian recommends you to convert your pages to the new editor, this may pose problems with some of your migrated macros.

On Server/DC it is possible to nest macros which contain content within one another. These are called bodied macros. This is essential to the functioning of some Refined Toolkit macros: for example, you place content in a Step macro within a Steps Step Container macro.

Due to a Confluence Cloud limitation, it is not possible to nest bodied macros in the new editor on Cloud. So when you convert a page with a nested body macro from the legacy editor to the new editor, the macro becomes uneditable.

...

  1. In Confluence, go to General Configuration.

  2. In the left-hand menu, find the Administration heading and click Macro usage.

  3. In the overview, look for the app Refined Toolkit for Confluence.

  4. Click these macros to see on which pages they are located:

    • UI Expands (contain UI Expand Container (contains Expand macros, which contain bodied content)UI Tabs

    • (contain UI Tab Container (contains Tab macros, which contain bodied content)

    • UI Steps (contain UI Step Container (contains Step macros, which contain bodied content)

  5. Take out the content out of each macro and paste it directly on the page. You can re-create the setup after migration, using the Cloud equivalents of these macros.

...