During the upgrade of Confluence to version 4 all the content will be migrated to a new storage format. As this might fail for some content there is a fallback: Snippets of wiki markup that can not be migrated will be wrapped in a macro called unsupported-wiki-markup. There might be different causes for the migration to fail, like a deactivated macro or a macro with a body that can not be migrated. However, some of those problems might be fixed later (e.g. by reactivating or upgrading the plugin). So afterwards the unsupported-wiki-markup macro might not be needed anymore.
Will this be detected somehow by the system? E.g. when a page is stored.
Alternatively, is there a way to rerun the migration process for the whole Confluence instance so that unnecessary occurences of an unsupported-wiki-markup macro are removed?
This community is celebrating its one-year anniversary and Atlassian co-founder Mike Cannon-Brookes has all the feels.Read more
Hi Community! Kesha (kay-sha) from the Confluence marketing team here! Can you share stories with us on how your non-technical (think Marketing, Sales, HR, legal, etc.) teams are using Confluen...
Connect with like-minded Atlassian users at free events near you!Find a group
Connect with like-minded Atlassian users at free events near you!
Unfortunately there are no AUG chapters near you at the moment.Start an AUG
You're one step closer to meeting fellow Atlassian users at your local meet up. Learn more about AUGs