I hadn't thought of using categories but that may indeed work for en.wiki :) thanks! On 24 Dec 2012 11:43, "John" <phoenixoverride(a)gmail.com> wrote:

Check the MediaWiki:Disambiguationspage language message - it exists for all languages. It lists all the templates that mark Disambig pages. (https://fr.wikipedia.org/wiki/MediaWiki:Disambiguationspage for the french wikipedia, https://en.wikipedia.org/wiki/MediaWiki:Disambiguationspage for english). I'm sure there are easy ways to check if a page is Disambig in PHP - not sure about JS.

Perhaps this helps something if you are familiar with javascript: http://de.wikipedia.org/wiki/MediaWiki:Gadget-bkl-check.js We in huwiki use an adopted version of this script to display links to disambpages with a different colour. -- Bináris

I implemented a fix for bug 6754 here: https://gerrit.wikimedia.org/r/#/c/40343/ It's a simple 2 line change to core that adds a 'disambiguation' page property to any page that includes '__DISAMBIG__'. I was originally considering implementing this as an extension, but it seems like a feature that would be generally useful to lots of wikis and is a much lighter-weight solution than a full-blown extension. The reason I used a doubleunderscore magic word is because they don't have to output anything and they automatically set a page property. In other words, they were invented for exactly this sort of purpose. Ryan Kaldari On 12/24/12 1:48 PM, bawolff wrote:

On 12/25/12 12:55 AM, Bináris wrote: Yes, the magic word can just be added to the templates. No need to add it to each page. Yes, the magic word is completely localizable and aliasable. It depends on one MediaWiki core change, which is here: https://gerrit.wikimedia.org/r/#/c/40349/ That's the hook that allows the extension to create a new double-underscore magic word (since they are handled differently than regular magic words and parser functions). As soon as that is code reviewed and merged in, it will just be waiting on the extension. I have no idea how long the process of getting the extension out there will take. Probably a month or two assuming it isn't shot down in flames. Ryan Kaldari

On 12/25/12 2:14 AM, Bináris wrote: The magic word can be localized and aliased through the extension's Disambiguator.i18n.magic.php file (similar to how other magic words are localized). The magic word will be localized, but the page property in the database won't be. The page property will always be called 'disambiguation'. If you know any bot writers that are dealing with disambiguation pages, I would love to know more about what their needs are specifically. Perhaps an API could be added to the extension if it would be useful. Ryan Kaldari

On Tue, Dec 25, 2012 at 6:00 AM, Liangent <liangent(a)gmail.com> wrote: One thing that would be nice would be the ability to go the other way. Consider for example this similar query that tests if the specified pages are in a category: api.php?action=query&prop=categories&clcategories=Category:All_disambiguation_pages&titles= We can do the "opposite", getting a list of pages in the category, something like this: api.php?action=query&list=categorymembers&cmtitle=Category:All_disambiguation_pages It would be nice to have a corresponding api.php?action=query&list=pageswithprop&pwpprop=disambiguation. At a glance, it looks like we could do it easily enough if someone adds an index on page_props (pp_propname,pp_page).

That is why I was suggesting adding a field to the page table, instead of using page_props On Wed, Dec 26, 2012 at 9:56 AM, Andrew Dunbar <hippytrail(a)gmail.com> wrote:

On Wed, Dec 26, 2012 at 10:41 PM, Brad Jorsch <bjorsch(a)wikimedia.org> wrote: Then we may want to get rid of tracking categories generated by code and use pageprops instead? and implement a generic Special:PagesByProperty in core, and use it like Special:PagesByProperty/disambig , Special:PagesByProperty/brokenfilelink etc? -Liangent

Tracking categories are nice for certain errors. They more explicitly show there is an error, because there is a category at the bottom of the page. User's can edit the category pages to give helpful information and even change the category name to localize it. Otoh I suppose such a special page could would also have a system message to provide useful introduction to what the property in question means. -bawolff

Well, it looks like my 2-line fix wasn't very popular. I abandoned that one and wrote an extension instead (plus a hook for core). This extension solves both bug 6754 and bug 35981. It will let us get rid of all the disambiguation code in core, and also stop relying on the MediaWiki:Disambiguationspage hack. Furthermore, it is backwards compatible and will allow the community to migrate to the new system whenever they want to. The old system will continue working in the meantime. In summary, the advantages of this extension over the old system are: 1. It will be trivial to query for which pages are disambiguation pages from the database - just test for the 'disambiguation' page property 2. No longer any need to keep track of all of the different disambiguation templates on all the wikis -- just add __DISAMBIG__ to them and you're done 3. The special page output is identical, but requires fewer queries and is more efficient 4. All the code is in an extension rather than in core (per bug 35981) I know you're all dying to +2 this new extension (or perhaps tell me why it's a horrible idea), but unfortunately I don't have rights to create new projects on gerritt, and strangely the IRC channels are a ghosttown this evening ;) Perhaps after you've all recovered from your eggnog hangovers someone could great a new project for me on gerrit: ssh -p 29418 gerrit.wikimedia.org gerrit create-project --owner=editor-engagement --parent=mediawiki/extensions --description='"Repository for the Disambiguator MediaWiki extension"' mediawiki/extensions/Disambiguator Merry Festivus! Ryan Kaldari On 12/24/12 5:10 PM, Ryan Kaldari wrote: