Make WordPress Core

Changes between Initial Version and Version 2 of Ticket #31007


Ignore:
Timestamp:
01/14/2015 06:20:15 AM (11 years ago)
Author:
jeremyfelt
Comment:

I think it belongs for the foreseeable future.

This screen - https://cloudup.com/cUp4Q3nHv17 - is only a precursor of things to come if you click Install. There is no friendly way to undo that process and the result itself can be pretty unfriendly. You could go back by removing the remaining defines and live in single site mode with some extra tables, but it's an ugly process.

The admin interface and workflows for a single site are much more developed than they are for multisite. A completely different experience awaits. I think for now it's nice that someone needs to lookup how to create a network before doing so.

I think I'd like to work backward and see constants like MULTISITE and SUBDOMAIN_INSTALL become less important first before opening the doors completely.

Legend:

Unmodified
Added
Removed
Modified
  • Ticket #31007

    • Property Keywords reporter-feedback added
    • Property Summary changed from Consider removing ALLOW_MULTISITE to Consider removing WP_ALLOW_MULTISITE
  • Ticket #31007 – Description

    initial v2  
    1 I'd like to suggest removing ALLOW_MULTISITE altogether, a constant which controls whether or not Tools > Network Settings is accessible (defaults to false).
     1I'd like to suggest removing WP_ALLOW_MULTISITE altogether, a constant which controls whether or not Tools > Network Setup is accessible (defaults to false).
    22
    33I've heard that multisite is gnarly currently, and we should only allow users access to multisite after we clean up some big ticket issues. I think this flag only reestablishes multisite's second-class citizenship.