Last modified: 2011-05-05 18:54:46 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 T30415, the corresponding Phabricator task for complete and up-to-date bug report information.
Bug 28415 - Special:Export has no way to communicate an error
Special:Export has no way to communicate an error
Status: NEW
Product: MediaWiki
Classification: Unclassified
Special pages (Other open bugs)
1.18.x
All All
: Normal enhancement (vote)
: ---
Assigned To: Nobody - You can work on this!
:
: 28833 (view as bug list)
Depends on:
Blocks:
  Show dependency treegraph
 
Reported: 2011-04-04 14:08 UTC by Dan Jacobson
Modified: 2011-05-05 18:54 UTC (History)
1 user (show)

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


Attachments

Description Dan Jacobson 2011-04-04 14:08:25 UTC
Type a unknown page name into
the big box on Special:Export.

Instead of indicating any error, one gets a file as if all is well. But if you examine it there is no payload at the bottom.

Whats worse, if only some of the page names you give are unknown, well, the
fact that they weren't found will also be unknown to you.

Maybe add a box, checked, "ignore missing pages". Which if the user
unchecks it, will bomb out if any page is not found.
Or -- no box to check, just bomb out before returning any
file. At least add a statement about what happens if a page is not
found there on the boilerplate.

Also please move
"enter the titles in the text box below, one title per line"
right next to the box.
Comment 1 Roan Kattouw 2011-05-05 18:02:34 UTC
*** Bug 28833 has been marked as a duplicate of this bug. ***
Comment 2 Roan Kattouw 2011-05-05 18:04:35 UTC
(In reply to comment #1)
> *** Bug 28833 has been marked as a duplicate of this bug. ***
This bug notes that, if the user specifies only missing pages (or URLs), Special:Export returns an XML file with no pages, just a siteinfo element. According to the reporter, Special:Import barfed on this (this is probably in MW 1.16 so it might've been fixed with the import rewrite). The exporter should never output anything that the importer can't import, so either of those two should be fixed.
Comment 3 Brion Vibber 2011-05-05 18:11:19 UTC
Dupe bug included some indications that Special:Import also fails in an unpleasant way when given an import file with no pages; that should also be handled better if it hasn't already been.

Note that Special:Export works by being given a set of zero or more titles, possibly expanding them into a larger list by fetching category listings, template usage, etc, and then goes through that list exporting whichever pages actually exist.

If you ask for 5000 titles and only 4998 pages exist, it's correct behavior to receive an XML output file with 4998 pages in it.

If you only asked for one, and it's not there, then yes that's information you may want to know. :) But keep in mind that some folks might even be deliberately asking for nonexistent pages just to get the export's siteinfo section -- this should not break.

What's needed presumably is a way to report that the output file doesn't/won't contain specific titles that you asked for (whereas say a template invocation where the template doesn't exist presumably shouldn't warn you, since you didn't explicitly ask for the template but it was brought in from another page you did ask for which did exist).

I guess this could be done by doing a separate hit to check all the pages you asked for before (or after? or ?) the actual export file build.
Comment 4 Dan Jacobson 2011-05-05 18:54:46 UTC
(In reply to comment #3)
> some folks might even be deliberately asking for nonexistent pages just to get the export's siteinfo section -- this should not break.
OK but if they are so smart they could use the API. Anyway, it's called "Export".

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


Navigation
Links