Last modified: 2011-04-30 01:16:49 UTC

Wikimedia Bugzilla is closed!

Wikimedia migrated from Bugzilla to Phabricator. Bug reports are handled in Wikimedia Phabricator.
This static website is read-only and for historical purposes. It is not possible to log in and except for displaying bug reports and their history, links might be broken. See T20602, the corresponding Phabricator task for complete and up-to-date bug report information.
Bug 18602 - info vs code reversed in api error message
info vs code reversed in api error message
Status: RESOLVED DUPLICATE of bug 17703
Product: MediaWiki
Classification: Unclassified
API (Other open bugs)
1.14.x
All All
: Normal enhancement (vote)
: ---
Assigned To: Roan Kattouw
:
Depends on:
Blocks:
  Show dependency treegraph
 
Reported: 2009-04-26 21:15 UTC by Chris
Modified: 2011-04-30 01:16 UTC (History)
4 users (show)

See Also:
Web browser: ---
Mobile Platform: ---
Assignee Huggle Beta Tester: ---


Attachments

Description Chris 2009-04-26 21:15:35 UTC
i was writing a bit of code to do a purge via the api, and i got an error message (which is unrelated to my problem)

array(1) {
  ["error"]=>
  array(2) {
    ["code"]=>
    string(61) "Only users with the 'purge' right can purge pages via the API"
    ["info"]=>
    string(9) "cantpurge"
  }
}

i noticed that the error code is in the info key, and the info string is the in code key.

does not seem to be related to the ApiPurge code, as i checked the debug from my apiwrite save page code, and i'm getting the same flipped format of error message

array(1) {
  ["error"]=>
  array(2) {
    ["code"]=>
    string(61) "You're not allowed to edit pages in the ``Article'' namespace"
    ["info"]=>
    string(18) "protectednamespace"
  }
}
Comment 1 Brad Jorsch 2009-04-27 02:20:58 UTC
This sounds like bug 17703, which was fixed in r47861 on trunk and r47862 on the 1.14 branch. Are you using an up-to-date version?
Comment 2 Chris 2009-04-27 02:31:13 UTC
ah, it seems that would be the cause of my problem. sorry about that.

 no, i'm likely not running the newest copy of 1.14.
I'll see about getting that updated. might fix a couple other things i'm seeing

*** This bug has been marked as a duplicate of bug 17703 ***
Comment 3 Roan Kattouw 2009-04-27 13:42:56 UTC
(In reply to comment #2)
> ah, it seems that would be the cause of my problem. sorry about that.
> 
>  no, i'm likely not running the newest copy of 1.14.
> I'll see about getting that updated. might fix a couple other things i'm seeing
> 
Note that the fix is in trunk (1.15alpha), but not in any release of 1.14; in fact, there is only one release of 1.14 (1.14.0) so far; I'll check with Tim whether it would be worthwhile do to a 1.14.1 bugfix release. Meanwhile, you can grab the current 1.14 branch (which is basically 1.14.0 with a bunch of bugfixes) from http://svn.wikimedia.org/svnroot/mediawiki/branches/REL1_14 using SVN.

Note You need to log in before you can comment on or make changes to this bug.


Navigation
Links