Last modified: 2012-05-28 19:10:51 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 T38337, the corresponding Phabricator task for complete and up-to-date bug report information.
Bug 36337 - add language column to mediawikis table
add language column to mediawikis table
Status: RESOLVED FIXED
Product: Wikimedia Labs
Classification: Unclassified
wikistats (Other open bugs)
unspecified
All All
: Normal enhancement
: ---
Assigned To: Daniel Zahn
:
Depends on:
Blocks:
  Show dependency treegraph
 
Reported: 2012-04-29 10:42 UTC by Daniel Zahn
Modified: 2012-05-28 19:10 UTC (History)
8 users (show)

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


Attachments

Description Daniel Zahn 2012-04-29 10:42:04 UTC
the mediawikis (non-wmf, non-wikifarm/hive) table does not have a language column, cause we never bothered to enter a language manually for all of these and back then we did not have API fetching

at least for all API wikis we can fetch "lang" (prefix, like "en") from API siteinfo, add it to db, and set a language name column to the one used in wikipedias where the prefixes match. (mysql console once)

add the column to display.html for project mw
Comment 1 Daniel Zahn 2012-04-29 11:04:11 UTC
i am starting to put ALL of the info the Mediawiki API returns on a "meta=siteinfo" query into the database table for mediawikis.

depending on the MW version there are different, more/less fields, but i am just getting everything i get from each and kept adding db fields until i did not get "unknown column" errors anymore. wikis not having a certain value will just have empty fields in db.

now my question to you:

here's an example which fields we can get:

http://cn.18dao.net/api.php?action=query&meta=siteinfo&maxlag=5

which of these would you think are interesting enough to add to the html tables? if you say "all", also have ideas on how to deal with the table getting to wide?

really want to put php and dbversions in there as well? sortable for all...?

should there be a separate "extended info" page for each displaying all, but just for one at a time when following a link from the current list? (that would be like just linking to the remote API but showing it in a slightly nicer way)
Comment 3 Robert Hanke 2012-05-28 19:10:51 UTC
Removed upon request

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


Navigation
Links