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?
- Queries
- All Stories
- Search
- Advanced Search
- Transactions
- Transaction Logs
Advanced Search
Feb 28 2019
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
In T3861#76112, @Void wrote:Task has been resolved upstream for a month.
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...
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.
In T3751#72015, @Xenic wrote:Is there a way for me to "reset" mobile view?
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
In T1404#66202, @Paladox wrote:We should uninstall NativeSvgHandler seeing as that's the problem.
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
In T3665#72178, @MacFan4000 wrote:@AmandaCath we can't change the extension files, so this would have to be reported upstream.
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.
Oct 8 2018
I've switched to a different version of AWB and it seems to have corrected the issue.
Oct 4 2018
Hm. This could entirely be because of J4.
I'm not having this issue with Referata or Wikipedia though, I'm able to login to those sites but not Miraheze, which lead me to believe it was Miraheze related, I will check with reporting the bug to the people who work on AWB if it's purely AWB related.
Unfortunately AWB is not controlled by Miraheze. This is either an error in your personal configuration/setup or an upstream problem with AWB itself.
Sep 21 2018
Sep 6 2018
Aug 24 2018
Upstream not interested in relaxing the restriction.
Aug 12 2018
We should uninstall NativeSvgHandler seeing as that's the problem.
Aug 2 2018
Thank you very much! @Paladox
@Centrist16 hi, we have upped the wgSVGMetadataCutoff limit for your wiki. So all new svg uploads should work now. I've gone ahead and reuploaded the svgs for the images you listed. Existing images will need to be reuploaded for the change to take affect against them.
I've done this commit https://github.com/miraheze/mw-config/commit/7ed4d0f4028d60759c66da13bcb91047a2e0e589 so that all new uploads will work. You will need to reupload for existing ones.
I finally traced this issue to wgSVGMetadataCutoff.
We are running "2.9.4+dfsg1-2.2+deb9u2" from stretch.
Which libxml2 version are we running?
Jul 25 2018
Fixed by paladox in 22db977a07fc
Someone from upstream says that the following code needs to be used:
This is still an issue, even ~6 months later, and therefore is not invalid. I have emailed the MediaWiki mailing list and CC’d staff@ - hopefully someone upstream can figure this out. Adding the upstream tag even though I didn’t file on WMF Phab (yet), since emailing the mailing list still technically counts as reporting/seeking advice from upstream.
Jul 24 2018
Jul 9 2018
Upstream task: https://phabricator.wikimedia.org/T199145
Jul 1 2018
This is an upstream issue
Jun 30 2018
Jun 25 2018
@Matthew Thank you for the update
Updated GitHub link (for my reference) https://github.com/miraheze/CreateWiki/blob/master/sql/cw_wikis.sql
I have begun work on this again, so sorry about the delay.
May 29 2018
While it seems an issue, it doesn't seem to be a big issue seeing as only one person has reported it since we began and this was resolved by disabling the troublesome extension.
Little progress and seemingly little interest for now.
With ManageWiki this can be handled by own wikis anyway when it is resolved, plus we have the log of this ticket anyway.
Upstream issue which has no progress in a long time and doesn't look like it will be getting any soon. Better to track the issue via WMF Phab and not Miraheze Phab (for many reasons) therefore closing as invalid as a dead ticket for us.
Seems blocked on policy within WMF.
This is 100% upstream and this isn't a specific request for anything for us to track, therefore invalid per upstream.
This falls into the category of "upstream issue (by way of issue or support) which is getting no progress and even so, having a ticket in our tracker is literally pointless. This isn't causing major issues therefore, if we get rid of this ticket no one will really notice or care".
May 24 2018
May 17 2018
May 14 2018
upstream blocked tasks are low
May 9 2018
May 8 2018
May 3 2018
Blocked by Upstream
Blocked by Upstream
It shouldn't be, but the wiki is closed, so for now closing as declined.
Issue has been resolved upstream.
Apr 22 2018
Removed from allthetropeswiki, developmentwiki, ircwiki, and takethatwikiwiki.