Last modified: 2014-05-09 06:06:03 UTC

Wikimedia Bugzilla is closed!

Wikimedia migrated from Bugzilla to Phabricator. Bug reports are handled in Wikimedia Phabricator.
This static website is read-only and for historical purposes. It is not possible to log in and except for displaying bug reports and their history, links might be broken. See T66903, the corresponding Phabricator task for complete and up-to-date bug report information.
Bug 64903 - Arch/Performance review of ExtraLanguageLink for WMF deploy
Arch/Performance review of ExtraLanguageLink for WMF deploy
Status: NEW
Product: MediaWiki extensions
Classification: Unclassified
ExtraLanguageLink (Other open bugs)
unspecified
All All
: Unprioritized normal (vote)
: ---
Assigned To: Nobody - You can work on this!
:
Depends on:
Blocks: 64786
  Show dependency treegraph
 
Reported: 2014-05-05 15:31 UTC by Greg Grossmeier
Modified: 2014-05-09 06:06 UTC (History)
5 users (show)

See Also:
Web browser: ---
Mobile Platform: ---
Assignee Huggle Beta Tester: ---


Attachments

Comment 1 Brad Jorsch 2014-05-06 14:26:58 UTC
I see you can find pages using this extension using Special:PagesWithProp or API action=query&list=pageswithprop. But there doesn't seem to be any way to search for pages using this extension for particular links short of reading and parsing the property for every page using the extension. Should there be such a way? I'd think yes.

For comparison, real langlinks can be queried using API action=query&list=langbacklinks and interwiki links using API action=query&list=iwbacklinks.

Gerrit change #111390 avoids this problem because the non-language langlinks added via that patch do get recorded in the langlinks table.
Comment 2 This, that and the other (TTO) 2014-05-07 05:05:59 UTC
(In reply to Brad Jorsch from comment #1)
> I see you can find pages using this extension using Special:PagesWithProp or
> API action=query&list=pageswithprop. But there doesn't seem to be any way to
> search for pages using this extension for particular links short of reading
> and parsing the property for every page using the extension. Should there be
> such a way? I'd think yes.

I can add an API module to search for uses of {{extralanguagelink}}, but I can't see any way of making it very efficient. Can API modules be marked expensive, or limited to a small number of results (10 or 20) at a time?

> Gerrit change #111390 avoids this problem because the non-language langlinks
> added via that patch do get recorded in the langlinks table.

It's not always appropriate to include extra language links in the langlinks table; hence this extension.
Comment 3 Brad Jorsch 2014-05-07 16:11:30 UTC
(In reply to This, that and the other from comment #2)
> It's not always appropriate to include extra language links in the langlinks
> table; hence this extension.

It seems odd to me that the links would be appropriate to display in the langlinks area of the web UI but not to include in the langlinks table.

Not storing them in langlinks might also have trouble with code (e.g. mobile) that fetches the langlinks via the API and constructs its own UI to display them.
Comment 4 This, that and the other (TTO) 2014-05-09 06:06:03 UTC
I would welcome review/merge of Gerrit change #111390; if that patch proves insufficient for resolving the two dependencies of bug 64786 then we can pick this up again.

Note You need to log in before you can comment on or make changes to this bug.


Navigation
Links