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
mediawiki.api.parse is deprecated #21
Comments
Thanks for reporting! |
We need to revert this one. |
@JeroenDeDauw This is not just a bloody joke, this appears to be a bloody mess to, just because we would like to support latest MW LTS and consecutive versions. So reverting and adding SemanticMediaWiki/SemanticMediaWiki@580c751 should help? Could you have a peep it this commit also added here will work for the extension? Thanks a ton! |
I'm not maintaining this extension. Perhaps only supporting what can easily be supported is the most pragmatic thing to do here. |
I am fully aware here. I was more seeking for input from someone who is more proficient in PHP than I am. |
So we just pass down this utter disaster from MW to the server admins. Fine with me. I am actually wondering why I still somehow tried to care. |
Actually this is not fine. This is bullshit at its best to put it in nice words. I currently fail to accept that we are unable to support wikis outside in a sane manner. |
@kghbln I just discovered this. Could you help me understand what the problem is? I do not want to lose you or this community. |
I did not see this before. Sorry and thank you for trying to make a difference. The issue basically was that obviously quite some people do not understand the reason for LTS releases. In these cases the strategy is to let wiki admins figure out what to do. I personally would have loved to have a version to support both the preceding and the following LTS branch for better experience. Tough titties. |
FYI:
The mw.Api parse method(s) are part of the
mediawiki.api
module bundle as ofMW 1.31MW 1.32, leavingmediawiki.api.parse
as deprecated alias, to be removed in MW 1.33.(Found via Codesearch.)
The text was updated successfully, but these errors were encountered: