You really do not have much left to do –
http://codex.wordpress.org/Giving_WordPress_Its_Own_Directory#Using_a_pre-existing_subdirectory_install
In the end the site in “http://www.siteA.com/B” will simply behave as though it has always been in “http://www.siteA.com/”. Very few files to duplicate.
Activate the network later if you want it.
Thanks David for your response!
Unfortunately, I actually don’t want Site B to become the primary site. I want to create another version of Site B to become my new Site A. Therefore I want to keep http://www.siteA.com/B to stay as is, but now I want Site A (which is currently a non WordPress site) to have the same customized look and functions of Site B. So essentially, I would like to create a new WordPress directory that will be the new Site A, but have the same look, plugins, etc as Site B.
I hope that doesn’t sound more confusing :/
thank you.
You may not need multisite to achieve this. You can install a regular version of WP in your root and share the themes plugins of the install in your /B/
You can have any number of single WP sites share the same wp-content directory by adding this to each wp-config.php sharing /B/’s themes/plugins.
define( 'WP_CONTENT_DIR', $_SERVER['DOCUMENT_ROOT'] . '/B/wp-content' );
define( 'WP_CONTENT_URL', 'http://www.siteA.com/B/wp-content');
Export/import your content and tweak your settings.
You could still activate a network in the main site and add subdir sites after that, too. Export/import content form your old “B” into your new”B”. Install the same themes and plugins from the original “/B/” and tweak settings.
