Migrate macros from org.radeox.macro.Macro to com.atlassian.renderer.v2.macro.Macro

XMLWordPrintable

    • 5

      NOTE: This suggestion is for Confluence Server. Using Confluence Cloud? See the corresponding suggestion.

      Macros that implement org.radeox.macro.Macro get wrapped by a com.atlassian.renderer.macro.RadeoxCompatibilityMacro at runtime. This compatibility wrapper sets an attachment path in the render context which, once set, becomes fixed for the entire page render. Our embedded image renderer checks this context path and uses it without question once a value has been set. As the compatibility macro sets the path to be the attachment path for the current page, it breaks embedded images from other pages. In essence any macro that implements org.radeox.macro.Macro will break images embedded from other pages.

      We don't want to "fix" this behaviour as doing so would affect all macros that implement this interface and we would recommend that macros now implement the com.atlassian.renderer.v2.macro.Macro interface instead.

      In light of this we should migrate the macros that confluence ships with to use the new interface as well.

            Assignee:
            Unassigned
            Reporter:
            Christopher Owen [Atlassian]
            Votes:
            0 Vote for this issue
            Watchers:
            1 Start watching this issue

              Created:
              Updated:
              Resolved: