Forge Confluence macro not available on legacy editor

Forge
, ,
1

Hi all,

i’ve developed a page-version tool as confluence-forge-macro (UI-Kit). The customer has a lot of pages in the legacy-editor format. But the forge-macro is not available on the legacy-editor pages.

My Question:
Is this a bug or a feature? I didn’t found anything about this issue in the documentation. Is there anything i can do, to use the macro in legacy-editor pages.

Turning all pages into the actual editor version is not acceptable by the customer, because they’ve many, many pages using the legacy format and on the other hand they will using legacy-macros wich will not run with the new format.

Best Regards

Gunther

4 Likes
2

Hey Gunther,

Unfortunately, Forge apps won’t work with the legacy editor. It’s not really a feature or a bug, just that the legacy editor is in maintenance mode and all new features and enhancements will be made in the new editor (which includes support for Forge).

Thanks for raising the lack of clarity in the documentation, I’ll raise it with our content team.

3 Likes
3

Hey Adam,

What will the migration path be for customers coming from server/DC? As all content is migrated to the legacy editor, does this prevent any app that has a pre-existing server/dc offering from ever becoming exclusively a Forge app? My reading is that app vendors who also haven’t yet created a cloud offering of a server product also couldn’t start building with Forge.

Cheers!

2 Likes
4

Hey @AdamMoore , any chance for some guidance on this :point_up: Cheers!

6

@AdamMoore We are investigating migrating one of our connect macros and this issue popped up as a potential blocker, as after cloud migrations many customers are left with many pages on the legacy editor until they are manually converted.

I have searched but cannot find any existing docs or feature request for this issue - do you know if this is still the case and no improvement is planned? With recent announcements about revenue share, it would be extremely unfortunate to need to keep a connect module for legacy editor macros indefinitely.

2 Likes
7

Was a public ticket ever raised on this?

8

@daviddrawio Not that I can find, unfortunately.

9

I think it’s also important to note that the Confluence team has shared that the Legacy Editor is being deprecated early 2026.

10

@SeanBourke Unfortunately, its still problematic - as our macros still often end up inside the new legacy content macro - e.g. if its in a very large page that cant be converted to new editor. Its not clear to me if our Forge macros will render in this context.

1 Like
11