How to remove unnecessary occurences of unsupported-wiki-markup macro?

Tino Winkler [Communardo] September 29, 2011

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?

1 answer

1 accepted

1 vote
Answer accepted
Matt
Atlassian Team
Atlassian Team members are employees working across the company in a wide variety of roles.
September 29, 2011

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.

Tino Winkler [Communardo] October 3, 2011

Thanks a lot Matt for pointing this out. Must have overseen this in the dokumentation.

Suggest an answer

Log in or Sign up to answer
TAGS
AUG Leaders

Atlassian Community Events