This part of the process requires you come to the realization that many, if not all, third-party modules that you used to create your site are not available for D6.10 because the developer stopped working on it OR it got integrated into D6. It is also the time to clean up. The objective for this process is to convert your site into a D4.6.8 default site. Below are the steps I did to clean up my site for the transition from D4.6.8 to D6.10.

Site Data

Nodes: Go through all your nodes and delete all the nodes you don't need to keep.

If you haven't already, set up a development space on the server that hosts your current site. Three years ago, a statement like that would turn me into a deer in the headlights. Let me help you.

1. Development Domain: Ask your hosting service to set up another site directory on your account using either a domain that you will use for development or something like dev.examplesite.com. It needs to be a separate directory (NOT a drupal site folder).
2. Database: Ask your hosting service to set up another database.

If you are faced with upgrading your Drupal 4.6.8 site, you might be feeling like I was, a little overwhelmed. This series of articles tells you how I went from 4.6.8 to 6.10 in a day. Before I begin, I want to thank Emma Jane Hogbin for talking me into simply opening another domain, copying my site into it, and upgrading my site one Dversion at a time versus rebuilding my site off-line and then trying to migrate.

There are a lot books out there on facilitation. They all say basically the same thing. They tell you a well planned event is better than one you do off the cuff. This is true. However, the best made facilitation plans have unknown factors that can prevent the plan from being successfully executed. I started facilitating in the early 90's. I have observed some challenges that not all facilitators consider when facilitating.

Challenges

Another way to customize a Drupal site is via its navigation. The menu structure that we will customize is the blocks. The primary links created using the admin/settings feature are shared by each site so they need to be common to each site. You want this to encourage a similar feel between the sites.

You can use the blocks to create custom navigation. To do this, you need to ensure that your taxonomy is set up to let you classify your records for use in one site versus the other, if needed.

Using Drupal themes out-of-the-box might not be enough to make the two sites unique enough. The next step is to customize the theme into something you can call your own. Some the themes require engines to run while others do not. In either case, there are typically two parts to a theme that you can customize, the file that calls out the layout or structure of the site pages and the file the defines the styles.

The guidance provided below assumes:

• You have read "Multiple Sites, Multiple Databases, One Installation of Drupal" located on this site.
• You have read and followed the instructions in "Two Sites, One Database, One Installation of Drupal: DB Setup" located on this site.
• You are working with Drupal 4.6.x.
• You are only sharing two sites.
• The primary site is already configured.
• You have a second domain directed to your Drupal home directory.

The guidance provided below assumes:

• You have read "Multiple Sites, Multiple Databases, One Installation of Drupal" located on this site.
• You are working with Drupal 4.6.x.
• You are only sharing two sites.
• The primary site is already configured.
• You have a second domain directed to your Drupal home directory.

The processes that differ are the database setup and the settings.php configuration. This article focuses on the database setup. There are two parts to this process: create new tables and edit tables.