Issue Summary

This is a very specific issue, so please, make sure to read all the description.

When we export a space that has pages on the new editor, containing Gliffy/Draw.io diagrams, from an instance that has both editing experiences to an instance that has only the new editor, the diagrams get broken with a 404 error.

Environment

• Cloud

Steps to Reproduce

1. On the instance with both editing experiences (instance A), create a page using the new editor on a space and add a Gliffy/Draw.io diagram;
2. After publishing the page, go to Space Settings > Content Tools > Export and export the page we created to XML;
3. On the instance with the new editing experience (instance B), go to Settings > Import Spaces and upload the .zip file from A;
4. After importing the space to B, access the page we added the diagram.

Expected Results

The diagrams are shown on the imported page.

Actual Results

The diagrams get broken, showing a 404 error.

Notes

• According to the information we have from the Draw.io support team, it seems that there is a call failing, which is the APgetLocation()

  om.atlassian.plugins.atlassian-connect-plugin:ap-navigator-v5.js?externals=_local-default_:33 no context function defined
  getLocation @ com.atlassian.plugins.atlassian-connect-plugin:ap-navigator-v5.js?externals=_local-default_:33
  b.handleRequest @ com.atlassian.plugins.atlassian-connect-plugin:ap-core-v5.js?externals=local-default_:52
  c.receiveMessage @ com.atlassian.plugins.atlassian-connect-plugin:ap-core-v5.js?externals=local-default_:65
  com.atlassian.plugins.atlassian-connect-plugin:ap-navigator-v5.js?externals=_local-default_:33 no context function defined
  getLocation @ com.atlassian.plugins.atlassian-connect-plugin:ap-navigator-v5.js?externals=_local-default_:33
  b.handleRequest @ com.atlassian.plugins.atlassian-connect-plugin:ap-core-v5.js?externals=local-default_:52
  c.receiveMessage @ com.atlassian.plugins.atlassian-connect-plugin:ap-core-v5.js?externals=local-default_:65
  com.atlassian.plugins.atlassian-connect-plugin:ap-extensions-v5.js?externals=_local-default_:64 Refused to get unsafe header "ETag"
  (anonymous) @ com.atlassian.plugins.atlassian-connect-plugin:ap-extensions-v5.js?externals=_local-default_:64
  q @ com.atlassian.plugins.atlassian-connect-plugin:ap-extensions-v5.js?externals=_local-default_:64
  f.onload @ com.atlassian.plugins.atlassian-connect-plugin:ap-extensions-v5.js?externals=_local-default_:68
  load (async)

• If we do the same steps, but adding the diagram on a page with the old editing experience, it the imported page shows the diagram fine on the instance B

Workaround

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