[wp-trac] [WordPress Trac] #32285: define( 'WP_ALLOW_MULTISITE', true );

[WordPress Trac]

#32285: define( 'WP_ALLOW_MULTISITE', true );
--------------------------------+------------------------
 Reporter:  colomet             |       Owner:
     Type:  enhancement         |      Status:  closed
 Priority:  normal              |   Milestone:
Component:  Networks and Sites  |     Version:  4.2.2
 Severity:  normal              |  Resolution:  invalid
 Keywords:                      |     Focuses:  multisite
--------------------------------+------------------------

Comment (by voldemortensen):

 Replying to [comment:4 nacin]:
 >
 > This constant exists as a deliberate hurdle to multisite. We could just
 as easily eliminate it or make it so you don't need to go into wp-
 config.php (twice) to get multisite up and running. But multisite remains,
 even after these many years, not for the faint of heart. So these barriers
 were purposely put into place as part of the 3.0 work. As the work led by
 @jeremyfelt and others continues, we will ideally relax this in the
 future.

 So I'm just ahead of my time :) I'll take it.

 On a serious note, if our overall efforts are to make multisite more
 available, it makes sense to me to make this small step now. Lowering the
 barrier gradually as we improve gradually will get more people into using
 multisite, which in turn creates greater need to improve multisite.

 In my mind I only see a few situations caused by this.
 1. A user goes through the normal install process and never actually goes
 into wp-config.php.
 2. A user quickly goes through the minimum changes required in wp-
 config.php to make a site work, i.e. database info.
 3. A more curious user reads through wp-config.php to see what's there,
 but doesn't know what multisite is so they move on.
 4. Much like 3, but curious enough to look into what multisite is.
 5. The user who already knows what multisite is and know whether or not
 they are going to use it.

 From my experience, cases 1 and 2 are the most common and this change
 wouldn't really effect them. Case 3 wouldn't really be effected because
 they'd just move on, but they will have at least heard of multisite. This
 change would only make case 5's job easier.

 So case 4 is the only one effected. Again from my experience (which is, of
 course, different from everyone else), case for is among the least common
 of the 5 cases. I see this as a way to get multisite a little more
 publicity without putting an option in the dashboard or in the install
 process.

--
Ticket URL: <https://core.trac.wordpress.org/ticket/32285#comment:5>
WordPress Trac <https://core.trac.wordpress.org/>
WordPress publishing platform