User Details
- User Since
- Sep 20 2016, 4:14 AM (405 w, 4 d)
- Availability
- Available
- LDAP User
- Antoine Mercier-Linteau
- MediaWiki User
- Tinss [ Global Accounts ]
Feb 3 2023
Thanks. I've found StructuredDiscussions / Flow much more practical for enterprise MW applications and indeed I'm not the only one. Fixing this issue would be much appreciated until support for Flow can resume from the community (I'm looking into assigning some dev resources to that task).
Jan 17 2023
@alistair3149, thanks for the patch. Will there be a way to disable the default PWA behavior ?
Aug 28 2022
@Seb35 , do you know in which MW version TextContent::getText() was introduced ? I'll update the extension the page.
Jun 22 2022
I really couldn't wait for that feature ;) The lack of a mobile app for an enterprise MediaWiki is a real drawback, so I took it upon myself to build Extension:PWA.
Feb 11 2022
Jan 19 2022
The patch in https://gerrit.wikimedia.org/r/622579 has been merged, it should make it master. Can that task be marked resolved?
Dec 2 2020
Thanks Kizule, I looked into fixing the extension in T268957 with that technique, but I think the issue lies in the revision now referencing the actor table (see this talk for an explanation).
Nov 30 2020
Jul 15 2020
In that case this parameter can probably be removed.
Apr 28 2020
@ssastry no yet. I'm running MW1.34 with Parsoid/JS and will wait for an official release before migrating.
Apr 22 2020
I second! I run a somewhat large wiki and no Parsoid/JS update has gone without troubles and downtime. Who doesn't love better and more coherent architecture?
Apr 21 2020
@Yaron_Koren, thanks a bunch. I'll let you +2 the changes on gerrit and close this task.
Apr 20 2020
Mar 31 2020
Is this bug still present? I've found in another bit of code that there is a recursive version for $parser->preprocess called parser->recursivePreprocess(). Maybe it's a fix?
Mar 23 2020
Feb 18 2020
I can no longer reproduce the bug in MediaWiki 1.34. This might have been due to a browser issue or something that has since been fixed in MediaWiki core.
I decided to go ahead and +2 the change.
Jan 22 2020
Well ... the issue disappeared with erasing the current DB, grabbing a backup and going through the update process again.
Jan 18 2020
@Smith.dan, can you give the patch that I made a run?
Jan 17 2020
@Smith.dan, how about filtering out items that are not accessible from queries?
Jan 16 2020
Thank you @MGChecker. Much appreciated.
Jan 14 2020
Nov 2 2019
Thanks a bunch everyone!
Oct 5 2019
@Nicolas_NALLET thanks a bunch, that worked.
Sep 29 2019
Bug was fixed in change ID: I64fb215117e7139bf3676902c66e08e9810243f1.
Sep 28 2019
Feb 28 2019
Aug 3 2018
Patch has been submitted in gerrit.
Jul 18 2018
Reading the abandoned change on gerrit, il seems that the OpenGraph protocol does not support relative URLs. Indeed, this is what searching the web for the issue confirms. Though it's not explicit about needing absolute URLs, the specification does not indicate that it can take a relative URL either; neither is Facebook's developer page.
Jul 12 2018
Jul 10 2018
Sorry, should have provided more information. I've updated the descritpion. I'm running REL1_31.
Sorry about that, I though that tag pertained to the new RecentChanges interface. My bad.
The issue is still there on REL1_31.
Maybe I got the tag wrong?