We’ve had a report from one of our customers that our dynamic content macros stopped working recently, showing the message
[confluenceUnsupportedBlock] instead of rendering correctly.
The customer indicated that the same problem had started occurring with a number of macros (not only ours).
Initially we were unable to reproduce the error that the customer was reporting, but later we discovered that the customer was one of the initial instances to have received the new Confluence editor.
Once we learned this, we were able to reproduce the problem ourselves by creating a new blog post in one of our test instances (90% of all cloud instances now use the new editor for blog posts).
In our case, the affected macros are
The developer blog post for the new editor mentions changes required to bodiless (
bodyType: none) and rich text (
bodyType: rich-text) macros to support the new editor, but says nothing about plain text macros.
Are there any known workarounds for this?
There are a number of
CONFCLOUD tickets open on JAC relating to issues with the new editor, so it could be a genuine bug in the editor (in which case we sincerely hope that Atlassian have suspended any further rollouts, as this has the potential to cause widespread issues).