Compatibility and migration
Remote Content was rebuilt on Atlassian’s Forge platform, replacing the earlier Connect version. The rebuild keeps the macro key that existing pages reference, so macros already saved in your Confluence content continue to render after the upgrade. You do not need to recreate them, and you do not need to reopen them.
What is preserved
| Macro key | Unchanged, so every saved macro on every page keeps working. |
| Stored settings | All seven configuration keys are read on load and rewritten on save. |
| Licensing | The app remains a paid app under the same Marketplace listing. |
| Anonymous and unlicensed viewing | Still supported, matching the previous behaviour. |
Behaviour changes
The Forge version fixes several defects in the old one. Each fix is an improvement, and each can visibly change a page that relied on the broken behaviour.
| Change | What you may notice |
|---|---|
| Addresses that include a scheme now work | The old version corrupted any address written with http:// or https://, so those macros showed nothing. They now render. If a page has had a blank embed on it for years, expect it to come to life. |
A scheme-less address now uses https | The old version forced http. A target that is HTTP-only may stop loading; a target that redirects to HTTPS now skips a redirect. |
| Margin top now applies | It was stored but never rendered. A macro with a stored value will shift down by that amount. |
| Macros with no height are taller | An unset height produced a roughly 150-pixel sliver. It is now 400 pixels. |
| Refused embeds explain themselves | A site that forbids framing showed a blank box. It now shows a message and an Open in new tab button. |
If a page looks different after the upgrade, one of the five rows above is almost certainly why.
Editing a migrated macro
Open a migrated macro, change what you like, and save. The panel reads every stored key when it opens and writes every stored key when it saves, so settings you did not touch survive the edit.
Publish the page after saving, as you would for any macro change.
Retired capabilities
The old version was served from a host of ours. The Forge version is not: it runs entirely inside Atlassian’s platform, with no server of ours anywhere in the picture. Nothing about the macro’s configuration depended on that host, so there is nothing for you to migrate.
For what the app can and cannot reach now, see Security and limitations.