Issue is blocked by something controlled by another entity.
Tue, Mar 5
Thu, Feb 28
Thanks @Paladox - I'll close this now.
I updated PageForms yesterday which brought in some fixes for PageForms.js.
It is now working! I could tell it was going to work because previously it had a processing circle of whirliness in the centre of the screen when you were creating a form and now it doesn't. I haven't closed this ticket. I'm interested as to whether someting happened overnight that sorted Cargo out?
Feb 20 2019
Completely upstream with no dependency on us in any way, task here adds no value.
Feb 4 2019
Feb 3 2019
Jan 27 2019
Jan 25 2019
You should be able to enable them now.
Jan 23 2019
Jan 16 2019
Correction, Special:ListFiles has been fixed. Is there an upstream task for Extension:Editcount?
Jan 12 2019
it's now resolved, maybe because of upgrading...
I confirmed it now. There was no problem.
Not able to reproduce this bug anywhere.
Now that we have upgraded to MediaWiki 1.32, is this still a problem?
Jan 9 2019
Jan 5 2019
@Corey try looking at the Stewards Noticeboard in the mobile view.
@Corey yes it is
The page is still showing properly for me.
Jan 1 2019
The page is displaying correctly for me.
Dec 31 2018
Seconding MacFan that this still does occur. Appears to be an upstream issue.
Blocked by upstream.
Dec 28 2018
And the 'problem' occurs on Wikipedia too when I edit there in Visual Editor mode.
Dec 8 2018
Dec 6 2018
Dec 3 2018
This is an upstream task, which are low prio
Nov 6 2018
Yeah, it looks like it's a PHP 7.x thing, since not all extensions have been upgraded for it.
Nov 5 2018
Nov 4 2018
Hi, i reverted https://github.com/miraheze/mw-config/pull/2432/files but never reopened this task so i apologise. private wiki's cannot use restbase yet but it is on upstream list of things to do.
It stil does not work for my (private) jcswiki. What should i do?
Oct 30 2018
Bug report upstream, fix would require no action from us so this task achieves nothing here.
Oct 11 2018
Not sure, but if it hasn’t been already, and we can confirm it’s not a Miraheze issue, it should be ASAP.
Has this been reported upstream?
Likely an extension bug unrelated to Miraheze.