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?
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?
Yes - See Wiki Markup to XHTML Migration > Re-running Migration in our Planning for Confluence 4.0 documentation.
Thanks a lot Matt for pointing this out. Must have overseen this in the dokumentation.
You must be a registered user to add a comment. If you've already registered, sign in. Otherwise, register and sign in.
Online forums and learning are now in one easy-to-use experience.
By continuing, you accept the updated Community Terms of Use and acknowledge the Privacy Policy. Your public name, photo, and achievements may be publicly visible and available in search engines.
You must be a registered user to add a comment. If you've already registered, sign in. Otherwise, register and sign in.