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.

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.

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 

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

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

Chrome gives a different popup error:

Error while loading plugins: TypeError: Cannot read property 'startBuild' of null

Since this is a bundled plugin for Confluence v3.2.1, we would expect it to be fixed asap instead of having to vote and wait until v3.3.

Thanks.

Thanks this helps for time being

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

The work around:

When the error: version.compatibility is null shows up.
Just hit enter.

Then click "Available Plugins" tab (even though it is highlighted).

Hope this helps.

Regards

Vincent Choy.

updated "affects versions" list to add 3.2.1 and 3.2

Adding Vincent's analysis and findings to the bug report:

Confluence loads the xml file from plugins.atlassian.com

eg: (this is just an example)
https://plugins.atlassian.com/server/legacy/confluence/xml/1724?&profile=confluence&decorator=none&buildNumber=1724&repoClientVer=2.1.6&os=x86&javaVer=1.6.0_10&javaVendor=Sun+Microsystems+Inc

For the "JavaMelody Monitoring Plugin Product compatibility " We
notice the xml returned does not contain the 'compatibility' nodes:

eg

https://plugins.atlassian.com/plugin/matrix/20909

</com.atlassian.plugin.repository.model.RepositoryPlugin-Version>
-
<com.atlassian.plugin.repository.model.RepositoryPlugin-Version>
<version>1.1</version>
<build>1100</build>
<releaseDate>2009-12-08 00:00:00.0 CST</releaseDate>
<state>stable</state>
-
<compatibility>
<startBuild>1722</startBuild>
<endBuild>1725</endBuild>
-
<workingBuilds class="linked-list">
<int>1722</int>
</workingBuilds>
<brokenBuilds class="linked-list"/>
</compatibility>

Could you please confirm that the compatibility nodes are being
returned for this plugin in production?

Thank you!

The code in question is repository.js:686

// Return the broken status of a version
RepositoryPluginsTab.Plugin.prototype.isVersionBroken = function (version) {
    // Find the build number for this
    var productBuild = RepositoryUI.getConfigSetting("productBuildNumber");
    // Check extremities
    if (version.compatibility.startBuild &&
version.compatibility.startBuild > productBuild) return true;
    if (version.compatibility.endBuild &&
version.compatibility.endBuild < productBuild) return true;
    // Check I am in the working list
    for (var i=0; i<version.compatibility.brokenBuilds.length; i++) {
        if (Number(version.compatibility.brokenBuilds[i]) ==
productBuild) return true;
    }
    return false;
};

the compatibility is assumed to exist (should the code be a bit more
defensive and do some prechecks?)

See screenshot of the version.compatibility = null error + the debug output.

Hope this helps.

Regards

Vincent Choy.

http://jira.atlassian.com/browse/CONF-19894