• Icon: Bug Bug
    • Resolution: Invalid
    • Icon: Low Low
    • None
    • None
    • None
    • Reproduced on 5.3-OD-6

      NOTE: This bug report is for Confluence Server. Using Confluence Cloud? See the corresponding bug report.

      Recently, lozenge macros (part of Adaptavist's Content Formatting plugin) pointing to URL's are broken.

      Steps to reproduce

      1. Add a lozenge macro to a page
      2. Edit the macro and insert the URL of a page (e.g. https://<subdomain>.atlassian.net/wiki/display/PA/PA+Home)
      3. Save

      Expected results

      The macro redirects to the linked page.

      Actual results

      The macro fails to render and displays a red warning icon with the following tooltip:

      Unhandled element type '{http://www.w3.org/1999/xhtml}a'
      

      Workaround

      Inserting the targeted page title (as opposed to its link) works.

            [CONFSERVER-30725] Lozenge macro is broken in latest versions of Confluence

            Hi Jeison

            Thanks for raising this issue. I think that you are correct, the first thing for us to do is to reach out to Adaptavist. This is an issue with one of their plugins so they'll need to look at what's going on. Details are here: https://marketplace.atlassian.com/plugins/com.adaptavist.confluence.contentFormattingMacros/version/330/support

            I'm going to close the issue out.

            Steve Haffenden (Inactive) added a comment - Hi Jeison Thanks for raising this issue. I think that you are correct, the first thing for us to do is to reach out to Adaptavist. This is an issue with one of their plugins so they'll need to look at what's going on. Details are here: https://marketplace.atlassian.com/plugins/com.adaptavist.confluence.contentFormattingMacros/version/330/support I'm going to close the issue out.

              shaffenden Steve Haffenden (Inactive)
              jspaniol Jeison
              Affected customers:
              1 This affects my team
              Watchers:
              2 Start watching this issue

                Created:
                Updated:
                Resolved: