Include constant for multi site in wp-config-sample

[sean212]

We could include a false constant in wp-config-sample.php so that developers can see a way to enable the multi-site.

The use of WP_ALLOW_MULTISITE in WP is checked to see if it is true before we enabling the multi-site.

We could also link them to the codex for working with WP in Multisite mode.

[sean212]

And comment included

[sean212]

From ​http://wordpress.org/extend/ideas/topic/definewp_allow_multisite-false.

[michaelh]

I believe the idea is to NOT expose multisite to the average user due to complexity.

The general thinking is that if a developer/installer/administrator can't add a line to wp-config.php then that person probably shouldn't be using the multisite ability.

Suggesting closing this.

[sean212]

Yes, that is true.

But why have WP_DEBUG there then? You can have WP_ALLOW_MULTISITE there to show a variable there and it can also provide a codex link that would allow you to see what you can do with it. Some people might not even notice the muti-site ability unless it is pointed out to them.

[nacin]

Some people might not even notice the muti-site ability unless it is pointed out to them.

For 3.0, that's kind of the idea. As I've said a few times before, MU is not for the faint of heart, and neither is multisite in 3.0. It'll get better in a future release, but for now we're hiding it behind a barrier because the learning curve is far too high for the average user.

We added WP_DEBUG to raise its profile. We don't need to be doing the same for WP_ALLOW_MULTISITE.