Step 7 "Next" goes to New Import Wizard
| Project: | Node import |
| Version: | 6.x-1.x-dev |
| Component: | User interface |
| Category: | bug report |
| Priority: | normal |
| Assigned: | Unassigned |
| Status: | active |
Jump to:
I'm trying to import the attached TSV file (a test file for a much larger import), but cannot get to step 8. I am trying to load it into the default product "Catalog" vocabulary for the products linked to Ubercart on my system (ubercart-6.x-2.0-rc7). My test product catalog has only two terms in it - "Part 000" and "Part XXX" as found in the attached file. I haven't even attempted anything hierarchical yet or with multiple terms...
I have tested with tagging on and off on the "Catalog" vocabulary with the same effect, as well as removing the terms and having an empty vocabulary. I am attempting all imports under the admin account.
The end result is always the same - when I click the "Next" button on Step 7, I get sent back to the New Import Wizard page where the buttons are defined for you. When I click on "List" there are no pending imports, and when I check the content and taxonomy lists nothing has been imported.
I have also had the same problem on RC4, which is why I attempted the dev version to see if it was something that has been fixed for RC5. Help!
Thanks!
-R
I'm running on a D6.14 WAMP system.
| Attachment | Size |
|---|---|
| sample_import.txt | 1.72 KB |
#1
I had the same problem... I suspect you're using Internet Explorer? Try using Firefox.
I don't understand why, but that fixed it for me.
#2
MW, I just tried the import with Firefox 3.0.14, and it did complete. I also ran into a similar problem when viewing the "preview" step and hitting "Reload" after changing the number of items to preview. It also only seems to strike when I try an Ubercart import as importing the same data as Page or Story nodes went through without a hitch. Possibly something in the way the form is being constructed?
It's probably a JS inconsistency with IE (I'm running 8.0.6001.18702 on Win XP SP3). I don't know if it's related or not, but when I turned on the JS debugger while going through the import, I ran across some invalid form submits being called from autocomplete.js on line 15 in D6.14. Maybe they were "upsetting" the MS JS interpreter...?
// $Id: autocomplete.js,v 1.23 2008/01/04 11:53:21 goba Exp $....
$(input.form).submit(Drupal.autocompleteSubmit);
I don't know if this would be classed as a bug in Node Import or in the Drupal core code, but it does seem like checking to make sure there is a valid form should be in the core code...
Thanks!
-R
#3
Same problem with Opera 10, this must be a JS problem indeed since it's on browser side (there's also a shared problem between IE and Opera for image upload when you ask to add another image in a content edit form, this is also a JS problem, maybe the same, FF goes well on this too).
#4
Subscribing
Opera 10.10
(now using opera from have installed Drupal, as Mozilla SeaMonkey and FF were slow with Drupal admin GUI)