Skip to content
This repository has been archived by the owner on Apr 6, 2021. It is now read-only.

Plugin-Manager showing up empty #7

Closed
invokr opened this issue Feb 15, 2015 · 0 comments
Closed

Plugin-Manager showing up empty #7

invokr opened this issue Feb 15, 2015 · 0 comments

Comments

@invokr
Copy link
Contributor

invokr commented Feb 15, 2015

Some of the internal plugins see to incorrectly remove themselves from the core.ext extension, which leads to the Plugin-Manager showing up empty.
The "crash" occurs when invoking lut[plugin.name] in c9.ide.plugins/manager.js on line 396.

I added the following code to c9.ide.plugins/manager.js:

if (typeof(lut[plugin.name]) != "undefined") {
    package.items.push({
    ...
    });
} else {
    console.log("UNDEFINED PACKAGE NAME", plugin.name, lut);
}

Which produces the following result.

console

I can't reliably reproduce the error but I guess it has something to do with the following line being commented out: // plugins.splice(plugins.indexOf(plugin), 1); in c9.core/ext.js.

xoob added a commit that referenced this issue Mar 11, 2015
Fix #6 gdb's setState() properly sets state var
dabbler0 pushed a commit to dabbler0/core that referenced this issue Nov 19, 2016
Fix c9#6 gdb's setState() properly sets state var
Sign up for free to subscribe to this conversation on GitHub. Already have an account? Sign in.
Labels
None yet
Projects
None yet
Development

No branches or pull requests

1 participant