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

@alistair3149, thanks for the patch. Will there be a way to disable the default PWA behavior ?

@Seb35 , do you know in which MW version TextContent::getText() was introduced ? I'll update the extension the page.

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.

The patch in https://gerrit.wikimedia.org/r/622579 has been merged, it should make it master. Can that task be marked resolved?

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

In that case this parameter can probably be removed.

In T250759#6309294, @Yaron_Koren wrote:

To be clear: I'm talking about the parameter called "namespace=", not "values from namespace=".

In T250759#6235974, @Yaron_Koren wrote:

That's very interesting - thanks for looking that up. My instinct is to go with the first option - remove the "namespace" parameter, since it doesn't seem necessary, or even all that useful. On the other hand, maybe there was some specific reason to add it, which I've forgotten now. Does anyone here really want this feature preserved - and if so, why?

@ssastry no yet. I'm running MW1.34 with Parsoid/JS and will wait for an official release before migrating.

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?

@Yaron_Koren, thanks a bunch. I'll let you +2 the changes on gerrit and close this task.

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?

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.

Well ... the issue disappeared with erasing the current DB, grabbing a backup and going through the update process again.

@Smith.dan, can you give the patch that I made a run?

@Smith.dan, how about filtering out items that are not accessible from queries?

Thank you @MGChecker. Much appreciated.

In T242699#5800882, @Aklapper wrote:

In T242699#5800475, @DannyS712 wrote:

Should be a part of #mediawiki-extensions-semanticacl per https://www.mediawiki.org/wiki/Extension:Semantic_ACL, but that project doesn't exist

Looks like @Tinss added an issue tracker value in https://www.mediawiki.org/w/index.php?title=Extension%3ASemantic_ACL&type=revision&diff=3572192&oldid=3324778 for reasons I don't know. If you would like to use Wikimedia Phabricator, please see https://www.mediawiki.org/wiki/Phabricator/Creating_and_renaming_projects - thanks.

Thanks a bunch everyone!

@Nicolas_NALLET thanks a bunch, that worked.

Bug was fixed in change ID: I64fb215117e7139bf3676902c66e08e9810243f1.

Patch has been submitted in gerrit.

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.

In T199177#4411037, @Aklapper wrote:

After waiting for how long? Which MediaWiki version are you running? Also see https://mediawiki.org/wiki/How_to_report_a_bug

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?