Support for Content Taxonomy CCK Fields

Note there was already an issue for content_taxonomy support: #600012: How to migrate multiple Taxonomy terms into CCK. I'm closing that as a duplicate, since this contains more info.

The preferable way to add support for another module is in its own file (i.e., modules/contrib/content_taxonomy.inc).

+1 for support for content_taxonomy module!

@2: Thanks a lot that worked awesome.

Please patch the module soon.

Hey everyone,

Now that this has been assigned to Migrate Extras, should we make a new migrate extras sub-module for content taxonomy?

--Ben

subscribe

well, not submodule, but integration, yes. We need a content_taxonomy.inc and a patch adding it to the integrations listed in migrate_extras_migrate_api().

great! looking for this too.

+1 for support for content_taxonomy module

+1 too ;D

Thanks Pimousse98 for sharing the code on #2 to migrate CCK taxonomy. I modified ../migrate_extras/content.migrate.inc and it worked for me too.

Hi KH,
Could you share your code for content.migrate.inc please?
Thanks a lot in advance!

greetings, Martijn

Hi Martijn,

Hope this is not too late for you...I was out on vacation and I am catching up :)

See attached file specifically where I've put in the code from #2 between the comments //616910 starts //616910 ends.

Regards,

KH

+1

subscribe

Has any one tried it with Migrate V2 module? The workaround above is for the older version of MigrateExtra module that handled that CCK fields.

Hi,
On project page there is stated: Notably, that means while CCK and filefield support were in migrate_extras for V1, they are in Migrate itself for Migrate V2.

What is the status on this issue in this perspective please?
greetings, Martijn

Since Drupal 7 natively handles term references, it makes sense that supporting Drupal 6 term references as provided by content_taxonomy should go into the Migrate module itself. Moving this issue over there.

Has anyone got it working with Migrate 2.0 version? Please share tips or code.

Finally...got it working with Migrate 2.0 version. It ended up a simple fix but took long time to figure out.

Need to register the "content_taxonomy" as field type inside the /plugins/destination/fields.inc file as below...and that's it.

class MigrateValueFieldHandler extends MigrateFieldHandler {
  public function __construct() {
    $this->registerTypes(array('value', 'list', 'list_boolean', 'list_number',
      'list_text', 'number_integer', 'number_decimal', 'number_float','content_taxonomy'));
  }

Hope it helps...

I misunderstood what Content Taxonomy does - it's not really analagous to D7 core functionality, so back over to Migrate Extras.

The suggestion in #23 only works when passing in tids, not names. Here's the equivalent implementation for migrate_extras, but it would be nice to support both tids and names as the D7 term reference handler does:

class MigrateContentTaxonomyFieldHandler extends MigrateValueFieldHandler {
  public function __construct() {
    $this->registerTypes(array('content_taxomony'));
  }
}

My two cents from migrating content_taxonomy fields from tids or term_names.

Instructions for developers:

The example field mapping code below shows how to import terms in content taxonomy field.

Note that these code snippet must go into your Migration subclass's constructor - see the migrate_example module for an example of how and where to use field mappings.

// Import source field "content_taxonomy" containing tids into
// destination field field_content_taxonomy:
$this->addFieldMapping('field_content_taxonomy', 'term');

// Import source field "content_taxonomy" containing names into
// destination field field_content_taxonomy:
$arguments = MigrateLinkFieldHandler::arguments('name');
$this->addFieldMapping('field_content_taxonomy', 'term')
   ->arguments($arguments);

I'm sorry. Forgot changing the status.

Hi trunks,
thank you for your patch. I found it very useful.

I'd like to point out a requirement that I found in your approach: terms must exist in vocabularies before importing content_taxonomy fields. I'm writing this just to help others who's willing to test your patch.

I'd also fix a line in the code you wrote in the issue, I will post it here as a whole. (MigrateLinkFieldHandler should be MigrateContentTaxonomyFieldHandler)

// Import source field "content_taxonomy" containing tids into
// destination field field_content_taxonomy:
$this->addFieldMapping('field_content_taxonomy', 'term');

// Import source field "content_taxonomy" containing names into
// destination field field_content_taxonomy:
$arguments = MigrateContentTaxonomyFieldHandler::arguments('name');
$this->addFieldMapping('field_content_taxonomy', 'term')
   ->arguments($arguments);

Greetings,
-ermannob

Hi ermanobb,

You're right. Here you are a new bugfixed revision for this patch.

By the way, it's a requisite migrating terms and vocabularies (implementing MigrateDestinationTerm or your own class) in your migration module before migrating nodes.

Hi trunks,
I made some improvements to your patch. I found some problem when having terms with same name in different vocabularies. I'm working on a large project where some terms names are identical but belong to different vocabularies.
I made some modifications that let developers restrict searching for terms in a particular vocabulary instead of searching through the entire term_data table.

For example:
$arguments = MigrateContentTaxonomyFieldHandler::arguments('name', 3);
'3' is the vid of the vocabulary to search into. It's an optional parameter.

[sorry, i couldn't produce a patch like yours, so I will post a patch for your patch and the entire file]

Greetings,
-ermannob

I'm trying again with a (supposed) proper patch. :)

Please review the Drupal coding standards for indentation, structure, etc.

I haven't used Content Taxonomy myself, so I will be dependent on someone (other than the patch author) who does to test this for functionality and set it to RTBC.

Thanks.

Thank you for pointing me to the right direction, mikeryan.
Not sure if there's more to do on my patch... any hints are welcome.
I'm trying again. :)

Committed, thanks.

Hello,

here is a patch (done with cvs diff...) of migrate_extras/content_taxonomy.inc to allow for merging source terms with destination terms for multi-valued taxonomy fields.

Maybe this won't be useful for general use cases, but it will help others finding the same need that I had.

Here's an example how to use the patch, within a Migration class's __construct():

    // We want to add source terms tid=19 & 21 into destination, by tid (1st param), looking up vocabulary 21 (2nd param), *with source+destination terms merging (3rd param)*.
    $arguments = MigrateContentTaxonomyFieldHandler::arguments('tid', 21, TRUE);
    $this->addFieldMapping('field_est_properties')
    ->defaultValue(array(19,20))
    ->arguments($arguments);

: )

Hi,
Any news on this please? Is there now a correct working migration for content_taxonomy migration from D6 to D7 to correctly migrate terms and term-fields references?
Greetings, Martijn

#36 says it was committed way back in March 2012, but it doesn't appear to be in the most recent version (from November 2012). What's up? Was it rolled back?

Perhaps a bit late for @Summit and @rootwook, but the commit in #36 is to the 6.x-2.x branch.

I'm pretty sure it doesn't belong there, but should be in the 7.x branch instead? (Unless entities and DB-TNG were backported while I wasn't looking? :)