Last modified: 2011-12-06 01:29:13 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 T27134, the corresponding Phabricator task for complete and up-to-date bug report information.
Bug 25134 - add title and/or pageid to action=parse output
add title and/or pageid to action=parse output
Status: NEW
Product: MediaWiki
Classification: Unclassified
API (Other open bugs)
unspecified
All All
: Normal enhancement with 2 votes (vote)
: ---
Assigned To: Nobody - You can work on this!
:
Depends on:
Blocks: 27810
  Show dependency treegraph
 
Reported: 2010-09-10 18:13 UTC by Umherirrender
Modified: 2011-12-06 01:29 UTC (History)
9 users (show)

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


Attachments

Description Umherirrender 2010-09-10 18:13:13 UTC
Please add the pageid and/or the title to the parse output.

Thanks.
Comment 1 Umherirrender 2010-09-10 18:36:13 UTC
Maybe all attributs like prop=info? The module cannot used as generator, so this can save a second query.

At least pageid/ns/title/revid/redirect. Thanks.
Comment 2 Bryan Tong Minh 2010-09-10 20:40:45 UTC
(In reply to comment #1)
> Maybe all attributs like prop=info? The module cannot used as generator, so
> this can save a second query.
> 
I think it should be able to be used as generator.
Comment 3 Roan Kattouw 2010-09-13 15:16:56 UTC
You can't use an action= module as a generator, that's impossible by design.

It sounds like parse should really be an action=query submodule rather than a separate module. Worth thinking about, I guess.
Comment 4 Bryan Tong Minh 2010-09-13 16:00:00 UTC
(In reply to comment #3)
> You can't use an action= module as a generator, that's impossible by design.
> 
> It sounds like parse should really be an action=query submodule rather than a
> separate module. Worth thinking about, I guess.
>
Or allow ApiQuery to operate on the ApiParse result. That would require several work on the query modules though.
Comment 5 Nicholas J Humfrey 2011-02-24 22:39:50 UTC
I would really appreciate being able to get the data returned by action=query&prop=info.

It isn't currently possible to get the last modified/touched date from a action=parse (even through screen scraping) and it seems wasteful to do a second request to get it.
Comment 6 DieBuche 2011-07-12 16:58:21 UTC
*** Bug 28814 has been marked as a duplicate of this bug. ***

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


Navigation
Links