Enable VisualEditor by default in NS_USER as well as $wgContentNamespaces

Initially we were only deploying to $wgContentNamespaces, but it's highly likely
that users will want to edit their own user pages in VE anyway. Note that this is
how it's been deployed for Wikimedia for a year now.

Additionally, this helps fix a bug in the browser tests that assumed NS_USER was
a VE-able namespace when that was only true in production config, and not for new
wikis (such as created during automated setup).

Bug: 57104
Change-Id: Icebc24f82fb49e9e80388b6202efa366360ce33c
This commit is contained in:
James D. Forrester 2014-03-10 17:10:13 -07:00
parent ab426682f6
commit d076d9e4a2

View file

@ -1125,7 +1125,7 @@ $wgVisualEditorParsoidTimeout = 100;
$wgVisualEditorSerializationCacheTimeout = 3600; $wgVisualEditorSerializationCacheTimeout = 3600;
// Namespaces to enable VisualEditor in // Namespaces to enable VisualEditor in
$wgVisualEditorNamespaces = $wgContentNamespaces; $wgVisualEditorNamespaces = array_merge( $wgContentNamespaces, array( NS_USER ) );
// List of skins VisualEditor integration supports // List of skins VisualEditor integration supports
$wgVisualEditorSupportedSkins = array( 'vector', 'apex', 'monobook', 'minerva' ); $wgVisualEditorSupportedSkins = array( 'vector', 'apex', 'monobook', 'minerva' );