I have TW set up and my view shows multiple taxonomy terms separated by commas. But when I try to configure the content set, in the position where the string of taxonomy terms should be, I have an entry marked "vid." Seems like something isn't going quite right when Migrate looks at a view that contains taxonomy terms. Any suggestions?

Comments

mikeryan’s picture

This description isn't quite clear - are you trying to migrate terms themselves (create Drupal terms from imported categories), or term assignments to nodes? In the former case, you need to have one term per row in the input view. In the latter case, there do seem to be issues, although I don't see anything involving "an entry marked vid". One issue is that it looks like the expected separator is "|" rather than ",", although even using the vertical bar doesn't quite work right.

emdalton’s picture

I'm trying to migrate term assignments. I manually added the terms I needed to the pages involved, but I'll try to explore this further on my test server, using the pipe as a separator.

mikeryan’s picture

Assigned: Unassigned » mikeryan
Category: bug » feature
Priority: Critical » Normal

OK, it worked fine for me once I set my vocabulary to multiple select. But, it's clearly an issue that the separator comes from a variable with no UI to set it, and that the variable is global. We should add "Multiple separator" as an option per content set.

mikeryan’s picture

Title: Still not able to import taxonomy terms » Set multiple separator per content set

Updating title...

mikeryan’s picture

Status: Active » Fixed

OK, you can now set a multiple separator on each content set, and it defaults to comma.

Status: Fixed » Closed (fixed)

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