Extension talk:StructuredDiscussions

Jump to navigation Jump to search

About this board

Any questions about the StructuredDiscussions extension.

Summary by Uvas magicas

for the problem this use the next patch

Uvas magicas (talkcontribs)

when trying to publish a topic in flow in visual edition I get this

[c5691ad38140b1463dccece8] Caught exception of type Flow \ Exception \ WikitextException

Valirius (talkcontribs)

I don't understand something by namespaces.

It's kind of

$wgNamespaceContentModels [NS_TALK] = 'flow-board';

$wgNamespaceContentModels [NS_USER_TALK] = 'flow-board';

configured in the config,

but there is no sense, it still gives an error

Fail to create title from namespace 2600 and title text 'w9wvzwvqp5gb5efg'

And judging by the info from MW (https://www.mediawiki.org/wiki/Extension_default_namespaces) - 2600 is just from him NameSpace.

It seems to me that you just need to add something correct in the config. Distribute roofing felts, declare namespace roofing felts.

Can someone help with this?

Reply to "Problem with Namespaces"

Flow + VisualEditor + Parsoid

Sokote zaman (talkcontribs)


With respect

I want to use the Flow plugin in version 1.35:

  1. Do I have to install and configure Parsoid independently to use the VisualEditor?
  2. If you do not need to install Parsoid to use the visual editor, then why does Flow make a mistake when using the VisualEditor?

[d7e427f10354b27af79815a5] Caught exception of type RuntimeException

Thanks to the support team members

Reply to "Flow + VisualEditor + Parsoid"

HTML to Wikitext Conversion Issue

Knomanii (talkcontribs)

I just did a fresh install of Mediawiki 1.35 with Flow-REL1_35.

When I click "Save" on any Flow comment with VisualEditor, I get this HTML to Wikitext conversion error.

What caused this error?

I did only the basic setup for VisualEditor and Flow with MW-1.35 — are any special Parsoid settings needed?

Any help would be appreciated.

Error message
Knomanii (talkcontribs)

Bump. Anyone able to help?

This extension does not work with a fresh install of 1.35.0. Is a RESTBase required or something?

Knomanii (talkcontribs)

Alternatively, if there's not a way to fix Visual Editing, can I disable it? Is it possible to only allow Source Editing?

Any help would be appreciated!

Sophivorus (talkcontribs)

I'm experiencing the same issue, only that I just upgraded from 1.34 to 1.35. On regular pages, the visual editor is working fine.

For now I 'fixed' it by disabling visual editing on talk pages, by setting $wgFlowContentFormat = 'wikitext';

I reported the issue at https://phabricator.wikimedia.org/T267407

Msnhinet8 (talkcontribs)

Me too, how can i do?

Spas.Z.Spasov (talkcontribs)


I'm experiencing the same problem. Recently I've switched from MW 1.34 to 1.35. Visual Editor works fine everywhere except Flow. I'm using the autoconfigure mode, so $wgVirtualRestConfig is not set. At the moment I found three different error messages:

Somme errors occurred with mw:Extension:Flow REL1_35, 07.11.2020

(1) When I'm tring to edit an old existing comment:

An error occurred. The error message received was: internal_api_error_Flow\Exception\WikitextException

(2) When I'm tring to save a comment in visual mode:

[X6akA72QQzSDKWPFYEuVSAAAAAU] Exception caught: Conversion from 'html' to 'wikitext' was requested, but core's Parser only supports 'wikitext' to 'html' conversion

(3) When I'm trying to switch from visual to text mode (the other direction works):

Unable to transfer content: Error contacting the server for conversion between wikitext and HTML. Please check your Internet connection or try again later if the problem persists. If you still get this error please file a bug

Here is my current Setup:

wfLoadExtension( 'VisualEditor' );
$wgGroupPermissions['user']['writeapi'] = true;
$wgSessionsInObjectCache = true;
$wgVisualEditorAvailableNamespaces = array(
        NS_USER => true,
        NS_HELP => true,
        NS_PROJECT => true,
        NS_TEMPLATE => true,
        NS_LINK => true

wfLoadExtension( 'Flow' );
$wgFlowContentFormat = 'html';
$wgFlowEditorList = array( 'visualeditor', 'none' );
$wgFlowParsoidTimeout = 100;
$wgFlowParsoidForwardCookies = true;

My additional research:

  1. I can switch between the visual and text mode only when I'm creating a new comment. Or sometimes when I save the post after 3rd message occurs, bot not every time.
  2. 1st problem appear when I'm in a text mode. If I'm in visual mode I can open an existing comment for edit, but of course I can't save it because of the 2nd issue.
  3. I can't say using $wgFlowContentFormat = 'wikitext'; solve any of the issues.
  4. Using $wgFlowEditorList = array( 'wikitext' ); in order to force the usage only of the wikitext editor doesn't work.
  5. $wgFlowContentFormat and $wgFlowEditorList doesn't change anything at all.

Does we need something like $wgGroupPermissions['flow']['writeapi'] = true;?

Cloudcell (talkcontribs)

bump. I'm experiencing the same issue. Tried everything.

Knomanii (talkcontribs)

Anyone know if this will be patched in MW-1.35.1?

Per phab:T267407, phab:T260648#6645078 seems to be the patch but I can't tell if it will be included in 1.35.1 or if it will resolve this issue downstream. (talkcontribs)

Running into the same issue. Tried switching flow content formats as well, no luck. Has anybody figured this out?

Cloudcell (talkcontribs)
2001:E60:B00C:A4BF:553D:8BF:6BB4:7CEC (talkcontribs)

Bump. Same issue using MW 1.35.1

Spas.Z.Spasov (talkcontribs)

I can't confirm the issue disappear with MW 1.35.1, but I can confirm the patch (phab:T260648#6645078) provided above works!

Knomanii (talkcontribs)

I just upgraded to MW 1.35.1 and encountered the same issue. I checked and the patch you mentioned (phab:T260648#6645078) was not included in 1.35.1. :(

But I was able to apply the patch, and it worked! Though I do hope WMF includes it in the next upgrade… I'm afraid it'll get overwritten when our staff upgrades our wiki next. They may not know how to fix this issue and ditch mediawiki altogether. It's somewhat frustrating that out-of-the-box fresh installs are this difficult to get working.

Anyhoo, thanks for mentioning the patch! I'm really glad it worked.

Beginneruser (talkcontribs)


I have same top error when use following config:

wfLoadExtension( 'VisualEditor' );
wfLoadExtension( 'Flow' );
$wgFlowContentFormat = 'html';

But when change config by remove the wfLoadExtension( 'VisualEditor' );

wfLoadExtension( 'Flow' );
$wgFlowContentFormat = 'html';

Error solve in Flow, But Visual Editor is disable

How use Visual Editor + Flow without error in Mediawiki 1.35.1 LTS version

Please help me!

Tinss (talkcontribs)
Beginneruser (talkcontribs)
MarkAHershberger (talkcontribs)

I'm not sure why I'm pinged here, but looking at the patch in gerrit, it looks like it has been forgotten about.

Reply to "HTML to Wikitext Conversion Issue"

SOLVED - How to post a Flow Topic using MWClient?

Summary by Revansx

API method provided

Revansx (talkcontribs)

RHEL7 + MW 1.34.4 + Flow 1.1.1

We use mwclinet on our MW server to do a variety of maintenance and support tasks. In certain situations, we would like to have an mwclient script generate a flow topic on a talk page.

Is it just an API call per the Flow API documentation or is there another way?

Ammcgillivray (talkcontribs)

Technical question: why don't comments show up in xtools?

Elli (talkcontribs)

I was looking at my contributions on xtools and comments I've made in threads here don't show up. Are the contributions handled differently on the backend?

DKinzler (WMF) (talkcontribs)

Yes, Flow re-implements many aspects of MediaWiki (like revision history, watchlist, protection, etc) and then tries to re-integrate with the standard UI and API. This integration is however incomplete.

Reply to "Technical question: why don't comments show up in xtools?"

Get notifications for topics but not talk pages

Novem Linguae (talkcontribs)

Hello. What's the best way to make sure that I can 1) watchlist entire talk pages, 2) not get ping notifications when a new topic is created, 3) get ping notifications when my specific topic(s) on that talk page get a reply? In preferences -> notifications, I found the "Structured Discussion" option, but I think it turns off both 2 and 3? Thank you.

Reply to "Get notifications for topics but not talk pages"

Missing messages in Structured Discussions after deploying a database from a backup

Summary by Rogue Vor tex

it turned out that all flows write the name of the database to the table and if you changed the name of the database, then all the old flows do not work, the saddest thing is that I did not find a script for servicing how to fix it, I decided by simply creating a database with the name as it was before so as not to edit in DB nothing handles, I decided to share here

Rogue Vor tex (talkcontribs)

I moved my wiki 1.34 to another hosting and when I deployed the database all messages in Structured Discussions disappeared, but when I tried to create a new discussion everything works fine, how can I get my messages back while the old wiki is still running where all the messages are still there?

Such a message on all pages where messages were left in the discussions:

Unknown topic

Return to Main Page

[ec6a92449bc3d4db30961b24] /wiki/%D0%9E%D0%B1%D1%81%D1%83%D0%B6%D0%B4%D0%B5%D0%BD%D0%B8%D0%B5:%D0%9E%D1%82%D1%81%D1%82%D0%B0%D0%B2%D0%BD%D0%BE%D0%B9_%D0%9F%D0%BE%D0%BB%D0%BA%D0%BE%D0%B2%D0%BD%D0%B8%D0%BA Flow\Exception\UnknownWorkflowIdException from line 127 of /home/admin/web/so-wiki.ru/public_html/w/extensions/Flow/includes/WorkflowLoaderFactory.php: The requested workflow does not exist on this wiki.


#0 /home/admin/web/so-wiki.ru/public_html/w/extensions/Flow/includes/WorkflowLoaderFactory.php(103): Flow\WorkflowLoaderFactory->loadWorkflowById(Title, Flow\Model\UUID)

#1 /home/admin/web/so-wiki.ru/public_html/w/extensions/Flow/includes/Actions/Action.php(105): Flow\WorkflowLoaderFactory->createWorkflowLoader(Title)

#2 /home/admin/web/so-wiki.ru/public_html/w/extensions/Flow/includes/Actions/ViewAction.php(20): Flow\Actions\FlowAction->showForAction(string, OutputPage)

#3 /home/admin/web/so-wiki.ru/public_html/w/extensions/Flow/includes/Actions/Action.php(50): Flow\Actions\ViewAction->showForAction(string)

#4 /home/admin/web/so-wiki.ru/public_html/w/includes/MediaWiki.php(511): Flow\Actions\FlowAction->show()

#5 /home/admin/web/so-wiki.ru/public_html/w/includes/MediaWiki.php(302): MediaWiki->performAction(Article, Title)

#6 /home/admin/web/so-wiki.ru/public_html/w/includes/MediaWiki.php(900): MediaWiki->performRequest()

#7 /home/admin/web/so-wiki.ru/public_html/w/includes/MediaWiki.php(527): MediaWiki->main()

#8 /home/admin/web/so-wiki.ru/public_html/w/index.php(44): MediaWiki->run()

#9 {main}

Ciencia Al Poder (talkcontribs)

I guess it could have been controlled with the $wgFlowDefaultWikiDb setting. I'll give a mention about that

Reply to "Missing messages in Structured Discussions after deploying a database from a backup"

Duplicate NS_TALK on the page?

Herakuresu (talkcontribs)


any ideas on how to duplicate on the single page the namespaces NS_TALK to have two different section of discussion (something like "$wgNamespaceContentModels[NS_TALK_2] = 'flow-board'"? Thank you for help

Revansx (talkcontribs)

I have wished for this too and have decided that the most logical way to do it is to develop a custom skin that renders both the content page and the talk page in side-by-side user-adjustable frames and allows the user toggle back and forth between them and change the ratio of the divider and even collapse one side entirely.

I have also envisioned a widget that would generate a fly-out talk topic that would pop open and closed from where the widget is embedded in the content.

That said these options do not exist. The best option I know about is the Extension:CommentStreams which I think was developed specifically for the purpose you are asking for.


Herakuresu (talkcontribs)

What do you think about create a Namespace and add a custom js that append the new voice at the side of Discussion that link at new namespace with the same pagetitle of main namespace? Or edit a skin (I don't know how yet) and add manually custom link to other namespace

Herakuresu (talkcontribs)
Revansx (talkcontribs)

In my early days (MW 1.17 - 1.27) I was excited about implementing cool custom things that I conceived very much like what you are describing here, but I eventually realized the hard way that I don't have time to maintain custom skins and extension as MW updates and changes. So I would say, for a temporary wiki for a single short-term project, you should defiantly go for it to the extent that you have the time and energy, but if you're main goal is to establish a stable long-term production application, I wouldn't stray too far from established configurations and products. I have regretted it every time I have ever tried.. and I've tried a lot! lol Good luck!

Reply to "Duplicate NS_TALK on the page?"
NGC 54 (talkcontribs)

"[09f7c37cb8ead58a2b338e39] Exception caught: Request to parsoid for "wikitext" to "html" conversion of content connected to title "Discuție_Utilizator:Administrator" failed: (curl error: 28) Timeout was reached".


Reply to "Error"