We have presented several examples as part of this migration blog post series. Today we are going to talk about what happens after import and rollback operations, how to recover from a failed migration, and some tips for writing definition files.
So far we have learned how to write basic Drupal migrations and use process plugins to transform data to meet the format expected by the destination. In the previous entry we learned one of many approaches to migrating images. In today’s example, we will change it a bit to introduce two new migration concepts.
Migrate process plugins transform data between source and destination. This gets more complicated for Drupal fields have multiple components. Today we will learn how to migrate into them and know which subfields are available.
Sometimes in a Drupal 7 to Drupal 8 migration we copy values verbatim from the source to the destination. Often, the data needs to be transformed to match the format expected by the destination. Today we will learn more about process plugins and how they work as part of the Drupal migration pipeline.
In the previous entry, we learned that the Migrate API is an implementation of an ETL framework. We also talked about the steps involved in writing and running migrations. Now, let’s write our first Drupal migration. We are going to start with a very basic example: creating nodes out of hardcoded data. For this, we assume a Drupal installation using the standard installation profile which comes with the Basic Page content type.
The Migrate API is a very flexible and powerful system that allows you to collect data from different locations and store tham in Drupal— it is a full-blown extract, transform, and load (ETL) framework.
We live amidst a Digital Commons - technology that is built with the principles of freedom and transparency baked into its code and design.
Ben will be presenting two sessions at Drupaldelphia. Come learn how to apply an Iterative UX approach to your work and how to scale community decision-making in your free software projects.
Test your Drupal site's functionality in a human-readable format. Behavior-driven development is a great way to write tests for code because it uses language that humans can understand. Let's see how to implement BDD in Drupal.
In preparation for Agaric's latest migration training, we've seen again that getting a development environment suitable for working on Drupal with Composer is a big road block. For that reason, here are instructions for getting it all going, suitable for our training or for working on Drupal in a code sprint, with only one hard requirement: PHP.