Last modified: 2014-09-25 12:37:54 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 T56366, the corresponding Phabricator task for complete and up-to-date bug report information.
Bug 54366 - no-external-page error should provide machine readable error info
no-external-page error should provide machine readable error info
Status: NEW
Product: MediaWiki extensions
Classification: Unclassified
WikidataRepo (Other open bugs)
unspecified
All All
: Normal enhancement (vote)
: ---
Assigned To: Wikidata bugs
https://test.wikidata.org/wiki/Specia...
: need-volunteer, testme
Depends on:
Blocks: repoapi
  Show dependency treegraph
 
Reported: 2013-09-20 07:20 UTC by Kunal Mehta (Legoktm)
Modified: 2014-09-25 12:37 UTC (History)
3 users (show)

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


Attachments

Description Kunal Mehta (Legoktm) 2013-09-20 07:20:53 UTC
When a sitelink is already in use, action=editentity gives a nice machine-readable error message like:

        "messages": {
            "0": {
                "name": "wikibase-error-sitelink-already-used",
                "type": "error",
                "parameters": [
                    "http://en.wikivoyage.org/wiki/Main_Page",
                    "Main Page",
                    "Q33",
                    "enwikivoyage"
                ]
            },

on the other hand, no-external-page (can test with a non-existent page) gives:

{
    "servedby": "mw1208",
    "error": {
        "code": "no-external-page",
        "info": "The external client site did not provide page information for site 'enwikivoyage' and title 'Main Pageddd'"
    }
}

It would be nice if we got the same level of detail for all errors.

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


Navigation
Links