Last modified: 2011-03-13 18:05:03 UTC

Wikimedia Bugzilla is closed!

Wikimedia has migrated from Bugzilla to Phabricator. Bug reports should be created and updated in Wikimedia Phabricator instead. Please create an account in Phabricator and add your Bugzilla email address to it.
Wikimedia Bugzilla is read-only. If you try to edit or create any bug report in Bugzilla you will be shown an intentional error message.
In order to access the Phabricator task corresponding to a Bugzilla report, just remove "static-" from its URL.
You could still run searches in Bugzilla or access your list of votes but bug reports will obviously not be up-to-date in Bugzilla.
Bug 9796 - Allow "action=render" to retrieve just the content for special pages
Allow "action=render" to retrieve just the content for special pages
Product: MediaWiki
Classification: Unclassified
Interface (Other open bugs)
All All
: Lowest enhancement (vote)
: ---
Assigned To: Nobody - You can work on this!
: 13478 (view as bug list)
Depends on:
  Show dependency treegraph
Reported: 2007-05-04 23:55 UTC by Daniel Trebbien
Modified: 2011-03-13 18:05 UTC (History)
2 users (show)

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


Description Daniel Trebbien 2007-05-04 23:55:39 UTC
Specifying `action=render` for any page title other than one starting with
`Special:` returns all XHTML that would normally appear inside of the
`bodyContent` div.

It would be nice if this worked with Special pages, too.
Comment 1 Rob Church 2007-05-05 01:15:26 UTC
Please give an example of how this would be useful.
Comment 2 Daniel Trebbien 2007-05-05 04:02:32 UTC
Rendering pages through action=render is much faster. It would also help out bot
Comment 3 Rob Church 2007-05-05 05:17:09 UTC
1. No, it's not
2. Bots should be using machine-readable interfaces, e.g. the API, or special
handlers for "action=raw" or similar
Comment 4 Jesse (Pathoschild) 2007-05-05 05:29:18 UTC
This would make it easier to dynamically retrieve content on special pages with
AJAX. For example, I am writing a script that displays subpages on the deletion
log. Loading the entire page makes it more difficult to work with, and increases
loading time for content that's stripped from the output anyway.

&action=raw does not work on special pages, apparently because they are not
output through the parser. That would be the ideal solution, combined with
machine-readable XML output (using the associated &ctype), but it sounds like
that would be difficult to implement.

&action=render would probably be much easier to implement, since it may not
involve changing the parser (only not displaying the surrounding skin). I looked
for a machine-readable interface with Special:Prefixindex-like functionality,
but couldn't find one.
Comment 5 Rob Church 2007-05-05 05:49:21 UTC
Special pages are always assumed to be viewed; the entire path of execution is
passed off to the special page execution function, which will then determine
what action to take based on parameters, often from a POST. It doesn't have
anything to do with the parser.

Since a special page contains no "content", asking for it to be "rendered"
doesn't make as much sense. Both cases presented indicate the need to develop
our API and other machine-readable interfaces further, not add kludges to the
code to output "bits of the page".
Comment 6 Daniel Trebbien 2007-05-05 14:40:59 UTC
I did not know that there was an API. Sorry about this ...
Comment 7 Alexandre Emsenhuber [IAlex] 2009-09-25 10:28:51 UTC
*** Bug 13478 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.