Extension:StructuredDiscussions/tr

StructuredDiscussions uzantısı, tartışma sayfaları için bir tartışma ve işbirliği sistemi sağlar. Bu sayfa Yapısal Tartışmaların nasıl kurulacağını ve yönetileceğini; kullanma kılavuzu için sayfasına bakın. Yapısal Tartışmalar'ı Deneme tahtası tartışma sayfasında kendiniz deneyebilirsiniz.

Bu uzantı daha önce Flow olarak biliniyordu ve bazı yerlerdeki (Git deposu gibi) adlar hala bunu yansıtıyor.

StructuredDiscussions uzantısı, Wikimedia Vakfı'daki İşbirlik ekibi tarafından geliştirildi. Hala hataları düzeltmek için sürdürülüyor, ancak uzantıda önemli bir gelişme yok, Eylül 2017'de "$to" olarak yeniden adlandırılması dışında 2015'ten beri yapıldı. Gelişim muhtemelen gelecekte tekrar başlayabilir. Bu uzantının geliştirme durumu ve tasarımına genel bakış hakkında daha fazla bilgi için Structured Discussions sayfasına bakın.

Yükleme sonrası
Git'ten indirmeseniz bile, komut satırından MediaWiki'nin yüklü olduğu klasörde "composer update --no-dev" komutunu çalıştırmanız gerekir.

Burada belirtilen betikleri da dahil olmak üzere StructuredDiscussions'u etkinleştirme veya devre dışı bırakma ile ilgili tüm talimatları uyguladığınızdan emin olun.

Bağımlılıklar

 * gerekli
 * - bildirimler için (örneğin gönderinize verilen yanıtlar)
 * Bir nesne önbelleği olması gerekir. Bunun için memcached kullanmanız önerilir. Şu anda Redis ile ilgili sorunlarla karşılaşabilirsiniz.
 * - otomatik olarak yüklenen şablonlar için (ör. #time)
 * = true  Special:EnableStructuredDiscussions için ve bu ad alanında zaten sayfalar varsa ad alanlarının içerik modelini değiştirirseniz (StructuredDiscussions'a doğru veya ondan uzakta) bozulmadan kaçınmak için gereklidir.


 * kesinlikle önerilir


 * Mesajları, performansı artıran HTML olarak saklama seçeneği için Parsoid. WMF vikileri bu şekilde yapılandırılır ve bu nedenle bugüne kadar en çok test edilen yapılandırmadır. MediaWiki-Vagrant kullanırsanız, StructuredDiscussions ile etkinleştirmek Parsoid'i etkinleştirir ve biçimi 'html' olarak ayarlar.


 * optional


 * - if you want to use the opt-in beta feature for user talk.
 * - for human-friendly timestamps such as "3 days ago"
 * - for VisualEditor support
 * bug? if you have the VisualEditor present (e.g. perhaps to provide OOUI),then StructuredDiscussions will attempt to contact Parsoid even if VE is not enabled
 * StructuredDiscussions can integrate with, , and , see
 * StructuredDiscussions will integrate with if you have it installed.
 * - to "Thank" users for their posts
 * - for analytics

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

Upgrading
The  variable, which enumerated StructuredDiscussions boards, was removed as part of T105574. Before upgrading to 1.26 or later, run the maintenance scripts:

The first script was part of MediaWiki core until version 1.34. From 1.35 onward, it is no longer needed.

Configuration
Here are some settings you need to make in.

Enabling or disabling StructuredDiscussions
To enable or disable StructuredDiscussions for a namespace in MediaWiki before 1.35, first run on the affected namespaces (or you can do it on  ). From 1.35 onward, this is no longer needed. E.g. if you are about to enable or disable it on NS_TALK (1) and NS_USER_TALK (3) as shown in the PHP config below:

If mwscript is not configured, replace  with

After the above, set  for particular namespaces. For example:

Do not reassign the global.

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

See for how to turn off all StructuredDiscussions pages on your wiki.

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

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

Parsoid must have been configured to match, using a line in Parsoid's  like:

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

See Parsoid/Setup#Configuration for more details.

"maximum function nesting level of '100' reached, aborting"
If you get this error, you need to set, probably in.

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

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

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

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

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

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

System messages
Using the "Source editing" option on StructuredDiscussions boards makes visible the help text. The "uses markup" part is linked through the system message MediaWiki:Flow-wikitext-editor-help-uses-wikitext which makes use of an interwiki link to MediaWiki.org.

In some cases, this interwiki link, instead of pointing to on MediaWiki.org, points to a (usually non-existent) Help:Formatting page on the host Wiki. This can be corrected by changing the interwiki link on MediaWiki:Flow-wikitext-editor-help-uses-wikitext to an external link such as.

Troubleshooting
Not getting Flow as expected? There are different fixes, depending on the source of the problem:

Wrong Custom-Namespace Declaration Order
The Flow declares must go after the declare for a custom namespace. Correct order is:

Wrong Native Constants
Talk pages in the Main namespace are defined as, not

The correct declaration is:

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

Non-Registered Extension Constants
namespace constant is supposed to be. But that constant does not work in the Flow declare-- you must use the actual number: 107. This works:

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

It's unknown to this author whether Page_Forms failed to register its constants correctly, or whether all extension must use numbers (not constants) with Flow. See list of some other extension namespace constants.

Old Remnants
If you're correctly getting Flow on all talk-pages in a namespace, except for one page in that namespace, there may be remnant junk in the talk page (even if it appears empty). Do the following:


 * 1) Browse to the talk page that won't load Flow, e.g.: Portal_Talk:Welcome
 * 2) Delete the Talk page using the Delete tab.
 * 3) Go to the content page for that talk page, e.g.: Portal:Welcome
 * 4) Click Discuss.
 * 5) You get Flow.

Architecture
See Flow/Architecture.

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

Moderation
See for more information on moderation in Flow.

Export and Import
There is maintenance script to export Flow data similar to Manual:DumpBackup.php

T114703 - gives some hints about the import.