Last modified: 2013-12-16 09:33: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 T17907, the corresponding Phabricator task for complete and up-to-date bug report information.
Bug 15907 - Descriptive error messages for "Could not open import file"
Descriptive error messages for "Could not open import file"
Status: RESOLVED DUPLICATE of bug 6646
Product: MediaWiki
Classification: Unclassified
Export/Import (Other open bugs)
unspecified
All All
: Low normal (vote)
: ---
Assigned To: Nobody - You can work on this!
:
Depends on:
Blocks:
  Show dependency treegraph
 
Reported: 2008-10-09 03:57 UTC by Mike.lifeguard
Modified: 2013-12-16 09:33 UTC (History)
3 users (show)

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


Attachments

Description Mike.lifeguard 2008-10-09 03:57:41 UTC
Currently full history imports are disabled on WMF wikis, but we get the oh-so-generic "Import failed: Could not open import file" error when attempting to do so. Please have Special:Import return a meaningful error message for each kind of error - this one in particular is quite misleading.
Comment 1 Mike.lifeguard 2008-10-09 04:09:17 UTC
(In reply to comment #0)
> Currently full history imports are disabled on WMF wikis, but we get the
> oh-so-generic "Import failed: Could not open import file" error when attempting
> to do so. Please have Special:Import return a meaningful error message for each
> kind of error - this one in particular is quite misleading.
> 

Apologies; it's not disabled totally, we're just limited to 1000 revisions (when it works). Still, the problem of terrible error messages remains generally.
Comment 2 Chad H. 2008-10-09 15:32:20 UTC
The wiki doing the import can't possibly know that :), it only knows that it can't get the data from Http::request() that it wanted.

Fwiw: I could do full history imports on my local install as of a few days ago. It doesn't _really_ get the full history, it just thinks it does. The importing wiki doesn't know how many revisions an article has, so it takes all that Special:Export gives it (in this case, 1000 max).
Comment 3 Mike.lifeguard 2008-10-09 16:15:43 UTC
(In reply to comment #2)
> The wiki doing the import can't possibly know that :), it only knows that it
> can't get the data from Http::request() that it wanted.
> 
> Fwiw: I could do full history imports on my local install as of a few days ago.
> It doesn't _really_ get the full history, it just thinks it does. The importing
> wiki doesn't know how many revisions an article has, so it takes all that
> Special:Export gives it (in this case, 1000 max).
> 

Then it should check
*how many Export is allowed to give us,
*how many we actually got, and
*how many there actually are

So we can have meaningful messages like:
*"We got 1000/1000 possible revisions, but there are still 442 remaining unimported revisions. [import-the-rest button]"
*"We got 888/888 possible revisions - that's everything!"
*"We got 345/1000 possible revisions because something bad happened. [try-again-but-skip-first-345-revs button]"
*"We got 1/1 possible revisions because that's all we're allowed. Boo-hoo."
*"We got nothing because something bad happened. Foreign wiki should give us 1000 revisions. [ask-again button]"
*"We got nothing because Export on foreign wiki is disabled. Boo-hoo."
Comment 4 Nemo 2013-12-16 09:33:21 UTC

*** This bug has been marked as a duplicate of bug 6646 ***

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


Navigation
Links