Hi,

I have a Drupal 6 vocabulary what I want to map through Migrate and Migrate_d2d to two Drupal 7 vocabularies. This because I use a existing theme in which a certain term_field is used through views and css and I also want to use the other "old" D6 field because I also use views and panels right now migrated from drupal 6.

The problem is that on the second vocabularies (the vocabularies related to the new theme), give the following errors while migrating.
The field mapping settings and fields are completely the same:

Error Field validation error for field_category: Category: illegal value.
Error	Field validation error for field_location: Location: illegal value.

is it impossible to migrate a Drupal 6 (source) vocabulary through migrate using the migrate_d2d UI to multiple Drupal 7 vocabularies?

Thanks a lot for your reply in advance,
greetings, Martijn

CommentFileSizeAuthor
#1 migrate-multipleterm-vocabulaire.png47.87 KBdcine
Support from Acquia helps fund testing for Drupal Acquia logo

Comments

dcine’s picture

I'm using "Migrate" (2.8), "Migrate extras" and "Migrate D2D" modules.
In my case, using Ui Wizard (Migrate D2D) I can migrate multiple terms vocabulaires from drupal 6 to drupal 7. This is a picture of my setup:

Migrate multiple term vocabulaires.

I hope that the example could help you (it is in Spanish, but i think that is )

Summit’s picture

Hi,
I have exactly the same configuration and have two vocabularies with the same settings.
What could be the case than that one vocabulary is correctly migrated (same VID nr?).
And the other one with different VID nr gives; Field validation error for: illegal value?

greetings, Martijn

mikeryan’s picture

Project: Migrate » Drupal-to-Drupal data migration

Moving to appropriate project.

mikeryan’s picture

Status: Active » Postponed (maintainer needs more info)

The UI doesn't provide a way to map a given source vocabulary to more than one destination vocabulary - you get the list of source vocabularies and for each one you select one destination (or none). To map one source to two destinations you would need to implement the second migration in code.

Summit’s picture

Hi,
Ok, so the error "illegal value" should be different in this perspective?
Thanks for reporting...future request to be able to use the UI also for this..where should I add that?
Greetings, Martijn

Summit’s picture

Hi,
Should I for the second vocabulary and destination, do something like this: https://www.drupal.org/node/2210683#comment-9815905
Because the mapping is not working for the second destination? I think this should be somewhere in the documentation...or is it already, then my mistake..?
greetings, Martijn

mikeryan’s picture

Status: Postponed (maintainer needs more info) » Active
mikeryan’s picture

Status: Active » Postponed (maintainer needs more info)

Don't forget to set the status to "Active" when providing more info to a "Postponed (maintainer needs more info)" issue.

I can't really tell from what you've described might be causing the "Illegal value" errors. How are those fields defined? Term references? If so, what vocabularies do they point to? And what exactly are your field mappings for those fields?

mikeryan’s picture

Status: Postponed (maintainer needs more info) » Closed (cannot reproduce)