Skip to content
New issue

Have a question about this project? Sign up for a free GitHub account to open an issue and contact its maintainers and the community.

Sign up for GitHub

By clicking “Sign up for GitHub”, you agree to our terms of service and privacy statement. We’ll occasionally send you account related emails.

Already on GitHub? Sign in to your account

Jump to bottom

Add Module Compatibility Property #177

Closed
WildcardSearch opened this issue Apr 15, 2014 · 1 comment
Closed

Add Module Compatibility Property #177

WildcardSearch opened this issue Apr 15, 2014 · 1 comment
Assignees
@WildcardSearch
Labels
enhancement fixed
Milestone
2.1

Comments

@WildcardSearch
Copy link
Owner

To help guard against visible errors due to incompatibility with this version's module changes, a new property will be introduced.

If a module does not have a compatibility field or the value of that field is less than 2.1 then the module will not be loaded. I'd also like to look at alerting admin in some way that the module needs updating.
@WildcardSearch WildcardSearch added this to the 2.1 milestone Apr 15, 2014
@WildcardSearch WildcardSearch self-assigned this Apr 15, 2014
@WildcardSearch WildcardSearch mentioned this issue Apr 15, 2014
Closed
WildcardSearch pushed a commit that referenced this issue Apr 15, 2014
Addressing #177
b4ca4aa 
. . . where a compatibility property was added to modules to determine
whether the module is compatible with >= 2.1
@WildcardSearch
Copy link
Owner Author

Done.

Again this is a change in the public API and modules will need to upgrade.

@WildcardSearch WildcardSearch mentioned this issue May 1, 2014
Merged
Sign up for free to join this conversation on GitHub. Already have an account? Sign in to comment
Assignees

@WildcardSearch WildcardSearch

Labels
enhancement fixed
Projects
None yet
Milestone
2.1
Development

No branches or pull requests
1 participant
@WildcardSearch