Content gets mixed up by using Include page macro
Asked by Marian Vidra:

Hi guys, any idea why the content of the page gets randomly spread out on the page after using of 'Include page macro'? The original content is in the order but then it gets mixed up. Is there any other way how to edit/fix it or should be any other macro used instead?

![Original.PNG](/t5/image/serverpage/image-id/84301i039E246A30B15AA5/image-size/large?v=v2&px=999 "Original.PNG")

The original content (above) is in the order but then it gets mixed up. Even in preview it looks alright (see the picture below).

![Preview.PNG](https://community.atlassian.com/t5/image/serverpage/image-id/84429iE2ACB5BCA16C261C/image-size/large?v=v2&px=999 "Preview.PNG")

But once it's Saved it gets randomly spread out all over the page.

![Include page macro.PNG](/t5/image/serverpage/image-id/84303i93BE35DD480DE905/image-size/large?v=v2&px=999 "Include page macro.PNG")

Is there any other way how to edit/fix it or should be any other macro used instead?


Answers:
author: Diego
body: Hello [@Marian Vidra](/t5/user/viewprofilepage/user-id/3778358) !

As I understand, when a page is included inside another the formatting is lost inside the page where it was included.

With the behavior in mind, I have a couple questions for clarification:
> 1. *Is the original page (the one being included) using the New Editor (Fabric) or the Old Editor (tinyMCe)?*
> 2. *Is the page which received the inclusion using the New Editor (Fabric) or the Old Editor (tinyMCe)?*
> 3. *Is this happening with any page that you try to include?*
> 4. *Is any other user able to see this problem?*

You can identify the new and old editors based on their toolbars. Here is what they look like:

**New Editor**
> ![Screen Shot 2020-04-24 at 12.56.00.png](https://community.atlassian.com/t5/image/serverpage/image-id/92081i059617573F4848F3/image-dimensions/584x31?v=v2 "Screen Shot 2020-04-24 at 12.56.00.png")

**Old Editor**
> ![Screen Shot 2020-04-24 at 12.56.11.png](https://community.atlassian.com/t5/image/serverpage/image-id/92082iE641187FF38BE15D/image-dimensions/583x28?v=v2 "Screen Shot 2020-04-24 at 12.56.11.png")

Let us hear from you!

comments: author: Marian Vidra
body: Hello [@Diego](/t5/user/viewprofilepage/user-id/1188952)

Correct, when a page is included it gets spread out all over the page.

1. The original page is using New editor

2. The page which received the inclusion is using New editor as well

3. Old editor inclusion to New editor worked fine

4. It's stored on public space which means it's accessible and visible to everyone including our customers


author: Diego
body: Hello again [@Marian Vidra](/t5/user/viewprofilepage/user-id/3778358) !

Thanks for the extra information. During this time between replies, I was able to find this bug:
> * ++***[\[Confluence Cloud\] Include Page macro displays content in legacy editor style](https://jira.atlassian.com/browse/CONFCLOUD-66520)***++

This means that the Include Page applies the Legacy Editor (tinyMCE) styling to everything inside it. The result of such behavior is that pages created with styling exclusive to the New Editor (Fabric) will have severe inconsistency when included in the Macro.

Currently, there is no workaround for this behavior. The only way to avoid it would be to keep using the Legacy Editor when creating new pages. As you have noticed, Legacy Editor pages do not suffer from the behavior described.

If you do not have the Legacy Editor, you can request it. More information can be found here:
> * ++***[\[Atlassian Community\] Change to your content is in your hands](https://community.atlassian.com/t5/Confluence-Cloud-articles/Change-to-your-content-is-in-your-hands/ba-p/1324476)***++

I hope this clears things up! Looking forward to your reply.


author: Marian Vidra
body: Hello [@Diego Canto Rodrigues](https://community.atlassian.com/t5/user/viewprofilepage/user-id/1188952)

Don't get me wrong but this is not what I expected.

Firstly, I got your answer after 2 months since I raised this issue.

Secondly, you just informed me you found the bug but there is no workaround for it. By the way, that Jira issue was opened a year ago.

I can't imagine we'd provide such delayed support to our customers and then just inform them we found a bug and let it sit there for a year.

Regards,

Marian


Tags: cloud

confluence-cloud