Earlier today, I added [1] the long-awaited action=edit module to the API.
Currently, all WMF wikis have $wgEnableWriteAPI = false; , so action=edit won't be available on them (along with delete, move, etc.), which is probably a good thing as long as these modules haven't been tested extensively. However, I suggest this setting be enabled on Testwiki [2] so it can be, well, tested. Maintainers of JS scripts that use the API (like Twinkle, maintained by Carl Fürstenberg AKA AzaTht whose repetitive bugging sped up the development of this module) could probably help here: they'll need to modify their code to use the API edit features at some point and will be able to use TestWiki for testing, and in turn their requests will help testing at TestWiki.
If anyone runs into any issues with the API edit modules, feel free to bug me at #mediawiki (where I'm known as RoanKattouw), file a bug report at BugZilla (be sure to set component=API and assign it to roan.kattouw@home.nl ) or send an e-mail to the mediawiki-api list [3].
Roan Kattouw (Catrope)
[1] http://svn.wikimedia.org/viewvc/mediawiki?view=rev&revision=31514 [2] http://test.wikipedia.org/ [3] mediawiki-api@lists.wikimedia.org
On 03/03/2008, Roan Kattouw roan.kattouw@home.nl wrote:
Earlier today, I added [1] the long-awaited action=edit module to the API.
\o/
I suppose this won't be in a tarball release until MW 1.13 ... pity, I was wanting the edit function for conversion from MoinMoin ;-)
- d.
David Gerard schreef:
On 03/03/2008, Roan Kattouw roan.kattouw@home.nl wrote:
Earlier today, I added [1] the long-awaited action=edit module to the API.
\o/
I suppose this won't be in a tarball release until MW 1.13 ... pity, I was wanting the edit function for conversion from MoinMoin ;-)
You can of course check out the SVN code [1].
Roan Kattouw (Catrope)
On 03.03.2008, 23:03 Roan wrote:
Earlier today, I added [1] the long-awaited action=edit module to the API.
Currently, all WMF wikis have $wgEnableWriteAPI = false; , so action=edit won't be available on them (along with delete, move, etc.), which is probably a good thing as long as these modules haven't been tested extensively. However, I suggest this setting be enabled on Testwiki [2] so it can be, well, tested. Maintainers of JS scripts that use the API (like Twinkle, maintained by Carl Fürstenberg AKA AzaTht whose repetitive bugging sped up the development of this module) could probably help here: they'll need to modify their code to use the API edit features at some point and will be able to use TestWiki for testing, and in turn their requests will help testing at TestWiki.
So, was it enabled on testwiki?
Max Semenik wrote:
On 03.03.2008, 23:03 Roan wrote:
Earlier today, I added [1] the long-awaited action=edit module to the API.
Currently, all WMF wikis have $wgEnableWriteAPI = false; , so action=edit won't be available on them (along with delete, move, etc.), which is probably a good thing as long as these modules haven't been tested extensively. However, I suggest this setting be enabled on Testwiki [2] so it can be, well, tested. Maintainers of JS scripts that use the API (like Twinkle, maintained by Carl Fürstenberg AKA AzaTht whose repetitive bugging sped up the development of this module) could probably help here: they'll need to modify their code to use the API edit features at some point and will be able to use TestWiki for testing, and in turn their requests will help testing at TestWiki.
So, was it enabled on testwiki?
I'd be a bit leery of enabling this on any of our sites atm. :) But I'm just paranoid about things running on our production systems...
-- brion
Brion Vibber schreef:
I'd be a bit leery of enabling this on any of our sites atm. :) But I'm just paranoid about things running on our production systems...
Well if not for testing experimental features, what is Testwiki for? ;)
Seriously, though, how much is Testwiki separated from the 'significant' wikis (Wikipedias, Wiktionaries, etc.)? In an ideal world, Testwiki would run on a separate server (or at least use a different DB server than the rest) so we don't find out about performance issues the hard way. It might also be a good idea to use a normal, one-server DB setup for (the low-traffic?) Testwiki rather than the über-setup the other wikis use, so we'll actually notice the difference between efficient and less-than-efficient queries (on the major DB cluster, both are like <1 ms IIRC).
Roan Kattouw (Catrope)
Roan Kattouw wrote:
Brion Vibber schreef:
I'd be a bit leery of enabling this on any of our sites atm. :) But I'm just paranoid about things running on our production systems...
Well if not for testing experimental features, what is Testwiki for? ;)
Primarily, it's for ensuring we didn't break everything immediately before pushing a software update from SVN to all the servers.
Seriously, though, how much is Testwiki separated from the 'significant' wikis (Wikipedias, Wiktionaries, etc.)? In an ideal world, Testwiki would run on a separate server (or at least use a different DB server than the rest) so we don't find out about performance issues the hard way.
By definition it has to be on the core cluster, since its primary purpose is to ensure things work on the core cluster before we push the software update.
-- brion vibber (brion @ wikimedia.org)
Brion Vibber schreef:
By definition it has to be on the core cluster, since its primary purpose is to ensure things work on the core cluster before we push the software update.
Sucks, at least for this purpose. Maybe there's a volunteer with a publicly accessible test wiki (I know for a fact that at least MinuteElectron has one) who'd be willing to enable the write API modules and let people test them?
Roan Kattouw (Catrope)
On 3/6/08, Roan Kattouw roan.kattouw@home.nl wrote:
Sucks, at least for this purpose. Maybe there's a volunteer with a publicly accessible test wiki (I know for a fact that at least MinuteElectron has one) who'd be willing to enable the write API modules and let people test them?
http://www.epstone.net/~andrew/wiki is available for this purpose, if anybody wants to have a go at it. I'll install the read/write API later today.
Andrew Garrett schreef:
http://www.epstone.net/~andrew/wiki is available for this purpose, if anybody wants to have a go at it. I'll install the read/write API later today.
No need to install anything, just update to the latest SVN version and set $wgEnableWriteAPI = true;
I guess Andrew's wiki is our official API edit test wiki then, so everybody who has written or is writing tools that use it should test their stuff there.
Roan Kattouw (Catrope)
On 3/6/08, Roan Kattouw roan.kattouw@home.nl wrote:
I guess Andrew's wiki is our official API edit test wiki then, so everybody who has written or is writing tools that use it should test their stuff there.
The wiki now has API editing enabled, at: http://www.epstone.net/~andrew/wiki/index.php?title=Main_Page
On Wed, Mar 5, 2008 at 12:23 PM, Max Semenik maxsem.wiki@gmail.com wrote:
On 03.03.2008, 23:03 Roan wrote:
Earlier today, I added [1] the long-awaited action=edit module to the API.
Currently, all WMF wikis have $wgEnableWriteAPI = false; , so action=edit won't be available on them (along with delete, move, etc.), which is probably a good thing as long as these modules haven't been tested extensively. However, I suggest this setting be enabled on Testwiki [2] so it can be, well, tested. Maintainers of JS scripts that use the API (like Twinkle, maintained by Carl Fürstenberg AKA AzaTht whose repetitive bugging sped up the development of this module) could probably help here: they'll need to modify their code to use the API edit features at some point and will be able to use TestWiki for testing, and in turn their requests will help testing at TestWiki.
So, was it enabled on testwiki?
-- Best regards, Max Semenik ([[User:MaxSem]])
Wikitech-l mailing list Wikitech-l@lists.wikimedia.org https://lists.wikimedia.org/mailman/listinfo/wikitech-l
You can check it yourself. If it is enabled, meta=siteinfo[1] should give writeapi="". It currently doesn't, so it is not yet enabled.
Bryan
[1] http://test.wikipedia.org/w/api.php?action=query&meta=siteinfo
wikitech-l@lists.wikimedia.org