-
Notifications
You must be signed in to change notification settings - Fork 7
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.
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
Migrate to new extension registration #23
Comments
In any case, I don't want the extension to require MediaWiki ≥ 1.25. I'll check if this can be done without duplicating all information about the extension in both the entry point and the JSON metadata file. |
Good point. I am not sure how to remain backward compatible without duplicating the info though... |
I don't think it's possible. So I think we should wait until doing this provides a real advantage, or 1.25 is the lowest supported version. |
Your call. I just looked up the lifecycle strategy. At the latest when the LTS version 1.23 support ends, which happens in May 2017, I guess you can safely drop the old way. |
Here's a method to handle both: https://github.com/enterprisemediawiki/MasonryMainPage/blob/master/MasonryMainPage.php |
The way extensions register themselves has changed. This page explains what extension developers can do.
You seem like eager to work on your project at the moment, so I won't prepare a comment yet :) Otherwise let me know.
The text was updated successfully, but these errors were encountered: