From WikiApiary, monitoring the MediaWiki universe
Displaying the versions
I think a pie chart is the better alternative to display the versions usage. However it seems that it is currently not possible to add a legend for the sections as it is possible for the bar chart. Thus we will have to go with the second best alternative, I guess. Cheers --[[kgh]] (talk) 06:04, January 1, 2013 (CST)
- Totally agree. I need to ask on the mailing list about the pie chart. I couldn't get labels or legend to appear at all. :-\ Thingles (talk) 07:53, January 1, 2013 (CST)
Today's changes to this template
Again, my mouth and my eyes are wide open. I never felt like being the brightest candle on the cake but this gives me the feeling that I am totally braindead. :) To cut a long story short: MAGNA CUM LAUDE :) --[[kgh]] (talk) 21:08, 31 January 2013 (UTC) PS Are you for hire? :)
- Well, what should one answer after reading this: Just "Thank you!" I guess. --[[kgh]] (talk) 21:10, 31 January 2013 (UTC)
- Thank you! :-) I'm guessing there would be some folks who would look at Template:Extension version grid and say "#arrayprint inside an #arrayprint with $ (MediaWikiVersions)\times (ExtensionVersions) $ SMW queries? terrible!" but it works rather nicely, if a little slow on pages like Extension:ParserFunctions. I was a little skeptical that #arrayprint would even work that way, but it did. I had thought about using Extension:Loops but it stops after 100 iterations and I think Extension:ParserFunctions would have hit that. Thingles (talk) 21:38, 31 January 2013 (UTC)
Template pages missing?
I'd like to "finalize" (for a bit at least) the extension pages (Template:Extension). I think the top header is now good and near final. Auto-populating values helps fill in everything. I still like the graph of versions, and I love the Version grid. There should definitely be a list of websites using it, but I'm thinking we should just show some, not 100, and use a format that brings their logo images in. What other things, if anything, should be here? Nemo_bis had suggested that he would consider linking from MediaWiki.org extension pages to the sister page on WikiApiary when there was good coverage. Not sure if 17,045 is enough, but would love to get the look of the page ready for that type of linking. Thingles (talk) 22:21, 31 January 2013 (UTC)
- What about showing only 10 random websites together with their logo, the extension's version and the MW version they use (table or template format should do this) and offer a download of the total list (or in chunks of 1000) as csv? --[[kgh]] (talk) 22:48, 31 January 2013 (UTC)
- I want to avoid random on that page as it will defeat caching and those are expensive pages to render and could get hit frequently. I would love to figure out a way to show 'related extensions' but I'm not sure how to do it. In essence, some way of highlighting when extensions are installed alongside each other. :-\ Thingles (talk) 01:36, 1 February 2013 (UTC)
- ad randomness) Yeah, got it. But doesn't already the graph defeat caching? Why not just provide links to subpages e.g. Extension:ParserFunctions/Wikis, Extension:ParserFunctions/Graph and Extension:ParserFunctions/Version grid to move load from the extension's page and split it up to smaller chucks. This would also prevent users from having to scroll down the page all the time. --[[kgh]] (talk) 22:45, 1 February 2013 (UTC)
- ad related) Perhaps the easiest way would be to extract the data directly from the database every month, put it through the mill somehow and then move the resulting info into the wiki again. Hmm, this was not really a big help, was it? :( In general this would be an extra treat which is not utmost necessary. Some kind of probability of two extensions installed on the same wiki lies already within the general extension stats. Apart from that I think that extension combinations are mostly use-case driven, meaning that if the websites are tagged properly here one will be able to more easily identify wikis doing something similar. Then one can have a look at what they are doing. This is another thing why descriptions and even more importantly tags are vital to be here. --[[kgh]] (talk) 22:45, 1 February 2013 (UTC)
Type override does not work ...
Bold all the things
Please revert this edit, you can't use an inline style (e.g. bold) wrapped around a block element (e.g. the table generated by
#ask). As a result every page using this template has everything on the entire page bolded because the generated
<b> is never properly closed when the browser parses the page – at least in Chrome and Safari (screenshot). --Krinkle (talk) 17:03, 22 May 2013 (UTC)
- Yeah, you are right. This edit was a bit on the stupid side. :( Talk about being bold. ;) Should be ok now. Just need to wait for the job queue. :) Thanks and cheers --[[kgh]] (talk) 17:39, 22 May 2013 (UTC) Hmm, how about doing a
<b> </b>instead of
hi please change the wording of
|default=This extension is not longer in use on any website.
|default=This extension is no longer in use on any website.
- I do not think that the release date is of any value. Then it comes to the date of the last update, you have my vote. Cheers --[[kgh]] (talk) 18:35, 12 April 2014 (UTC)
- This should be handled by the bot looking at commit information or pulling data from somewhere reliable. Would you mind adding this to the issue list for the WikiApiary bot at Github? 🐝 thingles (talk) 11:50, 14 June 2014 (UTC)
I’m a little concerned about using CURRENTUSER here from Extension:MyVariables. I believe that whenever this function is used it stops all MediaWiki caching, does anyone know for sure? Also, how do we handle when user is not logged in, should we be using CURRENTLOGGEDUSER? 🐝 thingles (talk) 11:49, 14 June 2014 (UTC)