Last modified: 2006-08-11 16:23:21 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 T8971, the corresponding Phabricator task for complete and up-to-date bug report information.
Bug 6971 - Special:Export returns no revisions if all revisions are requested
Special:Export returns no revisions if all revisions are requested
Status: RESOLVED FIXED
Product: MediaWiki
Classification: Unclassified
General/Unknown (Other open bugs)
unspecified
All All
: Normal normal (vote)
: ---
Assigned To: Nobody - You can work on this!
http://commons.wikimedia.org/wiki/Spe...
:
Depends on:
Blocks:
  Show dependency treegraph
 
Reported: 2006-08-10 19:37 UTC by Daniel Kinzler
Modified: 2006-08-11 16:23 UTC (History)
1 user (show)

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


Attachments

Description Daniel Kinzler 2006-08-10 19:37:59 UTC
Special:Export returns an empty XML skelleton if the "current revision only"
option is not checked. This is the case no matter if the 100-revision-limit is
hit or not. I suspect that it's a problem with the code that implements that
limit, so i'm posting it as a wikimedia issue rather than a mediawiki issue.

BTW: I'm not sure what the output is supposed to look like of the max number of
revisions is hit - is it truncated, or an empty skelleton, or does it result in
an error? Failing silently does not seem a good idea, an error message would be
nice.
Comment 1 Daniel Kinzler 2006-08-10 19:41:44 UTC
Forgot to mention: i tried this with commons, dewiki and enwiki. I expect it to
be the same for all projects.

Oh, and regarding the error message - some feedback if a non-existing page is
requested would be nice. OTOH, several bots and scripts rely on requesting a
non-existing page in Special:Export as a hack to fetch namespace names...
Comment 2 Daniel Kinzler 2006-08-11 14:53:27 UTC
This is related to (but kind of the opposite of) bug 6946
Comment 4 Brion Vibber 2006-08-11 16:23:21 UTC
Fixed in r16019.

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


Navigation
Links