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

User Macros cannot make use of the default parameter

XMLWordPrintable

      When creating a user macro, there is no support for specifying use of the default parameter – <ac:default-parameter> in storage format.

      When defining the macro parameters, parsing of parameters requires that the macro parameter have a name, otherwise the parameter is ignored (with the log warning of "Skipping undefined parameter for macro <macroName>"). However, the default parameter has no name.

      This is of particular concern to users upgrading from 3.5 to 4.x, where their user macros will be migrated to use <ac:default-parameter>, yet it cannot be referenced as a legitimate user macro parameter by the macro browser.

            [CONFSERVER-24254] User Macros cannot make use of the default parameter

            Makisa Appleton made changes -
            Resolution New: Obsolete [ 11 ]
            Status Original: Gathering Impact [ 12072 ] New: Closed [ 6 ]

            Makisa Appleton added a comment -
            Atlassian Update - September 2019

            Thank you for your interest in this ticket. The Confluence Server and Data Center team released a major upgrade to the editor in 6.14. Due to the age of this ticket and/or lack of updates, we suspect that this issue is no longer relevant or was resolved as a result of the upgrade and are now closing this ticket.

            If this issue is still a problem in your Confluence instance in version 6.15 or later, please tag me in your comment and we can reopen this ticket for review.

            You can read more about the editor upgrade in the 6.14 Release Notes.

            Thanks

            Makisa Appleton | Senior Product Manager, Confluence Server and Data Center

            Makisa Appleton added a comment - Atlassian Update - September 2019 Thank you for your interest in this ticket. The Confluence Server and Data Center team released a major upgrade to the editor in 6.14. Due to the age of this ticket and/or lack of updates, we suspect that this issue is no longer relevant or was resolved as a result of the upgrade and are now closing this ticket. If this issue is still a problem in your Confluence instance in version 6.15 or later, please tag me in your comment and we can reopen this ticket for review. You can read more about the editor upgrade in the 6.14 Release Notes . Thanks Makisa Appleton | Senior Product Manager, Confluence Server and Data Center
            Makisa Appleton made changes -
            Fix Version/s New: 6.14.0 [ 83892 ]
            Katherine Yabut made changes -
            Workflow Original: JAC Bug Workflow v3 [ 2898174 ] New: CONFSERVER Bug Workflow v4 [ 2992745 ]
            Owen made changes -
            Workflow Original: JAC Bug Workflow v2 [ 2790284 ] New: JAC Bug Workflow v3 [ 2898174 ]
            Owen made changes -
            Workflow Original: JAC Bug Workflow [ 2720136 ] New: JAC Bug Workflow v2 [ 2790284 ]
            Owen made changes -
            Symptom Severity Original: Major [ 14431 ] New: Severity 2 - Major [ 15831 ]
            Owen made changes -
            Workflow Original: Confluence Workflow - Public Facing - Restricted v5 - TEMP [ 2383762 ] New: JAC Bug Workflow [ 2720136 ]
            Status Original: Open [ 1 ] New: Gathering Impact [ 12072 ]
            Said made changes -
            Labels Original: affects-server editor macro-framework New: affects-server editor macro-framework tidy
            Katherine Yabut made changes -
            Workflow Original: Confluence Workflow - Public Facing - Restricted v5 [ 2277622 ] New: Confluence Workflow - Public Facing - Restricted v5 - TEMP [ 2383762 ]

              Unassigned Unassigned
              cdarroch Daz
              Affected customers:
              12 This affects my team
              Watchers:
              9 Start watching this issue

                Created:
                Updated:
                Resolved: