WordPress migration and some problems encountered [MySQL backup import export] [fixed link 404]

There are two general questions, one is Apache configuration, and the other is MySQL export and import. And some of the problem-solving processes and methods that are encountered after migration.

A machine for the old server, b for the new server, a machine using appserv,b using WMAP, in the configuration of multi-site, encountered a bit different.

Except to open httpd.conf.

Include conf/extra/httpd-vhosts.conf

LoadModule Rewrite_module modules/mod_rewrite.so

Configuring multi-site-corresponding directories in httpd-vhosts.conf

<virtualhost *:80>    ServerAdmin [email protected]    documentroot "c:/wamp/www/wp"    ServerName B.Com    Serveralias www. B.Com    errorlog "Logs/dummy-host.x-error.log"    customlog "Logs/dummy-host.x-access.log" common<Directory "C:/wamp/www/wp" >        Options Indexes followsymlinks        allowoverride all        Order allow,deny        All    </directory></virtualhost><virtualhost *:80>    ServerAdmin [email protected]    DocumentRoot "c:/wamp/www/"    ServerName www. A.com    errorlog "Logs/dummy-host2.x-error.log"    customlog "Logs/dummy-host2.x-access.log" common< Directory "c:/wamp/www/" >        Options Indexes followsymlinks        allowoverride all        Order allow,deny        Allow from all    </Directory></VirtualHost>

The following paragraph is WMAP setting the new setting

<Directory "c:/wamp/www/">        Options Indexes FollowSymLinks        allowoverride  All        Order Allow,Deny Allow from all</Directory>

From a machine to the site source to the B machine, a lot of methods, FTP

A the corresponding DB is backed up with mysqldump on a machine and downloaded to the B machine via FTP. Be sure to set the character set, or you will get an error when importing to the B machine.

mysql.exe-uroot  -p****   –default-character-set=utf-8   mydb   mytable  >   myt a ble.sql

b Machine execution &NBSP; &NBSP;MYSQL-UROOT-P–DEFAULT-CHARACTER-SET=UTF8&NBSP; MYTABLE&NBSP;&NBSP;<&NBSP; mytable.sql

In advance to create a good mytable library on the B machine, note that the database encoding to be consistent with the original

This problem often occurs when you use Navicat to back up a restore. It's probably the reason for the coding.

After WordPress migration, if the appearance of the homepage is normal, the article page 404 error, is due to fixed link problem.

1,.htaccess to open Write permissions, so that when the custom WP permanent LINK, WP will automatically rewrite. htaccess. The so-called delete or manual rewrite. htaccess is because it does not open its write permission.

2, locate the Apache file in the httpd.conf file, the #loadmodule rewrite_module modules/mod_rewrite.so before the # removed, load rewrite module.

3, see if the httpd.conf file in the Apache file is set by default allowoverride to None, and if so, change to all. or modify the Vhost segment where WordPress is added < directory/wp/> AllowOverride all </directory>

then go to WordPress backstage, re-determine the next fixed link, rewrite. htaccess file.

Restart Apache, everything is done.

See more about WordPress migration