Skip to main content

Migrate to Drupal 7


Migrate Module


  • Powerful object oriented framework for moving content into Drupal.
  • Minimal UI, primarily code based.
  • Migrate Extras provides support for many contrib modules
  • The best documentation is in the wine.inc and beer.inc example code.
  • Migrate is faster, and more flexible but you need to write code to map fields.
  • Feeds doesn't work well if you've got different content types that need to reference each other.

Main Concepts:-

  1. Source.
  2. Destination
  3. Map
  4. Field mapping.
  5. Field Handling.
  6. Migration

Source:

  • Interface to your existing data (SQL, CSV, XML, JSON).
  • Provides a list of fields and descriptions.
  • Iterates (reset, next) over rows.

Destination:

  • Interface for writing data to Drupal— typically to a Entity.
  • Creates one record for each record in the source. If you’re creating users and profiles, you’ll need two migrations.

Map:

Source:-










destination:-

Mapping of source and Destination in database:

  • Connects the source’s ID to the destination’s ID.
  • Provides lookup facilities.
  • Allows created items to be deleted as part of a rollback.

Field Mapping:-

Source:-







Destination:-








Field mapping from source to Destination:-








  • Links a source field to a destination field.
  • Lets you look up IDs from the other migration’s maps with sourceMigration().
  • If the destination has a complex structure (e.g. Address or file field) then additional data is passed in via arguments().

Migration:


  • Code that glues the parts together
  • In your constructor you setup: source, destination, map and field mappings
  • Allows customization at several points: prepareRow(), prepare(), complete().

Field Handling:-

  • Handles the details of converting the field into the structure that Drupal understands.
  • Turns $entity->field_bar = “foo” into                                                                                        $entity->field_bar[‘und’][0][‘value’] = “foo”.
  • Might pull additional data out of arguments.

  Destination Handling:-

  • Provides additional functionality to an existing destination, e.g. comment adding a field to nodes for comment status.
  • Destination delegates calls to fields(), prepare(), complete() to the destination handlers.
  • You probably won’t need to write one.

Comments

Post a Comment

Popular posts from this blog

Set the default language in Notepad++

I am showing this for the PHP language. In Notepad++   Click on Settings -> Preferences   Click on the New Document tab   Change the Default Language to PHP See below inage   To add an extension to load PHP editor for different extensions.   Click on Settings -> Style Configurator   In Language scroll down to PHP and click it.   In below it will show default ext.     Add your extensions at user exit. (Don't need '.').       eg:  inc install module   Click on Save & Close See below image for reference.

Difference between session.gc_maxlifetime and session.cookie_lifetime in Drupal setting.php

ini_set('session.gc_maxlifetime', 200000); This value is for the server. It is a settings for Session Garbage Collection. If the users last visit happened before 200000s then this session is eligible for garbage collection. Since it is GC, the session value may be discarded and not compulsory. If a GC action happens after the session was made eligible for the GC, it will be deleted. ini_set ( 'session.cookie_lifetime' , 2000000 ); This value is for the browser. This is the absolute maximum time till which a browser can keep this cookie active. A 0 value here means immediate or when the browser is closed. Source: 

Difference between webform vs entityform in Drupal 7

Drupal has a lot of modules aimed at helping site builders and users add forms to their sites. What follows is a rough comparison of 2 of them. If there are any I've missed, please add them. Webform Webform is a module designed to allow you to add custom forms to the front-end of your site. Each form is stored against a node, so you add new forms to your site as if you were adding content. It's useful for things like Survey websites or just where you want a couple of forms that differ from the standard contact form. Pros Webform has been around for a long time, its very well established and has a large number of modules that  integrate with it . Webform can make a wide variety of forms with lots of different elements available out of the box. Because Webforms are nodes, they inherit all the functionality that nodes have (scheduled publishing, cloning, access control, etc.). Webforms are lighter-weight and more scalable than entity-based forms. Can handle multiple-p...