Nov 30, 2011 at 8:39 PM
Edited Nov 30, 2011 at 8:40 PM
Yesterday I pushed a changeset preventing extensions from installing if they are not tagged with the correct OrchardVersion in the manifest.
Today I will work on preventing extensions from activating if they are missing a dependency: this issue.
Thanks for this.
Our internal testing of Orchard found it extremely fragile because of this with a workitem of, "Disable the ability to Enable Extensions from the Production Release" because we can't afford to bring down the entire site if someone decided to enable an extension.
This will help a lot.
Though, it still doesn't address rogue extensions that are just poorly coded. As I do vet all code in a module before enabling them in development environments, I doubt everyone that uses Orchard will do the same.