[wp-trac] [WordPress Trac] #11742: MU isn't fully compatible with custom content dir

[WordPress Trac]

#11742: MU isn't fully compatible with custom content dir
---------------------------------+------------------------------------------
 Reporter:  Denis-de-Bernardy    |        Owner:          
     Type:  defect (bug)         |       Status:  reopened
 Priority:  normal               |    Milestone:  3.0     
Component:  Upload               |      Version:  3.0     
 Severity:  major                |   Resolution:          
 Keywords:  multisite has-patch  |  
---------------------------------+------------------------------------------

Comment(by wpmuguru):

 Replying to [comment:27 nacin]:
 > In 3.0, wp-content/blogs.php will be a new file for millions of non-
 Multisite WordPress installations. That seems confusing and unnecessary.
 If we can avoid it, I think we should.
 >
 > I think we should move blogs.php into wp-admin/includes or wp-includes,
 and during an upgrade, copy it over an existing blogs.php only if it
 exists.

 We are including wp-content/blogs.php for the upgraded MU installs. That
 file will not be used by upgraded WP installs or new 3.0 installs. After
 3.0, we can set a rule to exclude the file, remove it or whatever.

 Trying to move it around, etc. will create problems for anyone who had
 implemented a custom content directory in MU.

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