Numbers get lost when using a csv file import when the target is a

autocomplete delux or
autocomplete term widget

when the target is a text widget = no problem.

Changing the number into text or adding a letter then it gets imported.
This got to be a parsing error.

CommentFileSizeAuthor
#4 feeds-numbers_in_taxonomy_bug-1426762-4.patch541 bytesaaronelborg

Comments

IT100’s picture

IT100 commented
IT100’s picture

IT100 commented

Has updating, debugging on the feeds module stopt?
My issue renders this module useless for me. Awkward, because al other features work fine.

regards.
C.

IT100’s picture

IT100 commented
Version: 7.x-2.0-alpha4 » 7.x-2.x-dev
Assigned: Unassigned » IT100
Status: Active » Fixed

found the bug in taxonomy.inc
Didn't make a patch but this hack will work. Please incorporate into the next release.

remove (line 92)

  elseif (is_numeric($term)) {
      $tid = $term;
  }

and change (line 96) $tid will be correct now.

    elseif (is_string($term) || is_numeric($term) ) {
      $tid = taxonomy_term_check_term($term, $vocabulary->vid);
    }
aaronelborg’s picture

aaronelborg commented
Issue tags: +number, +Feeds, +associate to multiple taxonomy terms, +feeds mapper, +feeds tamper, +explode
StatusFileSize
new feeds-numbers_in_taxonomy_bug-1426762-4.patch541 bytes

WOW!

This bug has plagued me for the past couple of days. I'm doing a CSV import as well using Feeds Tamper ('Explode') to get multiple values into a hierarchical select.

Couldn't tell if it was Feeds, Feeds Tamper, Hierarchical Select, core Taxonomy or what!!

IT100, your line number description was a little off but I thank you nonetheless. The fact that this was green (marked 'fixed') threw me too. Shouldn't the maintainer be the one who marks things?

Anyway, I'm using 7.x-2.0-alpha4+35-dev and it doesn't look like this got into the latest 7.x.2.x-dev, FWIW.

Patch attached.

Party planned.

IT100’s picture

IT100 commented

ah, great the patch. Yes the numbers, late hours hey... to tired for a patch.
well, invitation to your party accepted.. ;-)

regards.

Status: Fixed » Closed (fixed)

Automatically closed -- issue fixed for 2 weeks with no activity.

MTecknology’s picture

MTecknology commented
Status: Closed (fixed) » Active

I attempted to use this patch. It applied cleanly but did not have the desired result. The entity_reference autocomplete field still remains empty when I do an import. I made sure that I mapped the column in the csv file that maps to the reference field is a NID that should be mapped to.

MTecknology’s picture

MTecknology commented
Status: Active » Closed (fixed)

Apparently I re-opened this incorrectly. I guess it is the job of the entityreference module to deal with this. The existing issue for this is around abouts http://drupal.org/node/1616680.