Wikinews:Water cooler/technical/archives/2014/June


The Hot Cat widget......even when I'm signed in, every time I try to add a throws me into an editing screen. What gives?? --Bddpaux (talk) 22:26, 10 June 2014 (UTC)[reply]

Also, the "review progress" gadget — the thing that turns parts of the Wikinews logo red when there are articles waiting for review — is turning the logo all red (which should only happen if there's a long review queue; ten or more, iirc). --Pi zero (talk) 23:01, 10 June 2014 (UTC)[reply]
Fixed the review progress gadget (Caused by a combination of and not being robust in how apilib2.js reads XML). The hot cat thing is weird, not sure what that's about. Especially because its using same code as commons, commons has same version of mediawiki as we do, and the thing works on commons. Bawolff 23:49, 10 June 2014 (UTC)[reply]
  Done The hot cat issue was caused by changes in how MediaWiki makes its edit form. It was fixed by [1], but that change didn't propogate to wikinews very quickly due to caching. It should work now though. Bawolff 23:56, 10 June 2014 (UTC)[reply]

The entire site is, at this moment, almost entirely non-functional.

The search box is screwed up; afaics I can't access any page that isn't in mainspace (I tried SpecialːPrefixIndex and TemplateːLead article 4, and was told neither exists and offered the opportunity to create them.

The edit box I'm typing in is also royally screwed; I can't type colons in order to indent this comment, and I can't type the square brakets to specify links. I also can't sign this post because tilde doesn't work.

Okay, I've got things working again. Looks like the UI was deliberately trying to prevent me from being able to type anything, by going into some sort of international alphabet mode, but I've managed, for the moment at least, to convince it to use "native keyboard mode". That could be something bizarre I did by accident; but if it's the result of somebody introducing something they thought would be a desirable "feature"... then how can we shut it off for all users (including IPs) on this project? --Pi zero (talk) 02:02, 11 June 2014 (UTC)[reply]

  • Here's another couple of things that are broken, that I've noticed this morning.
  • {{hidden}} (with the result that lots and lots of stuff all over the side is inaccessible).
  • Gadget "Open links to external sites in a new window". Fixed.

--Pi zero (talk) 11:07, 11 June 2014 (UTC)[reply]

The {{hidden}} on this page seems to be working now? or is there something I'm missing... - Amgine | t 20:11, 12 June 2014 (UTC)[reply]
If it's working for you, that's significant, since it's still not working for me (though your hidden2 does work for me). --Pi zero (talk) 20:15, 12 June 2014 (UTC)[reply]
Well, the hidden2 is surprisingly fast. We need to add some css to make it otherwise the same. I think I'd suggest migrating due to the speed benefit. - Amgine | t 21:04, 12 June 2014 (UTC)[reply]
Sorry, I made a typo in my last fix which broke some things. I really thought I tested it... Bawolff 22:33, 14 June 2014 (UTC)[reply]
That's got it. Thanks! (Also, blimey. An apostrophe. What an appalling programming language.) --Pi zero (talk) 22:45, 14 June 2014 (UTC)[reply]

What the heck is up with the Newsroom page???

Look near the bottom........wonky no matter which browser/computer I use.....I know I'm overdue for new glasses, but sheesh!!! --Bddpaux (talk) 05:41, 29 June 2014 (UTC)[reply]

That is odd, I'm also seeing it and I can't what is causing the problem. But if you squint just right, it's almost sort of legible. :p Though, it certainly needs fixing. —Mikemoral♪♫ 11:40, 29 June 2014 (UTC)[reply]
What is it you both are seeing? --Pi zero (talk) 11:49, 29 June 2014 (UTC)[reply]
Here's a screenshot. For reference, I'm using Google Chrome on Windows 8. —Mikemoral♪♫ 11:55, 29 June 2014 (UTC)[reply]
Firefox doesn't do that for me. It looks like a skin problem, but I've tried switching to vector and it still doesn't happen for me. --Pi zero (talk) 12:10, 29 June 2014 (UTC)[reply]

It's happening in all four skins for me in Chrome. Though it looks fine in Firefox. I'm guessing it might be an issue with Chrome perhaps. —Mikemoral♪♫ 12:15, 29 June 2014 (UTC)[reply]