Default card in deck not being respected

  • 2
  • Problem
  • Updated 2 years ago
  • (Edited)
Hello

After upgrading our Dev Confluence instance from 5.8.10 to 5.9.7, the default card in a deck macro on (at least one) of our pages is no longer being respected. The Composition add-on version has not changed and remains at 5.1.1.

Rather than default to the first card ("Welcome"), as it did before, it now defaults to ""First Aiders").

Here is the source of my page:

<ac:structured-macro ac:macro-id="6aa72c8f-4b38-4323-be8b-2b954fc6b527" ac:name="deck" ac:schema-version="1">
  <ac:parameter ac:name="id">FLINT3</ac:parameter>
  <ac:rich-text-body>
    <ac:structured-macro ac:macro-id="55b44879-41dc-4568-b023-bbfc9318ee39" ac:name="card" ac:schema-version="1">
      <ac:parameter ac:name="default">true</ac:parameter>
      <ac:parameter ac:name="label">Welcome</ac:parameter>
      <ac:rich-text-body>
        <p> </p>
      </ac:rich-text-body>
    </ac:structured-macro>
    <ac:structured-macro ac:macro-id="2a8cc42c-2f0e-4988-9c80-27d777f62158" ac:name="card" ac:schema-version="1">
      <ac:parameter ac:name="label">First Aiders</ac:parameter>
      <ac:rich-text-body>
        <ac:structured-macro ac:macro-id="a2e44a8e-23ba-44f8-8849-b45075b11342" ac:name="deck" ac:schema-version="1">
          <ac:parameter ac:name="id">FLINT3-2</ac:parameter>
          <ac:rich-text-body>
            <ac:structured-macro ac:macro-id="0cc5d95a-cc70-41ab-8e0f-c5cfefe5be26" ac:name="card" ac:schema-version="1">
              <ac:parameter ac:name="default">true</ac:parameter>
              <ac:parameter ac:name="label">Reigate</ac:parameter>
              <ac:rich-text-body>
                <p> </p>
              </ac:rich-text-body>
            </ac:structured-macro>
            <ac:structured-macro ac:macro-id="3fdf9ef4-bfa8-4453-979d-88e94ffdb635" ac:name="card" ac:schema-version="1">
              <ac:parameter ac:name="label">London</ac:parameter>
              <ac:rich-text-body>
                <p> </p>
              </ac:rich-text-body>
            </ac:structured-macro>
          </ac:rich-text-body>
        </ac:structured-macro>
      </ac:rich-text-body>
    </ac:structured-macro>
    <ac:structured-macro ac:macro-id="869fab17-dd59-42a1-9c62-169277043ec5" ac:name="card" ac:schema-version="1">
      <ac:parameter ac:name="label">Reigate Starters</ac:parameter>
      <ac:rich-text-body>
        <p> </p>
      </ac:rich-text-body>
    </ac:structured-macro>
    <ac:structured-macro ac:macro-id="af9358b8-a3f8-42d3-bdb5-c31bd8596a87" ac:name="card" ac:schema-version="1">
      <ac:parameter ac:name="label">Using FLINT</ac:parameter>
      <ac:rich-text-body>
        <p> </p>
      </ac:rich-text-body>
    </ac:structured-macro>
    <ac:structured-macro ac:macro-id="f842dab6-8ba9-4be7-9e65-165bf46a4f54" ac:name="card" ac:schema-version="1">
      <ac:parameter ac:name="label">Food</ac:parameter>
      <ac:rich-text-body>
        <p> </p>
      </ac:rich-text-body>
    </ac:structured-macro>
  </ac:rich-text-body>
</ac:structured-macro>


I'd be grateful for your assistance.

Regards.

Paul
Photo of Paul Buckle

Paul Buckle

  • 9 Posts
  • 0 Reply Likes

Posted 3 years ago

  • 2
Photo of Paul Buckle

Paul Buckle

  • 9 Posts
  • 0 Reply Likes
Some further testing reveals that it's the nested deck under the parent deck's "First Aiders" card that is causing that card to be the default for the parent deck, even though it's not configured to be - removing it resolves the issue.

However, this is neither the expected behaviour or that seen before the Confluence upgrade.

Is it a bug and if so, when may I expect it to be addressed?

Thanks.

Paul
Photo of Nurhana Ziana Bt. Hanafi

Nurhana Ziana Bt. Hanafi, Employee

  • 3500 Posts
  • 269 Reply Likes
Hello Paul,

Yes, this is not supposed to be expected behavior on default cards. We will add a bug report for this.

Thanks&Regards,
Ziana
Photo of Paul Buckle

Paul Buckle

  • 9 Posts
  • 0 Reply Likes
Thank you Ziana.

Paul
Photo of Nurhana Ziana Bt. Hanafi

Nurhana Ziana Bt. Hanafi, Employee

  • 3500 Posts
  • 269 Reply Likes
Hello Paul,

This issue should be fixed in our latest Composition v5.2.0.

Thanks&Regards,
Ziana