Posted by John Concrane on July 7, 2019 in Software
Upgrading a website script version is one of the most complicated task a webmaster encounters 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.)
The very first thing you should do is to make a local version of the website. This is an essential step because making changes to a live website is very risky and is never a recommended practice. This way, if anything does go awry, your actual website will remain safe and functional. After clicking Continue, you will be brought to the screen in the following screenshot. Enter all the required details such as your existing website’s credentials, the database location and the location of your website files.
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. If the distribution is installed from scratch, we can be sure that the components we’re creating won’t conflict with existing components on the site. But when we’re converting an existing site into a one based on a distribution, there’s the potential that a component we’re creating will have the same name as one that already exists on the site. In certain cases, such a conflict can cause a site error that’s difficult to resolve. See more info on Drupal 7 Upgrade.