Confluence Page displaying legacy content and has limited functionality, how can i fix it? i tried looking up article but was not successful
Hi ravi kanth, that banner shows up when a Confluence page still contains content created in the legacy editor β from your screenshot it looks like the ConfiForms form on the page is rendering in legacy mode. The quickest fix: click the 'Make edits' button in that banner. Confluence opens the page in the editor and offers to convert the legacy content to the new format β accept the conversion, check the layout (form layouts can sometimes shift), then publish. If the banner returns, try re-editing and re-publishing the page once more, and make sure your ConfiForms app is on the latest version, since macro compatibility is usually what triggers this message. One tip: make a copy of the page first as a backup before converting, just in case the layout needs cleanup. Hope that helps!
Thanks for taking a look into post , I have tried looking for convert option but I'm having hard time finding it . Posting screen for reference . Can you let me know is it right location where convert option is present i.e. top right with three dots? Is Convert to live doc?
Hello @ravi kanth
Your page is already using the new Cloud editor. The warning appears because your ConfiForms content is preserved inside a Legacy Content macro, likely due to unsupported nested macros.
Atlassian confirms this is expected behavior, and there's no separate conversion button for that content.
https://support.atlassian.com/confluence-cloud/docs/the-legacy-content-macro/
If your form still works, you can leave it as it is.
Best,
Arekπ€ π§ββοΈ
Hi @ravi kanth, there isn't a convert option to find here, so you're not missing anything. @Arkadiusz Wroblewski nailed it: your page is already in the cloud editor, and Confluence wrapped the ConfiForms form in a legacy content macro because it uses nested macros the new editor doesn't support. The banner is a heads-up, not a sign anything's broken. If the form works, I'd leave it. You can still edit inside the macro, just make sure you're the only one in the page when you do, since Atlassian warns collaborative editing there can lose data. To lose the banner entirely you'd need to rebuild the form outside the macro, and only plain text copies out, so I'd ask Vertuna's support for their recommended cloud-editor setup first.
@ravi kanth as others pointed out, it's the macro rather than the page itself.
Now, I'd maybe suggest checking Atlassian Administration for any/all legacy apps that might need to be switched from Connect to Forge (potentially including ConfiForms) > more info on that here: Connect End of Support: What it means for private/custom apps π (it's not that fun, I'll say immediately π )
You could also check with Vertuna (app vendor) to see if they have any insights or tips&tricks about this π
Cheers, Tobi
It looks like you're new here. Sign in or register to get started.
