Extension talk:StructuredDiscussions/2015

<flow-action-unsupported>

Well i installed flow exstension and added this line to LocalSetting.php

1. $wgFlowOccupyNamespaces = array( NS_USER_TALK, NS_MAIN )
   

I don't know why i did it, i am probably retarded.

This overriden my mainpages content with flow. Then i tried to undo this by commenting out #$wgFlowOccupyNamespaces and it didn't help.

I now do have a "No such action" instead of title and "<flow-action-unsupported>" instead of content in every single page.

Runing update.php through mw-config did not help at all.

Lastly i tried to delete flow folder from exstensions and this makes site not loading at all. It says "Exception from line 324 of /var/www/data/www/somesite.com/includes/content/ContentHandler.php: No handler for model 'flow-board' registered in $wgContentHandlers" and a list of backtraces.

Any help? What to do? Undeadlol1 (talk) 16:21, 2 May 2015 (UTC)

What happens when you visit a new page in the main namespace? If you've commented out $wgFlowOccupyNamespaces then you should be able to edit the empty page as simple wikitext. As I recall, Flow behavior around January was as follows: if Flow occupies a namespace then when someone first visits a page in it Flow creates a dummy edit that changes the content type to 'flow-board'. Changing $wgFlowOccupyNamespaces doesn't undo this, you have to change the content type back to wikitext. You might be able to do this by View History of an occupied page, find this change and undo it, but there have been bugs with this.

Disclaimer: I used to work on Flow, my understanding is out of date. SPage (WMF) (talk) 23:40, 5 May 2015 (UTC)

How do i change content type back to wikitext? I am still in process of learning mediawiki. Undeadlol1 (talk) 15:52, 6 May 2015 (UTC)

You need to edit the relevant database entries. If you have access to phpMyAdmin or if you are comfortable with MySQL command line, you can do it with the following query:

UPDATE prefix_page SET page_content_model='wikitext' WHERE page_content_model='flow-board';

Where prefix is your database table prefix. ~Φנσѕєρнєяυм ^w•t•c 20:02, 19 June 2015 (UTC)

The fact that you get errors when visiting pre-existing wikitext pages after occupying a namespace is a known bug; we have a patch for it that's pending review, but it's not fixed yet. I don't know enough to be able to tell you how to clean up after this, but some combination of what @SPage (WMF): and @PJosepherum: said will probably work. Roan Kattouw (WMF) (talk) 21:47, 19 June 2015 (UTC)

flow_post.partial.handlebars

I installed the Flow extension on a wiki and get flow_post.partial.handlebars shown where the answers to a thread should be. Any idea where to look? Thanks Tuluqaruk (talk) 14:36, 11 June 2015 (UTC)

What versions of Flow and MediaWiki core are you using? Do you have JavaScript enabled or disabled? Legoktm (talk) 23:34, 11 June 2015 (UTC)

I have the same issue using a Vagrant copy last updated 8 days ago. JS is enabled. -happy5214 00:23, 12 June 2015 (UTC)

Proxy Error

The proxy server received an invalid response from an upstream server. The proxy server could not handle the request GET /index.php.

Reason: Error reading from remote server Fractalfederation (talk) 22:16, 16 June 2015 (UTC)

On all pages, or just Flow ones? I don't see that error right now. Is that because I'm looking at the wrong page, or because you've uninstalled Flow? Mattflaschen-WMF (talk) 22:37, 16 June 2015 (UTC)

I should of been more specific, it's on a personal MediaWiki install. I know y'all are still working on it, just figured you would want to know. Fractalfederation (talk) 23:12, 16 June 2015 (UTC)

So, I am trying to get it to work still.. I got an error message, "unable to connect to server" then i installed memcached and parsoid servers, and not it's saying invalid token.. any ideas? 2601:49:8100:E2B:3C22:2BB:9A5C:4AED (talk) 06:01, 18 June 2015 (UTC)

• An error occurred while contacting the server.
  • Invalid token 2601:49:8100:E2B:3C22:2BB:9A5C:4AED (talk) 06:07, 18 June 2015 (UTC)

Can you post a full screenshot of the error, or let the proxy pass it through?

The proxy error is probably because it receives the real error (which we would need for troubleshooting) from upstream, but then replaces it with its own error. Mattflaschen-WMF (talk) 19:20, 18 June 2015 (UTC)

How would I let the real error through? I enabled all the like 6-7 error settings, php ini etc and still didn't get one. Fractalfederation (talk) 20:27, 18 June 2015 (UTC)

proxy error happens when you go to user_talk with &action=edit&redlink=1 added to the URI btw 2601:49:8100:E2B:3C22:2BB:9A5C:4AED (talk) 06:30, 18 June 2015 (UTC)

Conversion from 'html' to 'wikitext' was requested, but core's Parser only supports 'wikitext' to 'html' conversion

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've got a problem with Flow. I use the VisualEditor togehter with parsoid in my server and these are the entry of my LocalSettings:

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

$wgFlowContentFormat = 'html';

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



$wgFlowOccupyNamespaces = array( NS_USER_TALK, NS_TALK );

But this error appears when trying to send a comment:

[f0126fac] Exception Caught: Conversion from 'html' to 'wikitext' was requested, but core's Parser only supports 'wikitext' to 'html' conversion Scharesoft~mediawikiwiki (talk) 10:21, 24 June 2015 (UTC)

If I disable "$wgFlowEditorList = array( 'visualeditor', 'none' );" it's working, but after sending a reply to a message this appears "flow_post.partial.handlebars flow_post.partial.handlebars". After reloading the talk page the reply appears. Scharesoft~mediawikiwiki (talk) 11:56, 24 June 2015 (UTC)

Not it's working, sorry. I forgot to define $wgFlowParsoidURL and $wgFlowParsoidPrefix.

But this error stays: flow_post.partial.handlebars flow_post.partial.handlebars flow_post.partial.handlebars Scharesoft~mediawikiwiki (talk) 12:09, 24 June 2015 (UTC)

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

flow_post.partial.handlebars appears after posting a message

After posting a message with flow an error message appears instead of the writen message:

flow_post.partial.handlebars

If there are multiple messages this appears multiple times (flow_post.partial.handlebars flow_post.partial.handlebars flow_post.partial.handlebars).

After reloading the page the correct message appeas.

This is my LocalSettings:

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

//$wgFlowContentFormat = 'html';

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



$wgFlowOccupyNamespaces = array( NS_USER_TALK, NS_TALK );

$wgFlowParsoidURL = 'http://localhost:8142';

$wgFlowParsoidPrefix = 'almanach'; Scharesoft~mediawikiwiki (talk) 12:13, 24 June 2015 (UTC)

I'm getting the exact same error. Anyone know what's causing it? Christharp (talk) 00:20, 10 November 2015 (UTC)

What versions/commits of core and Flow are you using? Mattflaschen-WMF (talk) 00:53, 11 November 2015 (UTC)

The problem is damaged file content in downloaded version.

In downloaded version file Flow/handlebars/flow_post.handlebars contains line:

Link: flow_post.partial.handlebars

instead of original template content... Pastakhov (talk) 08:00, 4 May 2016 (UTC)

Tracked at https://phabricator.wikimedia.org/T103702 Mattflaschen-WMF (talk) 15:24, 4 May 2016 (UTC)

Help with Flow Taking Over All Namespaces

I'm finding that when I enable flow with:

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

$wgFlowOccupyNamespaces = array(NS_PR_TALK);

Flow takes over any newly created page.

I don't think that I am having the same problem as Undead1lol in that when I run, SELECT page_content_model FROM <prefix>_page WHERE page_content_model='wikitext'; all pages are 'wikitext'; there are no 'flow-board' entries.

I am using: MediaWiki 1.25.1, PHP 5.6.11 MySQL 5.5.43 with Flow REL1_25-576f705.tar.gz

With the above settings, when I try to create a page in the main space, for example, it comes up as a flow discussion page.

I was using liquid threads and did run the script maintenance/convertLqt.php when I had liquidthreads enabled in some namespaces, but, I do not recall specifically which namespaces.

Everything seems to be working correctly except for Flow taking over pages. Also note, when I do not enable $wgFlowOccupyNamespaces = array (NS_PR_TALK); page creation acts as usual.

I'm testing with an account with sysops permissions. Are there additional settings, besides the two above, that are necessary to set up a basic flow install?

Would the $wgFlowDefaultWorkflow setting allow me to specify that the default workflow is to create a page and not interfere with Flow working seamlessly for talk pages?

Thanks, Loonybomber (talk) 01:35, 25 July 2015 (UTC)

data loss - not confirming page exit

Tracked in Phabricator
Task T96531

Can't believe one can lose edits just because they leave the page.

For example, just before I save my edit here, If I were to click on "By saving changes, you agree to our Terms of Use", I'd lose my changes by reading about saving my changes. Cpiral (talk) 15:39, 27 July 2015 (UTC)

This still happens, also if I close the window. Seems like a bug, if you leave editing a regular page as wikitext or VisualEditor the browser gives its default [Leave page] prompt. SPage (WMF) (talk) 05:11, 14 October 2015 (UTC)

I've bumped the priority of Phab:T96531 now that this is reproducible again. Quiddity (WMF) (talk) 17:34, 14 October 2015 (UTC)

Flow installation problem PHP Fatal error: Access level to Flow\Data\BagOStuff\BufferedBagOStuff::cas() must be public

I'm trying to do a manual install of flow.

I've installed the Echo extension successfully.

I've added require_once "$IP/extensions/Flow/Flow.php"; to /var/www/html/mediawiki/LocalSettings.php.

However, when I run php update.php in the maintenance folder I get the following output (error message at the end). Has anyone seen this error before, or has some idea how to fix it?:

.....

...*_from_namespace column of backlink tables already populated.

...Update 'FlowUpdateRecentChanges' already logged as completed.

...Update 'FlowSetUserIp' already logged as completed.

...Update 'FlowUpdateUserWiki' already logged as completed.

...Update 'FlowUpdateRevisionTypeId' already logged as completed.

Populating links tables...

PHP Fatal error:  Access level to Flow\Data\BagOStuff\BufferedBagOStuff::cas() must be public (as in class HashBagOStuff) in /var/www/html/mediawiki/extensions/Flow/includes/Data/BagOStuff/BufferedBagOStuff.php on line 20

If I comment out the flow extension line in my LocalSettings.php file then update.php runs just fine.

Version numbers for mediawiki software:

MediaWiki: 1.24.2

PHP: 5.5.9-1ubuntu4.9 (apache2handler)

MySQL: 5.5.43-0ubuntu0.14.04.1

.

Also, potentially of relevance, the cache is currently set to none. From my LocalSettings.php file:

$wgMainCacheType = CACHE_NONE; NcRubert054 (talk) 16:37, 7 August 2015 (UTC)

I changed my CacheType to memcached and I still get the error. 144.92.16.161 (talk) 17:58, 7 August 2015 (UTC)

It sounds like you're not using the right version of Flow. You need to use matching versions. If you're using the 1.24 branch of core, you need to use REL1_24 of Flow and Echo.

BufferedBagOStuff does not exist in that version. Mattflaschen-WMF (talk) 00:59, 11 November 2015 (UTC)

Is VisualEditor required?

I ask because as soon as I click into "start a topic" I get this console error:

Exception in module-execute in module ext.flow.editors.visualeditor:

load.php?debug=false&lang=en&modules=jquery%2Cmediawiki&only=scripts&skin=monobook&version=20150810…:175 ReferenceError: ve is not defined ReferenceError: ve is not defined

Flow-REL1_25-576f705 Subfader (talk) 21:56, 10 August 2015 (UTC)

It's meant not to be required. Mmullie (WMF) did you check this as part of https://gerrit.wikimedia.org/r/#/c/232462/ ?

(Note, it may have been fixed since 1.25 was cut). Mattflaschen-WMF (talk) 00:08, 20 August 2015 (UTC)

== good == Nathansiddins (talk) 16:15, 24 October 2015 (UTC)

Subscribe to new board topics

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 want to open a "news" board: Some user may want to be notified via Echo about new topics. Is it possible?

Edit: I think I can use the watchlist? The roadmap says there should be a more sophisticated way. They mean a button on top? I second that. Subfader (talk) 22:30, 10 August 2015 (UTC)

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

flow_post.handlebars is empty

When I download the gz, flow_post.handlebars is empty.

This leads to the error after posting:

Uncaught Error: Template handlebars/flow_post.handlebars not found in module ext.flow.templating

The fie tree tells me that it's a redirect or sth: https://git.wikimedia.org/tree/mediawiki%2Fextensions%2FFlow/c08e3017f24065c78baa71b8793221218ece9c91/handlebars

So I copied flow_post.partial.handlebars into flow_post.handlebars and now posting works without errors. Subfader (talk) 22:47, 10 August 2015 (UTC)

Thanks for the information, this helped me with my problem with Flow too :) Scharesoft (talk) 13:36, 10 September 2015 (UTC)

Flow with Discussion Permission Extension?

Who has used Flow along with a current extension that allows anyone to create and edit Discussion pages but restricts editing of all article pages to a group? What extension do you use for restricting access to articles but allowing anyone to create and edit discussions and would you recommend the solution? Mike46V (talk) 16:38, 11 August 2015 (UTC)

== awesome == Nathansiddins (talk) 16:15, 24 October 2015 (UTC)

Flow on User talk: Pages don't exist

I enabled Flow on the user talk ns and the "discussion" pages don't exist for the system.

The flow board loads, but:

• The discussion tab is .new
• The subline asks to "view or restor X edits"

I have to hack the system now to make these act as normal pages?

It appears topics also don't exist: Topic:Sn2g1yop0frbj7y7 Subfader (talk) 16:10, 12 August 2015 (UTC)

First, in order to troubleshoot any possible bugs, please let us know what versions/commits of both MediaWiki core and Flow you're using.

If I understand correctly, it sounds like we might be talking about a few different things:

1. When you first go to a new board (you're about to create it for the first time) in a Flow-enabled namespace, it's normal for the board not to exist, and the tab to be red. See for example https://ca.wikipedia.org/wiki/Viquip%C3%A8dia_Discussi%C3%B3:This_doesn't_exist_yet?useskin=monobook (using Monobook skin to illustrate the tab is red).

2. If you previously deleted any content there, it will also be listed in the subline as you said. I have not heard of any previous bug reports where it would wrongly claim there was deleted content when it's a totally fresh location.

3. You said, "It appears topics also don't exist: Topic:Sn2g1yop0frbj7y7". There were bugs about this (topics being red), but they should be fixed in latest Flow. Mattflaschen-WMF (talk) 01:25, 11 November 2015 (UTC)

I agree. This is a very poor user experience to have the "Talk" page displayed as "red link", not only in the interface but also in the journals - Steff-X (talk) 19:58, 7 November 2015 (UTC)

Please clarify exactly when it shows as red, and what versions/commits of both MediaWiki core and Flow you're using.

I'm assuming by journals you mean logs, such as the history page/RC. Please clarify, though. Mattflaschen-WMF (talk) 01:22, 11 November 2015 (UTC)

For the versions, I use Flow REL1_25-576f705 with Mediawiki 1.25.1

About the red links, the Talk tab is red even when it points to an existing Flow discussion. About the Logs, subjects in a Flow discussion (linking to index.php/Topic:xxxxxxxxx) are properly displayed in blue but links to talk pages (index.php/Talk:xxxxxx) are red even though the page exists. Steff-X (talk) 15:57, 11 November 2015 (UTC)

It seems that nobody cares since Wikimedia found a solution for their own use. Subfader (talk) 12:58, 8 November 2015 (UTC)

This is a modification to the extension to properly display active links in the tabs and in the journals.

• In file Flow.php, find the line "$wgHooks['ArticleDelete'][] = 'FlowHooks::onArticleDelete';". In a new line after that one, insert the following:

$wgHooks['TitleIsAlwaysKnown'][] = 'FlowHooks::onTitleIsAlwaysKnown';

• In file Hooks.php, after the line "protected static $abuseFilter;", insert the following 6 lines

public static function onTitleIsAlwaysKnown( $title, &$result ) {

$myOccupationController = self::getOccupationController();

if ($myOccupationController->isTalkpageOccupied( $title )) {

$result = true;

}

}

Now links handled by Flow should appear correctly. Other links should be untouched. Note that I am in no way skilled in PHP, so use at your own risks.

Warning: this modification makes the assumption that any talk page handled by Flow (virtually) exists, even if there are actually no data attached to the talk page. Distinguishing between talk pages with or without data would probably require an explicit access to the database (to the table Workflow, to be precise).

Steff-X (talk) 15:05, 10 November 2015 (UTC)

MW short hand links don't work

With $wgFlowEditorList = none, [[Help:Navigation|]] does not parse as link text "Navigation".

It does so here when I switch the editor tho, but not on my wiki where I use $wgFlowEditorList = array( 'none' ); Subfader (talk) 11:21, 29 August 2015 (UTC)

Are you using Parsoid with Flow, or not? Mattflaschen-WMF (talk) 22:55, 31 August 2015 (UTC)

No, I don't use Vector, the new editor or Parsoid. Subfader (talk) 15:14, 5 September 2015 (UTC)

Unfortunately, Parsoid has been required since September 2014. I've updated the docs to make this clearer. Sorry that it wasn't clearer before. Quiddity (WMF) (talk) 21:05, 5 September 2015 (UTC)

Parsoid is definitely recommended, but not strictly required currently. That bug is fixed. Updated the docs again. Mattflaschen-WMF (talk) 02:21, 6 September 2015 (UTC)

Filed as https://phabricator.wikimedia.org/T111625 . Mattflaschen-WMF (talk) 02:24, 6 September 2015 (UTC)

Priorities for the Collaboration (Flow) team

Please see Talk:Structured Discussions/2015/09#h-Priorities_for_the_Collaboration_(Flow)_team-2015-09-02T00:13:00.000Z for some details about the quarterly goals focus starting in October, for the Collaboration team (the primary developers of this extension). Feedback there will be appreciated. Thanks. Quiddity (WMF) (talk) 22:57, 2 September 2015 (UTC)

memcached: recommended or required?

The docs currently say both. If memcached is not an option, would Flow be out of the question? Cavila 18:53, 23 September 2015 (UTC)

I've clarified this.

Flow without an object cache is not usually tested. Flow is best tested with Memcached. Mattflaschen-WMF (talk) 20:50, 24 September 2015 (UTC)

Hi Mattflaschen,

I installed APCu Cache on MW 1.26 and PHP7.

Is there a possibility to use this cache ?

Or could I use memcache AND APCu at the same time in PHP ?

Thanks in Advance! Lanthanis (talk) 15:00, 17 November 2016 (UTC)

I'm not familiar with APCu, so I don't know if this configuration will work. Mattflaschen-WMF (talk) 01:51, 7 January 2017 (UTC)

Looks like this is not a hard requirement. I suspect that Flow does not really make sense without Memcached or Redis (as soon as fixed). However, this is a good question and needs to be clarified, I guess. [[kgh]] (talk) 20:58, 23 September 2015 (UTC)

Oh, that's a pity. My provider doesn't offer 'Memcached', or at least I can't find any evidence that it does. Cavila 09:32, 25 September 2015 (UTC)

It's a bit off topic but I believe that disaster is really going to strike sooner or later. [[kgh]] (talk) 17:23, 25 September 2015 (UTC)

Flow hangs when VisualEditor removed from interface

Tracked in Phabricator
Task T111624

Flow pages appear greyed out and the page hangs (i.e., continuous busy cursor) when the "Remove VisualEditor from the user interface" Gadget is in use. If Flow is incompatible with this Gadget in some way, there should be a clean abort with a message about the problem, rather than simply hanging. – Robin Hood  ^(talk) 18:25, 7 October 2015 (UTC)

Thanks for the report. That bug is tracked at Phab:T111624, and I've asked for input at MediaWiki talk:Gadget-oldeditor.js. Quiddity (WMF) (talk) 20:31, 7 October 2015 (UTC)

souka

this is very nice Souka sou (talk) 18:00, 23 October 2015 (UTC)

open flow discussion with preloaded text/template

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.

---

Dear dev,

Can I append preload content as a query string to flow url?

for example, www.mediawiki.org/wiki/Extension_talk:Flow?topic=a_new_question_regarding_flow Reasno (talk) 09:49, 11 November 2015 (UTC)

Yes you can. I updated Flow/Architecture/URLs#Flow URL summary. Use ?topiclist_preloadtitle=Any+title+text+here&topiclist_preload=StubPageTitle

This was undocumented functionality so it might break. SPage (WMF) (talk) 22:22, 12 November 2015 (UTC)

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

Restricting access to a Flow page

Interestingly enough, Flow works well with the extension Extension:Restrict access by category and group (RACG) which allows to restrict access to pages to member of a given group (see disclaimer below). As a consequence, it is possible to create a discussion which only members of a given group can access.

In order to achieve that, open the page Special:EnableFlow and enter the title of a non-existing page. In the section "Initial header of Flow board", add a category corresponding to the group allowed to access the talk, e.g. [[Category:Sysop]] for wiki administrators. Click on the create button and you are done.

Note: I have tested this solution on a private wiki version 1.25.1 with no cache, Flow v.REL1_25-576f705 and RACG v.2.

Disclaimer: MediaWiki was not written to provide per-page access restrictions, and almost all hacks or patches promising to add them will likely have flaws somewhere, which could lead to exposure of confidential data. Use this hack at your own risks. Steff-X (talk) 18:46, 30 November 2015 (UTC)

The main flaw is that a direct access to a topic (in the form "Topic:xxxxxxx") does not inherit its main page category, so it is not protected. Steff-X (talk) 19:38, 27 December 2015 (UTC)

Hi Steff-X. There's not currently a way to inherit categories (from page to topic), but a category in the Summary area will work for a topic. Perhaps you could test this scenario, to see how it works currently, and so that we can determine what features/settings might be desirable (both for your specific use-case, and possibly more generally):

• What happens if you add [[Category:Sysop]] just to the topic-summary, and not to the page itself? (Is it still visible by anons-etc, within the board?) Quiddity (WMF) (talk) 19:53, 28 December 2015 (UTC)

Can Conversations in flow be moved?

Can Conversations in flow be moved or transcluded to other talk pages if they are deemed more relevant to another conversation? Some thing (talk) 01:52, 3 December 2015 (UTC)

No. This is tracked in phab:T88140 "Moving topics between boards".

If you try to transclude a topic with {{Topic:Sttt7zyd1fjkznyk}}, you get error "Discussions cannot be embedded yet." SPage (WMF) (talk) 07:05, 4 December 2015 (UTC)

Upgrade from REL1_25-576f705 to REL1_26-981e2ff

Hi guys!

My topics disappear after update. Please help.

I'm trying to upgrade my wiki from 1.25 to 1.26. When I try maintence/update.php I've got: Couldn't load Title for log_id and list of the workflows. After it my topics disappear.

What's the problem? Anvk14 (talk) 01:48, 11 December 2015 (UTC)

[Discussion at duplicate thread: Talk:Structured Discussions/2015/12#h-Upgrade_from_REL1_25-576f705_to_REL1_26-981e2ff-2015-12-13T15:32:00.000Z.] Quiddity (WMF) (talk) 21:31, 21 December 2015 (UTC)

Flow

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

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

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

error?

MediaWiki internal .

Exception caught inside exception handler.

Set $wgShowExceptionDetails = true; at the bottom of LocalSettings.php to show detailed debugging information. 46.16.228.191 (talk) 22:53, 29 December 2015 (UTC)

As the message suggests, setting:

$wgShowExceptionDetails = true;

temporarily may help (don't leave it turned on, though, for security reasons).

It doesn't seem you got a short alpha-numeric code with the error. If you did, you could search for that code in the logs. Mattflaschen-WMF (talk) 01:14, 30 December 2015 (UTC)

Why leave such a mistake ? 46.16.228.191 (talk) 22:58, 29 December 2015 (UTC)

Hi. For information on debugging (including viewing errors), see Manual:How to debug. A list of related configuration variables is at Manual:Configuration settings#Debug/logging.

I hope that helps. If not, please help me understand your question/request, by explaining in a bit more detail. Thanks. :-) Quiddity (WMF) (talk) 00:04, 30 December 2015 (UTC)

Please tell me all the codes that I have to put on the LocalSettings.php? 46.16.228.138 (talk) 22:51, 30 December 2015 (UTC)

$wgShowExceptionDetails = true;

Just temporarily, to get a detailed error message. Then, check to make sure there is no sensitive information in the error, then post it here. Then remove the $wgShowExceptionDetails line. Mattflaschen-WMF (talk) 04:05, 31 December 2015 (UTC)

I was asked to add screen http://pastenow.ru/Upload/Paste/HELO.png http://pastenow.ru/Upload/Paste/HELP.png Takhirgeran Umar (talk) 07:19, 31 December 2015 (UTC)