The SiteInfo query currently provides all sorts of version numbers for the DB, the PHP install itself, etc..., but the one version number that *I*would find useful would be the version string from Parser.php.
My memory about variable scope in PHP is a bit fuzzy, so I'm not positive if the code in Parser.php itself would need to be changed. The variable containing it's version string is a const named VERSION, located on line 55 (according to the line numbering in the ViewVC online code listing, at least).
It'd kind of suck to need to change that in order to implement this but... well, personally I'd find the version number of Parser.php (and possibly some other internal version numbers) much more useful then the version numbers that are currently provided.
Regards, Nolan (aka User:Ohms law)
Nolan White wrote:
The SiteInfo query currently provides all sorts of version numbers for the DB, the PHP install itself, etc..., but the one version number that */I/* would find useful would be the version string from Parser.php.
My memory about variable scope in PHP is a bit fuzzy, so I'm not positive if the code in Parser.php itself would need to be changed. The variable containing it's version string is a const named VERSION, located on line 55 (according to the line numbering in the ViewVC online code listing, at least).
From the comment explaining it, that contains the ParserOutput format,
not the 'parser' version. You probably want a number that changed whenever the parser behavior changes, which doesn't exist.
mediawiki-api@lists.wikimedia.org