Extension talk:StructuredDiscussions/2021

Any questions about the StructuredDiscussions extension.

Error

"[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".

Solution? --Paloi Sciurala (talk｜contribs) 16:59, 21 January 2021 (UTC)

Duplicate NS_TALK on the page?

Hello,

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 Herakuresu (talk) 13:05, 3 March 2021 (UTC)

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.

/Rich Revansx (talk) 13:51, 3 March 2021 (UTC)

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 (talk) 14:53, 3 March 2021 (UTC)

Herakuresu (talk) 14:49, 3 March 2021 (UTC)

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! Revansx (talk) 16:14, 3 March 2021 (UTC)

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

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

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.

Backtrace:

#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} Rogue Vor tex (talk) 12:57, 13 March 2021 (UTC)

I guess it could have been controlled with the $wgFlowDefaultWikiDb setting. I'll give a mention about that Ciencia Al Poder (talk) 15:31, 15 March 2021 (UTC)

Get notifications for topics but not talk pages

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. –Novem Linguae (talk) 14:58, 16 March 2021 (UTC)

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

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? Elli (talk) 06:52, 7 April 2021 (UTC)

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. DKinzler (WMF) (talk) 09:20, 7 April 2021 (UTC)

SOLVED - How to post a Flow Topic using MWClient?

The following discussion is closed. Please do not modify it. Subsequent comments should be made on the appropriate discussion page. No further edits should be made to this discussion.

---

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? Revansx (talk) 13:22, 7 April 2021 (UTC)

token = site.get_token('flow')
site.post(action='flow',submodule='new-topic',page='Talk:Main Page',nttopic='Example',ntcontent='This is a test.',token=token)

see: Extension:StructuredDiscussions/API#new-topic Ammcgillivray (talk) 16:31, 7 April 2021 (UTC)

The discussion above is closed. Please do not modify it. No further edits should be made to this discussion.

Flow + VisualEditor + Parsoid

Hello

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 Sokote zaman (talk) 21:10, 4 May 2021 (UTC)

flow

for the problem this use the next patch - The patch with MW 1.38.0 and Flow 1.2.0 (74ffd17) 08:41, 26 May 2022 does not work, or you can config the next variable: $wgVirtualRestConfig['modules']['parsoid']['url'] and point to the url access of the rest.php of the wiki.

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

[c5691ad38140b1463dccece8] Caught exception of type Flow \ Exception \ WikitextException Uvas magicas (talk) 02:20, 26 May 2021 (UTC)

Problem with Namespaces

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? Valirius (talk) 09:47, 30 May 2021 (UTC)

Call to undefined method ContribsPager::getTagFilter()

Hi guys,

hope someone can help. I'm on mw 1.35.3 and I get

/var/www/html/w/extensions/Flow/includes/Hooks.php: Call to undefined method ContribsPager::getTagFilter()

How can I fix it? 193.16.224.3 (talk) 21:58, 14 July 2021 (UTC)

What you say doesn't seem to match the code.

REL1_35 has the method ContribsPager::getTagFilter() https://phabricator.wikimedia.org/source/mediawiki/browse/REL1_35/includes/specials/pagers/ContribsPager.php$434 Ciencia Al Poder (talk) 10:00, 15 July 2021 (UTC)

Error when adding text with VisualEditor

The following discussion is closed. Please do not modify it. Subsequent comments should be made on the appropriate discussion page. No further edits should be made to this discussion.

---

Hi team!

When I add text at Discussion pages with VisualEditor (not source editing) I have an error (see screenshot).

When I post messages with source editing then everything works perfect. How can fix the bug? Fokebox (talk) 21:53, 12 August 2021 (UTC)

What version MW? What version StructuredDiscussions? Check your Special:Version page and share the version info of the pertinent software. Revansx (talk) 23:26, 12 August 2021 (UTC)

I have:

|MediaWiki

|1.35.3

|-

|PHP

|7.4.21 (cgi-fcgi)

|-

|MySQL

|5.7.34

|-

|ICU

|57.1

|-

|Lua

|5.1.5

|}

Flow:

|Flow

|1.2.0 (28ad95e) 22:21, 22 July 2021

|}

This patch helped as in the topic below. Fokebox (talk) 07:45, 13 August 2021 (UTC)

Hi! I have updated my wiki to 1.38.0:

!Продукт

!Версия

|-

|MediaWiki

|1.38.0

|-

|PHP

|7.4.28 (cgi-fcgi)

|-

|MySQL

|5.7.27-30

|-

|ICU

|50.1.2

|-

|Lua

|5.1.5

|}

Flow:

|Flow

|1.2.0 (74ffd17) 08:41, 26 May 2022

|}

And the problem is back again. When I have a message made in VisualEditor I have error again. The patch I used to have (linked above) doesn't work, i.e. now it makes discussion pages with error. How to resolve the problem? Fokebox (talk) 13:56, 3 June 2022 (UTC)

This patch has resolved the problem. I hope that the solution will be deployed in future versions of extension Fokebox (talk) 07:29, 10 June 2022 (UTC)

The discussion above is closed. Please do not modify it. No further edits should be made to this discussion.

Timeout When Trying to Mention a Group of Users

The subject says it all: when I try to mention a group of users using <nowiki>{{FlowMention}}</nowiki> I get a timeout error. It happens, too, when just using links to the User accounts. I'm using Mediawiki 1.36.1 and StructuredDiscussions (Flow) 1.2.0 (5b40a68). I sewe a couple of mentions for timeout config settings on the extension page, but I'm not sure which, if any, might be applicable. Any insight would be appreciated. Grlucas (talk) 13:04, 26 August 2021 (UTC)

Update: It appears the post still worked when I refreshed the page. Still it would be nice to have the page update and not see the timeout. Grlucas (talk) 13:15, 26 August 2021 (UTC)

Move topic to a different flow (as admin)?

How can I move a topic to a different flow? 2001:16B8:121B:A000:548E:445:1A89:E74D (talk) 12:05, 28 August 2021 (UTC)

Using Flow version 0.1.0 2001:16B8:121B:A000:548E:445:1A89:E74D (talk) 12:39, 28 August 2021 (UTC)

"Changes recovered" Warning wrongly stating that board description (header) has unsaved changes

Hello,

When I edit the board description (header) of a talk page, I can save normally but if I click again on "Edit description", a warning "Changes recovered" appears, saying: "Your unsaved changes have been automatically recovered."

More problematic, if I refresh the page, the board description will spontaneously becomes editable with the same warning:

The only way to get rid of the warning is clicking on "Cancel", and we can then observe that the description was well saved.

I observe the problem with both Visual Editing and Source Editing

Does anybody encountered the same issue?

(Re)tested on a fresh install:

Mediawiki 1.35.3

Flow 1.2.0 (28ad95e)

VisualEditor 0.1.2 Jiou7 (talk) 21:56, 6 September 2021 (UTC)

The message you're seeing probably relates to an abandoned edit of the Discussion Page (Topic). The auto-recovery feature comes from Visual Editor. If you click on the 'Discussion' tab when the "Changes recovered" message appears, it will hopefully give you the option to "Abandon your unsaved changes". Greg Rundlett (talk) 14:58, 8 September 2021 (UTC)

Thank you for your answer. There is no abandoned edit in my case. I have the same issue with an empty talk page (no topic, no post).

If I click on the Discussion tab when the warning appears, I have the option to "abandon the unsaved changes" but they will be proposed to me again with the same warning when the page appears.

From an empty talk page (new page), here is what I observe:

- I create the description/header for the first time before any topic and I save. Then the page will be automatically refreshed (which seems to be normal, this is also the case if I create a topic first)

- I refresh the page and nothing weird happens, the description is in place and does not become editable and no warning appears

- I edit the description and I save. All good, no error.

- I refresh the page and then the description becomes automatically editable, the box being filled with the previously entered description and with the above-mentioned warning.

- it appears again if I refresh the page, even if I save again. It will stop appearing if I "cancel" and "discard changes". When I do, the description is actually the one which was said to be unsaved.

- all further edits willl display the same behavior.

If there is an existing topic on the talk page before I create the description for the first time, then I will directly have the buggy behavior (the warning/editable input box appear at first refresh, skipping the two first steps listed above). Jiou7 (talk) 21:18, 8 September 2021 (UTC)

Please apply patch 622258 to the repository

Yesterday I switched from MW 1.35 to MW 1.36 by using git and Extension:Flow expires the same problem discussed bellow. At the end of the discussion MarkAHershberger says: "I'm not sure why I'm pinged here, but looking at the patch in gerrit, it looks like it has been forgotten about." The solution of this and this topics was the same patch.

I can confirm the patch works like a charm with MW 1.36 too, but we still need to apply it manually. Spas.Z.Spasov (talk) 10:55, 3 October 2021 (UTC)

It currently breaks the tests, which suggests that it doesn't "work like a charm" entirely. However, gerrit is the right venue for code review requests. :-) Jdforrester (WMF) (talk) 16:52, 4 October 2021 (UTC)

Flow Board Description on the left

Presently, the Flow Board Description appears on right-hand side of the Flow Talk page.

How hard would it be to make a configuration parameter that configures flow to show the Flow Board Description on the left-hand side? Could this be done with Common.css?

(Sometimes it's the little things 😀 )

/Rich Revansx (talk) 14:46, 19 November 2021 (UTC)