Law & Society Blog

Read the instructions and follow them. In most instances, you should be fine. However, some combinations of MySQL, phpMyAdmin, and PHP seem to cause all sorts of mischief. The most common problems are misformed SQL commands upon import. For example, my source host (Globat, slow as molasses) exported the first SQL command of the Law & Society database as follows:

CREATE TABLE `wp_categories` (
`cat_ID` bigint(20) NOT NULL auto_increment,
`cat_name` varchar(55) NOT NULL default '',
`category_nicename` varchar(200) NOT NULL default '',
`category_description` longtext NOT NULL,
`category_parent` int(4) NOT NULL default '0',
PRIMARY KEY (`cat_ID`),
KEY `category_nicename` (`category_nicename`)
) ENGINE=InnoDB DEFAULT CHARSET=latin1 AUTO_INCREMENT=12 ;

The target host (Godaddy) complained about the command. The solution was to delete all references to the default charset (see bold text above). After that, the import went smoothly. Note that after importing a foreign database, the category structure is likely to be messed up. Creating a new category and assigning it to one post seems to reset or rebuild all other category subdirectories.

License

This work is published under a Creative Commons Attribution-Noncommercial 2.5 License.