How do I setup an existing Wordpress site to use multi-site feature on a local computer using mamp -
I have supported my existing Wordpress site to work at the local level to create a multi-site network. My goal is to not only leave the existing site, but to add a new homepage with my own theme. I am trying to create a multi-site inside a sub-folder.
I have got to work with a fresh installation, although I have participated in complications with an existing local site.
The steps I have taken:
-
I changed the .htcaccess file to:
# BEGIN Wordpress RewriteEngine On RewriteBase / RewriteRule ^ index \ .php $ - [L] # / Add a trailing slash to wp-admin ^ ([_ 0- 9a-zA-Z -] + /)? Wp-admin $ $ 1wp-admin / [R = 301, L] Rewrite code% {REQUEST_FILENAME} -F [OR] REWIND Condom% {REQUEST_FILENAME} -D Rivetrium ^ - [L] Remit Rules ^ ([_ _ 0- 9A -J-A-Z -] + /)? (WP - (content is included in | admin |). *) $ 2 [L] Rev. Raul ^ ([_ 0- 9A-GA-Z +] + /)? (. * .php) $$ 2 [L] Rev. Raul Index.php [L] # END WordPress
-
> Changed from: 8888 & amp; : 8889 to
: 80 & amp; nbsp; : 3306
-
I changed the host file in the terminal with the command:
sudo nano / etc / Host 127.0.0.1 vslocal.com 127.0.0.1 sub.vslocal.com
-
I did a search and changed it to database with local New domain for site
-
I've changed the wp-config.php file to be included in:
define ('MULTISITE', truth); Define ('SUBDOMAIN_INSTALL', incorrect); Define ('DOMAIN_CURRENT_SITE', vslocal.com '); Define ('PATH_CURRENT_SITE', '/'); Define ('SITE_ID_CURRENT_SITE', 1); Define ('BLOG_ID_CURRENT_SITE', 1);
I can get confused and I am having trouble with what has happened or wrong steps taken. I'm running on Mac OSX Yosemite and using MMP 2.2. Any help would be a lifesaver! Thanks! In addition to configuration syntax errors, in fact I have successfully migrated to the multisite from the server, I have been given the following:
The steps that have been taken will work properly.
1. Handle multisite files and break the B (localhost) by breaking the complete SQL to A; 2. DB-Config php has made changes to enable new DB connections and changes made to the domain. 3. Before changing the SQL, you will still see "Error connecting to DB". (But if you delete .htaccess or disable it, then the dubious message of the DB connection will end. Therefore, it means multiziz SQL migration is not completely accurate.) Detect and replace SQL string, ensure Make sure that all sites replace the oldurl to newurl in the options table, blog table and site table etc.
So I think that maybe the DB connection failure error is something with your SQL replacement.
Comments
Post a Comment