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 new server,a machine use appserv,b use WMAP, when configuring multi-site, encountered a bit different.

Except to open httpd.conf.

Include conf/extra/httpd-vhosts.conf

LoadModule Rewrite_module modules/mod_rewrite.so

Configure the appropriate folders for multiple sites 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 the WMAP setting of the newly added setting

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

From a machine to the site source code to the B machine, very many methods. Ftp

A machine with mysqldump to the corresponding DB back up, via FTP download to the B machine.

Be sure to set the character set. Otherwise, there will be 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 run &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. is probably the reason for the coding.

After the WordPress migration, assume that the home page is normal, the article pages 404 error, is due to fixed link issues.

1,.htaccess to open Write permissions. In this way, when you define the permanent link WP, WP will take the initiative to rewrite. htaccess. The so-called delete or manual override. 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, loaded into the rewrite module.

3, see if the httpd.conf file in the Apache file is set to AllowOverride to none by default, assuming that you want to change to all.

or change the WordPress vhost segment Join < directory/wp path/> allowoverride All </directory>

then go to WordPress backstage, and once again determine the fixed link. Rewritten. htaccess file.

Restart Apache, everything is done.

see a lot of other WordPress migrations

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