Drupal 8 upgrade guide

Updating a website software version is one of the most complicated task a webmaster has to deal with when managing a website. Migrating from Drupal 7? Here is a small guide with various details. Let’s start with basic info : How to see the NID of a node. If the node is in ‘edit’ mode, you can see the nid in the URL. (A node, in case you’re wondering, is a page like an article or a forum posting. You can design what fields it has and how they is displayed. Typically a node will consist of a heading, some body text, maybe an image, etc. Drupal assigns two URL addresses to each node, a human-friendly one made of words, and a nid, or node id.)

Drupal 8 turned one in the November of 2016. It is about time that the Drupal 7 website owners and administrators should start considering upgrading the websites to Drupal 8. With the Drupal team focused on improving Drupal 8, it is inevitable that Drupal 7 will stop getting official updates in the near future. The great thing about upgrading to Drupal 8 is the remarkably easy process as a result of the inclusion of a few great migration modules in its core. After proceeding, you will be brought to the Migrate UI where you can check all the potential issues and errors that you might encounter as well as all the available and the missing paths. Go through this screen and when satisfied, start the migration.

If you’re importing data from a non-Drupal datastore, start with Set up Migrate Demo Site and Source Data . We’ll walk through the process of connecting the migrate system to an external data source, writing custom migration paths, using custom process plugins to transform data during import, and best practices for executing your custom migrations. We’ll primarily look at using an external MySQL database as our data source, but the techniques learned will apply to any data source. We’ll also discuss how to extract data from CSV, JSON, and XML sources.

Download the latest release of the distribution. Download and extract the latest release and copy your existing site’s Drupal 7 version settings.php file and files directory to the sites/default directory in the distribution install. This will point the new site to your existing site database.

The steps above outline how to get a distribution minimally installed on an existing site. But you’ll still have a lot of work to do to reconcile your existing site content and structure with what has been created by the distribution. Here are a few tips to get you started–but you should begin with the assumption that there will be lots more you’ll discover and need to fix. Roles. Many distributions will create one or more custom roles. Examples include contributor, editor, and administrator. If any of these roughly correspond to existing roles on your site, delete the roles created by the distribution and rename the existing ones to use the distribution role names. For example, if your site has a role called “site administrator” and the distribution has created a role called “administrator”, delete the newly created “administrator” role and rename “site administrator” to “administrator”. After adjusting the role names, visit admin/config/people/accounts, ensure the “administrator” role is selected as the “Administrator role”, and save the form. Consolidating the roles in this way will get you the functionality of the distribution’s roles and permissions while maintaining your existing users’ role allocations. See extra details about Drupal 8 Migration.

About the Author