On Import, Map Wordpress Category and Tags to existing Drupal Vocabularies [#644826]

This would be nice for a few reasons:
1) If you have an existing Drupal site, you can keep your taxonomy condensed
2) Pathauto rules (I don't like the fact that all my automatically aliases have "wordpress-tag" in them)

At the very least, you should be able to rename the default taxonomy names on import, for pathauto.

Comments

Comment #1

kmonty

San Francisco, CA

CreditAttribution: kmonty commented 28 November 2009 at 15:29

For anyone else interested in doing this, I just hacked the module to map the imports myself. Typically I do not recommend hacking a contrib module, but since I am just running the import once then uninstalling the module, I'm willing to live with it:

if (!empty($wordpress_import->data['tags'])) {

    /*$tag_vocabulary_data = array(
      'name' => t('Wordpress tag'),
      'module' => 'wordpress_import',
      'tags' => 1,
      'nodes' => array($wordpress_import->options['nodetype'] => $wordpress_import->options['nodetype'])
    );*/

    //$wordpress_import->tags_vocabulary = wordpress_import_create_vocabulary('tag', $tag_vocabulary_data);
    
    // custom
    $wordpress_import->tags_vocabulary = '2';
    $wordpress_import->tags_map = wordpress_import_get_terms($wordpress_import->tags_vocabulary);

Instead of having the module run wordpress_import_create_vocabulary(), I just commented that line out and mapped $wordpress_import->tags_vocabulary to an existing vocabulary ID. Mine just happened to be "2"

Comment #2

kmonty

San Francisco, CA

CreditAttribution: kmonty commented 28 November 2009 at 15:29

Priority:

Normal

» Minor

Comment #3

bbenone CreditAttribution: bbenone commented 7 February 2011 at 01:12

Priority:

Minor

» Normal

I'm surprised in over a year that no one else has jumped on this thread mentioning it as an important feature.. I guess because you can just rename the vocab after the fact. However, it seems pretty logical to be able to select which vocab you want your tags put into at import time. (e.g. What if I want to use an existing vocabulary, and not create something new...)

Given all the other things we can map, I was surprised to not see this implemented.

Great module though :) -- I can live with this limitation, just would be a nice add.