Jump to: navigation, search

About this board

The Collaboration team has enabled Flow on this talk page.

Previous feedback is on Talk:Flow Portal/Archive2 (using old Liquid Threads), and on our labs server.

By clicking "Add topic", you agree to our Terms of Use and agree to irrevocably release your text under the CC BY-SA 3.0 License and GFDL (talkcontribs)

I get this error when I'm trying to use VisualEditor in Flow conversations:

[9149bd06] Exception Caught: Conversion from 'html' to 'wikitext' was requested, but core's Parser only supports 'wikitext' to 'html' conversion.

VisualEditor is working on other sites normally.

I have these lines in my LocalSettings.php:

$wgVisualEditorParsoidURL = 'http://localhost:8000';

$wgVisualEditorParsoidForwardCookies = true;

$wgSessionsInObjectCache = true;

$wgFlowContentFormat = 'html';

$wgFlowEditorList = array( 'visualeditor', 'none' );

Parsoid seems to depub html > wikitext without problems.

Can you tell how to fix this?

Mattflaschen-WMF (talkcontribs)

What version/git commit of Flow and core do you have?

In recent versions of Flow, you need to use $wgVirtualRestConfig (recommended, if it's mentioned in your Flow.php) or $wgFlowParsoid* variables (either the only way, or a deprecated but still-working way).

Mattflaschen-WMF (talkcontribs)

You can see (either for $wgVirtualRestConfig or history of that for the old way). (talkcontribs)

I'm using the latest version. I haven't defined $wgVirtualRestConfig in my LocalSettings.php and I cant find this from Flow.php. Flow parsoid configuration looks like this:

$wgFlowParsoidURL = null; // also see $wgVisualEditorParsoidURL

$wgFlowParsoidPrefix = null; // also see $wgVisualEditorParsoidPrefix

$wgFlowParsoidTimeout = null; // also see $wgVisualEditorParsoidTimeout

If i set $wgFlowParsoidURL = http://localhost:8000 i get an error: [c949daba] Exception Caught: Failed contacting Parsoid and neither editor is working in Flow conversations. (talkcontribs)

This is what logfile says:

FlowHooks::initFlowExtension: Warning: $wgFlowContentFormat was set to 'html', but you do not have Parsoid enabled.  Changing $wgFlowContentFormat to 'wikitext' (talkcontribs)

...and i've checked: Parsoid service is up and running. I even tested it on http://localhost:8000 and its working normally.

Mattflaschen-WMF (talkcontribs)

What do you have for all the $wgFlowParsoid... variables in your LocalSettings.php? You only mentioned one. They should all (well, one or two are optional) be set to the same as their equivalent VE one is/would be.

If you use IRC, joining us in #wikimedia-collaboration on Freenode may be faster. (talkcontribs)

require_once "$IP/extensions/VisualEditor/VisualEditor.php";

$wgVisualEditorParsoidURL = 'http://localhost:8000';

$wgVisualEditorParsoidForwardCookies = true;

$wgSessionsInObjectCache = true;

require_once "$IP/extensions/Flow/Flow.php";

$wgFlowContentFormat = 'html';

$wgFlowEditorList = array( 'visualeditor', 'none' );

#$wgFlowParsoidURL = 'http://localhost:8000';

$wgVirtualRestConfig['modules']['parsoid'] = array(

  'url' => 'http://localhost:8000',

  'domain' => 'localhost',

  'prefix' => 'localhost',


I also have defined namespaces but I didn't write those here. I haven't made changes to Flow.php or VisualEditor.php.

Mattflaschen-WMF (talkcontribs)

If $wgVirtualRestConfig is not mentioned in a comment in Flow.php, there is no need to set it for Flow's purposes, and it won't have any effect on Flow (other than maybe confusing people).

You should uncomment $wgFlowParsoidURL and also set $wgFlowParsoidPrefix, $wgFlowParsoidTimeout, and $wgFlowParsoidForwardCookies.

I think:

$wgFlowParsoidURL = 'http://localhost:8000';
$wgFlowParsoidPrefix = $wgDBname;
$wgFlowParsoidTimeout = 100;
$wgFlowParsoidForwardCookies = true;

should work.

You can raise the timeout if wanted/needed. (talkcontribs)


$wgVirtualRestConfig is not mentioned in Flow.php. Should I use these in LocalSettings.php or Flow.php?

$wgFlowParsoidURL = 'http://localhost:8000'; // also see $wgVisualEditorParsoidURL

$wgFlowParsoidPrefix = $wgDBname; // also see $wgVisualEditorParsoidPrefix

$wgFlowParsoidTimeout = 100; // also see $wgVisualEditorParsoidTimeout

$wgFlowParsoidForwardCookies = true;

If set these settings to LocalSettings.php and comment in Flow.php I get: "Due to a technical error, this post could not be retrieved." Failed connecting parsoid. Neither editor is working (WysiWYG, VE). If I do vice versa I get the same error. If I set these above setting to both files I get the same error.

Why does it fail if i use VisualEditor for e.g. new pages and can save those successfully. Ii can still access and see parsoid running at the server. I've restarted the service.

If i comment these setting in both of the files, WysiWYG wikitext editor is working but VE gives: Exception Caught: Conversion from 'html' to 'wikitext' was requested, but core's Parser only supports 'wikitext' to 'html' conversion.

My LocalSettings.php:

require_once "$IP/extensions/VisualEditor/VisualEditor.php";

$wgDefaultUserOptions['visualeditor-enable'] = 1;

$wgHiddenPrefs[] = 'visualeditor-enable';

$wgDefaultUserOptions['visualeditor-enable-experimental'] = 1;

$wgVisualEditorParsoidURL = 'http://localhost:8000';

$wgVisualEditorParsoidForwardCookies = true;

$wgSessionsInObjectCache = true;

require_once "$IP/extensions/Flow/Flow.php";




$wgNamespaceContentModels[NS_USER] = CONTENT_MODEL_FLOW_BOARD;

$wgNamespaceContentModels[NS_TALK] = CONTENT_MODEL_FLOW_BOARD;

$wgFlowContentFormat = 'html';

$wgFlowEditorList = array( 'visualeditor', 'none' );

require_once "$IP/extensions/Echo/Echo.php";

If I add this to LocalSettings.php:

$wgVirtualRestConfig['modules']['parsoid'] = array(


'url' => 'http://localhost:8000',


'domain' => $wdDBname,


'prefix' => '100'


I get: [98970307] Exception Caught: Conversion from 'html' to 'wikitext' was requested, but core's Parser only supports 'wikitext' to 'html' conversion (talkcontribs)

I corrected this one in LocalSettings.php:

$wgVirtualRestConfig['modules']['parsoid'] = array(


'url' => 'http://localhost:8000',


'domain' => 'localhost',


'prefix' => 'localhost'


I also tested echo 'Foo' | node parse and it is working. (talkcontribs)

Log file still says: Warning: $wgFlowContentFormat was set to 'html', but you do not have Parsoid enabled.

Mattflaschen-WMF (talkcontribs)

$wgVirtualRestConfig is not going to work with your version of Flow. Please do not change or post that setting.

Never change settings in Flow.php (unless you're a developer working on Flow, but that's a different matter). Please change Flow.php back to the version you downloaded.

Add the lines I mentioned to LocalSettings.php ($wgFlowParsoidURL, $wgFlowParsoidPrefix, $wgFlowParsoidTimeout, $wgFlowParsoidForwardCookies).

After changing LocalSettings.php, retest. If it doesn't work, post your full LocalSettings.php.

> Why does it fail if i use VisualEditor for e.g. new pages and can save those successfully. Ii can still access and see parsoid running at the server. I've restarted the service.

Flow uses a different set of settings. (talkcontribs)

Hi, Flow.php restored from the original file. Changed settings as you described - not working: Failed to contact Parsoid. Here is the LocalSettings.php:

#This file was automatically generated by the MediaWiki 1.25.1

# installer. If you make manual changes, please keep track in case you

# need to recreate them later.


# See includes/DefaultSettings.php for all configurable settings

# and their default values, but don't forget to make changes in _this_

# file, not there.


# Further documentation for configuration settings may be found at:


# Protect against web entry

if ( !defined( 'MEDIAWIKI' ) ) {



# Uncomment this to disable output compression

# $wgDisableOutputCompression = true;

$wgSitename = "Raksu";

####### UPLOAD FILE TYPES #######

$wgFileExtensions = array( 'png', 'gif', 'jpg', 'jpeg', 'doc',

    'xls', 'mpp', 'pdf', 'ppt', 'tiff', 'bmp', 'docx', 'xlsx',

    'pptx', 'ps', 'odt', 'ods', 'odp', 'odg', 'pdf');

# Custom Mediawiki settings

// Search settings

$wgAdvancedSearchHighlighting = true;

$wgEnableMWSuggest = true;

$wgUseTwoButtonsSearchForm = true;

#Set default searching

$wgNamespacesToBeSearchedDefault = array(

NS_MAIN =>           true,

NS_TALK =>           false,

NS_USER =>           false,

NS_USER_TALK =>      false,

NS_PROJECT =>        false,

NS_PROJECT_TALK =>   false,

NS_FILE =>           false,

NS_FILE_TALK =>      false,

NS_MEDIAWIKI =>      false,


NS_TEMPLATE =>       false,


NS_HELP =>           false,

NS_HELP_TALK =>      false,

NS_CATEGORY =>       true,



## The URL base path to the directory containing the wiki;

## defaults for all runtime URL paths are based off of this.

## For more information on customizing the URLs

## (like /w/index.php/Page_title to /wiki/Page_title) please see:


$wgScriptPath = "";

$wgScriptExtension = ".php";

## The protocol and server name to use in fully-qualified URLs

$wgServer = "";

## The relative URL path to the skins directory

$wgStylePath = "$wgScriptPath/skins";

$wgResourceBasePath = $wgScriptPath;

## The relative URL path to the logo.  Make sure you change this from the default,

## or else you'll overwrite your logo when you upgrade!

$wgLogo = "$wgResourceBasePath/resources/assets/raksu_uusilogo.png";

## UPO means: this is also a user preference option

$wgEnableEmail = true;

$wgEnableUserEmail = true; # UPO

$wgEmergencyContact = "";

$wgPasswordSender = "";

$wgEnotifUserTalk = false; # UPO

$wgEnotifWatchlist = false; # UPO

$wgEmailAuthentication = false;

## Database settings

$wgDBtype = "mysql";

$wgDBserver = "localhost";

$wgDBname = "wikidb";

$wgDBuser = "";

$wgDBpassword = "";

# MySQL specific settings

$wgDBprefix = "";

# MySQL table options to use during installation or update

$wgDBTableOptions = "ENGINE=InnoDB, DEFAULT CHARSET=binary";

# Experimental charset support for MySQL 5.0.

$wgDBmysql5 = false;

## Shared memory settings

$wgMainCacheType = CACHE_NONE;

$wgMemCachedServers = array();

## To enable image uploads, make sure the 'images' directory

## is writable, then set this to true:

$wgEnableUploads = true;

$wgUseImageMagick = true;

$wgImageMagickConvertCommand = "/usr/bin/convert";

# InstantCommons allows wiki to use images from

$wgUseInstantCommons = false;

## If you use ImageMagick (or any other shell command) on a

## Linux server, this will need to be set to the name of an

## available UTF-8 locale

$wgShellLocale = "en_US.utf8";

## If you want to use image uploads under safe mode,

## create the directories images/archive, images/thumb and

## images/temp, and make them all writable. Then uncomment

## this, if it's not already uncommented:

#$wgHashedUploadDirectory = false;

## Set $wgCacheDirectory to a writable directory on the web server

## to make your wiki go slightly faster. The directory should not

## be publically accessible from the web.

#$wgCacheDirectory = "$IP/cache";

# Site language code, should be one of the list in ./languages/Names.php

$wgLanguageCode = "fi";

$wgSecretKey = "secret_key_hided";

# Site upgrade key. Must be set to a string (default provided) to turn on the

# web installer while LocalSettings.php is in place

$wgUpgradeKey = "";

## For attaching licensing metadata to pages, and displaying an

## appropriate copyright notice / icon. GNU Free Documentation

## License and Creative Commons licenses are supported so far.

$wgRightsPage = ""; # Set to the title of a wiki page that describes your license/copyright

$wgRightsUrl = "";

$wgRightsText = "";

$wgRightsIcon = "";

# Path to the GNU diff3 utility. Used for conflict resolution.

$wgDiff3 = "/usr/bin/diff3";

# The following permissions were set based on your choice in the installer

$wgGroupPermissions['*']['edit'] = false;

## Default skin: you can change the default skin. Use the internal symbolic

## names, ie 'vector', 'monobook':

$wgDefaultSkin = "vector";

# Enabled skins.

# The following skins were automatically enabled:

wfLoadSkin( 'CologneBlue' );

wfLoadSkin( 'Modern' );

wfLoadSkin( 'MonoBook' );

wfLoadSkin( 'Vector' );

# Enabled Extensions. Most extensions are enabled by including the base extension file here

# but check specific extension documentation for more details

# The following extensions were automatically enabled:

wfLoadExtension( 'Cite' );

wfLoadExtension( 'CiteThisPage' );

wfLoadExtension( 'Gadgets' );

wfLoadExtension( 'ImageMap' );

wfLoadExtension( 'InputBox' );

wfLoadExtension( 'Nuke' );

wfLoadExtension( 'PdfHandler' );

wfLoadExtension( 'Renameuser' );

wfLoadExtension( 'SyntaxHighlight_GeSHi' );

wfLoadExtension( 'TitleBlacklist' );

wfLoadExtension( 'WikiEditor' );

# End of automatically generated settings.

# Add more configuration options below.

# WikiEditor settings

# Enables use of WikiEditor by default but still allow users to disable it in preferences

$wgDefaultUserOptions['usebetatoolbar'] = 1;

$wgDefaultUserOptions['usebetatoolbar-cgd'] = 1;

# Displays the Preview and Changes tabs

$wgDefaultUserOptions['wikieditor-preview'] = 1;

# Displays the Publish and Cancel buttons on the top right side

$wgDefaultUserOptions['wikieditor-publish'] = 1;

#Set Default Timezone

$wgLocaltimezone = "Europe/Helsinki";

$wgLocalTZoffset = date("Z") / 60;


require_once "$IP/extensions/UniversalLanguageSelector/UniversalLanguageSelector.php";

# EXTENSION: Visual Editor

require_once "$IP/extensions/VisualEditor/VisualEditor.php";

// Enable by default for everybody

$wgDefaultUserOptions['visualeditor-enable'] = 1;

// Don't allow users to disable it

$wgHiddenPrefs[] = 'visualeditor-enable';

// OPTIONAL: Enable VisualEditor's experimental code features

$wgDefaultUserOptions['visualeditor-enable-experimental'] = 1;

// URL to the Parsoid instance

// MUST NOT end in a slash due to Parsoid bug

// Use port 8142 if you use the Debian package

$wgVisualEditorParsoidURL = 'http://localhost:8000';

$wgVisualEditorParsoidForwardCookies = true;

$wgSessionsInObjectCache = true;

$wgVisualEditorNamespaces ['*'];

#$wgVisualEditorNamespaces = array( NS_MAIN, NS_TALK, NS_USER, NS_USER_TALK, NS_CATEGORY);

# EXTENSION: Confirm Account

require_once "$IP/extensions/ConfirmAccount/ConfirmAccount.php";

#$wgConfirmAccountRequestFormItems['Biography']['minWords'] = 0;

$wgConfirmAccountRequestFormItems['Biography']['enabled'] = false;

#$wgConfirmAccountRequestFormItems['Areasofinterest']['enabled'] = false;

 $wgMakeUserPageFromBio = false;

 $wgAutoWelcomeNewUsers = false;

 $wgConfirmAccountRequestFormItems = array(

 'UserName'        => array( 'enabled' => true ),

 'RealName'        => array( 'enabled' => true ),

 'Biography'       => array( 'enabled' => false, 'minWords' => 50 ),

 'AreasOfInterest' => array( 'enabled' => false ),

 'CV'              => array( 'enabled' => false ),

 'Notes'           => array( 'enabled' => false ),

 'Links'           => array( 'enabled' => false ),

 'TermsOfService'  => array( 'enabled' => false ),



# Disable reading by anonymous users

$wgGroupPermissions['*']['read'] = false;

# But allow them to access the login page or else there will be no way to log in!

# [You also might want to add access to "Main Page", "Wikipedia:Help", etc.)

# But allow them to read e.g., these pages:

$wgWhitelistRead = array ("Main Page", "Special:Userlogin", "Help:Contents", "-", "Special:Requestaccount", "Toiminnot:Pyydä_käyttäjätunnusta");

#$wgGroupPermissions['*']['createaccount'] = false;

# EXTENSION: Input box

wfLoadExtension( 'InputBox' );

# EXTENSION: Fancy Box Thumbs


# EXTENSION: MediaWiki Chat

require_once "$IP/extensions/MediaWikiChat/MediaWikiChat.php";

# EXTENSION: Access Control


# EXTENSION: User merge and delete

require_once "$IP/extensions/UserMerge/UserMerge/UserMerge.php";

// By default nobody can use this function, enable for bureaucrat?

$wgGroupPermissions['bureaucrat']['usermerge'] = true;

// optional: default is array( 'sysop' )

$wgUserMergeProtectedGroups = array( 'groupname' );

# EXTENSION: Enable Subpages

# Enable subpages in the main namespace

$wgNamespacesWithSubpages[NS_MAIN] = true;

# Enable subpages in the template namespace

$wgNamespacesWithSubpages[NS_TEMPLATE] = true;

# EXTENSION: Hide Prefix 

require_once "$IP/extensions/HidePrefix/HidePrefix/HidePrefix.php";


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

require_once "$IP/extensions/Flow/Flow.php";

#To enable Flow for a namespace, use $wgNamespaceContentModels. For example:




#$wgNamespaceContentModels[NS_USER] = CONTENT_MODEL_FLOW_BOARD;

$wgNamespaceContentModels[NS_TALK] = CONTENT_MODEL_FLOW_BOARD;


$wgFlowContentFormat = 'html';

$wgFlowEditorList = array( 'visualeditor', 'none' );

// 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.

$wgFlowParsoidURL = 'http://localhost:8000'; // also see $wgVisualEditorParsoidURL

$wgFlowParsoidPrefix = $wgDBname; // also see $wgVisualEditorParsoidPrefix

$wgFlowParsoidTimeout = 100; // also see $wgVisualEditorParsoidTimeout

$wgFlowParsoidForwardCookies = true;

//Flow talk notifications

require_once "$IP/extensions/Echo/Echo.php";

Reply to "Using VisualEditor in Flow"
Vojtěch Dostál (talkcontribs)

I just updated the page introduction to reflect the current development - it was confusing to me and I had to do a lot of research in the tech mailing list to understand what is going on. I hope it is all right but please check it. Not sure if it is better to start with "Flow is a project" or "Flow was a project" - the project is probably finished, right?

An update on what will happen to discussion pages in future would be desirable, too. Anyone?:)

Tar Lócesilion (talkcontribs)

AFAIK, (I'm not a WMF employee), Flow isn't directly finished, it's kind of suspended with no promise of continuation except for resolving some minor issues. So it still is a project. But no rush, the page should be updated by a member of the Collaboration team (who, again, AFAIK), are quite busy due to Workflows. And that's Workflows project which should be documented in the first instance, IMHO.

Quiddity (WMF) (talkcontribs)

Yes, Tar Lócesilion explained it well. (Thanks!) Feedback from the communities using Flow, will greatly help in future decisions about how much resources to put towards it.

I've tweaked the page a bit, and will do more as I get time.

There are some notes about the Workflows research at Collaboration/Workflows, but more needs to be added. (I didn't place it at "workflows" because that could be more confusing with workflow (disambiguation page), but I'm happy to change that.)

JoergenB (talkcontribs)

Does this suspended character of the project have bearings on the mass creation of templates on October 2?

I came to this page in order to ask about a handful of templates put on sv-wikibooks by the Flow talk page manager on that day. They do not have any associated wikidata item. They are not categorised. They have scanty documentation. In at least one case, they seem to call templates not existing in our project (or at least not existing with the expected name), causing an error when trying to view the template.

Does the project suspension mean that we had better handle these obstructions to a rational template handling by just deleting the templates; or could we expect that the October 2 templates on diverse projects at least will be collected in wikidata objects?

Regards, JoergenB (talk) 19:33, 8 October 2015 (UTC)

PS: I find a "Cancel" and a "Reply" button under the edit box; but no way to preview my reply. Is this the way iflow is/was supposed to work?

Reply to ""Flow is" or "Flow was"?"

Special:TranslatorSignup & Flow

Trizek (WMF) (talkcontribs)

(Transferred from here) I should say my talk page on d:m: and here are have Special:TranslatorSignup enabled, is this will be affected? --Liuxinyu970226 (talk) 03:34, 1 October 2015 (UTC)

Jay8g (talkcontribs)

Also, what happened to the title of this topic?

SPage (WMF) (talkcontribs)

I see two nifty diagonal 'O B J' glyphs before and after Special:TranslatorSignup. Cool! w:Specials_(Unicode_block) says

U+FFFC  object replacement character, placeholder in the text for another unspecified object, for example in a compound document.
Trizek (WMF) (talkcontribs)

You also see two squares on the <title> displayed (but not on the source) ?

Reply to "Special:TranslatorSignup & Flow"

Collaboration team and Community Tech team updates

Quiddity (WMF) (talkcontribs)

(Copying 2 announcements, by @Ryan Kaldari (WMF) and @Trevor Parscal (WMF) from and )

I'm pleased to announce that the Community Tech team has a new Product Manager – Danny Horn, who will be moving from the Collaboration team to join this new initiative. The Community Tech team is focused on building improved curation and moderation tools for experienced Wikimedia editors. Danny will be working with the team to develop the upcoming Community Wishlist Survey, which will help the team define and prioritize future projects. We're excited to have someone with Danny's product management experience as well as extensive wiki community experience working with this team.

Danny’s role on the Collaboration team will be filled by a new Product Manager which the Foundation is hiring for now. There’s an open job posting on the WMF job board.

Looking forward to working with Danny to build some awesome tools for the community!

Ryan Kaldari Engineering Manager, Community Tech Wikimedia Foundation


Hi. I’d first like to say that I’m excited about Danny’s new role and the positive impact I know he will have on the relatively new Community Tech team, and that he will be missed in the Editing group. This change now leaves an open position, which we are in the process of hiring a new Product Manager to fill. There’s an open position posted.

The Collaboration team, meanwhile, will continue their work to provide Flow as an opt-in Beta feature, allowing contributors to use Flow on their user talk page. This feature is currently available on, and will be enabled on other wikis upon request. Especially as more users enable Flow, the team will continue supporting users of the product by promptly triaging and resolving bugs.

This quarter, which began yesterday, The Collaboration team will be focusing on the development of cross-wiki notifications and other Echo improvements. They’re also continuing to advance efforts to research and prototype solutions for advanced editor workflows. Further feature development on Flow discussion tools will be based on an assessment following the 'workflows' research work, and on editor feedback at the wikis already using Flow.

- Trevor

Reply to "Collaboration team and Community Tech team updates"
Сунприат (talkcontribs)

What should I do to read the message appears at a certain date in the topic? The usual history with the help of round buttons I can see what posts have been added in the past few hours, without attempting to look at the time stamps. On the page history Flow (this applies especially to the big topics) there is no such. However, with notifications come links with which illuminated colored line new posts. In Flow will be an opportunity to highlight new messages between two dates?

Trizek (WMF) (talkcontribs)

Having a diff system as it is on a classical History page may be complicated: each message is independent.

When I click on a notification concerning new messages on Flow, I have a highlight on the Flow board (example). Don't you?

Quiddity (WMF) (talkcontribs)

If I understand correctly, there are 2 requests in this topic.

A way to link to a Flow topic (and board), so that it highlights (with the blue line) just the messages that were added or edited:

  1. between a specific time-span. E.g. just highlighting posts #3, 4, 5, in Topic:Sptu5vsmp6qy7jta (not posts #1, 2, 6, or more). Possibly using the round radio-buttons, similar to
  2. after a specific time-stamp. E.g. highlighting posts #3, 4, 5, 6, in Topic:Sptu5vsmp6qy7jta (not posts #1, 2). Possibly using the cur links.

This would (for example) let people who are not subscribed to a Topic, to still easily keep up-to-date with any changes.

Or (another example) to let people who are investigating a historical discussion, to more easily see what state an entire topic was in, at a specific time.

Is that accurate and complete? If so, #1 is Phab:T108407 and #2 is now phab:T114302. (Can you think of any other example use-cases, to add to that?) Thanks.

Сунприат (talkcontribs)

Yes. When debate comes to life in older topics. I not follow the theme, but suddenly it is at the top. And I have to scroll all in search of fresh dates. Topic:Sdoatsbslsafx6lw

Reply to "Read the latest posts"
Сунприат (talkcontribs)

Recently stopped working flow and flow page history. I found the problem: In the Firefox extension Adblock plus with filter EasyPrivacy ( ). many people use Adblock. Could you check what there interfere with flow

Quiddity (WMF) (talkcontribs)

I've tried enabling the extension, and the additional filter, but Flow and Flow history pages still work for me. Do I need to change any other settings, to reproduce this problem?

Also, please could you check your webconsole (ctrl-shift-k), and see if there are any errors from gadgets or userscripts after a page reload on a Flow page? Gadget/userscripts that give "TypeError" messages, having been creating some problems, tracked at phab:T111624. Thanks. :-)

Сунприат (talkcontribs)

Yes, the filter must be turned on before first loading Flow. If Flow loaded before turning on the filter, then after turning it continues to work. Try: Preferences - Advanced - Network / cached Web content - Clear Privat - delete cookies- delete all

Trizek (WMF) (talkcontribs)

I've also tried (actually, I use EasyPrivacy on Adblock since a long time on Firefox), and I have no errors.

Сунприат (talkcontribs)

This is because the banner! So if you do not close the banner.


Over the Flow board some gray screen. You can not click on it and a "waiting" cursor over it.

Trizek (WMF) (talkcontribs)

Thank you for the precision.

I've tried it on my side (remove cookies to display the banner) and nothing happens (Xubuntu 14.04). I've reported it.

Reply to "EasyPrivacy"
Orlodrim (talkcontribs)

The latest Tech/News says that Flow will be available as a beta feature. What exactly will happen to users that have checked the option "Automatically enable all new beta features"?

I would guess that there will just be a series of automatic renames when it is deployed, but since checking/unchecking the box is more complex than for other beta features (it triggers page moves, and unchecking it leaves a flow board around), I was wondering if anything special had been done about it.

Quiddity (WMF) (talkcontribs)

This feature will NOT be automatically enabled, even if the user has "Automatically enable all new beta features" checked. You can see what it looks like, and test it out the non-latest version, at testwiki:Special:Preferences#mw-prefsection-betafeatures, or the latest version at beta.wmflabs (not part of SUL - new account required).

Orlodrim (talkcontribs)

Thanks for the clarification.

Starting conversion of LiquidThreads to Flow at

Summary last edited by 17:26, 10 August 2015 1 month ago

See also: Discussion at wikitech-l and at Project:Current issues

Planned process at Flow/LQT conversion process

Quiddity (WMF) (talkcontribs)

LiquidThreads (LQT) has not been well-supported in a long time. Flow is in active development, and more real-world use-cases will help focus attention on the higher-priority features that are needed. To that end, LQT pages at will start being converted to Flow in the next couple of weeks.

There are about 1,600 existing LQT pages on Mediawiki, and the three most active pages are VisualEditor/Feedback, Project:Support desk, and Help talk:CirrusSearch. The Collaboration team has been running test conversions of those three pages, and fixing issues that have come up. Those fixes are almost complete, and the team will be ready to start converting LQT threads to Flow topics soon. (If you’re interested in the progress, check out phab:T90788 and linked tasks.) The latest set is visible at a labs test server: and See an example topic comparison here: Flow vs LQT)

The VisualEditor/Feedback page will be converted first (per James' request), around the middle of next week. We’ll pause to assess any high-priority changes required. After that, we will start converting more pages. This process may take a couple of weeks to fully run.

The last page to be converted will be Project:Support desk, as that is the largest and most active LQT Board.

LQT Threads that are currently on your watchlist, will still be watchlisted as Flow Topics. New Topics created at Flow Boards on your watchlist will appear in your Echo notifications, and you can choose whether or not to watchlist them.

The LQT namespaces will continue to exist. Links to posts/topics will redirect appropriately, and the LQT history will remain available at the original location, as well as being mirrored in the Flow history.

There’s a queue of new features in Flow that will be shipped over the next month or so:

  • Table of Contents is done
  • Category support for Flow Header and Topics is done
  • VE with editing toolbar coming last week of March (phab:T90763)
  • Editing other people’s comments coming last week of March (phab:T91086)
  • Ability to change the width & side rail in progress, probably out in April (phab:T88114)
  • Search is in progress (no ETA yet) (phab:T76823)
  • The ability to choose which Flow notifications end up in Echo, watchlist, or both, will be coming up next (no ETA yet)

That being said -- there are some LiquidThreads features that don’t exist in Flow yet. We’d like to hear which features you use on the current LQT boards, and that you’re concerned about losing in the Flow conversion. At the same time, we’d like further suggestions on how we could improve upon that (or other) features from LQT. Please let us know what you think!

He7d3r (talkcontribs)

What happens to my LQT list of "New messages (123)", which I can check periodically at Special:NewMessages, once this conversion is done? Will I lose the list? Will it be moved to my "Messages (1234)" in Echo's menu, so that I can continue to check the list periodically to see what I missed in the last few days/weeks in pages I watch?

DannyH (WMF) (talkcontribs)

We're going to be doing more work on notifications and watchlists over the next month. Right now, you can subscribe to a board and get Echo notifications for new topics, and new posts on topics that you're following show up in Echo and your watchlist.

There are several things that this notification system doesn't do -- one of them is giving the LQT-style overview of what's happened on the page since you were there last. That's one of the things that we need to spec out and build.

Quiddity (WMF) (talkcontribs)

Filed as phab:T93109. Thanks.

John Vandenberg (talkcontribs)

Who will be the main point of contact? How long is the entire conversion process expected to take?

Is there a compiled list of all pages which are planned to be converted, and has any thought been put into determining which pages will be after the first and before the last page to be converted? Is LiquidThreads Test Page going to be converted (it might be a waste of resources to undertake this in production, however it would be a useful test case for being undertaken in a test/qa/beta environment), or is there a list of pages which wont be converted?

Is there an opt-out procedure, where a person/group can opt to restore a page to wikitext?

Is there a process in place to rollback the conversion if bugs are found in the conversion script or Flow software (single page and/or entire conversion)?

Also, I request that user_talk: pages of unsuspecting (i.e. not opt'ed-in) users are not done *early* in the migration. While they might be smaller and easier to migrate, selecting them early in the process will cause a lot of grief as these are a cohort of people who are unlikely to be prepared to be beta testers on their own user_talk page.

Quiddity (WMF) (talkcontribs)

Thanks for the good questions and suggestions. User:DannyH (WMF) and I are the main points of contact.

There's now a (draft) of the planned process, including timeline, at Flow/LQT conversion process, which should answer all of your questions.

Ciencia Al Poder (talkcontribs)

An edit toolbar is definitively handy in Support Desk, and I assume it would be also handy in other boards. Specially to escape markup (<nowiki></nowiki>) and the charinsert extension with other things like <code></code> and <syntaxhighlight></syntaxhighlight>

Florianschmidtwelzow (talkcontribs)

I understand it so, that you still can switch between the actual source editor and the editing toolbar. But i agree: We need a way to edit the plain wikitext (or the editing toolbar needs to support _all_ possible wikitext constructs (VE doesn't actually)).

DannyH (WMF) (talkcontribs)

We're about to release v1 of a VisualEditor toolbar; it should be on Mediawiki in the next couple of weeks. This first version is only going to have four items -- Bold/Italics, Links, Mentions and a switch for wikitext editing. We're definitely going to do more work on toolbars, but we want to see how this first one works before making any solid plans.

Florianschmidtwelzow (talkcontribs)

Sure, but there should be always a switch to view the wikitext version of an answer :)

WhatamIdoing (talkcontribs)

If you're going to add Bold and Italics, could you please also add Code? That gets used a lot on this wiki, and it should be just as easy to add as Bold and Italics.

Qgil-WMF (talkcontribs)

You can check the current iteration at phab:T90764, and more related discussions in phab:T78346.

Ciencia Al Poder (talkcontribs)

Editing other people’s comments is also needed, since new people often paste PHP configurations or logs, without wrapping them inside <pre></pre> tags, so someone needs to fix them to make the posts readable

Florianschmidtwelzow (talkcontribs)

I'm not sure, but i can edit comments from other people, so i think there is an user right, which is currently set to sysop only?

Ricordisamoa (talkcontribs)

Yes, flow-edit-post is only granted to administrators.

Quiddity (WMF) (talkcontribs)

That is changing very soon, per phab:T90670 ("Enable Flow post editing for autoconfirmed users on, English, Russian") as a first step. (Currently in code-review, so nearly here).

Be..anyone (talkcontribs)

Special:ListGroupRights shows flow-edit-post for autoconfirmed today.

Edit by Sänger: And I had to try this asap, seems to work for typing, now the final click on save...

Petrb (talkcontribs)


I think you all missed some old good rants. So here is one :) why the hell is the URL Topic:Sdoatsbslsafx6lw and not something easy to read and remember?

DannyH (WMF) (talkcontribs)

Yeah, I agree that's annoying. We need a unique ID for topics, so that we can do things like moving a topic from one board to another, or generating a feed of the discussions you're involved in. But that gives us ugly links that are impossible to make sense of. There are a couple ideas for how to make them easier to read -- either adding extra text at the end that has the topic title, or generating links that automatically display with the correct title. It's not at the top of the list right now, but it's something we'll need to build.

He7d3r (talkcontribs)


Qgil-WMF (talkcontribs)

Yes, please! Will an opt-in kind of feature ensue, or should I create some LQT discussion pages only to get them converted to Flow soon? 0 :-)

DannyH (WMF) (talkcontribs)

Assuming the LQT conversion goes smoothly, we'll start talking about turning Flow on for pages that don't exist yet, and then the wikitext pages. But feel free to use your own workarounds. :)

Jdlrobson (talkcontribs)

Yeh this works on mobile! Liquid threads 0 flow 1!

He7d3r (talkcontribs)

I can haz togglezz? (phab:T93024)

Kghbln (talkcontribs)

Is there an equivalent to "Special:NewMessages" for Flow? I use this to keep important threads sticky in privacy. I probably could use personal categories for this once it is implemented (for MonoBook?) but these categories would not be private. I cannot really use my watchlist for this since I follow much more threads which only pop up when action takes place. So basically something inbetween inintial notification of a new post and watching all interesting threads will be cool.

Kghbln (talkcontribs)

Admittedly I did not read the talk following the initial post till now. So I am not the only one missing this and I believe that phabricator:T93109 addresses this.

Whatamidoing (WMF) (talkcontribs)

Quiddity, have you tested Flow with MassMessage delivery?

Quiddity (WMF) (talkcontribs)

Yes. It works, but the only problem is phab:T86812. (It pings the sender, if a signature is included)

WhatamIdoing (talkcontribs)

Maybe not quite the only problem: See James F's talk page.

Mattflaschen-WMF (talkcontribs)

In general, please specify the problem you're referring to, as it may not be evident to everyone, or may be fixed later.

I'm assuming you mean {{subst:#ifeq:{{subst:CONTENTLANG}}|en||I apologize for sending this message in English.}} (no subst support). This has been fixed since that post (phab:T68307).

Ciencia Al Poder (talkcontribs)

Am I the only seeing that link as a red link (with redlink=1)?

Florianschmidtwelzow (talkcontribs)

Nope, see phabricator:T105859, too, which I created this morning :)

Mattflaschen-WMF (talkcontribs)

Thank you both for reporting the red link issue.

Florianschmidtwelzow (talkcontribs)

I have another question: Why doesn't Flow use the entire screen width? There is a lot of free space on the right side :(

He7d3r (talkcontribs)

@user:Florianschmidtwelzow: See phab:T88114 .

Florianschmidtwelzow (talkcontribs)

Oh, haven't found this :( But that looks good, would be great to have this design! :)

Quiddity (WMF) (talkcontribs)

After a number of more rounds of testing and tweaking, this has now started, with the first two pages converted per Flow/LQT conversion process.

Please let us know if you can see any problems.

I've heard one comment about there being too many notifications sent, and would like to get more feedback on that. [Update: Bug filed for getting too many notifications - phab:T98996 - they were only meant to show up for threads that we still had as "Unread" in our Special:NewMessages list. Apologies for the noise.]


Quiddity (WMF) (talkcontribs)

Update: The "Day 4" list of the process has now completed.

Some more imperfections were revealed or better understood, and new blocking tasks filed against phab:T92303, particularly including:

Please let us know if you have any other feedback or noticed any problems with these pages. Thanks!

He7d3r (talkcontribs)


He7d3r (talkcontribs)

Are the "watch" stars supposed to be unchecked on each of the LQT topics which were still in my Special:NewMessages? (I continue watching the whole talk pages, but none of the individual topics are marked as watched)

Mattflaschen-WMF (talkcontribs)

It should remain watched if the LiquidThreads thread was watched (we are copying this over).

Special:NewMessages is not the same thing as whether a thread is watched. If a LQT thread is watched, it will say "Unwatch", and otherwise "Watch" (since it's giving you a link to change the status).

Quiddity (WMF) (talkcontribs)

@Mattflaschen-WMF: I believe He7d3r is concerned about pages where he had watchlisted the LQT page, without necessarily interacting with any of the existing threads. LQT would still keep notifying him of any new activity. We plan to do that as a user-option, via phab:T100528 ("Improve organisation and control for (flow) notifications" - see phab:F169936 mockup in particular - feedback there would be appreciated!), but it isn't ready yet.

In the meantime, it would be good to automatically add all old LQT threads to a user's watchlist, if they're watchlisting the whole page. Is that possible? (Both for already converted pages, and for future LQT conversions).

Qgil-WMF (talkcontribs)

My Talk page in Flow! I'm trying to suppress a show-off behavior here, staying civil and humble.  :P

I got more notifications than needed this evening, but if I understand correctly all of them were related to LQT -> Flow conversions, right? Since LQT is not widely used in Wikimedia, this would not be a big problem or a problem at all in most wikis. For wikitext -> Flow conversion of discussion pages, no notifications should be sent for regular pages, but one notification would be welcome to notify users that their Talk page has changed to Flow.

Also, what happens with subpages of Talk pages with discussion? I don't think I have any (definitely not with LQT), but as a theoretical case...

Qgil-WMF (talkcontribs)

Mmm, in fact User talk:Qgil-WMF/LQT Archive 1 is not "an archived LiquidThreads page" as the template says. Only the wikitext part is there, the LQT was converted to Flow topics, and they are in User talk:Qgil-WMF. A small detail, since the text of the template can be simply edited.

Also, the format of the title of the converted LQT topics containing a link (Tech News) looks bad now, but maybe this is also a transitional problem? I'll wait till next Monday to see how the new Tech News topic looks like.

Ciencia Al Poder (talkcontribs)

Flow topics do not allow wikitext AFAIK, so all wikitext in old headers will be shown as raw wikitext instead. Apparently, LQT allowed links there Thread:LiquidThreads_Test_Page/Test_message_with_a_link_to_Extension:LiquidThreads_in_the_header

He7d3r (talkcontribs)

See T59153.

Mattflaschen-WMF (talkcontribs)

All the LQT content is in fact archived (not just the Flow version, but also the original versions), but it is not shown on that page because it's no longer a LQT talk page. Like you suggested, changing the template is possible.

Flow topic titles do not support wikitext.

Qgil-WMF (talkcontribs)

The script leaves a comment in the description of the new Flow Talk page: "Previous page history was archived for backup purposes at User talk:Qgil-WMF/LQT Archive 1 on 2015-06-10."

In future migrations, I think it would be useful to use this chance to link to a Flow help page, for the owner of the Talk page and whoever lands there. The description can be edited, so users can just remove it whenever they want.

Ciencia Al Poder (talkcontribs)

With LQT, following a talk page automatically gave you notifications on every LQT post/edit of that page. But this doesn't seem to be true with flow posts (at least in Project:Current issues in my case)

Qgil-WMF (talkcontribs)

Actually this is for me a key feature of Flow over LQT or wikitext discussions. While I am not able to follow i.e. Village Pump Technical (and every time I watch that page I end up unwatching it because I can't cope with that rhythm of updates), with Flow I could receive notifications for new threads, and then subscribe only to those I care about. It makes a whole difference, which is almost critical for more casual contributors with less time to invest following discussions.

Ciencia Al Poder (talkcontribs)

I wasn't aware that Flow notifies about new threads. If that's true, that's fine, then. A good idea, indeed.

The problem is that is a changed behavior over LQT, not sure if well documented, and unexpected over existing messages that were converted to flow which weren't automatically followed when the conversion was done, so I had to manually subscribe to them (after noticing I received no notifications)

He7d3r (talkcontribs)

FYI: that is the main feature of a gadget used on Portuguese Wikipedia since ~4 years ago. See

Sänger (talkcontribs)

No, you only have two choices:

  1. Watch the whole page and get informed over new topics (but not new posts)
  2. Watch a thread and get informed about any new post in it

If you want to get everything, you have to watch every new thread manually after being informed about it via #1

Quiddity (WMF) (talkcontribs)

At phab:T100528 there are some ideas around increasing the control that editors have, beyond what we currently have with wikitext/LQT/Flow. See the 3rd and 4th image in the description, for the TL;DR.

Rich Farmbrough (talkcontribs)

You asked for comments here. Which shows a problem in that there is no-where to comment, only reply - and which comment should I reply to?. I'm not sure if this project has been abandoned or not but if not:

  • I thanked someone I was then unable to reply to his thread.
  • I can't see the date stuff was posted - oh it's a mouse over.- hidden information is not useful
  • The use of a "..." icon is not intuitive, I stumbled across it. There's a reason we have "v t e" on navboxes, it works and is relatively clear. Unfortunately we were forced to have V T E which goes completely against the WP style..
  • No preview WTF? - ohh unless I swap editors form the one it gives me - which breaks the markup even when I fix it.

Rich Farmbrough 17:21, 14 September 2015 (UTC).

Mattflaschen-WMF (talkcontribs)

You can reply to a post, or reply to a topic. To reply to the topic, you can use the textbox at the very bottom of the topic.

The project has not been abandoned. Per the announcement, "Flow will be maintained and supported".

I was not able to reproduce the 'thank' issue, and I have not heard that reported before. Please provide exact steps, and your browser.

The intention with the dates is that you can see the most commonly wanted information (human-readable dates) immediately, while getting the exact dates by mouseover or on the history page. But see phab:T94648.

If you are having issues with switching to VisualEditor, please let us know or file them in Phabricator. We will track down the underlying issue.

He7d3r (talkcontribs)

See and phab:T100996-->phab:T69258 for the issues with VE.

Rogol Domedonfors (talkcontribs)

Is there a browser support matrix for Flow? (I would have added this as a new topic, but it seems that my browser is imperfectly supported ...)

Mattflaschen-WMF (talkcontribs)

I don't think this is explicitly listed anywhere, but our matrix is in practice similar to Grade A at that link (for JavaScript support). More browsers have full no-JS support.

To help us figure out the problem you experienced, please note your browser, browser version, what you tried, and what happened.

You can file on Phabricator or reply here.

Reply to "Starting conversion of LiquidThreads to Flow at"

Request: magic word for the topic

Summary by Trizek (WMF)

Reported: task T113230

Сунприат (talkcontribs)

I would like use it like this in the phabricator. In the phabricator you write "{{T123}}" and get the link "T123:Page name". For Flow that might look like ""{{Topic:123}}" and get the link "T123:Page name""

Trizek (WMF) (talkcontribs)

Good suggestion. I've reported it (but I didn't find your Phabricator account).

At the moment, quoting this way {{Topic:Spbw1hvvrt474nb3}} does not embed the conversation.

Reply to "Request: magic word for the topic"
Сунприат (talkcontribs)

Will be there a way to see all unresolved topics? When a scrollbar is small you can estimate the volume of pages, but in the normal Flow did not know where the bottom is.

Trizek (WMF) (talkcontribs)

The Browse topic bar lets you find all topics on the page. The solved ones are grey links.

There is plans to add more information on this browsing bar. A filter should be a good option, too.

Subfader (talkcontribs)

Hui, looking forward to that :)

Сунприат (talkcontribs)

Then the the filter must be part of the priorities of the workflow and not in Freezer.

Reply to "Workflow"