Extension:StructuredDiscussions

The Flow extension provides a new discussion and collaboration system for talk pages

See Flow for an overview of what this extension is planned to address over time and try it out.

Installing
The easiest way to install Flow is to use the MediaWiki-Vagrant appliance and enable its flow role.

To install the extension manually:

Running "update.php" can leave temporary /tmp/mw-UIDGeneratorUUID-UID-xx files that MediaWiki may be unable to open (T55791). If you get a "Permission denied" error upon first visiting a Flow board you have to delete these files. Also, update.php will create FlowMention to support Flow's mention feature in VE (either @ or a toolbar menu provides a convenient auto-complete interface for mentions).

Dependencies

 * required: Extension:Echo for notifications (e.g. replies to your post)
 * required: It is recommended to use memcached as your cache. You may encounter problems with Redis currently.
 * strongly recommended: Parsoid for the option to store posts as HTML which improves performance. This is how WMF wikis are configured, and hence is the most tested configuration by far. If you use MediaWiki-Vagrant, enabling Flow enables Parsoid and sets the format to 'html'.
 * optional: Extension:CLDR for human-friendly timestamps such as "3 days ago"
 * optional: Extension:VisualEditor for VisualEditor support
 * bug? if you have the VisualEditor present (e.g. perhaps to provide OOjs UI),then Flow will attempt to contact Parsoid even if VE is not enabled
 * optional: Flow can integrate with Extension:AbuseFilter, Extension:SpamBlacklist, and Extension:ConfirmEdit, see /Spam
 * optional: Extension:Thanks to "Thank" users for their posts (requires Echo)
 * optional: Extension:EventLogging for analytics

Only for REL_1_24

 * required: Extension:Mantle (install REL_1_24 of that as well).

Verifying installation
Visit one of the pages you enabled for Flow (see ) and try adding a topic and editing its header.

Upgrading
The  variable, which enumerated Flow boards, was removed as part of T105574. Before upgrading to a newer version without this functionality, run the maintenance scripts:

The first script is part of MediaWiki core.

Configuration
Here are some settings you need to make in LocalSettings.php.

Enabling Flow
To enable Flow for a namespace, use. For example:

To enable it on a single page, use Special:EnableFlow. This requires the flow-create-board right, which can be granted to any group (see Manual:User rights).

Parsoid configuration
Flow uses the Virtual REST Service to contact a Parsoid or RESTBase service. If your wiki loads the VisualEditor extension, then you've probably already set this up. Look for the following in your :

A single Parsoid server can handle multiple wikis. The Parsoid  setting identifies your wiki configuration to Parsoid. By default it is set to the hostname named by, but you can pick an arbitrary string. Older versions of Parsoid also used a unique "prefix" to identify the server; you may need to list that here as well.

Parsoid must have been configured to match, using a line in Parsoid's localsettings.js like: Again, the "domain" property is optional in the Parsoid configuration; it defaults to the hostname used in the  property if not specified. The "prefix" property can also be omitted unless you are running an older version of Parsoid. Make sure the  and   listed in Parsoid's   match what's in your wiki's.

See Parsoid/Setup for more details.

"maximum function nesting level of '100' reached, aborting"
If you get this error, you need to set, probably in /etc/php5/apache2/php.ini.

"Exception Caught: CAS is not implemented in Xyz"
Flow invokes  and some cache implementations including   (APCBagOStuff) don't implement CAS. You probably need to use a different cache, for example install memcached and set.

Permissions
Users must have the core  permission to perform any write action in Flow. Many wikis only grant this permission to the 'user' (logged-in) or 'autoconfirmed' group.

Flow defines many actions such as  and   (see the list in ). The permissions vary depending on whether the post is your own and whether it has been moderated. For example, by default users can edit their own posts, but only users in the 'sysop' group have the  permission to edit anyone's post. You can override which groups have which permissions and what permissions are required for each Flow action; see Manual:User rights for an overview of permissions.

Migrating existing pages
To migrate a single existing page, use Special:EnableFlow. It will handle archiving of a single page (then enabling Flow) automatically.

The script maintenance/convertNamespaceFromWikitext.php automates this namespace conversion and archiving, see Flow/Converting talk pages. It is somewhat WMF-specific, so evaluate its operation and backup your database before running it. Another script maintenance/convertLqt.php converts LiquidThreads pages and their threads to Flow boards and topics, see Flow/Converting LiquidThreads. Similar caveats apply.

Flow adds a Topic: namespace, see Extension default namespaces. You can visit Special:PrefixIndex/Topic: to see if there are existing pages that conflict with this; if so run the maintenance script maintenance/namespaceDupes.php.

Architecture
See Flow/Architecture.

Spam
See Extension:Flow/Spam for more information on how to fight spam in Flow.

Moderation
See Extension:Flow/Moderation for more information on moderation in Flow.