Stewards' noticeboard

Archive Index (Archive 1 (12 August-19 November 2015) Archive 2(16 November 2015-24 January 2016) )

Can't access my wiki without resetting password each time
Hi.

I'm new to wiki's and it might be that I'm doing something wrong. Every time I, and my other members, try to access our wiki (https://pifusas.miraheze.org/wiki/Forside) we need to reset our passwords to be able to enter. The system does not accept our newly created passwords as we submit them if we revisit after browser has been closed.

Regards Sindre (talk)

"Hi, I am also new at Miraheze and I have a very similar problem. I have been granted a new private wiki (Thank you, Miraheze). I am not able to use the newly created password, even if I just log out and try logging back without closing the window. It accepts the password, but does not login, it just says something like I do not have rights to read. I have checked cookies, they are enabled. I have tried to erase them, no success."

EDIT: Is there any solution please? Thank you Regards Adamk (talk)
 * : does this still occur? We fixed this problem a few days ago, so hopefully this does not happen anymore. Southparkfan (talk) 14:49, 14 February 2016 (UTC)
 * : True, it's working now! Thanks a lot! Adamk (talk) 16:12, 14 February 2016 (UTC)

Mail from Miraheze in Gmail spamfolder
When received mail from the Miraheze server it's delivered in the spam folder at Google Gmail servers. I reported this before at IRC and it was fixed for a while, but goes wrong again.

A copy/paste of the mail header below. When looking to that it looks like SPF is not working optimal since the status is neutral instead of permitted. I also suggest to look at http://mxtoolbox.com/domain/miraheze.org/ as well for advise, which suggest to add dmarc and optimize 3 DNS settings. And take a look at https://toolbox.googleapps.com/apps/checkmx/check?domain=miraheze.org which suggest to add DKIM --- Mail header ---

Delivered-To: jurjen@jurjendevries.com Received: by 10.28.12.68 with SMTP id 65csp2810490wmm; Tue, 19 Jan 2016 15:19:51 -0800 (PST) X-Received: by 10.28.218.81 with SMTP id r78mr506797wmg.91.1453245591944; Tue, 19 Jan 2016 15:19:51 -0800 (PST) Return-Path:  Received: from mail.miraheze.org ([2a00:d880:6:787::2]) by mx.google.com with ESMTP id b6si36410447wmh.122.2016.01.19.15.19.51 for ; Tue, 19 Jan 2016 15:19:51 -0800 (PST) Received-SPF: neutral (google.com: 2a00:d880:6:787::2 is neither permitted nor denied by domain of noreply@miraheze.org) client-ip=2a00:d880:6:787::2; Authentication-Results: mx.google.com; spf=neutral (google.com: 2a00:d880:6:787::2 is neither permitted nor denied by domain of noreply@miraheze.org) smtp.mailfrom=noreply@miraheze.org Received: from localhost (unknown [IPv6:2a00:d880:6:786::2]) by mail.miraheze.org (Postfix) with ESMTPSA id 5B93A504E00A for ; Tue, 19 Jan 2016 23:19:51 +0000 (UTC) List-Help: https://www.mediawiki.org/wiki/Special:MyLanguage/Help:Watchlist From: Permanent Future Lab  Reply-To: reply@not.possible Date: Tue, 19 Jan 2016 23:19:51 +0000 Message-ID:  X-Mailer: MediaWiki mailer List-Unsubscribe:  MIME-Version: 1.0 Content-type: text/plain; charset=UTF-8 Content-transfer-encoding: 8bit Subject: Permanent Future Lab page Museum voor Communicatie Den Haag has been changed by BartWR To: Jurjendevries 
 * I added our IPv6 addresses to our SPF record. Southparkfan (talk) 16:11, 24 January 2016 (UTC)
 * I just check it with the e-mail watchlist function. Still goes to spam folder. --Jurjendevries (talk) 22:57, 24 January 2016 (UTC)
 * Was the SPF still denied by miraheze.org? I do not have this error at all with Outlook. Southparkfan (talk) 17:10, 25 January 2016 (UTC)
 * The SPF is not authorative. Like an agent, it neither confirms nor denys. John (talk) 15:26, 29 January 2016 (UTC)
 * I'm going to work on this today and in the future as a continuation project as the mail setup is my area here. I have already added DKIM recently. John (talk) 15:26, 29 January 2016 (UTC)
 * I've done a bit of work on this, the SPF record accepts our emails and the DKIM set up seems valid. There should no longer be any issues with this hopefully. John (talk) 16:56, 29 January 2016 (UTC)
 * I can confirm that I receive an e-mail today in my Google inbox folder instead of the spam folder. Great job, thanks! --Jurjendevries (talk) 10:18, 3 February 2016 (UTC)

Constant error
There seems to be a error when I click on links that is similar to the below:

[811d20be] 2016-02-02 00:07:52: Fatal exception of type MWException

Note: the error message doesn't actually appear blue.

I really don't like it, and it is seemingly effecting  all  Miraheze wikis. Could you please fix this? Lemondoge T C GC 00:42, 2 February 2016 (UTC)

My users and I are getting this error too. It seems if I refresh multiple times, I'll actually be able to see the page, but doing that while editing is extremely annoying. Rikki21 (talk) 04:54, 2 February 2016 (UTC)
 * Looks like an error occured on one of our mwservers. Investigating. Southparkfan (talk) 06:49, 2 February 2016 (UTC)
 * Update: the CSS magic word was not recognized on mw1:

2016-02-02 06:48:12 mw1 allthetropeswiki: [c37445f1] /w/index.php?title=Special:RecentChanges&limit=50  MWException from line 337 of /srv/mediawiki/w/includes/MagicWord.php: Error: invalid magic word 'css' Thia did not occur on mw2. mw1 is still giving strange ecceptions, although at a much less rate. Rebuilding LC cache there again. Not able to depool mw1.. Southparkfan (talk) 10:02, 2 February 2016 (UTC)
 * 1) 0 /srv/mediawiki/w/includes/MagicWord.php(262): MagicWord->load(string)                         #1 /srv/mediawiki/w/includes/parser/Parser.php(5212): MagicWord::get(string)
 * 2) 2 /srv/mediawiki/w/extensions/CSS/CSS.php(124): Parser->setFunctionHook(string, string)         #3 [internal function]: wfCSSParserFirstCallInit(Parser)
 * 3) 4 /srv/mediawiki/w/includes/Hooks.php(201): call_user_func_array(string, array)
 * 4) 5 /srv/mediawiki/w/includes/parser/Parser.php(328): Hooks::run(string, array)                   #6 /srv/mediawiki/w/includes/parser/Parser.php(338): Parser->firstCallInit
 * 5) 7 /srv/mediawiki/w/includes/parser/Parser.php(5055): Parser->clearState                       #8 /srv/mediawiki/w/includes/parser/Parser.php(415): Parser->startParse(Title, ParserOptions, integer, boolean)                                                                                     #9 /srv/mediawiki/w/includes/OutputPage.php(1752): Parser->parse(string, Title, ParserOptions, boolean, boolean, NULL)                                                                              #10 /srv/mediawiki/w/includes/OutputPage.php(1694): OutputPage->addWikiTextTitle(string, Title, boolean, boolean, boolean)
 * 6) 11 /srv/mediawiki/w/includes/OutputPage.php(3927): OutputPage->addWikiText(string)              #12 /srv/mediawiki/w/includes/specialpage/SpecialPage.php(452): OutputPage->wrapWikiMsg(string, string)
 * 7) 13 /srv/mediawiki/w/includes/specialpage/ChangesListSpecialPage.php(49): SpecialPage->outputHeader
 * 8) 14 /srv/mediawiki/w/includes/specials/SpecialRecentchanges.php(64): ChangesListSpecialPage->execute(NULL)
 * 9) 15 /srv/mediawiki/w/includes/specialpage/SpecialPage.php(384): SpecialRecentChanges->execute(NULL)
 * 10) 16 /srv/mediawiki/w/includes/specialpage/SpecialPageFactory.php(553): SpecialPage->run(NULL)
 * 11) 17 /srv/mediawiki/w/includes/MediaWiki.php(281): SpecialPageFactory::executePath(Title, RequestContext)
 * 12) 18 /srv/mediawiki/w/includes/MediaWiki.php(714): MediaWiki->performRequest
 * 13) 19 /srv/mediawiki/w/includes/MediaWiki.php(508): MediaWiki->main
 * 14) 20 /srv/mediawiki/w/index.php(41): MediaWiki->run
 * 15) 21 {main}

display:inline-block not working correctly for Chrome
I'm unsure where to ask this, but as the inline-block command works on Chrome from other websites I am assuming it's a wiki issue? This is what I'm working on. It displays correctly in Firefox and IE, but not Chrome. Does anyone happen to know why? Rikki21 (talk) 00:19, 3 February 2016 (UTC)
 * Hi, It might just be a chrome error, try using Explorer/Firefox. SleepyMode  10:47, 3 February 2016 (UTC)

Several pbs on wiki "ggdr"
Hi, I have 3 problems on the wiki "ggdr" (http://ggdr.miraheze.org) ! Erreur lors de la création de la miniature : convert: unable to open image `/mnt/mediawiki-static/ggdrwiki/b/bd/Schma_de_ligne_030.png': No such file or directory @ error/blob.c/OpenBlob/2709. convert: unable to open file `/mnt/mediawiki- static/ggdrwiki/b/bd/Schma_de_ligne_030.png' @ error/png.c/ReadPNGImage/3922. convert: no images defined `/tmp/transform_660dcd41af4e-1.png' @ error/convert.c/ConvertImageCommand/3210. Error code: 1 What's the matter? Babskwal (talk) 10:43, 8 February 2016 (UTC)
 * on the home page (only: it works normally on all the other pages), "HTTP 500 error"; why that and only on the home page ???
 * when the users try to connect to ggdr, they can't, and have to make as if they had forgotten their password, change it and then connect... ?
 * the first time I inserted files, it has worked correctly; but since the last week, instead of the image, it displays
 * Seems fixed to me?
 * I don't understand it?
 * I don't know why this fails, but replacing the "é" with an "e" (when either uploading or renaming) seems to fix the issue for me. I'll investigate why special characters fail. Southparkfan (talk) 11:58, 8 February 2016 (UTC)
 * 1. OK, thanx !
 * 2. When I try to connect with my password, I get :

Vous ne pouvez pas lire cette page, pour la raison suivante : L’action que vous essayez de réaliser n’est permise qu’aux utilisateurs d'un des groupes : Administrateurs, member.
 * The only solution I found is to ask for a new password...
 * 3. If renaming can fix the pb, I can always use "e" instead of "é" ! Babskwal (talk) 13:33, 8 February 2016 (UTC)
 * Problem again... :(
 * Fixed avoiding the "é". Babskwal (talk) 10:09, 9 February 2016 (UTC)
 * I think this is a known issue with foreign-language wikis? As a logged in steward, when I navigate to the wiki I get a permission error. -- Cheers, NDKilla ( Talk • Contribs ) 13:24, 9 February 2016 (UTC)
 * PS: I get 504 gateway timeouts trying to load the main page. -- Cheers, NDKilla ( Talk • Contribs ) 13:26, 9 February 2016 (UTC)
 * Points 1&3 fixed (new main page without parser functions). Don't know for #2 : the only solution I've found to avoid this permission error is ask to change ther password... Babskwal (talk) 11:00, 10 February 2016 (UTC)
 * Babskwal: I hope to fix that login error soon. A workaround is to let your users login on this wiki, Meta. Any wiki with a .miraheze.org subdomain is in our (technical) control, so it's safe to login. Southparkfan (talk) 14:08, 10 February 2016 (UTC)
 * Update: we've fixed the login problem on private wikis. Southparkfan (talk) 19:00, 11 February 2016 (UTC)
 * Update: we've fixed the login problem on private wikis. Southparkfan (talk) 19:00, 11 February 2016 (UTC)

Hey guys. First I want to thank you for the new wiki, cybercrime.miraheze.org. I have been having an issue:

I have been able to add two people to administer the wiki (I have it protected). There is another user I need to add to it. I type this username verbatim into the search in special:userrights but nothing comes up.

Any suggestions? The user I am trying to add is Njfazz and our wiki is cybercrime.miraheze.com.

He says he has confirmed his email (which is what allowed me to add the other two admins).

Thanks again!

Visual Editor error
Hi. I was able to use the visual editor until recently, when it keeps giving me a 401 parsoid error whenever I try to edit a page on my wikis (hobbies.miraheze.org & biblicalwiki.miraheze.org). I am able to use it at meta.miraheze.org though. Your assistance is much appreciated!
 * A Parsoid server error? Looking after it. SleepyMode  18:13, 23 February 2016 (UTC)
 * It appears both wikis are registered by the parsoid server, also, It seems to work on every other wiki. SleepyMode  18:18, 23 February 2016 (UTC)
 * I believe the issue is persistent among private wikis and really is a design factor of MediaWiki and VisualEditor unfortunately. I'll take a look at how it interacts with unreadable APIs. John (talk) 18:34, 23 February 2016 (UTC)
 * I was able to use Visual Editor on my private wiki for a few weeks. It started to give me the 401 error recently. Not sure if this helps, but under VisualEditor's troubleshooting section at https://www.mediawiki.org/wiki/Extension:VisualEditor, it states:
 * parsoidserver-http-bad-status : 401
 * Caused by read or edit restrictions. If you've set up a private wiki and don't want to use cookie forwarding, you can explicitly remove restrictions for Parsoid by IP address. -- Cat (talk) 21:16, 23 February 2016 (UTC)
 * we were already using that, but because we use external Parsoid servers (and we have IPv6 stuff), we had to add "::ffff:" to our Parsoid IPs. VisualEditor should work now. Southparkfan (talk) 13:01, 26 February 2016 (UTC)

Development wiki Dormancy policy Exception
Hello there, I think you should look at that. Recently, I got some medical "Distrubances", and.. I can't work on my wiki, As I won't be here for a long while too, I'm not sure anyone can mainitance the wiki as the staff of it are busy in other things. SleepyMode 15:18, 24 February 2016 (UTC)