Converting a Connect on Forge Macro to Forge Macro causes adfExport to be used in Preview Mode instead of render for current Macros

XMLWordPrintable

    • Type: Bug
    • Resolution: Unresolved
    • Priority: Medium
    • Component/s: Ecosystem
    • Minor

      Issue Summary

      When converting a Macro in manifest.yml from

      confluence: 
           dynamicContentMacros: 
            ...
            renderModes: 
               default: 
                 url: /macro-render.html
      

      to

      macro: 
        ...
        adfExport: 
          function: exporter
      

      Any macros that were created when the app was pure Connect or using the Connect on Forge format (that is, rendered with an <iframe/> and all.js, when viewed in Edit -> Page Preview will display using

            adfExport: 
                function: exporter
      

      instead of the same as with Page View.

      Steps to Reproduce

      1. Add a Connect on Forge macro to a page that has a renderModes section
      2. Convert the macro in manifest.yml to a pure Forge macro, which uses UI Kit or Custom UI
      3. Edit the page
      4. Select ... -> Preview

      Expected Results

      The Preview looks the same as View mode

      Actual Results

      The adfRender is called instead of the normal render (depending on UI Kit or Custom UI)

      Workaround

      Currently there is no known workaround for this behavior. A workaround will be added here when available

              Assignee:
              Unassigned
              Reporter:
              James Richards
              Votes:
              0 Vote for this issue
              Watchers:
              1 Start watching this issue

                Created:
                Updated: