I’m pretty sure this is ok, but would like to confirm before I try. I’m testing a migration to WP3, which is installed in a sub-sub-folder:
My first question is when enabling multisite, I get Subdirectory install (that’s what I want), then “Server Address: The internet address of your network will be example.com”. Given most ppl (and examples) discuss installing into root or a subdomain, I want to confirm that this won’t do anything outside of my /deeply/nested folder. I’m pretty sure no, but I’d hate to kill whatever’s in root by mistake.
My second question is a little more complex. Currently the live site I’m migrating is visible as a different (sub-)domain, running of a sibling folder (eg /deeply/nested-folder/), and visible as eg:
(the domain is just pointed at that folder). My plan is to change where the domain is pointing (/deeply/nested-folder/ to /deeply/nested/) so this folder will become the new live site.
Currently I’m using pretty URLs, /%category%/%postname%/ and nested categories to create two subsites, which I hope to turn into multisite sites:
Could someone please tell me if this will cause problems with the “existing WordPress installation” bug that changes permalinks? Would I be better installing WP 3.0.1 fresh and importing the data? (atm I’m using a file copy and duplicated database of the live site’s 2.9 install)
Thanks for your time
peace - boblet