Hi everyone,

This is Anna from the Confluence team. Thank you for previously raising this bug and bringing it to our attention.

Within our company roadmap and work capacity, we try to address or review each bug request but admit that not each one will be resolved. To continue the culture of being honest and open, we are closing this bug to focus on our upcoming roadmap for all Confluence users.

As we continue to roll out features we do look at requests made by our users and if you feel like this bug is still impacting your team please let us know by posting a comment and we will review.

Thank you again for providing valuable feedback to our team!

Best,

Anna

Hi Anna.

My comment is from nearly 3 years ago. For all I know you have already fixed this bug in a later release. I wouldn't know because we simply stopped using Confluence for the project I manage. The lack of support was a major factor in this decision, and Confluence did not provide the reliability we needed.

Thanks,
Tom

Hi everyone,

This is Anna ** from the Confluence team. Thank you for raising this bug and bringing it to our attention. After our investigation into this issue, we weren’t able to reproduce the described behavior within our instances. We didn't get `Unsupported content` error.
We would like to get to the root cause of what you’re experiencing. Could you provide some more details or a screenshot to help us narrow down this case?

We will keep this issue open for another 14 days, but if we don’t hear back by then we will need to close this out to focus on our upcoming roadmap for all Confluence users.

Best,

Anna

I am receiving this error when I edit a child page's content template. But, it happens intermittently. 

Steps:

Create a template

Create a child page

• Click on the "+"
• Search for template
• save the page
• edit the page by moving / editing a template component
• Publish

Error= You will receive the Unsupported Content Error

Expected Result: Edits should be saved

Workaround: Go to page history, revert to previous/ Edit the page, redo the work in steps, saving more often.  

If you need to edit the template components, go to the global template editor, select your template to edit and save. 

BUT, even after trying to work with the template in the global template editor and using the template without editing, I still receive the error on occasion. 

Same experience as Simone and Cody.

I experience the same as Simone, from the above comment. Usually this only occurs when I copy a page and then after editing and publishing, the page will be blank.

Same issue repetitively. 

The worst scenario I have experienced of this occurring, is when I have created a new page and it occurs on the first save. I cannot retrieve anything I have added to the page, and am left with a blank page, starting from scratch again.

Same issue Liz D described.

I was having the same issue, which was quite annoying. Sometime, I was at least still able to export the confluence page to Word to rescue the content, sometime I was not. 

However, I was able to reproduce the issue as described by Liz with one difference. In my case, the error occurred only when using H1 headlines. 

When re-styling a confluence area, this might get a huge issue. In our case it's at least annoying as we now know how to avoid that...

Nevertheless, I would be happy if somebody from Confluence could have a look into this. 

There are multiple scenarios that trigger the "Unsupported Content" error, beyond what is described in the summary & steps to reproduce, so maybe this bug ticket should be renamed to be more specific?

In my experience, this is most consistently caused by the following steps:

1. Insert at least one Layout section macro.
2. Type a line of text in one of the Layout columns.
3. Apply a heading style to that text (I've seen it with H1 - H3, but maybe lower heading styles also cause the same issue)
4. Select the line of text, cut it (ctrl-x), and paste it in a different column.
5. Publish the page.

Now you're likely to see the "Unsupported Content" error.

What I've noticed is that the problem is triggered during Step 4. When you cut out a line of Heading text and paste it somewhere else, the original location still has a Heading style applied to the now-blank spot. In other words, there's an empty Heading.

This is specifically a problem when the empty Heading is left inside of a Layout Section, although it's possible that it can occur elsewhere too (inside other macros or in tables, perhaps).

I imagine that it may have something to do with the fact that Heading styles automatically generate anchor links, so maybe the page breaks whenever the system tries to generate an anchor link from an empty Heading. I assume it doesn't know what to do when it fails to find a string of text for the anchor. I'm not sure, but maybe it's worth looking into.