While using a script designed to easily lock accounts on a wiki farm recently upgraded to mw 1.29.1 (using the relevant version of CA), I noticed that the script no longer locked user accounts, but also did not report an error. I therefore took to the ApiSandbox to more easily process the results from testing, as well as to be sure that it was not the script causing these errors. Using the format of
{ "action": "setglobalaccountstatus", "user": "Void-test", "locked": "lock", "reason": "Testing API", }
(format and token omitted), I obtained these results from the various formats:
{ "setglobalaccountstatus": { "user": "Void-test", "hidden": "", "reason": "Testing API" } } a:1:{s:22:"setglobalaccountstatus";a:3:{s:4:"user";s:9:"Void-test";s:6:"hidden";s:0:"";s:6:"reason";s:11:"Testing API";}} { "setglobalaccountstatus": { "user": "Void-test", "locked": false, "hidden": "", "reason": "Testing API" }, "_type": "assoc" } <?xml version="1.0"?> <api> <setglobalaccountstatus user="Void-test" hidden="" reason="Testing API" /> </api>
Only rawfm acknowledges the locked state of the account. None change the fact that the account remains unlocked. If I lock the account before running a test, the end result is that the account is unlocked. I do not believe that the output changes.