Go to the plugin repository.

      It gives a popup error

      Error while loading installed plugins: TypeError: version.compatibility is null

          Form Name

            [CONFSERVER-19873] Plugin Repository is not working on QA-EAC

            The resolution says 'fixed' but I'm running 3.3 now and it still occurs when I select "Current confluence build" as the Confluence build number in the Admin page of the Plugin Repository. If I select "Latest confluence build", the error does not occur. In my build, Confluence v3.3 does not appear in the list of build options available (the list only goes up to 3.2.1).

            Tom Richards added a comment - The resolution says 'fixed' but I'm running 3.3 now and it still occurs when I select "Current confluence build" as the Confluence build number in the Admin page of the Plugin Repository. If I select "Latest confluence build", the error does not occur. In my build, Confluence v3.3 does not appear in the list of build options available (the list only goes up to 3.2.1).

            Hi,

            I'm running 3.2.1_01 and experiencing similar problem.
            While trying to open "Plugin Repository" in Admin area I'm getting -
            "Error while loading installed plugins: TypeError: Cannot read property 'startBuild' of null

            Look here: https://support.atlassian.com/browse/CSP-47431

            I'm adding myself to a watch list here.

            Leon Kolchinsky added a comment - Hi, I'm running 3.2.1_01 and experiencing similar problem. While trying to open "Plugin Repository" in Admin area I'm getting - "Error while loading installed plugins: TypeError: Cannot read property 'startBuild' of null Look here: https://support.atlassian.com/browse/CSP-47431 I'm adding myself to a watch list here.

            Thanks, Stefan! When can we expect a patch or new version of Confluence with the fixes included?

            Tom Richards added a comment - Thanks, Stefan! When can we expect a patch or new version of Confluence with the fixes included?

            This was fixed by cleaning up the plugin data returned by plugins.atlassian.com.

            CONF-19987 adds an enhancement request to recover gracefully from such error conditions.

            Stefan Saasen (Inactive) added a comment - This was fixed by cleaning up the plugin data returned by plugins.atlassian.com. CONF-19987 adds an enhancement request to recover gracefully from such error conditions.

            I'm running 3.2.1_01, and it's showing this error. I downloaded the latest release to try and fix this problem, which seemed to appear spontaneously.

            Tom Richards added a comment - I'm running 3.2.1_01, and it's showing this error. I downloaded the latest release to try and fix this problem, which seemed to appear spontaneously.

            What do u mean by unreleased versions ? 3.2.1 was downloaded from Atlassian site itself.

            Thanks & Regards,
            Sandhya Kaithakkat
            SaaS Project Manager/Salesforce Admin
            Direct : 415.275.9152
            Fax : 415.332.1010
            www.orgplus.com 

             
             

            Sandhya Kaithakkat added a comment - What do u mean by unreleased versions ? 3.2.1 was downloaded from Atlassian site itself. Thanks & Regards, Sandhya Kaithakkat SaaS Project Manager/Salesforce Admin Direct : 415.275.9152 Fax : 415.332.1010 www.orgplus.com     

            Jonathan G added a comment -

            The latest version is 3.2.1_01, although if you're seeing this problem on any released version then this indicates it's more of a problem than we initially thought. We'll try to get it fixed up asap.

            Jonathan G added a comment - The latest version is 3.2.1_01, although if you're seeing this problem on any released version then this indicates it's more of a problem than we initially thought. We'll try to get it fixed up asap.

            I am running 3.2.0_01... Your latest stable version AFAIK.

            --Russ

            "Jonathan Gilbert [Atlassian] (JIRA)" <jira@atlassian.com> wrote:

            [ http://jira.atlassian.com/browse/CONF-19873?page=com.atlassian.jira.plugin.system.issuetabpanels:comment-tabpanel&focusedCommentId=197027#action_197027 ]

            Jonathan Gilbert [Atlassian] commented on CONF-19873:
            -----------------------------------------------------

            This bug only affects unreleased versions; any version we release will not exhibit this behaviour.


            This message is automatically generated by JIRA.
            -
            If you think it was sent incorrectly contact one of the administrators: http://jira.atlassian.com/secure/Administrators.jspa
            -
            For more information on JIRA, see: http://www.atlassian.com/software/jira

            Aras Memisyazici added a comment - I am running 3.2.0_01... Your latest stable version AFAIK. --Russ "Jonathan Gilbert [Atlassian] (JIRA)" <jira@atlassian.com> wrote: [ http://jira.atlassian.com/browse/CONF-19873?page=com.atlassian.jira.plugin.system.issuetabpanels:comment-tabpanel&focusedCommentId=197027#action_197027 ] Jonathan Gilbert [Atlassian] commented on CONF-19873 : ----------------------------------------------------- This bug only affects unreleased versions; any version we release will not exhibit this behaviour. – This message is automatically generated by JIRA. - If you think it was sent incorrectly contact one of the administrators: http://jira.atlassian.com/secure/Administrators.jspa - For more information on JIRA, see: http://www.atlassian.com/software/jira

            Jonathan G added a comment -

            This bug only affects unreleased versions; any version we release will not exhibit this behaviour.

            Jonathan G added a comment - This bug only affects unreleased versions; any version we release will not exhibit this behaviour.

            Is there any update on this? I am also affected by this problem and although I realize a lame work-around does exist (acknowledge error and re-click Available Plugins) I would really like for this bug to be fixed ASAP.

            Thanks,
            --Russ

            Aras Memisyazici added a comment - Is there any update on this? I am also affected by this problem and although I realize a lame work-around does exist (acknowledge error and re-click Available Plugins) I would really like for this bug to be fixed ASAP. Thanks, --Russ

              Unassigned Unassigned
              mhrynczak Mark Hrynczak (Inactive)
              Affected customers:
              2 This affects my team
              Watchers:
              9 Start watching this issue

                Created:
                Updated:
                Resolved: