[wp-trac] [WordPress Trac] #12931: Upgrading a Single Site install to MultiSite Install with Subdirs is not safe

[WordPress Trac]

#12931: Upgrading a Single Site install to MultiSite Install with Subdirs is not
safe
--------------------------+-------------------------------------------------
 Reporter:  nacin         |       Owner:  nacin      
     Type:  defect (bug)  |      Status:  accepted   
 Priority:  high          |   Milestone:  3.0        
Component:  Multisite     |     Version:  3.0        
 Severity:  blocker       |    Keywords:  needs-patch
--------------------------+-------------------------------------------------
Changes (by gazouteast):

 * cc: gazouteast (added)


Comment:

 Block conversion to subdir multisite for a pre 3.0 single site install
 which is upgraded.

 Problem - when the single site install is in the hosting space root and is
 the hosting account domain name, with add-on domains in subdirectories of
 the hosting root that have their own domain name.

 example =
 /public_html/root_domain
 /public_html/root_domain/addon_domain1
 /public_html/root_domain/addon_domain2
 Where root_domain.com + addon_domain1.com + addon_domain2.com are all
 valid domain names with their own sites (not domain mapped subdomains).

 the root_domain could be DNS wildcarded for a subdomain install, I have
 done it at least once that I recall, but hosting services fight it tooth
 and nail and I've started seeing it as a prohibited activity in terms and
 conditions from some of them (alongside using WP caching plugins being
 prohibited at some too).

 Blocking sub-directory network conversions for hosting root directory
 existing installs will effectively block those sites from upgrading to
 multi-blog.  A workaround needs identified and supplied.

 Gaz

-- 
Ticket URL: <http://core.trac.wordpress.org/ticket/12931#comment:7>
WordPress Trac <http://core.trac.wordpress.org/>
WordPress blogging software