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

{plugins-supported} macro is not working correctly after upgraded from 2.10 to 3.1

    XMLWordPrintable

Details

    Description

      Test results from confluence 3.1 vs 2.10

      Results from Confluence 3.1:

      
      1. {plugins-supported:by=atlassian} 
      
      This parameter is still working.
      
      2. {plugins-supported}
      
      This macro yields the following error. 
      
      "No supported plugins found for profile 'default'."
      
      3. {plugins-supported:profileKey=confluence}
      
      This macro yields the following error. 
      
      "No supported plugins found for profile 'default'. Invalid profile key specified 'confluence'." 
           
      

      Results from Confluence 2.10:

      
      1. {plugins-supported:by=atlassian} 
      
      This parameter works.
      
      2. {plugins-supported}
      
      This macro works
      
      3. {plugins-supported:profileKey=confluence}
      
      This macro yields the following error. 
      
      Invalid profile key specified 'confluence'. 
           
      

      It seems to me the profileKey parameter is broken in Confluence 3.1 (at least for the default setting)

      Attachments

        Activity

          People

            xtjhin Joshua Tjhin (Inactive)
            vchang Vincent Chang
            Votes:
            0 Vote for this issue
            Watchers:
            1 Start watching this issue

            Dates

              Created:
              Updated:
              Resolved: