Adding a Connect dynamic content macro with custom editor to the new template throws Cannot read properties of null

XMLWordPrintable

    • Type: Bug
    • Resolution: Fixed
    • Priority: Low
    • Component/s: Ecosystem
    • Severity 3 - Minor

      Issue Summary

      Adding a dynamic content macro with editor to the new template does not work, and we see the error below in the browser console.

      Uncaught TypeError: Cannot read properties of null (reading 'url')
    at window._AP._convertConnectOptions (com.atlassian.plugins.atlassian-connect-plugin:iframe-insertion-v5.js?assetVersion=1000.0.0-84bfa54b457619827&externals=__local-default__:5:786)
    at com.atlassian.plugins.atlassian-connect-plugin:content-resolver-v5.js?assetVersion=1000.0.0-84bfa54b457619827&externals=__local-default__:5:1423
    at v (batch.js?assetVersion=1000.0.0-84bfa54b457619827&externals=__local-default__&locale=en-GB:15:5)
    at batch.js?assetVersion=1000.0.0-84bfa54b457619827&externals=__local-default__&locale=en-GB:15:338

      Steps to Reproduce

      1. Create a Connect app with dynamicContentMacros with custom editor configuration
      2. Go to Space settings → Look and feel → Templates → Create a new template
      3. Add the dynamic content macro

      Expected Results

      The editor appears and works as expected.

      Actual Results

      The editor dialog appears, but shows Laoding app...

      and the error in the Browser Console shows

      Uncaught TypeError: Cannot read properties of null (reading 'url')
    at window._AP._convertConnectOptions (com.atlassian.plugins.atlassian-connect-plugin:iframe-insertion-v5.js?assetVersion=1000.0.0-84bfa54b457619827&externals=__local-default__:5:786)
    at com.atlassian.plugins.atlassian-connect-plugin:content-resolver-v5.js?assetVersion=1000.0.0-84bfa54b457619827&externals=__local-default__:5:1423
    at v (batch.js?assetVersion=1000.0.0-84bfa54b457619827&externals=__local-default__&locale=en-GB:15:5)
    at batch.js?assetVersion=1000.0.0-84bfa54b457619827&externals=__local-default__&locale=en-GB:15:338

      Workaround

      1. Create a new template and save first.
      2. Click on edit to the saved template and add the macro.

        1. Screenshot 2025-07-14 at 5.22.04 pm.png
          Screenshot 2025-07-14 at 5.22.04 pm.png
          37 kB

            Assignee:
            Roman Toropov
            Reporter:
            Ramchandra Kudtarkar
            Votes:
            16 Vote for this issue
            Watchers:
            8 Start watching this issue

              Created:
              Updated:
              Resolved: