Last modified: 2012-10-15 22:57:59 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 T36058, the corresponding Phabricator task for complete and up-to-date bug report information.
Bug 34058 - ApiQueryParseTree doesn't work when XML format is requested
ApiQueryParseTree doesn't work when XML format is requested
Status: RESOLVED INVALID
Product: VisualEditor
Classification: Unclassified
General (Other open bugs)
unspecified
All All
: Low normal
: ---
Assigned To: Nobody - You can work on this!
:
Depends on:
Blocks:
  Show dependency treegraph
 
Reported: 2012-01-31 00:41 UTC by Neil Kandalgaonkar
Modified: 2012-10-15 22:57 UTC (History)
7 users (show)

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


Attachments

Description Neil Kandalgaonkar 2012-01-31 00:41:21 UTC
Something like this query:

    http://wiki.ivy.local/w/api.php?action=query&prop=parsetree&titles=Main%20Page&format=json

Returns a sensible data structure. However, when formatted as XML, an error is returned:

    Warning: htmlspecialchars() expects parameter 1 to be string, object given in /Users/neilk/Sites/trunk/includes/Sanitizer.php on line 978

I've tried other variants and sometimes I do get reasonable XML back but with empty contents. Is it not possible for the API to return arbitrary PHP data structures? Is there something to be done with 'indexed tags'?
Comment 1 Neil Kandalgaonkar 2012-01-31 16:00:02 UTC
The code in question was added r110344.
Comment 2 James Forrester 2012-06-22 21:32:04 UTC
Fixed with new version of VE (code replaced).
Comment 3 James Forrester 2012-10-15 22:57:59 UTC
Mass-moving old VisualEditor tickets to the VE product. Search for this message to mass-delete bugmail.

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


Navigation
Links