As suggested by Timo - currently we have 'wmgUseVisualEditor' and 'wmgVisualEditorParsoidPrefix' which both need to be defined for each wiki we're putting VE on, which is a bit annoying (and prone to mistakes) - when we have all 295 Wikipedias with it switched on, it will be even worse. We should probably clean this up a bit.
Version: unspecified
Severity: enhancement
| Status | Subtype | Assigned | Task | ||
|---|---|---|---|---|---|
| Invalid | Jdforrester-WMF | T50426 VisualEditor: Pre-beta needs (tracker) | |||
| Resolved | • Catrope | T49557 VisualEditor: Clean up the way that VE must be configured per wiki |
We could replace wgUseVisualEditor with a visualeditor.dblist file, and change the Parsoid prefixes to be equal to $wgDBname.
(In reply to comment #1)
We could replace wgUseVisualEditor with a visualeditor.dblist file, and
change the Parsoid prefixes to be equal to $wgDBname.
That sounds like a start, but we're going to want to run some wikis in nothing (no preference to switch on - just not in the .dblist file?), some in alpha (opt-in, limited namespaces) and some in beta (default, all "content" even-numbered namespaces that won't break - e.g. MediaWiki:, Template:, Schema:, ? others). Would we want two .dblist files? And some magic juice to decide what namespaces were safe?
Related URL: https://gerrit.wikimedia.org/r/64493 (Gerrit Change I621e98da3be4f787e294d97b350b92d217f43a00)
(In reply to comment #1)
We could replace wgUseVisualEditor with a visualeditor.dblist file, and
change the Parsoid prefixes to be equal to $wgDBname.
$wgUseVisualEditor (or wmgUseVisualEditor) seems fine to me, not sure if a dblist would make things easier.
Getting rid of having to configure wmgVisualEditorParsoidPrefix for each wiki would be great (or at least setting it dynamically/automatically from CommonSettings.php).