My website is running on Conf 2.2.9 and I don't have any trouble with decks - the plugin pages are full of them.

Some possibilities:

1. Put each {deck} and {card} macro on its own line. Due to the hackery I had to do to get nesting working there are sometimes rendering issues caused if they share space with other content.

2. Are you using a custom theme? Themes are often missing some critical JavaScript includes which will render the page inoperable if not present.

David

Thanks for the quick reply.

I'm using the Left Navigation Theme - you're correct, if I use the default theme it does work.

Thanks,

Michael

I have had an idea to try working around the dependency problem - I'll keep you posted as to when/if it's implemented.

With Regards,
Dhivya.M

Also, as an aside, it's usually a good idea to have a {card} macros on their own line, rather than at the start of end of other content.

We are using theme builder. the space which was built by theme builder the code for composition plugin works fine.

But the code im using is in default Theme only doesnt works.

With Regards,
Dhivya.M

Confluence 2.1.2
Composition Plugin version 2.0
No custom theme
Each line of the macro is on its own line

I checked the error console in FireFox and it said "Element.show is not a function" - the offending line is:

Element.show(el);

Approvals Workflow Plugin

The deck & cards display fine on the 'View' tab, but not on the 'Published' version of the page. FF's error console shows the same error above (Element.show is not a function) for the Published view.

The 'View' and 'Published' versions are both decorated by page.vmd, but the plugin introduces a new mode (released) which is used to render the article's content differently in the mode-specific section (e.g. #if $mode == "view" ... #if $mode == "released").

The only differences I can see between the two blocks of code in our page.vmd are:

• "view" mode sets $labelable = $page
• "view" mode parses /labels/labels-include.vm

Our test installation is using Confluence 2.7.3, and it seems to work fine on both the 'View' and 'Published' tabs in that version. We'll be upgrading our live instance to the same version soon so I'll let you know whether that fixes the issue or not.

Hope the above information helps!

I added the following to the "released" mode decorating block:

<script type="text/javascript" language="JavaScript" src="$webResourceManager.getStaticResourcePrefix()/labels-javascript"></script>

I thought I'd look into the labels javascript in a bit more depth, and the Element.show function (and a bunch of others) are all defined in the above javascript.

Why on earth they decided to include a whole truckload of generic javascript in a 2389472189471 line file that only gets included if labels are present on a page is beyond me... but it seems that's what they did.

So my guess is that the custom themes that are broken do not parse /labels/labels-include.vm, or are parsing a modified version that does not include the above script.