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

Confluence throws Can't find brush for language

XMLWordPrintable

      Steps to reproduce:

      1. install Confluence 5.9.x
      2. Configure Code Macro via Administrations > Configure Code Macro > add a new language.
      3. create a new page
        1. insert Code Macro
        2. select the newly created syntax highlighter

      Expected Behaviour:
      Code will be highlighted nicely

      Actual Behaviour:
      Error "Can't find brush for: <language>" is thrown when the page is accessed

      Misc:
      The same Custom Brush works in Confluence 5.7.x and Confluence 5.8.x

        1. Error.png
          Error.png
          61 kB
        2. failing-YAML-brush.png
          failing-YAML-brush.png
          32 kB

          Form Name

            [CONFSERVER-40838] Confluence throws Can't find brush for language

            Minh Tran added a comment - - edited

            Dear All,

            This ticket has been marked as duplicate with CONF-40325. The ticket https://jira.atlassian.com/browse/CONF-40325 has been resolved

            Thanks,
            Minh Tran
            Confluence BugMaster
            Atlassian

            Minh Tran added a comment - - edited Dear All, This ticket has been marked as duplicate with CONF-40325 . The ticket https://jira.atlassian.com/browse/CONF-40325 has been resolved Thanks, Minh Tran Confluence BugMaster Atlassian

            Brendan McNamara (Inactive) added a comment -

            This bug is a duplicate of CONF-40325. We are close to completing the fix for this issue and expect the fix to be released in an upcoming 5.10 bugfix release. We will update this ticket again when the fix is available. Please see CONF-40325 for a documented workaround for this issue if you are unable to wait for the new release.

            Brendan McNamara (Inactive) added a comment - This bug is a duplicate of CONF-40325 . We are close to completing the fix for this issue and expect the fix to be released in an upcoming 5.10 bugfix release. We will update this ticket again when the fix is available. Please see CONF-40325 for a documented workaround for this issue if you are unable to wait for the new release.

            Bernd Winkler added a comment -

            Can you please give us a timeline, when this problem will be fixed?

            Bernd Winkler added a comment - Can you please give us a timeline, when this problem will be fixed?

            Manu Ohayon added a comment -

            Same problem with Confluence 5.10.0. This is a major problem for my company as we're developing our own language & compiler...

            Manu Ohayon added a comment - Same problem with Confluence 5.10.0. This is a major problem for my company as we're developing our own language & compiler...

            Karin Maurer added a comment -

            Same problem. Please fix.

            Karin Maurer added a comment - Same problem. Please fix.

            Deleted Account (Inactive) added a comment -

            I was able to get around this by downgrading the macro. I followed the workaround directions on a different bug, here:
            https://jira.atlassian.com/browse/CONF-40325
            As noted in the other bug, you'll want to do this in a test environment first.

            Deleted Account (Inactive) added a comment - I was able to get around this by downgrading the macro. I followed the workaround directions on a different bug, here: https://jira.atlassian.com/browse/CONF-40325 As noted in the other bug, you'll want to do this in a test environment first.

            Antti Hietala added a comment -

            @ads12042 the error only impacts custom brushes. Try switching to a native (built-in) brush that has a syntax similar to your custom brush. When our custom YAML brush broke we switched to the native JavaScript brush. The two languages have pretty much identical syntax highlight.

            Antti Hietala added a comment - @ads12042 the error only impacts custom brushes. Try switching to a native (built-in) brush that has a syntax similar to your custom brush. When our custom YAML brush broke we switched to the native JavaScript brush. The two languages have pretty much identical syntax highlight.

            Carmen Nadeau added a comment -

            We just updated to 5.9.8 and it is still there. My people did not check this so we have to live with this until it is fix. Any workaround guys ??
            Any idea when this will be fix ?
            It is a must for us .

            Carmen Nadeau added a comment - We just updated to 5.9.8 and it is still there. My people did not check this so we have to live with this until it is fix. Any workaround guys ?? Any idea when this will be fix ? It is a must for us .

            Steven F Behnke added a comment -

            Complete nightmare for me. I have tons of usermacros documented in our Confluence using a brush for Velocity and now not only do they not get highlighted, they throw one Alert per code-macro on a page!

            This has broken my documentation. I will not send my users to pages where they are spammed with 10+ alerts. I cannot go through and change all the macros just to change it back when this is fixed.

            Steven F Behnke added a comment - Complete nightmare for me. I have tons of usermacros documented in our Confluence using a brush for Velocity and now not only do they not get highlighted, they throw one Alert per code-macro on a page! This has broken my documentation. I will not send my users to pages where they are spammed with 10+ alerts. I cannot go through and change all the macros just to change it back when this is fixed.

            DCO ADISTA-FINGERPRINT added a comment -

            Could we have a feedback on this issue?

            DCO ADISTA-FINGERPRINT added a comment - Could we have a feedback on this issue?

              Unassigned Unassigned
              jalbion Janet Albion (Inactive)
              Affected customers:
              44 This affects my team
              Watchers:
              37 Start watching this issue

                Created:
                Updated:
                Resolved: