Confluence 4.3 incorrectly translates deck/cards wiki of the Customware Composition plugin when upgrading from 3.5.16

[Julio Mugabe]

We use the deck/card macros to create tabs on our pages and this has been working okay on 3.5.16. However we are testing out new upgrade 4.3 and the pages dont render these macros as before. This is a huge blocker we have over 1000 pages that use this macro, updating them manually is not feasible. I raised this issue with Customware and they mentioned to me that the issue is with the Confluence upgrade translation.

The links below further explain the problem and the issue does not seem to be with this 3rd party plugin but rather how Confluence translates the deck/card..wiki

• http://community.customware.net/customware/topics/deck_and_card_not_working_as_expected_and_nullpointerexception_error_in_the_page

• https://answers.atlassian.com/questions/57516/navigation-tabs-not-displaying-in-confluence-4-2-1

[Eric Koepfle]

I found this as well, when going from 3.5.17 to 5.0.3. What a PITA!

[Michael Roff]

Check to see if the name of your decks have any spaces in them. If they do, remove them and see if that makes a difference. There might also be a problem with special characters, so I recommend removing those as well just in case.

To test this you don't need to go through the whole upgrade again, just change your wikimarkup and then paste it into Confluence 4 using the insert wiki markup option.

[Davet]

Sorry about the misleading info...our decks and cards migrated to 4.x and are rendering perfectly because we don't nest decks.

[Davet]

Hmmm...if I were you I would be upgrading to 4.2.x

It is a bit soon to be upgrading to 4.3.x as you have found

[Bob Swift OSS (Bob Swift Atlassian Apps)]

I don't think it is just a 4.3 problem, it is a 4.x problem.

[Bob Swift OSS (Bob Swift Atlassian Apps)]

Have you tried surrounding the entire deck/card markup with the wiki macro from Wiki Plugin for Confluence ? I would expect this to revert to the Confluence 3.x behavior. If this does work, then there are ways to automate adding this to pages using How to automate adding text to Confluence pages or similar. Of course you need to do this on Confluence 3.x BEFORE the page gets migrated.

[CharlesH]

One approach might be to do a space export (XML) then unpack this and edit the file(s) representing the wiki content. In a tool like Notepad++ you should be able to use search/replace and regular expressions to correct the nesting of the deck macros as explained by Eng Liew Lee. After that, remove the space from Confluence and then reimported the re-packed XML export. I would advise doing this on a test platform first to gain confidence in the process.