Navigation Menu

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.

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

Closed
Krinkle opened this issue Jan 18, 2019 · 9 comments
Closed

mediawiki.api.parse is deprecated #21

Krinkle opened this issue Jan 18, 2019 · 9 comments

Comments

@Krinkle
Copy link

Krinkle commented Jan 18, 2019

FYI:

The mw.Api parse method(s) are part of the mediawiki.api module bundle as of MW 1.31 MW 1.32, leaving mediawiki.api.parse as deprecated alias, to be removed in MW 1.33.

(Found via Codesearch.)

@kghbln
Copy link
Member

kghbln commented Jan 19, 2019

Thanks for reporting!

@kghbln kghbln self-assigned this Jan 19, 2019
@kghbln kghbln mentioned this issue Mar 4, 2019
6 tasks
kghbln added a commit that referenced this issue Mar 5, 2019
@kghbln kghbln closed this as completed Mar 5, 2019
@kghbln
Copy link
Member

kghbln commented Aug 25, 2019

We need to revert this one.

@kghbln
Copy link
Member

kghbln commented Nov 9, 2019

@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!

@JeroenDeDauw
Copy link
Member

I'm not maintaining this extension. Perhaps only supporting what can easily be supported is the most pragmatic thing to do here.

@kghbln
Copy link
Member

kghbln commented Nov 9, 2019

I'm not maintaining this extension.

I am fully aware here. I was more seeking for input from someone who is more proficient in PHP than I am.

@kghbln
Copy link
Member

kghbln commented Nov 9, 2019

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.

@kghbln
Copy link
Member

kghbln commented Nov 23, 2019

Fine with me.

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.

@hexmode
Copy link
Member

hexmode commented Nov 24, 2019

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.

@kghbln
Copy link
Member

kghbln commented Mar 7, 2020

@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.

@kghbln kghbln closed this as completed Mar 7, 2020
@kghbln kghbln mentioned this issue Mar 7, 2020
Sign up for free to join this conversation on GitHub. Already have an account? Sign in to comment
Projects
None yet
Development

No branches or pull requests

4 participants