Stewards' noticeboard

Archive Index

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)

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)

Our wiki is giving an error
Hi, I just tried to visit the wiki (Aikatsu! Photo on Stage!!) to add something, and suddenly it's giving me (and all other visitors) an error. It was working about half an hour ago when I was there.

The message it's showing is the following:

MediaWiki internal error.

Exception caught inside exception handler.

Set $wgShowExceptionDetails = true; at the bottom of LocalSettings.php to show detailed debugging information.

Sei (talk) 15:35, 30 January 2016 (UTC)
 * We are really sorry for the inconveniences and will try to fix this issue ASAP. Reception123  (talk) ( contribs  ) 15:44, 30 January 2016 (UTC)
 * Southparkfan is resolving this issue immediately. We are very sorry for any inconveniences caused. Reception123  (talk) ( contribs  ) 15:47, 30 January 2016 (UTC)
 * A fault at my side caused temp. problems at your wiki. It has been fixed, sorry for the issues. Please let me know if I can help you with anything else. Southparkfan (talk) 15:49, 30 January 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)