Template talk:MW file

Moving this box to the right?
Could we move this box to the right side of the screen? What do you all think? Adamtheclown 06:36, 22 November 2010 (UTC) Example:

Instead of this:

it would be like this:

Adamtheclown 06:38, 22 November 2010 (UTC)

translation tags broken
It seems, that one of the last changes to this template breaks the usage, e.g. see Manual:GlobalFunctions.php (you can see the closing translate tags, that shouldn't be). Please fix it :) --Florianschmidtwelzow (talk) 19:42, 23 January 2015 (UTC)
 * Fixed. Thanks. --Shirayuki (talk) 00:39, 24 January 2015 (UTC)
 * Great, thanks :)

Links to non-existent code in older/newer releases
Look at Manual:HTML_templates. is a brand-new file in 1.25, so the links to
 * 1.24.2 • 1.23.9

are broken. Conversely, Manual:DumpInterwiki.php is so old that its release links and Classes generated (from master) documentation link are all 404. Is there a way to hint to the template "Don't bother providing links to MW stable release number and MW legacy release number, the code wasn't available? Ideally it would do the right thing when the stable and release versions advance and the file becomes available in those releases. Easier said than done :)

-- SPage (WMF) (talk) 23:55, 2 April 2015 (UTC) (edited)


 * The last resort is adding a "added in" parameter as for some other templates. --Nemo 05:31, 3 April 2015 (UTC)
 * Yes, if  supported starting and ending release parameters (like MW version's  parameters), and if the template could do semantic versioning comparisons of these against MW stable branch number and friends, then then the template could infer to leave out links. Sounds like a lot of work... -- SPage (WMF) (talk) 01:27, 8 October 2015 (UTC)

-- Wladek92 (talk) 15:55, 29 February 2020 (UTC)

Similar remark for Manual:MimeMagic.php see Topic:Vho2o28hvu52yik1 Not fine to see link to releases appearing AFTER the product has been removed.

link to doxygen doc?
I stumbled across Manual:Code/Entry, which fabricates links to doxygen docs for entry points. I wonder if we could add something similar to this template. E.g. includes/actions/Action.php is at https://doc.wikimedia.org/mediawiki-core/master/php/Action_8php.html. This file documentation rarely has anything interesting, but it usually lists the class(es) in the file, and their doxygen is sometimes good, e.g. class. -- SPage (WMF) (talk) 06:36, 5 August 2015 (UTC)

Removed in version
Files get removed... We should be able to document them as such Reedy (talk) 01:05, 25 March 2022 (UTC)

Support file moves
Sometimes, files get moved. For example, Manual:LinksUpdate.php has (as of this writing) the correct path /includes/deferred for versions <= 1.37, but for >= 1.38 the location is /includes/deferred/LinksUpdate (An all-new directory :D) and the link to source is broken. How should this template work for none of these links to be broken? Something like adding optional parameters legacyLoc=, ltsLoc=, stableLoc= that can be changed or something? 92.66.237.19 15:35, 21 June 2022 (UTC)


 * Yeah… there is  and , but… I have no idea what are they good for, as they seem to get appended to the current path parameter. --Mormegil (talk) 14:52, 15 November 2022 (UTC)