Legacy editor compatible with Forge

Alberto Barón March 12, 2024

Hi!!
I have a client that has migrated from Server to Cloud its confluence. Inside, they contains legacy editor pages that are in the cloud environment but with some macros not working.

For some customized macros, they decided to create some Forge apps but now we are in a trouble:

- We can use Forge apps in new editor pages but it won´t work in all pages with legacy editor.

- We can convert legacy editor pages to new editor pages but some macros like panel won´t work. 

 

One option that we has though is to create Atlassian Connect apps instead of using Forge apps.. but I have read that this won´t be a good solution because in some time it will be removed... (I am not sure if it was official documentation). 

 

Could you help me to choose the correct path before wasting more time ?

 

Thanks!!!

 

2 answers

1 accepted

0 votes
Answer accepted
marc -Collabello--Phase Locked-
Community Leader
Community Leader
Community Leaders are connectors, ambassadors, and mentors. On the online community, they serve as thought leaders, product experts, and moderators.
March 12, 2024

Hi @Alberto Barón ,

It seems you are in a difficult situation.

Indeed, some Forge macros won't work in the legacy editor, and some old macros don't work in the new editor.

If you would move to Connect macros, I understand that there is no deprecation date for Connect at this moment.  I would think that Connect will work for years to come, because Forge has not yet reached feature parity.

Alberto Barón March 19, 2024

Hi!!
I have moved to atlassian connect apps and I´ll test that everythig works. 

Thank you

0 votes
Shawn Doyle - ReleaseTEAM
Community Leader
Community Leader
Community Leaders are connectors, ambassadors, and mentors. On the online community, they serve as thought leaders, product experts, and moderators.
March 12, 2024

This is a common dilemma when migrating to the cloud. 

The path I'd recommend is systematically going space by space and page by page converting to the new editor, and then updating the non-working macros to the closest equivalent that is available. I'd favor the forge over connect, but I wouldn't reject the connect ones out of hand as @marc -Collabello--Phase Locked-  mentioned, you may have years of availability left.

I'd copy a set of troublesome pages first, to test and find which equivalent addons/macros will work best before attacking any live pages full-on.

It's tedious. 

Suggest an answer

Log in or Sign up to answer
DEPLOYMENT TYPE
CLOUD
PRODUCT PLAN
FREE
PERMISSIONS LEVEL
Site Admin
TAGS
AUG Leaders

Atlassian Community Events