Uploaded image for project: 'Confluence Data Center'
  1. Confluence Data Center
  2. CONFSERVER-24900

Macro conversion from Confluence 3.x to 4.x fails on mixed case macros

    • Icon: Bug Bug
    • Resolution: Duplicate
    • Icon: Low Low
    • None
    • 4.1
    • None

      When upgrading a 3.x instance to 4.x, the macro conversion runs but ignores a macro that is defined with a mixed case. An example of this is with the Gliffy plugin macro:

      {gliffy}

      However, on a page, the user defined the macro as

      {Gliffy}

      Even though this macro works fine in Confluence 3.x, it does not get converted to a 4.x macro.

            [CONFSERVER-24900] Macro conversion from Confluence 3.x to 4.x fails on mixed case macros

            Sander Brienen [Avisi] added a comment - I posted a workaround on Answers: https://answers.atlassian.com/questions/44384/macros-with-different-case-not-upgraded-from-confluence-3-to-confluence-4

            Anatoli added a comment -

            dkjellin, is that the issue you hit in support and created a patch for?

            Anatoli added a comment - dkjellin , is that the issue you hit in support and created a patch for?

            I have the same issues with

            {numberedheadings}

            vs.

            {numberedHeadings}

            This is the case for over 500 pages in Confluence and they don't display correctly at the moment since they contain macro's in their body that have of course not been upgraded as well.

            We need the fix urgently to get this problem resolved for our users.

            Sander Brienen [Avisi] added a comment - I have the same issues with {numberedheadings} vs. {numberedHeadings} This is the case for over 500 pages in Confluence and they don't display correctly at the moment since they contain macro's in their body that have of course not been upgraded as well. We need the fix urgently to get this problem resolved for our users.

            Anatoli added a comment -

            Hi Eric, thanks for reporting this issue. From my testing it is a general problem for any macro not just Gliffy.

            Anatoli added a comment - Hi Eric, thanks for reporting this issue. From my testing it is a general problem for any macro not just Gliffy.

              Unassigned Unassigned
              e4741b7c6c16 Eric Chiang
              Affected customers:
              2 This affects my team
              Watchers:
              1 Start watching this issue

                Created:
                Updated:
                Resolved: