Versions Compared

Key

  • This line was added.
  • This line was removed.
  • Formatting was changed.
Comment: Modified contents as per style guide and content consistency

...

panelIconIdatlassian-question_mark
panelIcon:question_mark:
panelIconText:question_mark:
bgColor#B3F5FF

Problem

Why do I see “This rendering mode is not supported.“?

Cause

The HTML Macro application is designed to generate dynamic macros for inserting I-frames insert the dynamic macro containing HTML markup into the Confluence pages, by default. However, it has limitations, especially when using Confluence's Native PDF Confluence’s PDF/Word export feature. Confluence does not support the export and rendering of dynamic macros in this scenario.

The only possible option in such cases is to use the static macros. Using static macros ensures compatibility with Confluence’s Native PDF export, addressing errors or limitations linked to dynamic macros.

Preview mode

...

export mode only works with static macros, and in most cases, Confluence macros usually have a static counterpart for each dynamic macro to enable smooth export. However, the content handled by our HTML Markup app cannot be rendered from within a static macro. 

A warning panel is shown whenever a user tries to export, notifying that this functionality is not supported. Refer to the screenshots below:

Preview mode

...

Exported to Word/PDF document

A warning panel is shown, notifying the user that this functionality is not supported.

...

Published page

...

Filter by label (Content by label)
showLabelsfalse
max5
spacescom.atlassian.confluence.content.render.xhtml.model.resource.identifiers.SpaceResourceIdentifier@1422e
showSpacefalse
sortmodified
reversetrue
typepage
cqllabel = "html-macro-cloud" and type = "page" and space = "HTMLM"
labelskb-how-to-article

...