Jump to content

Extension talk:StructuredDiscussions/2020

Add topic
From mediawiki.org

Any questions about the StructuredDiscussions extension.

Flow board not showing up in NS_TALK (but works in NS_USER_TALK)

[edit]

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.


On my way to upgrade from MW 1.31 to 1.34...

Ran maintenance scripts. In LocalSettings.php, I have $wgNamespaceContentModels[NS_TALK] = 'flow-board';.

When I display a talk page, I get {"flow-workflow":"ukgb3icb8mwig3lr"} even if the content model of that page is flow-board. Flow is working fine in NS_USER_TALK and NS_PROJECT_TALK.

It seems that MW is ignoring the content model of that page and simply displaying it as wikitext...

Thanks! Tinss (talk) 07:08, 21 January 2020 (UTC)Reply

Deleting the talk page makes flow appear again. But all discussions get lost in the process.
On investigating the issue, it appears to be a bug with MW 1.34's migration and handling of content models. I've filed a bug with the issue. Tinss (talk) 20:51, 21 January 2020 (UTC)Reply
The problem disappeared with erasing the current DB, loading a backup and redoing the update. Tinss (talk) 02:01, 22 January 2020 (UTC)Reply
The discussion above is closed. Please do not modify it. No further edits should be made to this discussion.

Reply alignment of last comment seems to be wrong

[edit]
Hi,
If you reply on the last comment of a (threading) depth, then the reply has the same depth as the comment. Is there a way to fix that?
I'm on mediawiki version 1.31. 2A02:8071:B9D:DD00:2169:FC6D:D7E5:A2E6 (talk) 23:26, 8 February 2020 (UTC)Reply
This is my second reply to my first comment and has now depth +1 as I would expect to be for the first reply to my first comment. 2A02:8071:B9D:DD00:2169:FC6D:D7E5:A2E6 (talk) 23:29, 8 February 2020 (UTC)Reply
This is a reply to my first comment and has the same depth as my first comment. 2A02:8071:B9D:DD00:2169:FC6D:D7E5:A2E6 (talk) 23:27, 8 February 2020 (UTC)Reply
I think it’s intentional and it’s better this way. People normally reply to the last message in a thread, and if that one would also be indented, we would quickly run out of horizontal place: at most one word would fit in a line, the rest would be the indentation. In wikitext discussions this issue caused the rise of hacks like {{Outdent }}, but SD’s current implementation makes them needless. Tacsipacsi (talk) 23:38, 8 February 2020 (UTC)Reply
Well yes, but it does not make sense that his second reply would be above his first reply. MavropaliasG (talk) 04:17, 9 February 2020 (UTC)Reply
@MavropaliasG yes, that's how I see it too.
@Tacsipacsi You can set $wgFlowMaxThreadingDepth.
So for me it's very strange and unintuitive. Hope it's a bug and will be soon fixed :) 2A02:8071:B9D:DD00:5AE:3D80:82A6:44FD (talk) 20:38, 9 February 2020 (UTC)Reply
As discussions are usually linear, this second reply to the same message case is relatively rare, may happen a lot after the first reply, and is usually a short subthread. If I now replied to the first message, and each message would be indented as you imagine, it would look like (intentionally ignoring 2A02:8071:B9D:DD00:2169:FC6D:D7E5:A2E6’s second reply):
2A02:8071:B9D:DD00:2169:FC6D:D7E5:A2E6
2A02:8071:B9D:DD00:2169:FC6D:D7E5:A2E6
Tacsipacsi
MavropaliasG
2A02:8071:B9D:DD00:5AE:3D80:82A6:44FD
Tacsipacsi
Tacsipacsi
It’s a lot harder for me to follow. I think it’s an intentional feature, so won’t be β€œfixed”, although I don’t know anything certain about this matter. Tacsipacsi (talk) 23:24, 9 February 2020 (UTC)Reply

Exception caught: Request to parsoid for "wikitext" to "html" conversion of content connected to title "TΓ³pico:Vhaglhbjzfms3qgm" failed: (curl error: 28) Timeout was reached

[edit]

Hi there!

After installing the extension, its dependencies and Parsoid, when I go to create a topic, it returns the following:

Exception caught: Request to parsoid for "wikitext" to "html" conversion of content connected to title "TΓ³pico:Vhaglhbjzfms3qgm" failed: (curl error: 28) Timeout was reached

Backtrace:

#0 /var/lib/mediawiki/extensions/Flow/includes/WorkflowLoaderFactory.php(103): Flow\WorkflowLoaderFactory->loadWorkflowById(Title, Flow\Model\UUID)

#1 /var/lib/mediawiki/extensions/Flow/includes/Actions/Action.php(105): Flow\WorkflowLoaderFactory->createWorkflowLoader(Title)

#2 /var/lib/mediawiki/extensions/Flow/includes/Actions/ViewAction.php(20): Flow\Actions\FlowAction->showForAction(string, OutputPage)

#3 /var/lib/mediawiki/extensions/Flow/includes/Actions/Action.php(50): Flow\Actions\ViewAction->showForAction(string)

#4 /var/lib/mediawiki/includes/MediaWiki.php(499): Flow\Actions\FlowAction->show()

#5 /var/lib/mediawiki/includes/MediaWiki.php(294): MediaWiki->performAction(Article, Title)

#6 /var/lib/mediawiki/includes/MediaWiki.php(865): MediaWiki->performRequest()

#7 /var/lib/mediawiki/includes/MediaWiki.php(515): MediaWiki->main()

#8 /var/lib/mediawiki/index.php(42): MediaWiki->run()

#9 {main}


Environment:

Debian 9

MediaWiki 1.33.1
PHP 7.1.33-10+0~20200220.32+debian9~1.gbpd6a133 (apache2handler)
MariaDB 10.1.44-MariaDB-0+deb9u1
Elasticsearch 6.8.6
Lua 5.1.5

Node.js 10

api.php /api.php

Parsoid 11

/etc/mediawiki/parsoid/config.yaml

services:

  - module: ../src/lib/index.js

   entrypoint: apiServiceWorker

   conf:

       # For backwards compatibility, and to continue to support non-static

       # configs for the time being, optionally provide a path to a

       # localsettings.js file.  See localsettings.example.js

       #localsettings: ./localsettings.js

       # Set your own user-agent string

       # Otherwise, defaults to:

       #   'Parsoid/<current-version-defined-in-package.json>'

       #userAgent: 'My-User-Agent-String'

       # Configure Parsoid to point to your MediaWiki instances.

       mwApis:

       - # This is the only required parameter,

         # the URL of you MediaWiki API endpoint.

         uri: 'https://ius.wiki.br/api.php'

         # The "domain" is used for communication with Visual Editor

         # and RESTBase.  It defaults to the hostname portion of

         # the `uri` property below, but you can manually set it

         # to an arbitrary string.

         #domain: 'localhost'  # optional

         # To specify a proxy (or proxy headers) specific to this prefix

         # (which overrides defaultAPIProxyURI). Alternatively, set `proxy`

         # to `null` to override and force no proxying when a default proxy

         # has been set.

         #proxy:

         #    uri: 'http://my.proxy:1234/'

         #    headers:  # optional

         #        'X-Forwarded-Proto': 'https'

/var/log/parsoid/parsoid.log

{"name":"parsoid","hostname":"ius-wiki-br","pid":6387,"level":30,"levelPath":"info/service-runner","msg":"master(6387) initializing 1 workers","time":"2020-02-23T14:04:32.117Z","v":0}{"name":"../src/lib/index.js","hostname":"ius-wiki-br","pid":6398,"level":30,"levelPath":"info","msg":"loading ...","time":"2020-02-23T14:04:33.248Z","v":0}{"name":"../src/lib/index.js","hostname":"ius-wiki-br","pid":6398,"level":30,"levelPath":"info","msg":"ready on :8142","time":"2020-02-23T14:04:33.270Z","v":0}{"name":"parsoid","hostname":"ius-wiki-br","pid":6387,"level":40,"levelPath":"warn/service-runner","msg":"startup finished","time":"2020-02-23T14:04:33.272Z","v":0}{"name":"parsoid","hostname":"ius-wiki-br","pid":6387,"level":50,"message":"worker died, restarting","worker_pid":6398,"exit_code":null,"levelPath":"error/service-runner/master","msg":"worker died, restarting","time":"2020-02-23T14:38:08.1$Killed{"name":"parsoid","hostname":"ius-wiki-br","pid":765,"level":30,"levelPath":"info/service-runner","msg":"master(765) initializing 1 workers","time":"2020-02-23T14:38:35.233Z","v":0}{"name":"../src/lib/index.js","hostname":"ius-wiki-br","pid":1162,"level":30,"levelPath":"info","msg":"loading ...","time":"2020-02-23T14:38:40.884Z","v":0}{"name":"../src/lib/index.js","hostname":"ius-wiki-br","pid":1162,"level":30,"levelPath":"info","msg":"ready on :8142","time":"2020-02-23T14:38:40.973Z","v":0}{"name":"parsoid","hostname":"ius-wiki-br","pid":765,"level":40,"levelPath":"warn/service-runner","msg":"startup finished","time":"2020-02-23T14:38:40.975Z","v":0}


Stunnel for Lets Encrypt:

/etc/stunnel/parsoid.conf

cert = /etc/letsencrypt/live/ius.wiki.br/fullchain.pem

key = /etc/letsencrypt/live/ius.wiki.br/privkey.pem

[parsoid]

accept = 8143

connect = 8142

/etc/default/stunnel4

ENABLED=1


LocalSettings.php

$wgContentHandlerUseDB = true;

$wgFlowContentFormat = 'html';

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

  'url' => 'https://ius.wiki.br:8142',

);

wfLoadExtension( 'Flow' );

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

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


According to the Parsoid/Troubleshooting page, it listens to the api.php. Following the steps at Extension:VisualEditor#Linking_with_Parsoid_in_private_wikis, when I type in the browser https://parsoid.ius.wiki.br:8143 or https://ius.wiki.br:8143, i don't receive the β€žWelcome to the Parsoid web service.β€œ It returns ERR_CONNECTION_TIMED_OUT.


Does anyone knows how to solve this?


Thanks in advance. E. A. Ferreira Macedo (talk) 19:54, 22 February 2020 (UTC)Reply

Embedding images in StructuredDiscussions

[edit]

Hi, I would love if StructuredDiscussions allowed users to embed images in line with text.


Is this planned to be implemented? MavropaliasG (talk) 06:10, 24 February 2020 (UTC)Reply

It’s already possible, although only in source mode: <figure-inline></figure-inline> here you are. I don’t think there are any development plans other than maintenance, as Wikimedia Foundation has given up on this, just like so many other things… Tacsipacsi (talk) 00:07, 25 February 2020 (UTC)Reply
Thank you for the reply and the tip.
That's sad to hear. I think the extension is fantastic. I hope it gets picked up again MavropaliasG (talk) 00:50, 25 February 2020 (UTC)Reply
I also love this, but the Talk pages consultation 2019 concluded with a direction towards improving wikitext talk pages instead of creating things like this one. I don’t think there’s much chance for this to be further developed by WMF; probably a volunteer or a third-party could pick it up. Tacsipacsi (talk) 09:59, 26 February 2020 (UTC)Reply
[edit]

Deployed this, but while the old (non StructuredDiscussions pages) are archived, there's nothing linking it back to the new "Talk" page. All the templates, etc., seem to be in place... Help? 2605:E000:63C3:E400:75D3:DA1F:2519:432F (talk) 02:11, 26 March 2020 (UTC)Reply

visual editor in Structured Discussions in MobileFrontend is possible

[edit]

? 89.138.150.22 (talk) 03:23, 3 April 2020 (UTC)Reply

install

[edit]

hi

how can i install Extension:StructuredDiscussions in my wiki?

i use host no vps.


Msnhinet8 (talk) 02:35, 6 April 2020 (UTC)Reply

Manual:Extensions#Installing an extension
If you don't have access to SSH you can download the extension, unpack it and upload the self named folder (usually inside the zip folder) into the "extensions" directory using FTP. Then you visit the extensions page and follow the instructions for what to add to you LocalSettings.php file. BUT be careful because flow can temporarily down your site if it the prerequisites are missing when you enable it in LocalSettings.php (removing or commenting out the line to activiate flow in LocalSettings can often get your site back up by disabling it again). It also requires mw-update to be run which causes changes to the database. If anything goes wrong it can mess up your database. You should always back up your database before installing extensions that make database changes in case anything goes wrong because without that it is unrecoverable (you might already know this).
Flow's prerequisites also need to be installed before trying to run flow. And FLOW does NOT appear to be compatible with Mediawiki 1.34.0 or 1.34.1 as it says it is, ssh in both versions spits out an error saying that it is only compatible with the next (not stable) version 1.35, though it works with 1.32 and 1.33. TiltedCerebellum (talk) 05:36, 19 April 2020 (UTC)Reply

can't access SpecialPages

[edit]

Hi !

After installation of StructuredDiscussions on mediawiki 1.34.1 i can't access on SpecialPage

http error 5000

Any idea to fix it ? 165.169.24.216 (talk) 15:28, 8 April 2020 (UTC)Reply

Same, flow isn't working on 1.34.1. I installed composer and did composer update --no-dev after reading a suggestion elsewhere, didn't work. When trying to do the update SSH spits out an error on 1.34.1, so I downgraded to 1.34.0 and again on ssh using "php update.php" it's saying it's not compatible with 1.35 either:
" Uncaught ExtensionDependencyError: Flow is not compatible with the current MediaWiki core (version 1.34.1), it requires: >= 1.35.0."
And after downgrade:
" Uncaught ExtensionDependencyError: Flow is not compatible with the current MediaWiki core (version 1.34.0), it requires: >= 1.35.0." TiltedCerebellum (talk) 04:17, 19 April 2020 (UTC)Reply

Enabling Structured discussions without console access

[edit]

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.


I'm using a shared host without console access. Is it possible to run populateContentModel.php ? Is it possible to activate the extension in another way? Costas Athan (talk) 12:35, 9 April 2020 (UTC)Reply

Maybe your host allows you to set up cron jobs. Add the script to a cron. Ciencia Al Poder (talk) 15:24, 9 April 2020 (UTC)Reply
Two small questions:
  1. --wiki=somewiki. Is somewiki the wiki's name as it was given during initial installation? Is it case sensitive?
  2. When I ran the cron jobs I kept a log file. I got this notice: Undefined index: SERVER_NAME in /[path]/public_html/includes/GlobalFunctions.php on line 1350
    Did everything go OK or did something fail and I should rerun the commands? Costas Athan (talk) 21:22, 9 April 2020 (UTC)Reply
The --wiki parameter is only relevant on a wiki farm. That's probably not needed in your setup.
The "Undefined index: SERVER_NAME" is a known bug: T172060. But it's not harmful, you can safely ignore it, or define $wgOverrideHostname in LocalSettings.php Ciencia Al Poder (talk) 21:19, 10 April 2020 (UTC)Reply
Thanks for your time and the info! Costas Athan (talk) 06:53, 11 April 2020 (UTC)Reply
I actually think it does. Thanks for the idea! Costas Athan (talk) 15:54, 9 April 2020 (UTC)Reply
The discussion above is closed. Please do not modify it. No further edits should be made to this discussion.
[edit]

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.


RedHat7
MediaWiki 1.34.1 (d07521a)
PHP 7.2.30 (apache2handler)
MariaDB 5.5.65-MariaDB
ICU 50.2
Echo – (bf9195d) 10:52, 6 April 2020
Flow 1.1.1 (5a1c2eb) 19:38, 17 April 2020

When I run:

sudo php /opt/htdocs/mediawiki/maintenance/refreshLinks.php 1080 --e 1087
I get the following error:
$ sudo php /opt/htdocs/mediawiki/maintenance/refreshLinks.php 1080 --e 1087
Refreshing redirects table.
Starting from page_id 1080 of 1087.
Refreshing links tables.
Starting from page_id 1080 of 1087.
[112ae3971d7874e72cbfe77f] [no req]   TypeError from line 26 of /opt/htdocs/mediawiki/extensions/Flow/includes/Model/WikiReference.php: Argument 8 passed to Flow\Model\WikiReference::__construct() must be an instance of Title, null given, called in /opt/htdocs/mediawiki/extensions/Flow/includes/Model/WikiReference.php on line 81
Backtrace:
#0 /opt/htdocs/mediawiki/extensions/Flow/includes/Model/WikiReference.php(81): Flow\Model\WikiReference->__construct(Flow\Model\UUID, string, Flow\Model\UUID, Title, string, Flow\Model\UUID, string, NULL)
#1 /opt/htdocs/mediawiki/extensions/Flow/includes/Data/Mapper/BasicObjectMapper.php(38): Flow\Model\WikiReference::fromStorageRow(array, NULL)
#2 /opt/htdocs/mediawiki/extensions/Flow/includes/Data/ObjectLocator.php(315): Flow\Data\Mapper\BasicObjectMapper->fromStorageRow(array)
#3 /opt/htdocs/mediawiki/extensions/Flow/includes/Data/ObjectManager.php(307): Flow\Data\ObjectLocator->load(array)
#4 /opt/htdocs/mediawiki/extensions/Flow/includes/Data/ObjectLocator.php(119): Flow\Data\ObjectManager->load(array)
#5 /opt/htdocs/mediawiki/extensions/Flow/includes/Data/ObjectLocator.php(70): Flow\Data\ObjectLocator->findMulti(array, array)
#6 /opt/htdocs/mediawiki/extensions/Flow/includes/Data/ManagerGroup.php(127): Flow\Data\ObjectLocator->find(array)
#7 /opt/htdocs/mediawiki/extensions/Flow/includes/Data/ManagerGroup.php(139): Flow\Data\ManagerGroup->call(string, array)
#8 /opt/htdocs/mediawiki/extensions/Flow/includes/LinksTableUpdater.php(121): Flow\Data\ManagerGroup->find(string, array)
#9 /opt/htdocs/mediawiki/extensions/Flow/includes/LinksTableUpdater.php(50): Flow\LinksTableUpdater->getReferencesForTitle(Title)
#10 /opt/htdocs/mediawiki/extensions/Flow/includes/Content/BoardContent.php(195): Flow\LinksTableUpdater->mutateParserOutput(Title, ParserOutput)
#11 /opt/htdocs/mediawiki/includes/Revision/RenderedRevision.php(267): Flow\Content\BoardContent->getParserOutput(Title, integer, ParserOptions, boolean)
#12 /opt/htdocs/mediawiki/includes/Revision/RenderedRevision.php(236): MediaWiki\Revision\RenderedRevision->getSlotParserOutputUncached(Flow\Content\BoardContent, boolean)
#13 /opt/htdocs/mediawiki/includes/Revision/RevisionRenderer.php(215): MediaWiki\Revision\RenderedRevision->getSlotParserOutput(string)
#14 /opt/htdocs/mediawiki/includes/Revision/RevisionRenderer.php(152): MediaWiki\Revision\RevisionRenderer->combineSlotOutput(MediaWiki\Revision\RenderedRevision, array)
#15 [internal function]: MediaWiki\Revision\RevisionRenderer->MediaWiki\Revision\{closure}(MediaWiki\Revision\RenderedRevision, array)
#16 /opt/htdocs/mediawiki/includes/Revision/RenderedRevision.php(198): call_user_func(Closure, MediaWiki\Revision\RenderedRevision, array)
#17 /opt/htdocs/mediawiki/includes/Storage/DerivedPageDataUpdater.php(1290): MediaWiki\Revision\RenderedRevision->getRevisionParserOutput()
#18 /opt/htdocs/mediawiki/includes/Storage/DerivedPageDataUpdater.php(1312): MediaWiki\Storage\DerivedPageDataUpdater->getCanonicalParserOutput()
#19 /opt/htdocs/mediawiki/includes/Storage/DerivedPageDataUpdater.php(1606): MediaWiki\Storage\DerivedPageDataUpdater->getSecondaryDataUpdates(boolean)
#20 /opt/htdocs/mediawiki/includes/page/WikiPage.php(2145): MediaWiki\Storage\DerivedPageDataUpdater->doSecondaryDataUpdates(array)
#21 /opt/htdocs/mediawiki/maintenance/refreshLinks.php(276): WikiPage->doSecondaryDataUpdates(array)
#22 /opt/htdocs/mediawiki/maintenance/refreshLinks.php(199): RefreshLinks::fixLinksFromArticle(integer, boolean)
#23 /opt/htdocs/mediawiki/maintenance/refreshLinks.php(84): RefreshLinks->doRefreshLinks(integer, boolean, integer, boolean, boolean)
#24 /opt/htdocs/mediawiki/maintenance/doMaintenance.php(99): RefreshLinks->execute()
#25 /opt/htdocs/mediawiki/maintenance/refreshLinks.php(492): require_once(string)
#26 {main}

/mediawiki/maintenance/update.php runs without error

The Talk page works as expected.. it's just the refresh links that is failing.

Please advise. Ty Revansx (talk) 20:49, 23 April 2020 (UTC)Reply

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

Removal instructions

[edit]

Add removal instructions, and how to restore your wiki to pre-installation state. Jidanni (talk) 01:36, 26 April 2020 (UTC)Reply

Oh. it's in Extension:StructuredDiscussions/Turning_off_all_StructuredDiscussions. Jidanni (talk) 02:01, 26 April 2020 (UTC)Reply

Structured Discussions in MobileFrontend without Visual Editor

[edit]

How do I make the StructuredDiscussions extension work in MobileFrontend if I do not want to install VisualEditor? The problem is the ability to leave a comment in the thread ... 109.87.112.220 (talk) 13:49, 12 May 2020 (UTC)Reply

Thanks for reporting this bug! This is now fixed in the latest version of Structured Discussions. If you don't want to upgrade, you can also fix it yourself, by editing includes/Hooks.php in the StructuredDiscussion extension and changing:
$resourceLoader->register( 'ext.visualEditor.supportCheck', [] );
to:
$resourceLoader->register( 'ext.visualEditor.supportCheck', [ 'targets' => [ 'desktop', 'mobile' ] ] ); Catrope (talk) 20:18, 12 May 2020 (UTC)Reply
Thank you so much, I followed the recommendations and everything works fine. Thanks again! 109.87.112.220 (talk) 09:44, 13 May 2020 (UTC)Reply

New install - almost new MediaWiki - Class 'Pimple\Container' not found

[edit]

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 everyone, I'm trying to install StructuredDiscussions on a basically brand new 1.32 MediaWiki instance and receiving the following error:


Command 'php update.php'

failed with return code 255 and error message

PHP Fatal error: Class 'Pimple\Container' not found in

.../extensions/Flow/includes/Container.php on line 5


I've tried running composure update in my root MediaWiki folder, Flow extension folder, etc. as I've seen online and it returns composer command not found.


Do I need to run populateContentModel.php and $wgNamespaceContentModels[namespace] before trying to enable Flow? 2605:6000:1025:883:8D5E:A5D3:192D:CD5F (talk) 18:41, 12 May 2020 (UTC)Reply

I ran populateContentModel.php and $wgNamespaceContentModels[namespace] and am still receiving the same error. 2605:6000:1025:883:8D5E:A5D3:192D:CD5F (talk) 18:54, 12 May 2020 (UTC)Reply
If "composer update" says "composer command not found", you will need to install composer. See installation instructions here. Catrope (talk) 19:11, 12 May 2020 (UTC)Reply
The discussion above is closed. Please do not modify it. No further edits should be made to this discussion.

Class 'Pimple\Container' not found

[edit]

'composer update --no-dev' worked successfully. But 'php update.php' failed with error message:

Error from line 5 of D:\xampp\htdocs\mediawiki\extensions\Flow\includes\Container.php: Class 'Pimple\Container' not found
Extension:StructuredDiscussions says "You also need to run the command "composer update --no-dev" from the command line, on the folder where MediaWiki is installed, even if you don't download from git.", but it seems to be wrong. Shirayuki (talk) 07:52, 23 May 2020 (UTC)Reply
I think that's wrong, composer update --no-dev should be run on the folder where the extension is installed (extensions\Flow) Ciencia Al Poder (talk) 13:43, 23 May 2020 (UTC)Reply

FlowMention is not working on my private Wiki

[edit]

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.


This might be because my "Template:FlowMentions" is empty. Can anyone help me out? 93.195.151.221 (talk) 19:12, 25 May 2020 (UTC)Reply

Nevermind, I managed to make it work by changing the content of my "Template:FlowMention" to "@[[User:{{{1}}}|{{{1}}}]]" 93.195.151.221 (talk) 19:32, 25 May 2020 (UTC)Reply
The discussion above is closed. Please do not modify it. No further edits should be made to this discussion.

LiquidThreads conversion

[edit]

Hi,

Is the LiquidThreads conversion tool known to be functional?

The documentation at Flow/Converting LiquidThreads looks patchy, and the people who were involved in writing it are, unfortunately, not around. Amir E. Aharoni {{🌎🌍🌏}} 10:25, 1 July 2020 (UTC)Reply

It's known to have issues (which is why LQT is still installed on the Foundation's servers). Jdforrester (WMF) (talk) 11:23, 1 July 2020 (UTC)Reply

Prevent editing of "About this board" description

[edit]

Hello, please tell me how to prevent registered users from changing the description of "About this board"? 109.87.112.220 (talk) 07:30, 2 August 2020 (UTC)Reply

For a single board in particular, or for every board? Jackmcbarn (talk) 23:48, 2 August 2020 (UTC)Reply
I would like to close the description editing for all boards, since users often create not a new topic, but edit the board description and want to get an answer ... 109.87.112.220 (talk) 10:11, 3 August 2020 (UTC)Reply

How to disable the extension on a namespace

[edit]

Hi,

I tried what is written under "Enabling or disabling StructuredDiscussions" and also Extension:StructuredDiscussions/Turning off all StructuredDiscussions. But nothing works. So how do you disable this extension on an enabled namespace? I'm using mediawiki 1.31. 2A02:8071:BCA:6E00:5405:D51E:1840:5627 (talk) 22:17, 3 August 2020 (UTC)Reply

Expected mass rollback of all peer transactions (DBO_TRX set)

[edit]
MediaWiki 1.35.0-rc.1
PHP 7.3.21 (fpm-fcgi)
MariaDB 10.2.32-MariaDB-1:10.2.32+maria~bionic
ICU 63.1
Flow 1.2.0 (6ec941d) 11:45, 13 July 2020
Echo – (3c62654) 20:47, 13 July 2020

when I use "Enable Structured Discussions"

it shows "An error occurred. The error message received was: Flow\Import\PageImportState::rollback: Expected mass rollback of all peer transactions (DBO_TRX set)"

Everything works right, just an error was threw

I found https://phabricator.wikimedia.org/T197234 which is not so helpful.

Please Advise ε€•θˆžε…«εΌ¦ (talk) 17:43, 15 August 2020 (UTC)Reply

Error on Archive pages

[edit]

Hi guys,


I'm getting this error:

The page is being handled by Structured Discussions, but the Title class indicates that the content model is 'wikitext'. This is a misconfiguration or inconsistent state. For example, this may actually be a non-Structured Discussions page in a Structured Discussions namespace, with rev_content_model not populated.


How can I fix this? 2A02:8071:BA4:9200:C45:4321:3C4:EF8C (talk) 13:24, 2 September 2020 (UTC)Reply

Manually change the content model of the page (Special:ChangeContentModel). if this error is widespread, running populateContentModel.php may help Ciencia Al Poder (talk) 15:51, 2 September 2020 (UTC)Reply

hCaptcha is not working with this extension.

[edit]

When I enter a post, Captcha appears, but it is not saved. How to fix it? 112.76.30.2 (talk) 02:09, 5 October 2020 (UTC)Reply

See Extension:ConfirmEdit#hCaptcha:

Note: hCaptcha will not currently work with the VisualEditor.

I don’t know exactly what part of VisualEditor hCaptcha doesn’t work with, but VE and StructuredDiscussions use the same underlying technologies, so if it doesn’t work with VE, it’s not a surprise that it doesn’t work with SD either. Probably you’ll get better answers on Extension talk:ConfirmEdit. Tacsipacsi (talk) 23:06, 7 October 2020 (UTC)Reply

HTML to Wikitext Conversion Issue

[edit]

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
Error message

Knomanii (talk) 08:58, 20 October 2020 (UTC)Reply

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 (talk) 07:40, 24 October 2020 (UTC)Reply
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! Knomanii (talk) 23:33, 25 October 2020 (UTC)Reply
You can using $wgFlowEditorList. Tinss (talk) 04:27, 20 January 2021 (UTC)Reply
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 Sophivorus (talk) 14:43, 6 November 2020 (UTC)Reply
Me too, how can i do? Msnhinet8 (talk) 05:33, 7 November 2020 (UTC)Reply
Hello!
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;? Spas.Z.Spasov (talk) 14:50, 7 November 2020 (UTC)Reply
bump. I'm experiencing the same issue. Tried everything. Cloudcell (talk) 13:23, 9 December 2020 (UTC)Reply
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. Knomanii (talk) 07:12, 18 December 2020 (UTC)Reply
Running into the same issue. Tried switching flow content formats as well, no luck. Has anybody figured this out? 154.21.21.29 (talk) 13:48, 21 December 2020 (UTC)Reply
After I switched to MW-1.35.1 the issue disappeared (and the patch https://phabricator.wikimedia.org/T260648#6645078 is no longer required, at least for my installation) Cloudcell (talk) 22:56, 24 December 2020 (UTC)Reply
Bump. Same issue using MW 1.35.1 2001:E60:B00C:A4BF:553D:8BF:6BB4:7CEC (talk) 15:25, 11 February 2021 (UTC)Reply
I can't confirm the issue disappear with MW 1.35.1, but I can confirm the patch (phab:T260648#6645078) provided above works! Spas.Z.Spasov (talk) 15:37, 11 February 2021 (UTC)Reply
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. Knomanii (talk) 09:06, 1 March 2021 (UTC)Reply
Hi
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! Beginneruser (talk) 19:20, 21 April 2021 (UTC)Reply
@Beginneruser you need to apply the patch in phab:T260648#6645078. Tinss (talk) 22:21, 21 April 2021 (UTC)Reply
Hi @Tinss
Thank you
But
I want when will the official patch be released?
@Catrope and @MarkAHershberger do you know? Beginneruser (talk) 01:40, 22 April 2021 (UTC)Reply
I'm not sure why I'm pinged here, but looking at the patch in gerrit, it looks like it has been forgotten about. ☠MarkAHershberger☒(talk)☣ 17:08, 24 April 2021 (UTC)Reply

Issue saving the topic/replying

[edit]

When i click save on flow comment or create topic i get the red bar that would contain the error message but there's only the red box but no message and it seems like it doesn't save my topic and comment, but if i refresh the page i can see that the topic/comment is in fact saved. any help would be very much appreciated Aiinori (talk) 10:23, 21 October 2020 (UTC)Reply

adoption of this extension across MediaWiki ecosystem?

[edit]

Any information of adoption of this extension across MediaWiki ecosystem? What is the reason it is not used everywhere? ~ Zblace (talk) 10:06, 24 October 2020 (UTC)Reply

The Talk pages consultation 2019 concluded with improving wikitext talk pages instead of replacing them. I’m sad because actually structured discussions are superior in many ways to trying to programmatically find structure in unstructured wikitext talk pages, although the talk pages project looks promising in many aspects. Tacsipacsi (talk) 12:15, 25 October 2020 (UTC)Reply
Yes, that's a pity. However, I suspect Flow will stay very much alive as it's a much better solution for enterprise MediaWiki. Tinss (talk) 04:29, 20 January 2021 (UTC)Reply
Yeah, probably it will stay alive in the sense that it will be used. However, it isn’t likely to be developed any further by WMF. Tacsipacsi (talk) 10:58, 20 January 2021 (UTC)Reply

Templates do not display

[edit]

In my wiki, no template is displayed in the discussions. Even the Mention template do not display anything.

Example: Hello @Username 001! displays Hello !

How can I do?

Thanks in advance Manu.wikidebats (talk) 13:53, 25 October 2020 (UTC)Reply

getText() not defined

[edit]

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, I get this error message when starting a thread in mw-1.35:

[X5WM0bIuxep@xjG3HFs8xQAAFhQ] Exception caught: Call to undefined method Flow\Content\BoardContent::getText()

I believe that method was deprecated in 1.35, so any idea why it's used in the 1.35 release? 188.113.87.232 (talk) 14:39, 25 October 2020 (UTC)Reply

Additionally, same error when updating description 188.113.87.232 (talk) 14:53, 25 October 2020 (UTC)Reply
Good job dude 95.128.116.49 (talk) 13:09, 6 November 2020 (UTC)Reply
Can verify this is also present in my 1.34 installation 188.113.87.232 (talk) 13:00, 31 October 2020 (UTC)Reply
Problem is resolved. I enabled debug logging and saw there was another extension using a hook and getText() without checking content model first. 2001:700:302:10:0:0:0:99 (talk) 11:56, 1 November 2020 (UTC)Reply
The discussion above is closed. Please do not modify it. No further edits should be made to this discussion.

If I have shared host?

[edit]

If I use shared host, can I install this extension some way without use server commands? АргскригициониСц (talk) 18:18, 14 November 2020 (UTC)Reply

I'm on a shared host and recall this extension being tricky but not impossible to install.
That said, my host does allow limited use of commands over ssh, so I could run basic commands like php composer.phar (because I couldn't install composer on shared hosting) and the update script.
Also, if you're on MW-1.35 then you don't need to run certain scripts anymore. From: Extension:StructuredDiscussions#Upgrading, " The first script was part of MediaWiki core until version 1.34. From 1.35 onward, it is no longer needed."
That said, I'm still having my own issues with the extension on 1.35.0, per my thread below. Although it seems to be an issue with the extension expecting a RESTbase server, which probably won't be resolved until there's a broader fix of that issue upstream. Knomanii (talk) 01:53, 22 November 2020 (UTC)Reply