Misplaced Pages

This is an old revision of this page, as edited by Davey2010 (talk | contribs) at 00:51, 2 June 2016 (→WP:Comments in Local Time). The present address (URL) is a permanent link to this revision, which may differ significantly from the current revision.

• Table of contents
• First discussion
• End of page
• New post

• WP:VPT
• WP:VP/T
• WP:TECHPUMP
• WP:PUMPTECH

Newcomers to the technical village pump are encouraged to read these guidelines prior to posting here. Questions about MediaWiki in general should be posted at the MediaWiki support desk.

view · edit Frequently asked questions (see also: Misplaced Pages:FAQ/Technical) Click "" next to each point to see more details. If something looks wrong, purge the server's cache, then bypass your browser's cache. This tends to solve most issues, including improper display of images, user-preferences not loading, and old versions of pages being shown. No, we will not use JavaScript to set focus on the search box. This would interfere with usability, accessibility, keyboard navigation and standard forms. See task 3864. There is an accesskey property on it (default to accesskey="f" in English). Logged-in users can enable the "Focus the cursor in the search bar on loading the Main Page" gadget in their preferences. No, we will not add a spell-checker, or spell-checking bot. You can use a web browser such as Firefox, which has a spell checker. If you have problems making your fancy signature work, check Help:How to fix your signature. If you changed to another skin and cannot change back, use this link. Alternatively, you can press Tab until the "Save" button is highlighted, and press Enter. Using Mozilla Firefox also seems to solve the problem. If an image thumbnail is not showing, try purging its image description page. If the image is from Wikimedia Commons, you might have to purge there too. If it doesn't work, try again before doing anything else. Some ad blockers, proxies, or firewalls block URLs containing /ad/ or ending in common executable suffixes. This can cause some images or articles to not appear. For server or network status, please see Wikimedia Status. If you cannot reach Misplaced Pages services, see Reporting a connectivity issue.

Village pumps

policy

tech

proposals

idea lab

WMF

misc

• Refining the administrator elections process
• Blocks for promotional activity outside of mainspace

• view
• edit
• history
• watch
• archive
• talk
• purge

Not able to edit

@Bishonen reported on IRC that she can't edit anything in the past hours (seems like T134869, but more severe: appears not periodically but continuously). I don't know much about it, just she asked me to report it. --Tacsipacsi (talk) 12:45, 15 May 2016 (UTC)

Thanks, Tacsipacsi. I've realized I can in fact edit after a fashion using Chrome. But I really really don't want to. In Firefox it's impossible. I have the latest version of Firefox for OSX, and it can neither preview nor save since at least seven hours. All I get when I try is the "Secure Connection Failed" message. Does the phabricator report mean I can look forward to the problem being fixed? Anybody got any idea of the timescale for that? How long a wikibreak should I take? :-( User:RexxS, you got anything? Bishonen | talk 14:15, 15 May 2016 (UTC).

This is a shot in the dark and probably not related, but are you using Avast Antivirus? I had an issue with HTTPS content not loading properly on Misplaced Pages that was fixed by disabling HTTPS scanning in Avast. clpo13_(talk) 16:05, 15 May 2016 (UTC)

Not using it, no. But thanks. Bishonen | talk 16:31, 15 May 2016 (UTC).

@Bishonen: All of the other reports I've been able to track down associate the problem with Firefox version 46 (which was originally released on 3 May 2016 and my version is currently at 46.0.1). I'm currently using Chrome this month as part of my usual anti-checkuser strategy, but I'll get Famously Sharp to attempt a post on your user talk. Hmmz - it works. Ok - only suggestion I can make is for you to try Firefox version 47 which is in Beta - download from https://www.mozilla.org/en-US/firefox/beta/all/ (the OSX version is in blue in the middle column). --RexxS (talk) 19:42, 15 May 2016 (UTC)

• Bishonen, have you tried reloading the page? These past few days, I have randomly got a Firefox error message about the connection being insecure, but reloading the page always solves the problem. --Stefan2 (talk) 20:41, 15 May 2016 (UTC)

• Many times, but it didn't help. But actually it has just started working quite smoothly! Long may it last. I don't see myself as a Beta user, much. Bishonen | talk 20:48, 15 May 2016 (UTC).
  • I've been getting the "Your connection is not secure" warning for a week or so. SarahSV 06:28, 18 May 2016 (UTC)
    • Did you try the usual WP:BYPASS procedures? Whatamidoing (WMF) (talk) 20:46, 18 May 2016 (UTC)

• Whatamidoing (WMF), thanks for the reply. When it happens a notice appears saying "try again," so I have to click on that, then a second notice appears, which I think says "resend," and I have to click on that too. Then the edit is saved or the preview viewable, whichever it was. SarahSV 06:14, 19 May 2016 (UTC)

• I've been having this problem off and on as well; unlike Bishonen it's not consistent, but rather happens randomly about every tenth time I try to save an edit. I am running Avast, but I've already turned off https scanning as directed when I first Googled to solve the problem — but even with that turned off, the problem still recurs. It appears to interfere more actively with using Twinkle than with conventional editing — for the XFD module in particular I almost always have to undertake a second attempt because the first one fails under an unspecified error message, which I'm presuming is related to this "secure connection issue" because if everybody were having as many Twinkle failures as I've been having, Twinkle's talk page would be flooded with requests. But it's not, which means this is pretty clearly a "just happening to me" problem. Bearcat (talk) 19:56, 23 May 2016 (UTC)
  • I have also been having the issue similar to Bearcat (though probably less severe, and not particularly with AfD) – is there a Phab job on this? Or is no one working on it at all?... --IJBall (contribs • talk) 02:25, 27 May 2016 (UTC)
    • Firefox 46.0.1 here. Had "Secure Connection Failed" problem months ago, and it stopped. Now it's doing this again. I've had this happen several times today. — Maile (talk) 23:58, 30 May 2016 (UTC)

Why am I seeing a "Welcome" message?

Soon some of you may see a "Welcome" dialog in the wikitext editor, as per my heads-up here. (Remember that the English Misplaced Pages is a Single Edit Tab wiki now, so if you don't know or remember what this entails, check the related announcement from last month). Best, --Elitre (WMF) (talk) 13:46, 19 May 2016 (UTC)

Lets keep an eye out for user issues in case we need a MediaWiki:Sitenotice. — xaosflux 14:36, 19 May 2016 (UTC)

I just got this stupid popup, I've been editing for seven years and am at no. 185 in the most edits list. I turned off VE as soon as an option to do so was available. I've been an admin since 2011 ferchrissakes. Get real. --Redrose64 (talk) 19:33, 19 May 2016 (UTC)

Joining Redrose64 in not welcoming this in the least. In the best of circumstances I hate these not-really-there phenomena that social media uses nowadays; my screen freezes with the darned thing hovering there and it's never clear what I should click on to be able to use the window again. In this case it almost gave me a heart attack - I was previewing and thought I'd lose the edit. I took the risk of clicking on "Edit" or whatever and thank all the gods, neither lost the edit nor crashed my browser. WMF: I volunteer here, doing the work that makes this wiki popular enough that you get to be handsomely paid for whatever it is you do. Stay out of my workflow. Take your abysmal Visual Editor and shove it, don't thrust it in front of me, I and the vast majority of the people who actually work around here told you it sucks, it sucks, that's it, stop demanding we choose between it and what works! Yngvadottir (talk) 19:49, 19 May 2016 (UTC)

Please relax a bit, it makes everyone's participation a whole lot more pleasant. —TheDJ (talk • contribs) 19:57, 19 May 2016 (UTC)

Don't tell me to relax. It came up again. Do you work for that awful outfit? If so, please report that the experience of having this pop-up freeze one's screen is not pleasant. Yngvadottir (talk) 20:08, 19 May 2016 (UTC)

"Do you work for that awful outfit" No, not that that should have anything to do with how we communicate with eachother. —TheDJ (talk • contribs) 21:08, 19 May 2016 (UTC)

It really is disruptive - I get a box with no "dismiss" option - only "start editing" that is quite jarring - when I clicked on it, it just went away. Completely useless in the workflow for me as an editor, and unexpected. I think we should put up the site notice to warn about this - any objections? — xaosflux 20:20, 19 May 2016 (UTC)

I know that this is a case of hindsight, and given that all I know of this is what I learned from mucking about with scripts in...the other thread, I probably don't have all the information I would need to speak intelligently about this. But just for curiosity's sake, shouldn't it have been possible to prevent the message from popping up for current users by adjusting the starting value of visualeditor-hidebetawelcome in everyone's preferences? New accounts could have the welcome enabled, of course, since it's targeted to them, but would it not have been straightforward enough to just set that pref to "true" for all current users? Maybe this version of the welcome is different though or something, so I might not understand correctly. Writ Keeper ⚇♔ 20:21, 19 May 2016 (UTC)

@Writ Keeper: I made the decision not to do that intentionally, I'm afraid. Doing the fetch of the users' edit count and registration date would have added another few ms to every edit page load for every editor for the rest of time. Pre-setting tens of millions of rows in the databases to fake 'visualeditor-hidebetawelcome' as true would be a pretty major step which we go out of our way to avoid. Note that any account that's seen the dialog before (e.g. in the visual editor) won't get the prompt (unless they've reset their preferences), it's just a one-time thing regardless of which editor you use. Jdforrester (WMF) (talk) 21:38, 19 May 2016 (UTC)

Hmm, I guess I can understand that. I know my ops people always get mad at me when I write update queries for them to execute that hit millions of rows. I wouldn't have said it's a dealbreaker--there are generally speaking ways to do it gradually without totally destroying the database--but I can respect it, as long as it was at least thought about. Writ Keeper ⚇♔ 21:42, 19 May 2016 (UTC)

When I just now brought up a deleted page to check its logs, I got the "Welcome to Misplaced Pages" popup smack in the middle of my screen, that told me to click on it to begin editing. I've been on Misplaced Pages for about 7-8 hours today, and this just popped up the first time. If it's an oversight, please give us an opt out. This shouldn't be coming up for anyone but people who have never edited at Misplaced Pages before. And considering how hard internet users work to keep popups off their screens, maybe this was not the best of ideas. And by the way, in my Preferences, "Temporarily disable the visual editor while it is in beta" has been checked off as long as the option has been there. — Maile (talk) 20:30, 19 May 2016 (UTC)

I just got it straight across the board, testing all the wikis. — Maile (talk) 23:38, 19 May 2016 (UTC)

You should see it once per wiki while logged in. This means once at the English Misplaced Pages, once at the German Misplaced Pages, once at the French Misplaced Pages, etc. – all the languages times all the projects (times all the accounts, if you have more than one, as I do). Most editors don't spend much time doing cross-wiki work, so most editors won't see it more than once or twice. Personally, I've already clicked past it at least six times in the last hour. (Also, it's faster to click "Start editing" on that dialog than to go to Preferences, find an item, and opt-out.) Whatamidoing (WMF) (talk) 00:16, 20 May 2016 (UTC)

\o/ I just got one Fred Gandt · talk · contribs 20:56, 19 May 2016 (UTC)

I just got it too. DuncanHill (talk) 21:01, 19 May 2016 (UTC)

Yup, looks like we all got a VisualEditor prompt. — Andy W. (talk · ctb) 21:11, 19 May 2016 (UTC)

We are blessed! ;-) Fred Gandt · talk · contribs 21:30, 19 May 2016 (UTC)

• Ok so for a sitenotice, I'm not sure linking to Misplaced Pages:VisualEditor/Updates/Single Edit Tab is the most informative page? Anyone got anything better? — xaosflux 21:14, 19 May 2016 (UTC)

Why not link to this angry public flogging thread, since it is going to contain all the answers as time goes on - seriously? Fred Gandt · talk · contribs 21:30, 19 May 2016 (UTC)

Will mock something up and post back soon. — xaosflux 21:38, 19 May 2016 (UTC)

• Ironically I got the welcome message on Commons but not here .... I feel even more blessed lol, –Davey2010 21:52, 19 May 2016 (UTC)

Teacher's pet ;-) Fred Gandt · talk · contribs 22:07, 19 May 2016 (UTC)

• Playtime again in the main sandbox.--TMCk (talk) 22:18, 19 May 2016 (UTC)

Site notice

Mockup:

Any suggested changes? — xaosflux 23:46, 19 May 2016 (UTC)

What action do you expect typical users to take in response to that proposed message? Whatamidoing (WMF) (talk) 00:07, 20 May 2016 (UTC)

I trust the typical users will band together and demand another site notice to explain the first site notice which explains the trivial pop-up, using There Was an Old Lady Who Swallowed a Fly as a general guide to strategy. --Tagishsimon (talk) 00:12, 20 May 2016 (UTC)

Become aware of what is going on. I'm not about to slam it up there unless there is some agreement here that it will be useful. — xaosflux 00:15, 20 May 2016 (UTC)

Good call. You do not have 'some agreement', or, at least, you do have some dissent. --Tagishsimon (talk) 00:17, 20 May 2016 (UTC)

Xaosflux, there's no clear "call to action", if you don't mind the designers' jargon. It first tells editors something that they'll find out on their own (so it's redundant), and then it offers a place to discuss something or another about "this", but at the time that they're offered this option to discuss something, they don't know what you want them to discuss, because they haven't seen the dialog yet. If I didn't already know what this message was about, I'd be confused by it. The discussion is also unlikely to provide actual value to the participating editors: by the time you know enough to discuss it, you've already dismissed it.

For the record, I don't think it's an unreasonable thing to consider; in fact, I very briefly considered a CentralNotice myself. It's a tool I often consider, but rarely use, for user interface changes. However, I decided that the net result of any such message would be thousands of editors at 800+ WMF wikis spending collectively hundreds of hours trying to figure out what I was talking about. That time would be far more than they would spend in dismissing the one-time dialog when it reached them – and they'd still have to dismiss the dialong anyway. So based on that analysis, it didn't seem like a valuable use of volunteer time and attention, and I abandoned the idea. Whatamidoing (WMF) (talk) 00:45, 20 May 2016 (UTC)

To be clear, unless there is actual support I'm not touching the sitenotice. My goal was to get information in front of people to avoid drama, certainly not make more. — xaosflux 01:00, 20 May 2016 (UTC)

I'm not going to pretend to know exactly why this welcome popup is popping up, but get the jist. Please bare that in mind as I suggest that if there's to be a site notice to act as a heads up, it should be simple, honest and self contained advice.

Something like "Because of a discussion that lead to a decision to implement a thing, the WMF did a thing which lead to a discussion which reversed the decision, and resulted in a technical glitch. This glitch will manifest as a welcome message that pops up as editors begin editing. This popup will only show once on each Wiki thing, and other than getting in the way a little, changes nothing. Welcome to Misplaced Pages! ;-)" - with obvious editing.

It's not a call to action, or an obscure and confusing riddle; it just says what's happening to alleviate potential surprise and maybe save some freaking out. Fred Gandt · talk · contribs 01:06, 20 May 2016 (UTC)

It may be simpler to just make the popup itself do the talking since I'm sure a lot of editors have not yet been harassed by it. For some reason, it popped up at least twice for me, and the option buttons were, as stated, not very clear on what to expect when selecting the edit option. I, for one, did not know whether to expect the familiar editing format of some newfangled thing to waste my time. -- André Kritzinger (talk) 01:20, 20 May 2016 (UTC)

I'd be in a favor a single in the top right corner, clicking it: dismisses the box forever and keeps all your settings exactly how they were prior to the popup. — xaosflux 01:45, 20 May 2016 (UTC)

An would do it. It was the first thing I was looking for when the popup popped up... André Kritzinger (talk) 02:11, 20 May 2016 (UTC)

Me too. Fred Gandt · talk · contribs 03:40, 20 May 2016 (UTC)

A forever X would be a step forward, click it once and it stays gone for all eternity. Even better, if our Preferences had an option to suppress any and all popups that Wikimedia could come up with, forever and ever and ever. — Maile (talk) 14:15, 20 May 2016 (UTC)

@Elitre (WMF):; @Whatamidoing (WMF): -- Any options for tweaking the UI of this popup as suggested above? — xaosflux 14:44, 20 May 2016 (UTC)

I've asked. I don't know whether I'll get a definitive answer today, but I'll let you know. One of the devs also suggested making it possible to dismiss things like this by clicking anywhere outside the box, so there may be more than one 'leave me alone' approach implemented. Whatamidoing (WMF) (talk) 16:31, 20 May 2016 (UTC)

If there's a need for the Welcome message, making it accidentally dismissable is not a good idea. --Pipetricker (talk) 09:02, 21 May 2016 (UTC)

I was gone for a few days, and when I returned a pop-up greeted me when I wanted to edit. I agree with Maile above, quit spamming us with the VE already. I already have just one edit tab, I suppressed the VE one. Manxruler (talk) 15:26, 25 May 2016 (UTC)

Could just use my method of nuking any unwanted stuff with uBlock Origin's element picker; it seems to do the trick most of the time... 02:49, 27 May 2016 (UTC)

Disabling in all wikis

So far this has worked for me: I've added in m:Special:MyPage/global.css a

.oo-ui-windowManager-floating {
    display: none;
}

This should also prevent other past and future similar-looking popups/splashscreens/whatever. I'm also filing a few reports about specific problems, please do the same. Nemo 11:40, 22 May 2016 (UTC)

I think this is terrible advise for people. Anyone going this direction should consider if it is not wiser to disable all Javascript instead. We have two modes of operation, without JS and with. That's what can be supported, not some freak of nature in between state that this would create.

For instance. I'm in the process of removing the jquery UI dialog popup that we have on thumbnail videos, with oojs ui dialogs. By doing this you would have autoplaying but invisible videos after you click them at some point in the future. And though I am now warned, there is no way in hell that I will take this into account when creating my patches. —TheDJ (talk • contribs) 13:49, 22 May 2016 (UTC)

This is really bad advice. It will hide every OOjs UI dialog, on every page, in every tool. And then developers will have to field bug reports from people who thoughtlessly copy and paste this. Matma Rex talk 14:18, 22 May 2016 (UTC)

I wrote the following in my global .js and it seems to be working:

if (mw.user.options.get('visualeditor-hidebetawelcome') === 0)
	{ var VEBapi = new mw.Api();
	  VEBapi.post({
		'action': 'options',
		'token': mw.user.tokens.get('editToken'),
		'change': 'visualeditor-hidebetawelcome=1'
	  });
	}

BethNaught (talk) 15:16, 22 May 2016 (UTC)

Much better advise, though

1. You are not declaring your dependencies (mediawiki.api and user.options), by wrapping with mw.loader.using
2. You are not using postWithToken(), which does automatic token retrieval and token retry (in case it expired)
3. You are using editToken, but this has since been replaced with the 'csrf' token
4. You change the preference, but not the local state

And because of all that complexity, we have a wrapper module named 'mediawiki.api.options'

mw.loader.using( , function () {
	if (mw.user.options.get('visualeditor-hidebetawelcome') === 0) {
		new mw.Api().saveOption('visualeditor-hidebetawelcome', '1');
		mw.user.options.set('visualeditor-hidebetawelcome', '1');
	}
} );

—TheDJ (talk • contribs) 16:11, 22 May 2016 (UTC)

I have a couple of problems with this message, some of which I admit are repeats:

1. I don't see a use for it
2. If WMF wants to communicate with me, shouldn't they do it whether I have Javascript enabled or not? Even if there is a Visual Editor that requires Javascript and I have it disabled, shouldn't they tell me about it anyway?
3. If the WMF wants to communicate with me, why don't they leave me a talk page message like everybody else? Why have multiple methods of communication to maintain and debug?
4. If the WMF is going to put up a message box that looks like any standard alert anywhere else on OSes or the web, shouldn't it have a standard X in the upper right corner?

The only thing I can think of more useless than the welcome message would be having a sitenotice warning people about the welcome message. Wnt (talk) 12:16, 23 May 2016 (UTC)

• Adding this to meta User/Global.js works, does anyone know if a meta gadget would be able to provide that (in lieu of having each person have to edit their .js file)? — xaosflux 15:44, 25 May 2016 (UTC)

Gone, but like the cat in the hat, keeps coming back

To all of the above, I was about to say I haven't experienced the popup since I initially encountered them on each wiki. However....I just opened Commons to an image, and the minute I clicked on "Edit", the popup blocked my screen. Nothing really got rid of it until I accidentally clicked on switching to Visual editing. Then I had another popup telling me to click on an icon to get out of Visual editing. Except...there was no icon there. And I don't have noscript on that page. So, I finally shut down the window and came back in, and no popups. If I'm in Visual edit, I don't know what it's supposed to look like.

Get rid of this for everybody. It serves no useful purpose for potential editors. Anyone clicking on the Edit tab already knows they're editing, and they don't need a popup to input a separate step. So the question is...exactly what purpose does it serve? If one encounters popups on the internet, they're most likely tracking something. Is that the underlying purpose with this? Editing on Misplaced Pages should not require the user to keep clicking away popups just to edit. Clicking on the "Edit" tab should work. — Maile (talk) 13:18, 23 May 2016 (UTC)

Page last modified footer MediaWiki:Lastmodified

I believe the interface page MediaWiki:Lastmodified (mw:MediaWiki:Lastmodified) is obsolete since MediaWiki 1.8 and should be deleted. The current phrasing of MediaWiki:Lastmodified does not match the footer text that appears on articles (missing the word "on") and I believe the current footer text is the default text from MediaWiki:Lastmodifiedat (mw:MediaWiki:Lastmodifiedat).

If it's unused, I intend to delete MediaWiki:Lastmodified to prevent confusion over the interface. Rather than being bold in this case, I wanted to ask people more familiar with the Mediawiki side of things if there's any reason it should still exist.

Just for completeness, there's also MediaWiki:Lastmodifiedatby (mw:MediaWiki:Lastmodifiedatby) and the obsolete since MW 1.8 MediaWiki:Lastmodifiedby (mw:MediaWiki:Lastmodifiedby). There also an unrelated mw:Extension:LastModified. Jason Quinn (talk) 19:36, 26 May 2016 (UTC)

@Jason Quinn: I checked over on test2wiki, the last modified displays with out it, and even putting nonsense in that field does not replace the footer. — xaosflux 19:54, 26 May 2016 (UTC)

Interestingly, a long deleted version on test2wiki has a fundraising commercial in it! — xaosflux 19:57, 26 May 2016 (UTC)

MediaWiki:Lastmodified is indeed unused and not listed at Special:AllMessages. https://en.wikipedia.org/Example?uselang=qqx confirms that MediaWiki:Lastmodifiedat is used. PrimeHunter (talk) 21:01, 26 May 2016 (UTC)

I deleted the page as non-controversial technical cleanup, leaving the talk page with an explaination and a link to this discussion. Marking as resolved. Jason Quinn (talk) 17:13, 27 May 2016 (UTC)

Warning message when moving to a salted title?

Am I losing it, or did there used to be a warning message appear when you tried to move a page to a salted title (similar to the message you get when you try to move a page to a title that already exists)? I've just tested at User:Jenks24/Test and User:Jenks24/Test2 and I didn't get any warning, the moves just went through straight away. If this was just a figment of my imagination, would it be at all possible to implement some sort warning message? As someone who often does a lot of page moves, I generally don't check each and every redlink title to see if they're salted. Jenks24 (talk) 21:17, 26 May 2016 (UTC)

This would be super helpful, especially with the advent of the extended-mover right. Writ Keeper ⚇♔ 21:34, 26 May 2016 (UTC)

Page movers will get an error that they can not move a page to a page that is protected against creation "You do not have permission to move this page, for the following reason: You cannot move a page to this location because the new title has been protected from creation.". — xaosflux 03:19, 27 May 2016 (UTC)

Normally, yes, but in this case, Casliber originally placed the salt with "extended-confirmed" protection, rather than full-protection; this would've still allowed users, including extended movers, to move the page. The point I was making about extended mover specifically is more that, if such a thing were to happen again to someone with the extended-mover bit, and if people were to get angry about it, it'd be a rather unfair source of ammunition for the removal of said bit. Writ Keeper ⚇♔ 03:37, 27 May 2016 (UTC)

Which page are we talking about here? Cas Liber (talk · contribs) 04:08, 27 May 2016 (UTC)

The Battle of Fashion. Writ Keeper ⚇♔ 06:52, 27 May 2016 (UTC)

@Xaosflux: Yes, I'm talking about when the person making the move does have permission to move over a protected page (e.g. an admin over full protection, or in this case a page mover over extended confirmed). Would it be possible to create a warning message for these situations? Jenks24 (talk) 13:42, 27 May 2016 (UTC)

Anything should be possible :D It doesn't looks like we can do this locally, would require a software patch, so you will need to fill a phabricator request; if doing so suggest it includes multiple checks: (a)Move target was previously deleted (b)Move target has any type of create protection (c)Move target is on the title blacklist . — xaosflux 13:49, 27 May 2016 (UTC)

phab:T85393 is related. — JJMC89 (T·C) 00:23, 28 May 2016 (UTC)

Highlight of "updated since my last visit"

In page histories the phrase "updated since my last visit" is now highlighted, annoyingly, in a bright green background. Is this just me? Is it intentional? If so, was this ever discussed here? If so, how to turn this off in my personal CSS? ―Mandruss ☎ 21:28, 26 May 2016 (UTC)

I tried what seemed like the logical CSS thing and it caused a style flash and then the bright green comes back aaaaaaaah make it stop before my retinas burn off. Opabinia regalis (talk) 22:14, 26 May 2016 (UTC)

+1 - Why the bloody hell make it bright green ? ... It sure as shit gets your attention and quite frankly I'd rather it didn't. –Davey2010 22:23, 26 May 2016 (UTC)

Mandruss and Davey2010, this has existed for a while now. I've been receiving this notification/phrase when I get beaten to a revert, more often than not. It's not new - the colour may have changed, perhaps, but then I can't see certain shades due to my eyesight. Do let me know if that is the case here! Regards --PatientZero 16:41, 27 May 2016 (UTC)

It was only the text colour that was green never the background (which is the case now), Cheers, –Davey2010 17:35, 27 May 2016 (UTC)

The problem was the bright green background, which has now been corrected (see below). It existed for well under 24 hours, so you may have missed it. ―Mandruss ☎ 16:45, 27 May 2016 (UTC)

Thanks for the pointer Mandruss and for explaining that you were indeed talking about the colours. I think I did miss it, thankfully. --PatientZero 16:49, 27 May 2016 (UTC)

The styling of updatedmarker was changed at phab:T134515. I think it looks horrible. MediaWiki:Common.css already says:

.updatedmarker {
    background-color: transparent;
    color: #006400;
}

It appears we now need !important to override the default. I suggest we add that:

span.updatedmarker {
    background-color: transparent;
    color: #006400;
}

This also works in your CSS. PrimeHunter (talk) 22:30, 26 May 2016 (UTC)

The obvious design here is to eliminate those messages and draw a horizontal line above which all edits are "new". Not obvious to those who control the design, apparently, so I'll settle for a return to something at least less intrusive. ―Mandruss ☎ 22:41, 26 May 2016 (UTC)

No important needed (it hardly ever is), just use the same selector. —TheDJ (talk • contribs) 23:06, 26 May 2016 (UTC)

@Mandruss: You can put this in your common.js to do that (unfortunately :last-of-type does not work on classes so it cannot be done with CSS):

$('.mw-history-line-updated').last().append('<hr />');
$('.updatedmarker').hide();

– nyuszika7h (talk) 14:47, 31 May 2016 (UTC)

Thanks for the thought. I'm just as interested in the community benefit as in my own. And the more we customize our own individual wiki-worlds, the less effectively we can communicate, help one another, and make collective decisions as to the user interface. I believe in minimizing personal customization (especially that not supported in Preferences) and implementing good design site-wide. ―Mandruss ☎ 15:07, 31 May 2016 (UTC)

Green "Highlighter" spewing across edit history unread sections. Why?

This changed during my night, and now when I look at a page's edit history, all I can see is bright pukey green highlighter where there used to be a soothing green emphasis in text colour only. This is not an improvement to the project. I've messed around in my preferences, but I have no idea how to turn it back, and thus reduce my migraine. Any ideas? -Roxy the dog™ woof 07:41, 27 May 2016 (UTC)

You're not the only one. The same thing happened to me last night already, and this morning I have more problems - including search box not working and javascript problems on Wikidata. A mouse must have gotten into the works! Oh, and I've just noticed other script errors under the edit box here. Either it's a Wikimedia problem, or our browsers I guess (I predict the former)! Jared Preston (talk) 07:50, 27 May 2016 (UTC)

Thanks to RedRose for moving my query to the correct place. Note to self - "read the page first." Unfortunately, the solutions proposed above are written in gobbledegook, a language I don't speak. When the scriptkiddies above have a solution, could they please explain it in english here, preferably highlighted in green? Thanks. -Roxy the dog™ woof 09:07, 27 May 2016 (UTC)

@Roxy the dog: I can put in a CSS rule for you, but I need to know which skin you use - at Preferences → Appearance, in the first large box, which of the four is currently selected? --Redrose64 (talk) 09:39, 27 May 2016 (UTC)

Vector. I have no custom CSS. and Thanks. -Roxy the dog™ woof 09:45, 27 May 2016 (UTC)

I created User:Roxy the dog/vector.css, you may need to WP:BYPASS your cache to see a difference. --Redrose64 (talk) 10:28, 27 May 2016 (UTC)

I have updated MediaWiki:Common.css with .span. This returns the former behaviour for me. PrimeHunter (talk) 10:31, 27 May 2016 (UTC)

My eyes are grateful. -Roxy the dog™ woof 11:02, 27 May 2016 (UTC)

PrimeHunter - I bloody love you!! - Thank you! –Davey2010 17:35, 27 May 2016 (UTC)

I'm used to seeing different styles, since most of the large wikis have different colors. I do miss the green dots from enwiki when I'm elsewhere. But I want something that doesn't exist anywhere: a little button that always gives me the diff of all the changes since my last visit, without needing to scroll down and find the (cur) to click on. In fact, if visiting any page would automagically first check whether the page is on my watchlist and, if so, show me any changes since my last visit, that would be ideal. WhatamIdoing (talk) 16:36, 27 May 2016 (UTC)

Rollback function has been changed

This section in a nutshell: This issue should now be resolved. If you are having new issues please comment below. Opening rollback links in a new tab or page now requires additional confirmation. Just click the links where they are and the rollback will happen without changing the page. This is a suspected breaking change to portions of script utilities such as Twinkle, Stiki, and LAVT. A developer has processed the reversion request and production updates are scheduled by 2016-05-28.

I've started experiencing a new behavior when using rollback (on one Win XP computer + newest Firefox, I'll check newer Windows platforms later). The most annoying one is that "blind" rollback (rollback without viewing the diff) now requires confirmation - an extra page pops up asking 'do you want to revert this edit' OK? Does anyone know where this implementation was discussed and how to bypass this feature? I've lost a quick rollback function for dealing with obvious vandals. Materialscientist (talk) 22:21, 26 May 2016 (UTC)

I'm on the other side of that fence. I found it annoying when a stray click rolled back stuff I didn't intend to roll back. I gave up the rollback right after about the fourth time that happened to me. It's simply poor design to do something like that without a confirmation click, which only takes another second or two. But I don't know whether it was discussed. ―Mandruss ☎ 22:29, 26 May 2016 (UTC)

I'm with Materialscientist, it's also screwed up Twinkle's automatic completion of the linked article field when warning users. I've just returned to anti-vandal work after a short break, and don't feel inclined to continue unless I can do so efficiently.  —SMALLJIM  22:44, 26 May 2016 (UTC)

See phab:T49782 about that. Helder 16:03, 27 May 2016 (UTC)

I just rolled back two edits on this page - neither required a confirmation. — xaosflux 22:57, 26 May 2016 (UTC)

Also with my testing account using all defaults - I do get the little spinning circle and the upper right corner has a popout confirmation box, but I am not getting a confirmation prompt at all. Xaosflux ep (talk) 22:59, 26 May 2016 (UTC)

Can you verify you are actually using rollback? (Hover the link and ensure it has &action=rollback). What is the exact text of the message you are getting? — xaosflux 23:01, 26 May 2016 (UTC)

I'm thinking the enhanced "rollback" with WP:Twinkle is what you are seeing broken - I'm having a problem with it as well. — xaosflux 23:04, 26 May 2016 (UTC)

This was intentionally changed due to phab:T88044. —TheDJ (talk • contribs) 23:09, 26 May 2016 (UTC)

(edit conflict)Something has changed, but I did not get a confirmation dialog when I just now rolled back. There was a (JQuery?) box that briefly appeared in the top right corner indicating that that the roll back was successful.- MrX 23:11, 26 May 2016 (UTC)

Let me rephrase my original comment. If I preview the diff (of the edit I want to revert) then rollback doesn't ask to confirm it. If I try revert without seeing the diff then I'm asked to confirm it. I want to avoid this confirmation dialogue. I also want to see what I've rolled, particularly when rolling multiple edits (now I don't see it). I do not use Twinkle, just plain rollback. Materialscientist (talk) 23:16, 26 May 2016 (UTC)

I used the rollback link from history with no confirmation dialog appearing.- MrX 23:25, 26 May 2016 (UTC)

I used rollback from RecentChanges - no confirmation either - @Materialscientist: Can you copy the url you are using (copy before clicking) and paste here? — xaosflux 23:29, 26 May 2016 (UTC)

• OK, reproduced the problem: If using standard rollback, in a new tab/window it is no longer instantly working-ending in a confirmation. If you just click the links they process in-page now, instead of going to a new page. — xaosflux 23:36, 26 May 2016 (UTC)

• Should we be able to have our cake and eat it too? (Basically just remove the Revert edits to this page? prompt?) — xaosflux 23:41, 26 May 2016 (UTC)

  @Krinkle: - any hints? — xaosflux 23:44, 26 May 2016 (UTC)

  (ec) Xaosflux is absolutely correct in that the confirmation dialogue appears only when I open the rollback in a new tab, which I always do, as I want to keep the starting page (be it my pre-designed watchlist or recent changes log). It doesn't appear if I roll in the same tab, but then I (1) don't see what I've rolled, and (2) can't revert several edits from the same user/IP. Annoying. Materialscientist (talk) 23:47, 26 May 2016 (UTC)

• WP:LAVT seems broken for me. I also don't like that I click rollback, and the page refreshes suggesting that I haven't rolled back when I indeed have. (it still says "Rollback 2 edits") — Andy W. (talk · ctb) 23:53, 26 May 2016 (UTC)

  Admin rollback is definitely broken for Lupin's Anti-vandal tool. (Non-admin javascript is okay) The HTML that gets returned seems different, and the tool thinks that someone else has edited since the vandalism event. — Andy W. (talk · ctb) 00:00, 27 May 2016 (UTC)

• I've created phab:T136375 asking for a roll back - not sure if that will happen - please feel free to subscribe. — xaosflux 00:12, 27 May 2016 (UTC)

• WP:Stiki was broken with me too (since two hours ago). I've confirmed that my regular rollback issues are independent of the PC platform (WinXP, Win10) and Misplaced Pages skin (MonoBook, Vector). Materialscientist (talk) 00:16, 27 May 2016 (UTC)

• Added watchlist notice. — xaosflux 00:27, 27 May 2016 (UTC)

• The problem with Twinkle hasn't happened to me, even though I use Twinkle all the time. One somewhat annoying Twinkle-related thing I have experienced is that if you revert an edit by clicking on "Rollback AGF", it opens the user whose edit you're reverting's talk page and the Twinkle menu's warn option. However, this really isn't an issue for me since typically it's in everyone's best interest not to WP:BITE good-faith newcomers who make honest mistakes, and instead it is better to explain what they did wrong. However, I am unclear on whether this thread is for discussing a Twinkle error or, as Materialscientist's comment above would suggest, a WP:ROLLBACK error. Everymorning (talk) 00:38, 27 May 2016 (UTC)

  We think the unexpected Twinkle behavior is tied to this change. — xaosflux 00:41, 27 May 2016 (UTC)

• Please see my comments posted at WP:ANI at Misplaced Pages:Administrators' noticeboard/Incidents#Malfunction_with_automated_rollback. This recent change has effectively broken rollback while using Lupin's Anti-vandal tool and is producing inaccurate results when clicking (rollback) directly from the page history as well. Oftentimes it will incorrectly state that "rollback failed" when in fact it succeeded, and in other cases it fails to rollback entirely, on what appears to be a completely inconsistent basis. Is there an option in preferences which would allow us to revert back to the original rollback features before this change was implemented? Regards, Yamaguchi先生 (talk) 00:42, 27 May 2016 (UTC)

• Same problem using OSX Safari or Chrome. --Cameron₁₁₅₉₈ 00:50, 27 May 2016 (UTC)

• It's only saying that rollback failed if you're clicking the link multiple times before it has the time to process it (at least, that's what I've found from some limited testing). Same thing if you open the rollback link in a new tab 50 times; it will say that it has failed for the 49 times after the initial processing of the action. Obviously this change should have been better communicated to the maintainers of the anti-vandalism scripts, so they could update them before the change. There is no way of changing back on a per-person basis. Ajraddatz (talk) 00:51, 27 May 2016 (UTC)

  No, we are not sharing the same experience in that case. I am seeing failures based upon a single click on an intermittent basis. A window box temporarily appears in the upper right hand corner of my screen notifying that rollback has failed, while a check of the page history reveals that the rollback actually succeeded. Regards, Yamaguchi先生 (talk) 01:04, 27 May 2016 (UTC)

Oh, this sounds familiar — it wasn't with rollback, but I noticed one of those "blah blah has failed blah blah" popups when doing something or other, even though it was still working on whatever it was (the popup went away once the action finished)... Idk if that's related though. Goldenshimmer (talk) 01:45, 27 May 2016 (UTC)

• Any Idea if this is effecting Huggle too? --Cameron₁₁₅₉₈ 00:53, 27 May 2016 (UTC)

  I just fired up Huggle and made a revert OK. — xaosflux 01:01, 27 May 2016 (UTC)

• Additional error As a test, I used rollback on the latest Sandbox edit, opening it in a new tab; it asked if I wanted to use rollback, and when I clicked yes, it went through properly. I then clicked rollback (no new screen) on my own edit, and again it went through properly. I then clicked rollback on my second edit (the result should have been the removal of the text in question), and I get a failure message:

  Rollback failed Cannot roll back edit to Misplaced Pages:Sandbox by Nyttend (talk · block · contribs) because someone else has edited the page. The last revision was by Nyttend (talk · contribs).

  When I open it in a new tab, it produces the confirmation page properly, but okaying the action produces the same error message. As of 01:00, 27 May 2016 (UTC), nobody has edited the page since my latest edit; it's not like an intervening edit got in the way. This is distinctly not good: the software's thinking that I've tried to roll back my first edit to the page, not my latest. Rollback should always attempt to revert the latest edit, doing any consecutive previous ones along the way, but here it's trying to do something different. Nyttend (talk) 01:00, 27 May 2016 (UTC)

  PS, the sandbox-maintenance bot just removed stuff, so I rolled it back, rolled back my rollback, and attempted to rollback my rollback rollbacking, but once again, the third edit failed. I understand that self-reverting twice is an exceptionally rare situation, but that doesn't mean that we should ignore the tool's misanalysis of what link was clicked. Nyttend (talk) 01:02, 27 May 2016 (UTC)

  @Nyttend: It's behaving as I would expect.

  • Your first rollback reverts all consecutive edits made by the most recent editor (Epizode), producing revision 722273317 of 00:54, 27 May 2016, identical to revision 722270423 of 00:31, 27 May 2016 by Everymorning;
  • your second rollback reverts all consecutive edits made by the most recent editor (Nyttend), producing revision 722273325 of 00:55, 27 May 2016, identical to revision 722271034 of 00:36, 27 May 2016 by Epizode;
  • your third attempt to rollback reverts all consecutive edits made by the most recent editor (Nyttend). This would produce a version identical to revision 722271034 of 00:36, 27 May 2016 by Epizode but as noted, that is identical to revision 722273325 of 00:55, 27 May 2016 by Nyttend, which is the current version; so since it's a no-change edit, you get the "Rollback failed" error message.

  It has worked like that since I was given WP:ROLLBACK in June 2010. Rollback doesn't toggle between versions, it reverts to the most recent version that was made by any person who is not the most recent editor. --Redrose64 (talk) 07:10, 27 May 2016 (UTC)

Ok, this is kind of off topic, but I'm wondering, what exactly is the big deal over having rollback? Can't you do the same thing with a couple extra clicks by going to the page revision right before the offending editor, clicking "edit", and clicking "save"? This has puzzled me for a while. Goldenshimmer (talk) 01:43, 27 May 2016 (UTC)

Replied on your talk. — xaosflux 01:47, 27 May 2016 (UTC)

• Not sure if I really like this change. At the very least, there should be an option in Special:Preferences to revert it. Now I have to go through additional clicks in order to get to the user's talk page and be able to warn them with Twinkle with the "linked page" field automatcially filled in. I can at least confirm the option to leave a custom edit summary with a rollback as described at Misplaced Pages:Rollback#Additional_tools still works. —k6ka 🍁 (Talk · Contributions) 02:35, 27 May 2016 (UTC)

There's an incongruency with this change and the user's settings. At Preferences -> Browsing, I have "After rolling back a user's edit, automatically open their contributions page" enabled. Enabling this gives a rollback failed message which may or may not be correct (it seems non-deterministic).

After I disable "After rolling back a user's edit, automatically open their contributions page", rollback indeed asks for a confirmation. — Andy W. (talk · ctb) 03:33, 27 May 2016 (UTC)

That would be mw:MediaWiki:Gadget-modrollback.js. Helder 16:57, 27 May 2016 (UTC)

• This change has absolutely neutered massRollback, which now requires me to go through each rollback page that pops up and individually confirm that I mean to roll it back. This makes it much more time-consuming to keep track of and revert the few prolific sockpuppeteers that I would consider myself an expert on identifying. What problem was trying to be fixed when this was implemented? This seems to have created more issues than it solved. ~ Rob 04:31, 27 May 2016 (UTC)

Apparently the problem was the use of GET where the software should use POST. Helder 16:57, 27 May 2016 (UTC)

We've elevated this to a talk page notice? At minimum, we should have a temporary roll back the change so developers like myself (STiki) have time to accommodate the change. Why are we breaking legacy functionality? "Because it would be nice..." for HTTP POST/GET semantics to be normalized? This is much more understandable for security issues, but script/tool editors should have gotten some lead time on this one. What trouble does a temporary withdrawal cause? West.andrew.g (talk) 04:35, 27 May 2016 (UTC)

• I can see no benefit in the new design. It now requires a lot of extra work when mass-reverting changes made by a single user. . . Mean as custard (talk) 08:30, 27 May 2016 (UTC)
• It's as if Preferences → Appearance → Don't show diff after performing a rollback is permanently enabled. You can still get to the diff showing the rollback that you made, it's in the little box that appears at upper right, but it's an extra click following a (potentially large) mouse move to that box, which you might not complete before it fades. --Redrose64 (talk) 08:36, 27 May 2016 (UTC)
• Please could someone explain to me, preferably in words of one syllable: (a) when and where script developers were notified that this change was happening; and (b) how it affects scripts that do rollback using AJAX, by querying the rollback token and then POSTing it. Thanks. Philip Trueman (talk) 11:08, 27 May 2016 (UTC)

  (a) This was added to the Tech News. Helder 16:57, 27 May 2016 (UTC)

  • Granted. But this says nothing about scripts that do rollback via AJAX. No window is opened. Philip Trueman (talk) 18:37, 27 May 2016 (UTC)
• WTF is this? Change rollback back. Was there even any community discussion or consultation before this change was made? Absolutely textbook case of a solution looking for a problem, and not only are anti-vandal tools like STiki now broken, the "warn" function of Twinkle is dead as well since the "linked article" field no longer autocompletes as rollback doesn't open in a new page anymore. This is some VisualEditor level incompetence and whoever instigated this deserves a good WP:TROUTing (and then some). Again, change this shit back. Satellizer el Bridget  11:46, 27 May 2016 (UTC)
• @West.andrew.g: Not sure what you mean by "talk page notice"? I added this to the watchlist notice because I thought it would reach the right audience without being too intrusive to people that don't use rollback. — xaosflux 13:00, 27 May 2016 (UTC)
  • Oops, sorry, I meant watchlist notice. West.andrew.g (talk) 15:01, 27 May 2016 (UTC)
• This is really annoying. The whole point of admin rollback is to be able to do a quick rollback. WTF? --jpgordon 13:27, 27 May 2016 (UTC)

• Comment: I was wondering why Twinkle suddenly stopped working. Is this going to be fixed anytime soon? Why would a change like this take place without discussion and testing? GenQuest 13:42, 27 May 2016 (UTC)

  The place to complain about "why was this done" or "roll this back" is phab:T136375 - if it gets enough noise perhaps the developers will revert. — xaosflux 13:51, 27 May 2016 (UTC)

With respect, Xaosflux, no it isn't. The developers should be monitoring this page on a regular basis especially after any major change is implemented, because it's the first place that reports about such changes are likely to be raised. A pretty obvious way of helping to keep their customers happy, I'd have thought.  —SMALLJIM  14:21, 27 May 2016 (UTC)

@Smalljim: I agree they should be, and I did link this discussion to the phab ticket that I opened asking for a revert. From what I can tell this is change was wide in scope, so reaches far beyond the English Misplaced Pages. I suggested the phab page so it could get more "heat". — xaosflux 14:50, 27 May 2016 (UTC)

As a tool developer I am monitoring this page, and its the first place I come when something breaks. If a mistake is made and something is broken, developers fix it. This is something else entirely. This is a change with seemingly inconsequential benefit that breaks a whole host of tools (CBNG, Lupin, Twinkle, and STiki). I can't imagine how many man-hours are going down the drain, and how much more vandalism is surviving longer than it should. It takes me time to code up a fix, test it, and push a new version. Responsible development finds the tools effected by a change and gives them lead time to make a change (and ideally, doesn't break legacy functionality without a darn good reason). Look to the recent "authentication manager" changes for a good example on how this is done. I haven't seen any mention made of harm incurred for a short term withdrawal of the change. West.andrew.g (talk) 15:01, 27 May 2016 (UTC)

Yes, thanks for your efforts over this, Xaosflux. The apparent lack of any awareness (here and at phab) by the devs of the mess that this has caused is disappointing. I should think it's something their managers could usefully look into correcting - these are paid staff, aren't they?  —SMALLJIM  15:10, 27 May 2016 (UTC)

At the risk of looking like I'm just piling on here, I'd like to add my voice to those saying that these recent changes are entirely detrimental to the use of rollback (at least the way I use it). Reverting vandalism and other unconstructive edits is simply more difficult and time consuming now. Some of the problems I now encounter include: 1) Repeatedly being asked to confirm each rollback when rolling back multiple edits by one user, 2) after using rollback Twinkle no longer opens a user talk page with the "linked page" field automatically filled in, and 3) inaccurate "rollback failed" messages. Deli nk (talk) 14:00, 27 May 2016 (UTC)

And to add to the cheer, Cluebot NG seems to have been AWOL since yesterday evening. Now, I wonder how that could be? Philip Trueman (talk) 14:02, 27 May 2016 (UTC)

I'll add an issue I've observed: when rolling back with the option that allows one to enter an edit summary, which I almost always use, my summary text is not saved. DonIago (talk) 14:03, 27 May 2016 (UTC)

• As Materialscientist said, normal rollback displays a loading gif, opening in a new tab needs confirmation. What pisses me off is that after the rollback is complete, it does not reload the page (previously it led to a new page with affirmation). Yet to see the behaviour with multiple edits. Nice to know the devs give zero fucks about the tons of scripts and users who were about to be affected by this. --QEDK (T ☕ C) 15:08, 27 May 2016 (UTC)
  • There is a difference between not giving a fuck and misjudging the impact of a change. —TheDJ (talk • contribs) 15:13, 27 May 2016 (UTC)
    • Whatever you say. Just rubs me a bit on the wrong side when all we try to is help the project and then we take a step back. Not a big deal, guess I should be more calm. --QEDK (T ☕ C) 15:21, 27 May 2016 (UTC)
      • Speed is probably the WORST metric there is when it comes to development. 17:53, 27 May 2016 (UTC) — Preceding unsigned comment added by TheDJ (talk • contribs)
        • Back when I was a programmer in IBM, it was impressed upon us that "timeliness is part of quality". More seriously, I agree with you on the general point, but here we are discussing the particular point of the speed with which the developers admit their mistakes. By my standards, they are not doing well. Philip Trueman (talk) 18:29, 27 May 2016 (UTC)
    • I can't defend QEDK's language, but we won't be able to tell which of the two it is until we see how quickly the developers fix things. Philip Trueman (talk) 15:27, 27 May 2016 (UTC)

Argh, same for Huggle actually. I can't revert on Huggle - at first I thought it might be down to my name change and HG not recognising my new name but nope, just saw this. I am therefore outlining that this has happened on Huggle too. Regards --PatientZero 15:13, 27 May 2016 (UTC)

@Patient Zero: Huggle is working just fine for me. —MRD2014 (formerly Qpalzmmzlapq) T C 17:10, 27 May 2016 (UTC)

MRD2014 - I'll try again now. You changed your name too, didn't you? I was Chesnaught555. --PatientZero 17:21, 27 May 2016 (UTC)

As noticed above, a developer is on this, and nothing should be broken anymore very soon. Thanks for your patience. --Elitre (WMF) (talk) 15:51, 27 May 2016 (UTC)

Thank you Elitre (WMF). --PatientZero 15:54, 27 May 2016 (UTC)

Why are WMF ruining everything on this site ? ... As if VE, Flow and the green-background update thing isn't bad enough They now mess around with (and ruin) Rollback ...., WOuld be nice if they actually left things alone ......., 'Don't fix what isn't broken springs to mind. –Davey2010 16:56, 27 May 2016 (UTC)

I agree Davey2010. Rollback was working fine until all this happened. --PatientZero 17:22, 27 May 2016 (UTC)

Good to hear that everyone knows best about things they don't know jack about. —TheDJ (talk • contribs) 17:53, 27 May 2016 (UTC)

I've never said I know best and I'll admit I don't know best inregards to rollback however when you fuck around with a tool that's used by a lot of people on a daily basis and don't bother saying anything then you should know shit's going to hit the fan - As I said above if you don't fix what isn't broken then there's not going to be a problem, Everything gets updated and improved that's life but this wasn't an improvement ... it was an inconvenience as demonstrated in this tread alone. –Davey2010 13:56, 28 May 2016 (UTC)

Huggle now works for me, by the way. That's that sorted. --PatientZero 17:24, 27 May 2016 (UTC)

• Rollback works for me, but I don't like the new way it works. Before it would rollback the edit(s) and show me a new page with the edits removed, similar to an undo. Now, I get one of those little bubbles in the upper right-hand corner of the screen saying the rollback was successful, but it stays on the page, making me feel like it didn't work. I don't mind the bubble (they're now all over the place, e.g., "edit saved"), but I'd like to see the "proof" without going to history.--Bbb23 (talk) 18:35, 27 May 2016 (UTC)

• Somehow I don't think it has affected me. Whether I click on the rollback button on the same tab or opened a new tab with rollback, I get the same result (action complete with diff). Is this only a problem for Twinkle / Huggle / other similar scripts that piggyback on rollback for editors that have the rollback button? (But if you have Twinkle why do you need rollback so desperately? Just handle it at software level!) Deryck C. 22:18, 27 May 2016 (UTC)

@Deryck Chan: The changes were reversed (albeit temporarily) when you tested it out. —k6ka 🍁 (Talk · Contributions) 22:30, 27 May 2016 (UTC)

Reversion is queued

A developer has processed the reversion request and it has gone live.

A reversion of the breaking portion of the change is currently queued for updates and should be deployed in a few hours. The new change is not a 100% reversion - so keep an eye out for anything unexpected. — xaosflux 19:15, 27 May 2016 (UTC)

Rollback is back to normal here now – straight to a page showing the diff of my edit so I can confirm I reverted the vandalism that I intended to. Just as it should be. And then on moving to the vandal's user talk page, Twinkle picks up the article title so I can warn without copy-pasting the title. Just as it should be :)  —SMALLJIM  20:15, 27 May 2016 (UTC)

So that works, but ClueBot NG is still down. —MRD2014 (formerly Qpalzmmzlapq) T C 21:12, 27 May 2016 (UTC)

(edit conflict)Rollback looks good. I confirmed that the generic WP:LAVT seems good. User-derived independent versions might still have issues (out of scope). Any confirmation about STiki or ClueBot NG? (I'm a bit worried about the bot) — Andy W. (talk · ctb) 21:15, 27 May 2016 (UTC)

Message left for operator User_talk:ClueBot_Commons#Your_bot_may_need_to_be_restarted - this is something the operator will need to address. — xaosflux 21:24, 27 May 2016 (UTC)

ClueBot NG has been given a restart and should hopefully be back reverting - Rich 22:07, 27 May 2016 (UTC)

• I'm seeing a random "1" at the bottom-left of the diff page after a rollback. Noticed it on the Simple English Misplaced Pages too. —k6ka 🍁 (Talk · Contributions) 22:20, 27 May 2016 (UTC)

  @K6ka: Thanks for the note - looks like that is a bug that got rolled in to the release - I've notified the developer. — xaosflux 22:44, 27 May 2016 (UTC)

• @K6ka: - the spurious "1" problem has been resolved. — xaosflux 23:18, 27 May 2016 (UTC)

I think it's still broken

I use PILT - my own modified version of AVT. One big difference is that PILT does MediaWiki rollback using AJAX rather than by opening a new window. That has stopped working and is still broken. Philip Trueman (talk) 09:50, 28 May 2016 (UTC)

A bit more thorough description than: "broken" is usually helpful. Unfortunately i don't have the rollback permission, so I can't really test this. —TheDJ (talk • contribs) 19:54, 28 May 2016 (UTC)

"Doesn't work"? More seriously, I think there is an onus on the developers to tell the users and script writers precisely what they have changed. Something has changed, and not been reverted, in the way Misplaced Pages responds to a script that queries the rollback token for a diff and then issues an AJAX POST with an option of action=rollback, passing the token. Maybe there's an additional required option now - I don't know. Maybe that action is no longer accepted, in which case they should justify the reduction in functionality. If there's a way for a script to query why such a request was not actioned I should very much like to learn it, but I'm not aware of one. Philip Trueman (talk) 03:25, 29 May 2016 (UTC)

An update: The relevant Phabricator request seems to have been removed by Aklapper. Frankly, I'm not impressed. Please can it be said boldly: This project is suffering from a total disconnect between the developers of the MediaWiki software and the users thereof. I want, very much, for that disconnect to be healed. If it is not, the project is heading for the garbage can. It is disappointing that the developers simply do not seem to care. Philip Trueman (talk) 20:05, 29 May 2016 (UTC)

Developer console allows you to use the debugger to step through any code and to inspect the requests and responses of any XHR (or normal for that matter) request. This might sound a bit snappy, but things change. If you can't debug this code now, then that means that you can't maintain it, which means that it by definition is going to break. If you write code you are a developer, not a user who needs to be told which 'importScript' to change. There is onus on MediaWiki developers to tell fellow developers about deprecations and removals yes, but there is no onus on them to figure out all problems. If you can't inspect a request, when other tools seem to have recovered just fine, then I feel very demotivated to start reading every character that was changed in the php code to figure out what is the reason for the 'breakage'. —TheDJ (talk • contribs) 20:29, 29 May 2016 (UTC)

You make a fair point but I do not completely agree with you. I want to start by saying that in real life I am a professional software developer. I am used to writing code to documented APIs. Often, those APIs are not documented as clearly or completely as I as a developer might wish - DWARF has been a particular challenge, to take a recent example. The plain fact is, the MediaWiki API has changed recently, and I am not aware of any relevant change to the documentation thereof. I have seen indications that the developers are changing things in the area of rollback and AJAX - beyond that, I am ignorant. I very much want to know exactly what it is they have changed (that is still changed), and what they have changed it to. My code uses the API in a way different from that used by Twinkle, AVT, Cluebot NG and the like. So? I don't see that that makes me a second-class user - I want to know what the relevant change is. My code had not changed. I regard the failure of the developers to be more forthcoming as arrogant, high-handed, and worthy of condemnation. I will, as you suggest, apply what tools I can to determine where things have changed, but some constructive input from the developers would be welcome. Philip Trueman (talk) 21:03, 29 May 2016 (UTC)

@Philip Trueman: Hi, could you explain which specific Phabricator request I "removed"? Phabricator tasks cannot be removed, however the associated projects of a task can be changed (if you referred to that). If you have specific questions why I did something, please elaborate and I'm happy to explain. Thanks, --AKlapper (WMF) (talk) 08:40, 30 May 2016 (UTC)

I apologise - I should have said 'closed'. As I understand it, you closed a request where a user (me) had made it clear that the fix seemed not to be complete, yes? Philip Trueman (talk) 08:43, 31 May 2016 (UTC)

@Philip Trueman: Thanks for clarifying. Hmm, the only activity of your Phabricator account seems to be in phab:T136375 which was closed by a developer in phab:T136375#2335144 (though more followup fixes took place after that action). My first activity in that task was removing unrelated projects from that task. Seems like some misunderstanding here. :) --AKlapper (WMF) (talk) 09:56, 31 May 2016 (UTC)

@Philip Trueman: I notice PILT uses the (since 1.24 deprecated) rvtoken parameter of the revisions module. Reading the diffs of the code, I suspect that this deprecated accessor was not converted along with the other tokens and might have broken in this latest changes. I'm verifying with other developers. —TheDJ (talk • contribs) 14:48, 30 May 2016 (UTC)

It appears this is also be reverted, still under (closed task) phab:T136375. — xaosflux 16:57, 30 May 2016 (UTC)

Yes. PILT is working again. Thanks to those who listened. Philip Trueman (talk) 11:09, 1 June 2016 (UTC)

TheDJ: Thanks for this. I need to find the time to fix this, and any other deprecated usages, but it may take a few days. Philip Trueman (talk) 08:43, 31 May 2016 (UTC)

Visual editor breaks reference popups

Hi! Idk if this is a bug or intended behavior, but after making and saving an edit using the visual editor, the popups to show footnote references don't show up any more... is this something wrong with my configuration, or a bug? Thanks! :) Goldenshimmer (talk) 01:37, 27 May 2016 (UTC)

Try doing a reload on the page. After doing a Save VE does not do a full reload of the page and this can mess with some scripts. I think this relates to T53565 and something to do with LivePreview. To work after a save scripts need to listen for some specific hook. I don't really know why they decided not to just reload the page after a save, but then there is a lot I don't understand about VE/parsoid. --Salix alba (talk): 06:41, 27 May 2016 (UTC)

Thanks :) Goldenshimmer (talk) 07:48, 27 May 2016 (UTC)

"What links here" query

I've moved this discussion here from VPR - it seems to be more relevant to this page. Previous discussion is between the lines:

When you check the "what links here" list for a page, you get all the pages which link to it in order of the pages' creation date. Is there any way to add an option button (or perhaps there's a script?) which will display all the linked pages in alphabetical order? Grutness...wha? 09:17, 21 May 2016 (UTC)

Support - would make life so much easier. DuncanHill (talk) 11:05, 25 May 2016 (UTC)

This is more of a WP:VPT issue than VPR; there may already be a script to do this. --Redrose64 (talk) 19:37, 25 May 2016 (UTC)

I'll move this discussion there. Grutness...wha? 01:37, 27 May 2016 (UTC)}}

Grutness, DuncanHill: You can add

if ( mw.config.values.wgCanonicalSpecialPageName === 'Whatlinkshere' ) {
	$( function() {
		'use strict';
		var ul = $( '#mw-whatlinkshere-list' );
		ul.before( '<button id="whatlinksheresort">Sort</button>' );
		$( '#whatlinksheresort' ).click( function() {
			var li = ul.children( 'li' );
			li.detach().sort( function( a, b ) {
				return $( a ).find( 'a' ).first().text().localeCompare( $( b ).find( 'a' ).first().text() );
			} );
			ul.append( li );
		} );
	} );
}

to Special:MyPage/common.js. You can then style the button any way you want at Special:MyPage/common.css. Example:

#whatlinksheresort {
	margin-left: 1em;
}

Nirmos (talk) 12:22, 27 May 2016 (UTC)

Oh, that's excellent! Thank you! Grutness...wha? 12:43, 27 May 2016 (UTC)

Mobile Misplaced Pages is totally broken right now

Using a phone, web Misplaced Pages, no app. In mobile view, you can no longer view notifications, edit pages, or watch pages. It is as if pages are half loaded. Not sure what could be causing this. Section headings are also no longer collapsed, the top left corner menu button doesn't work, and the banner at the bottom of pages which links to the page history isn't displaying properly. There is likely other things. I have only noticed this today. Assuming it will be fixed at some time. —DangerousJXD (talk) 02:02, 27 May 2016 (UTC)

Is anyone still experiencing this problem? Whatamidoing (WMF) (talk) 16:41, 27 May 2016 (UTC)

I saw this yesterday, somewhat later in the day, and it's working okay now on my iPad. Pleasant bonus, today I can switch between Desktop View and Mobile View without (usually) bringing up the app. Better control. Jim.henderson (talk) 22:37, 27 May 2016 (UTC)

The problems I described above appear to have been fixed. —DangerousJXD (talk) 00:18, 28 May 2016 (UTC)

Tags for removal of PROD templates?

I posted this message at Misplaced Pages talk:Tags more than a month ago but have not received a response regarding this. I am perfectly aware that once PROD templates are removed in an article, unless it is a BLPPROD template, the tag should not be re-added. However, in most cases (at least ones that I have seen), there's no indication that an edit removed a PROD template as for whatever reason no edit summary was included. This is particularly the case for newly-created articles which are not appropriate for Misplaced Pages but do not fit into any of the speedy deletion criteria so are instead PRODded, then the PROD tags are removed by the article creator (frequently without an edit summary), and so sometimes these articles end up outstaying their welcome. Would it be possible to add a tag for PROD removal, much like how there's a tag for CSD, AFD, and BLPPROD template removal, if only for tracking purposes? As far as I know, reading through Misplaced Pages talk:Tags' archives, such a tag is supposed to exist but for whatever reason has not been implemented. Narutolovehinata5 02:17, 27 May 2016 (UTC)

Watchlist the pages you PROD, it's that simple. Also NaruSaku 4eva. --QEDK (T ☕ C) 19:23, 27 May 2016 (UTC)

An actual one-click archiver

Archy McArchface () is a script that allows a user to select and archive multiple discussions to another page. Archy McArchface was created to better enable experienced editors to clear out old discussions without having to rely on OneClickArchiver, which functions much awkwardly when used to archive more than one discussion on a given talk page.

Users are encouraged to try it and provide useful feedback. Bugs and other issues can be reported at my talk page. →Σσς. (Sigma) 02:36, 27 May 2016 (UTC)

Preferences

On IE v. 11 using Windows 10, I have lost several of my preferences, nor can I get to any but the first Preferences → User profile page. The other tabs show up as links, however when clicked, nothing happens. Examples of lost preferences are my time/purge link at the top right of the page is gone, I can no longer right click a lead section to edit, none of my edit page prefs are appearing and so on and so on. It's been like this most of the day (that I've noticed). Where have all the flowers gone, long time passing?  OUR Misplaced Pages (not "mine")! Paine  08:36, 27 May 2016 (UTC)

Does the second link of Preferences → Gadgets work for you? --Redrose64 (talk) 08:40, 27 May 2016 (UTC)

Hi, Redrose64! The Preferences → Gadgets second link just takes me to the top page, Preferences → User profile. I've tried logging out and logging back in, logging out, rebooting and logging back in, but nothing thus far has worked.  OUR Misplaced Pages (not "mine")! Paine  09:06, 27 May 2016 (UTC)

I just changed my password, and that didn't help either.  OUR Misplaced Pages (not "mine")! Paine  09:10, 27 May 2016 (UTC)

Preferences aren't only affected - many tools and options based on JavaScript don't function, like NavPopup, tools above/bellow edit field, many sysop's functions (some of which are enabled in Preferences), and many more... I've noticed this in "my nightly shift" on hr-wiki about 4AM CEST. Among IE, also have tried FF and classic view on mobile phone, with the same problem. --Bonč (talk) 09:13, 27 May 2016 (UTC)

I did a Java update today, I think it was 91, so that might be a clue.  OUR Misplaced Pages (not "mine")! Paine  09:16, 27 May 2016 (UTC)

Same problem for me using Pale Moon and Java 8u91 but all seems ok using Chrome on the same PC. Nthep (talk) 09:27, 27 May 2016 (UTC)

Me too. Gadgets and preferences are broken in Pale Moon 26.2.2, but work fine in M$ Edge. —Wasell 09:32, 27 May 2016 (UTC)

I think that there's a general JavaScript problem, see for example DangerousJXD's thread Mobile Misplaced Pages is totally broken right now and Jared Preston's comment at Green "Highlighter" spewing across edit history unread sections. Why? above. --Redrose64 (talk) 09:34, 27 May 2016 (UTC)

It's a global problem, first spotted last night on hr-wiki, but also is true for other wikis (de, sr...). On some other sites (like JS examples on www.w3schools.com/) everything is OK. So, it's seems this problem is a result from new "fixing" in WM software. --Bonč (talk) 09:37, 27 May 2016 (UTC)

I meant "general" as in "affects all use of JavaScript within the Wikimedia sites", i.e. Misplaced Pages, Commons, Meta and so on. --Redrose64 (talk) 09:42, 27 May 2016 (UTC)

Coming to you from Firefox – when I first opened it the v. was 30, and it began to update to v. 46.0.1. At v. 30 the problems persisted; however, at v. 46.0.1 all is well and working properly. Checked Chrome and can confirm that it works as expected.  OUR Misplaced Pages (not "mine")! Paine  10:53, 27 May 2016 (UTC)

Just reported the IE11 incompatibility with Java 8u91 to Microsoft (endash) fingers crossed. OUR Misplaced Pages (not "mine")! Paine  11:15, 27 May 2016 (UTC).

This appears to be tracked in Phab T136387. —Wasell 11:28, 27 May 2016 (UTC)

• Same problems here. Cant even see the "show" link on the collapsed navigation templates. This is crazy. I cant hover over wikilinks and see any of the fancy stuff from where i usually reverted vandals. Twinkle options have also gone i guess.... §§Dharmadhyaksha§§ {Talk / Edits} 12:11, 27 May 2016 (UTC)

And now I can't even log in! (User:Wasell) --151.177.60.175 (talk) 12:27, 27 May 2016 (UTC)

Special:CentralAuth/Wasell currently displays: Exception encountered, of type "Exception". This indicates you are probably hit by the older phab:T119736. PrimeHunter (talk) 12:49, 27 May 2016 (UTC)

testwiki:Special:CentralAuth/Wasell indicates a problem at bewiki. Try if you can log in at be:Special:UserLogin. PrimeHunter (talk) 13:02, 27 May 2016 (UTC)

That worked lovely! Thanks! —Wasell 13:13, 27 May 2016 (UTC)

• This problem is not limited to IE11. I'm running IE10 under Windows 7 (blame my company's IT department!) and having the same problems: can't access other tabs on the Special:Preferences page, and my WP:Twinkle tools are gone. WikiDan61_ReadMe!! 13:23, 27 May 2016 (UTC)

I should think the vandals are having a whale of a time today. CluebotNG has been down for about 18 hours, sTiki, LAVT and Twinkle are not working properly. Here, Twinkle won't even load now on Firefox 24, or IE 11, or Pale Moon 22, or an old version of SRware Iron (a Google Chrome clone). Neither will Popups, or the preferences tabs as noted above. Seems OK on the latest version of Firefox (43.0.1) that I've just loaded onto a laptop. Are we all suddenly expected to only use the latest browser versions? - I have good reasons for not doing so, and of course others don't get the option. This needs fixing! Smallerjim (talk) 13:52, 27 May 2016 (UTC) (aka User:Smalljim)

Problem appears to be fixed now. —Wasell 15:19, 27 May 2016 (UTC)

Partly - things are loading now, but that rollback change is still extant and is still stopping Twinkle from working properly.  —SMALLJIM  15:24, 27 May 2016 (UTC)

This is entirely unrelated to the rollback change. The problematic deployment of CentralNotice changes was reverted. Matma Rex talk 15:37, 27 May 2016 (UTC)

Thanks for forcing this through, Matma Rex. It looks as if we can be hopeful that the change to rollback will be rolled back soon as well. Two separate, erm, unwelcome changes in 24 hours is a record, I think!  —SMALLJIM  15:59, 27 May 2016 (UTC)

I did not "force" anything, I had an obviously broken change reverted ("obviously" as in "syntax errors in JavaScript"). Like I said, that was not related to the rollback thing, and the reverts of them are similarly unrelated. Matma Rex talk 16:03, 27 May 2016 (UTC)

Well, thank you for that, you and all the devs who worked on this to fix things! All is back to normal, and I have no words to tell you how good that is!  OUR Misplaced Pages (not "mine")! Paine  01:26, 28 May 2016 (UTC)

Tool to close RMs

I was wondering if there's a tool to close requested moves (I think no), if there isn't, there's a job for coders with time on their hands. --QEDK (T ☕ C) 15:22, 27 May 2016 (UTC)

There isn't one, as far as I know. And I doubt one will be built to be honest because it will be largely pointless (like the current TFD closer) where it simply adds the templates to substitute in the closing without actually carrying out any of the actions required after the close (this is what makes the AFD script so great). Jenks24 (talk) 13:10, 29 May 2016 (UTC)

Actually, it should be possible to write a script that does most of the things listed in the closing instructions. I don't think we should try and get a script to do history merges or history swaps, but doing the actual page move, fixing any double redirects, updating free use rationales, and updating the category sort keys all sound like good candidates for automation. It wouldn't be the simplest script to write, but there are plenty of more complicated ones on Misplaced Pages already. — Mr. Stradivarius 14:37, 29 May 2016 (UTC)

Problem staying logged in

Hi. I'm on Windows 10, MSIE11, all current updates applied. Set to accept cookies. I log in to Misplaced Pages and select "stay logged in for 30 days", but it only keeps me logged in in that browser window. If I open a link in a new tab or window, it thinks I'm not logged in. If I close the browser Window, it doesn't remember me any more. This problem is new today. Any ideas please? Thanks in advance. --Stfg (talk) 16:26, 27 May 2016 (UTC)

Have you tried allowing cookies for this site specifically, instead of just allowing cookies in general? http://www.technipages.com/wp-content/uploads/2014/07/IE-Per-Site-Cookies.png The Quixotic Potato (talk) 19:44, 27 May 2016 (UTC)

Yes, I've done that for wikipedia.org (and restarted, though I don't think that was necessary). The problem isn't happening on Chrome, only on IE. Another thing that's happening is that the next logged-in session doesn't remember that I've told the watchlist to hide the list of meetups. I strongly suspect that some malware has got in and has arranged for cookies to be deleted at end of session, but I've no idea how to track it down if so. --Stfg (talk) 21:04, 27 May 2016 (UTC)

I don't think it is very likely that malware is deleting your cookies, but you can download the free version of malwarebytes on malwarebytes.org and use it to scan your computer. Also make sure you have a virusscanner that is up to date, and use that to scan your computer too. But I strongly suspect that the problem is something else (but I don't know what). Do you have Norton Internet Security installed? Many people report that NIS can cause this problem. Have you tried to recreate the problem when starting IE with all addons disabled (Win+R to open the Run box, then type iexplore –extoff and click on OK.)? And have you tried clearing the cache and the cookies? The Quixotic Potato (talk) 21:28, 27 May 2016 (UTC)

Surely you've checked that IE is not deleting cookies on exit, haven't you? Tools > Internet options > General. If the box is ticked (checked), untick it. Akld guy (talk) 00:16, 28 May 2016 (UTC)

That wouldn't explain the behaviour the OP described ("If I open a link in a new tab or window, it thinks I'm not logged in.") but it is a good idea to check it. The Quixotic Potato (talk) 00:25, 28 May 2016 (UTC)

He/she also said, "If I close the browser Window, it doesn't remember me any more." which is the classic symptom of ticking the box. Akld guy (talk) 02:33, 28 May 2016 (UTC)

Thanks guys for spending your time on this. I do appreciate it. (I'm a he, by the way.) Yes, I did make sure that box (Delete browsing history on exit) is unchecked. It's certainly worth asking that sort of question, though. It would be silly to miss the solution by being too "polite" to ask if I had done something, however obvious.

I've tried all the things that The Quixotic Potato suggested yesterday. Malwarebytes found a couple of PUPs, which it has deleted, but the problem persists. Running with add-ons disabled didn't change the situation. (I haven't recently acquired any new add-ons, unless something has found a way to hide.) I don't use Norton. My antivirus is Kaspersky Total Security 2016, and its up-to-date. In two full scans yesterday, it didn't see anything amiss. The problem of being forgotten when clicking a link in a new tab or window also occurs in YouTube (but strangely, it does not occur on my Open University login, which does recognise me after a shift-click).

Yesterday morning when I switched on, I noticed some strange behaviour which I tracked down to the FUvirus. I thought that by lunch time I had got rid of it, and no other strange behaviour has been repeated. What I fear may have happened is that the intruder may have managed to plant some code that overrides the setting that Akld guy asked me to check, and deletes cookies anyway. I've had both Kaspersky and malwarebytes scan the IExplore.exe file specifically, and neither sees anything to worry about. What do you think?

Thanks again. --Stfg (talk) 10:35, 28 May 2016 (UTC)

Main page optimisation

Just a quick question, sorry if it's not the right place, but what resolution are we aiming to have the main page optimised for (not the mobile variant, obviously). Thanks. The Rambling Man (talk) 19:58, 27 May 2016 (UTC)

Not the answer you want: all resolutions, see Responsive web design (but ensuring that it looks good on the most commonly used resolutions may be a good idea). The Quixotic Potato (talk) 21:30, 27 May 2016 (UTC)

Except that we don't use responsive web design on the main page. It uses a fixed table layout which doesn't change in any way (except that the mobile view excludes all content other than TFA and ITN, presumably for bandwidth reasons). For some time I've been meaning to propose that we use media queries to allow the featured picture to appear larger for people with large screens, but have never got around to it. — This, that and the other (talk) 06:29, 28 May 2016 (UTC)

The Rambling Man did use the word "aiming". I think almost everyone agrees that the current homepage is far from perfect. If you ever make that proposal, please think about Viewport Sized Typography. The Quixotic Potato (talk) 10:54, 28 May 2016 (UTC)

Actual answer: none. The main page is a dinosaur from web 1.0, where screensizes could only go up and mobile internet was still sience-fiction. I have been trying for three years to get us out of the stone age. -- ] {{talk}} 08:12, 28 May 2016 (UTC)

Pish, we're at least up to the bronze age. I actually kind of miss the stone age version, back when we were more concerned about information density than making things look pretty. —Cryptic 08:59, 28 May 2016 (UTC)

Getting colour to display properly

Having an issue with the King's Park F.C. and it's one that has baffled me for several years. On the infobox why do the sleeves on the kit display as blue and white rather than claret and white? From what I can see the colour codes (don't know the proper name, sorry) are the same and yet they display differently.I'm sure it's something simple but this sort of thing is beyond me so if some nice person could fix it I would be grateful. As ever, apologies in advance if this is the wrong place but there are so many helpdesk type things on here now that I never know which is which any more! Keresaspa (talk) 00:44, 28 May 2016 (UTC)

The problem is in nested template {{Football kit}} - using _whitestripes breaks it - checking further. — xaosflux 01:34, 28 May 2016 (UTC)

Oh, well, looks like you found it just as I was looking into it. Fixed. -- The Voidwalker 01:41, 28 May 2016 (UTC)

(edit conflict) @Keresaspa: the "pattern" actually a complete picture File:Kit left arm whitestripes.png, that is replacing the underlying color. You would need to make a new pattern and upload it. For additional help on that see Template talk:Football kit. (Looks like The Voidwalker already took care of it.) — xaosflux 01:43, 28 May 2016 (UTC)

Thanks folks, looks great now :) Keresaspa (talk) 01:46, 28 May 2016 (UTC)

Permanently use Desktop version on a phone or tablet

A reader contacted Wikimedia (ticket:2016052610025225), desiring to turn off the mobile mode permanently.

According to Misplaced Pages:Village_pump_(technical)/Archive_136#How_to_disable_mobile_interface.3F, if they have cookies enabled and click on the desktop mode it should be permanent. However, they claim this is not so, or if so then the cookies must be expiring quickly because the reader has to re-enable the desktop option every couple of days.

Can we provide any advice?--S Philbrick(Talk) 13:08, 28 May 2016 (UTC)

It's not permanent but these cookies last for 30 days (as mandated by wmf:Privacy policy). User must have cookies enabled, and prefferrably JS too. Max Semenik (talk) 00:53, 29 May 2016 (UTC)

If they are using a browser, they may be able to workaround by changing their load page to this. — xaosflux 02:09, 29 May 2016 (UTC)

I know this is then just for logged-in users, but can it be made permanently through a user-.css or .js (or a gadget or preference)? --Dirk Beetstra 05:06, 29 May 2016 (UTC)

Sphilbrick, Beetstra: You can add

location.host = location.host.replace( 'm.', '' );

to Special:MyPage/minerva.js. Nirmos (talk) 09:11, 29 May 2016 (UTC)

@Nirmos: Nope, that results in a constant refresh of the page (at least in the non-mobile). --Dirk Beetstra 10:33, 29 May 2016 (UTC)

Beetstra: You added it to Special:MyPage/common.js. It needs to be in Special:MyPage/minerva.js. Nirmos (talk) 10:54, 29 May 2016 (UTC)

Ah, thanks .. have to start keeping track of the different .js-s. At the moment it is not clear what .js does what and when (I thought this was skin-dependent ..). --Dirk Beetstra 10:58, 29 May 2016 (UTC)

@Nirmos: that had the same effect on mobile than what I earlier saw on a regular site: continuous refresh of the mobile site. --Dirk Beetstra 15:52, 29 May 2016 (UTC)

Beetstra: Does it work better if you make the assignment conditional?

if ( location.host.includes( 'm.' ) ) {
	location.host = location.host.replace( 'm.', '' );
}

Nirmos (talk) 19:08, 29 May 2016 (UTC)

I'm afraid that doesn't work. As long as the desktop page redirects to the mobile site, you will get stuck in a loop. -- ] {{talk}} 19:21, 29 May 2016 (UTC)

Redirect not listed in NewPages

The redirect We Are the Luniz is not shown in the list of redirects created by MBisanz and the recreation of the deleted page is not shown in Special:RecentChangesLinked/Wikipedia:Articles for deletion/We Are the Luniz. GeoffreyT2000 (talk) 17:16, 28 May 2016 (UTC)

Rollback past SineBot?

One minor annoyance I've encountered when using rollback (both Twinkle and the tool) is that when the editor being rolled back does not sign their initial post, SineBot will usually sign it for them. This cases a break in the string of edits and rollback only goes back to SineBot's edit. Is there a way we could have rollbacks ignore SineBot and include them in the rollback? A similar issue occurs when references are rescued by AnomieBOT. See the edit history on Talk:Racism from May 28 for an example of what I'm referring to. EvergreenFir (talk) Please {{re}} 18:34, 28 May 2016 (UTC)

Twinkle has a button to restore a particular revision. →Σσς. (Sigma) 19:01, 28 May 2016 (UTC)

@Σ: I do use that when I realize there's an intervening edit. Problem is when I don't. Takes more time too (on my slow ass laptop with 40+ tabs open and whatnot). EvergreenFir (talk) Please {{re}} 04:41, 29 May 2016 (UTC)

True WP:ROLLBACK (as opposed to Twinkle's rollback) is a MediaWiki feature, which "rollbacks the last edits made by the last editor of the page; in other words, it restores the last version of the article whose editor is not the last one". It has no way of knowing that SineBot has a special task to perform: as far as the MediaWiki software is concerned, SineBot is just another user, which may well be the editor that is not the last editor. It could find out that SineBot is a bot, but would have no way of distinguishing it from e.g. Cyberbot II (talk · contribs) which also edits Talk: pages.

To get the behaviour of true rollback changed would need a phab: request. --Redrose64 (talk) 15:58, 1 June 2016 (UTC)

Odd error when using efn

A recent minor edit to Mark XIV bomb sight has caused a large error message to appear due to an empty REF tag. There is no ref tag at that point, it's an EFN. There are other EFNs on the page that are working fine. Can someone spot what's going on here? Maury Markowitz (talk) 01:38, 29 May 2016 (UTC)

It looks like User:Kind Tennis Fan already fixed this. — xaosflux 02:10, 29 May 2016 (UTC)

@Maury Markowitz and Kind Tennis Fan: As AustralianRupert noticed, the problem was the equals sign inside the URL; but the change to using {{cite web}} added undesirable quote marks. All that was necessary was to explicitly number the parameter, i.e. use {{efn|1=An image instead of {{efn|An image. --Redrose64 (talk) 17:22, 1 June 2016 (UTC)

No longer getting indications of "Since your last visit" in edit histories

As someone who monitors hundreds if not thousands of articles, I rely on the green highlighting of the "new since your last visit" to show me how far back I should check the changes to an article. I find that highlighting is not there any more in my page view. Can someone please explain or repair this? Thanks. Please ping me as this page is fairly active and I may therefore miss replies. Softlavender (talk) 03:27, 29 May 2016 (UTC)

I saw them first appear just a couple days ago and now they're gone... didn't even know it was a possibility to have them. EvergreenFir (talk) Please {{re}} 04:42, 29 May 2016 (UTC)

@Softlavender: This in your CSS:

span.updatedmarker {
  color: black;
  background-color: #0f0;
}

should produce: updated since my last visit. But you should currently be seeing: updated since my last visit. The latter is set for the English Misplaced Pages in MediaWiki:Common.css. Are you seeing nothing at all now? PrimeHunter (talk) 10:25, 29 May 2016 (UTC)

I have from time immemorial seen the green highlighting, which I personally need. Now I do not see the green highlighting, only the words ("updated since your last visit"). Can someone explain to me how to fix it and get the green highlighting back, if it is an individual thing? Softlavender (talk) 11:15, 29 May 2016 (UTC)

@Softlavender: Save the above code in your CSS. PrimeHunter (talk) 11:26, 29 May 2016 (UTC)

Tool is down

The ref refill tool is down since a day or two back. I am not sure if this is the correct forum for this request but if someone could take a look at what the problem is that would be appreciated. Or if someone could direct me to the user in charge of the tool. Thanks. --BabbaQ (talk) 17:57, 29 May 2016 (UTC)

I can't help, but I tried to use it a couple days ago and it failed to work, so just corroborating your experience.--S Philbrick(Talk) 21:37, 29 May 2016 (UTC)

Could you provide steps to reproduce the problem? How to get to the "ref refill tool"? Thanks! --AKlapper (WMF) (talk) 08:44, 30 May 2016 (UTC)

WP:REFILL is hosted at toollabs:refill and Zhaofeng Li is the maintainer. I was able to use it without any problems. — JJMC89 (T·C) 10:06, 30 May 2016 (UTC)

@BabbaQ, Sphilbrick, AKlapper (WMF), and JJMC89: I'm the maintainer of the tool, and the problem has been fixed. Sorry for the interruption. Zhaofeng Li (Please {{Ping}} when replying) 10:58, 30 May 2016 (UTC)

Thanks for the notice and, more importantly, thanks for the tool. I manually improve refs when there are a few needing improvement, but when there a lot, the tool is very helpful.--S Philbrick(Talk) 11:53, 30 May 2016 (UTC)

Watchlist problem

The "mark all as read" button on my watchlist has gone (Windows 8.1, Firefox 46). It's still there on Commons. What's going on? BethNaught (talk) 19:15, 29 May 2016 (UTC)

I'm moving some watchlist styles around; hitting a snag, trying to fix. -- ] {{talk}} 19:22, 29 May 2016 (UTC)

Reverted. Please allow 5 minutes for the button to reappear. -- ] {{talk}} 19:42, 29 May 2016 (UTC)

It's now reappeared to me. BethNaught (talk) 19:44, 29 May 2016 (UTC)

Bold links in watchlist

Links in the watchlist such as User talk:Shhhhwwww!!‎ in mine next to a green bullet stay bold. GeoffreyT2000 (talk) 19:47, 29 May 2016 (UTC)

Here too. Bug in Gadgets/Resource Loader being stuck in some state, again. -- ] {{talk}} 21:36, 29 May 2016 (UTC)

It has happened before, but that was always fleeting. Now it seems to be there permanently until you click on the page concerned. I don't understand the whys and wherefores, and I don't really see any point in the bolding. In addition I find it aesthetically annoying and wish it gone. -- Ohc  08:19, 30 May 2016 (UTC)

@Edokter: try a whitespace change on the resources to trigger it perhaps ? —TheDJ (talk • contribs) 08:36, 30 May 2016 (UTC)

It seems to have cleared. -- ] {{talk}} 10:45, 30 May 2016 (UTC)

Baffled by escaping characters in an SQL query

I'm trying to run some queries to track use of a particular set of DOI citations, using Quarry. The problem is that DOIs linked through a citation template are partly URLencoded, which means a lot of %3F and so on - and % is the normal SQL wildcard.

Searching for the unencoded form - '%dx.doi.org/10.1093/ref:odnb%' - gives me a few dozen entries, all of which are cases where the DOI is linked directly. The partly URLencoded form is %dx.doi.org/10.1093%2Fref%3Aodnb%2F%, and it seems like the escaped form for a SQL search would be either %dx.doi.org/10.10932Fref3Aodnb2F%, or '%dx.doi.org/10.1093!%2Fref!%3Aodnb!%2F%' ESCAPE '!' (explicitly calling an escape character). Both of these, however, don't work. It should be returning somewhere around four thousand results, and returns none at all. Any ideas where I'm going wrong? Andrew Gray (talk) 22:17, 29 May 2016 (UTC)

The %2F stuff is what you see in a link, but a slash (/) is stored in the external links table. Same for %3F and colon (:). I think you need to use / and : with no urlencoding. Johnuniq (talk) 22:51, 29 May 2016 (UTC)

That only produces a very small number of results, though. There should be about 4300 articles (everything using {{cite ODNB}} will generate these DOIs) but the non-encoded version gets about seventy or eighty, all from non-templated links. It seems there must be some distinction in the way they're stored, but I can't figure out what. Andrew Gray (talk) 22:55, 29 May 2016 (UTC)

Can you find an example of a link you want the query to list, but which is not? That is, please post a link to the article and the wikitext in that article which generates the link. Johnuniq (talk) 23:23, 29 May 2016 (UTC)

I imagine Alain de Lille would be one such article. There's a DOI in the ONDB ref. I notice in Andrew's escaped version, that the first forwardslash (between dx.doi.org and 10.1093) is not URL-encoded ... sadly my quarry queries are yet to be executed, so I don't know if this is material. --Tagishsimon (talk) 23:42, 29 May 2016 (UTC)

More ODNB DOIs than you can shake a stick at --Tagishsimon (talk) 01:00, 30 May 2016 (UTC)

And, fwiw I got to that by looking at format of EL_to values for the article Alain de Lille in query 10128 --Tagishsimon (talk) 01:03, 30 May 2016 (UTC)

You can use a regex with RLIKE to catch both the normal and URL-encoded versions in one query, using something like RLIKE '.*dx.doi.org/10.1093(/|%2F)ref(:|%3A)odnb(/|%2F).*'. There's a demo query for Alain de Lille using this syntax at query 10132. — Mr. Stradivarius 01:10, 30 May 2016 (UTC)

Also, performance-wise I am guessing that it would help to anchor the regex to the start of the string, like ^(https?:)?//dx.doi.org/10.1093(/|%2F)ref(:|%3A)odnb(/|%2F).*. — Mr. Stradivarius 01:16, 30 May 2016 (UTC)

This is amazing - thanks all. So it looks like the database stores the slash encoded but the colon unencoded. Odd! Andrew Gray (talk) 14:27, 30 May 2016 (UTC)

Font problem

I normally use Firefox (version 44) on Windows 7. I wanted to try Chrome. After installing Chrome, I had problems with fonts. Chrome would show an Arial font but instead of in regular, it was in italics. Many things at Misplaced Pages that had been normal were italicized. I replaced my Arial regular font and it fixed the problem.

However, I still have a problem. Article titles that should be normal are bold italics. Firefox shows the titles properly (although I had to make a long-standing setting change to force it to do so). AFAIK, nothing else in Windows itself is problematic, just Misplaced Pages, and thus far only article titles.

Is there anything I can do to fix this? Thanks.--Bbb23 (talk) 23:06, 29 May 2016 (UTC)

Possibly: Visit (URL) chrome://flags and enable "Disable DirectWrite". ref = www.youtube.com/watch?v=YkXd7lK8K7A Fred Gandt · talk · contribs 03:22, 30 May 2016 (UTC)

@Fred Gandt: Thanks. Unfortunately, that didn't work.--Bbb23 (talk) 12:19, 30 May 2016 (UTC)

TOC limit overide

Is there a way to set my settings so that limits on Table of Contents (TOC) can be overridden? I find a number of articles where the TOC has been manually limited, and sometimes I've had issues with over-protective editors complaining that the TOC is too long when I remove the limit. (The last "discussion" I had on this issue was a disaster, so I'd prefer some individual setting.) I prefer to see the full contents listed, but I don't know of any way to expand a limited (not hidden) TOC, either through my settings or an individual page. - BilCat (talk) 01:11, 30 May 2016 (UTC)

Assuming there is no built in way, it can (I have no doubt) be done by user script or user CSS. Will you provide an example page where the TOC is limited, so I can see the code? Fred Gandt · talk · contribs 03:14, 30 May 2016 (UTC)

It's usually done by a template like {{TOC limit}}, on e.g. Audi. If you add the following CSS to your common.css then it will always show all of the TOC levels:

/* Always show all TOC levels */
.toclimit-2 .toclevel-1 ul,
.toclimit-3 .toclevel-2 ul,
.toclimit-4 .toclevel-3 ul,
.toclimit-5 .toclevel-4 ul,
.toclimit-6 .toclevel-5 ul,
.toclimit-7 .toclevel-6 ul {
	display: block;
}

Hope this helps. — Mr. Stradivarius 03:32, 30 May 2016 (UTC)

Thank you both. I'm may be inactive for a few days because of a family illness, but I'll will check this out in a few days when I can. Thanks again. - BilCat (talk) 12:14, 30 May 2016 (UTC)

Thanks Mr. Stradivarius, I've tried it, and works. - BilCat (talk) 14:55, 30 May 2016 (UTC)

Cluebot NG is still down since rollback change

A discussion was happening at User talk:ClueBot Commons#Your bot may need to be restarted. Other than Rich, who looks to be investigating, is anyone else able to assist with the problem? — Andy W. (talk · ctb) 04:19, 30 May 2016 (UTC)

@Andy M. Wang: ClueBot NG is back up and running again. —MRD2014 (formerly Qpalzmmzlapq) T C 17:38, 30 May 2016 (UTC)

Tech News: 2016-22

Latest tech news from the Wikimedia technical community. Please tell other users about these changes. Not all changes will affect you. Translations are available.

Recent changes

• There is now a standard way to get the target of a redirect page from a Lua module.

Problems

• A new way to handle rollback was introduced. It broke some tools and scripts and was reverted. This will be re-planned after review.
• CentralNotice didn't work in some older browsers. This has now been fixed.

Changes this week

• When you edit a file or category page with the visual editor the rest of the page will be shown in its normal place.
• The Translate extension will get an edit summary field.
• A change to the <charinsert> feature could break some user scripts. Contact Bawolff if the "click to insert special characters" links in the edit window break on your wiki.
• Elasticsearch will be upgraded on Wikimedia wikis this week. This should not affect you, but if you have problems with the search function this is probably the reason.
• The new version of MediaWiki will be on test wikis and MediaWiki.org from 31 May. It will be on non-Misplaced Pages wikis and some Wikipedias from 1 June. It will be on all wikis from 2 June (calendar).

Meetings

• You can join the next meeting with the VisualEditor team. During the meeting, you can tell developers which bugs you think are the most important. The meeting will be on 31 May at 19:00 (UTC). See how to join.

Tech news prepared by tech ambassadors and posted by bot • Contribute • Translate • Get help • Give feedback • Subscribe or unsubscribe.

16:18, 30 May 2016 (UTC)

Category:Former monarchies

Hi, Anybody know how to move the last (alphabetically) members of Category:Former monarchies (i.e. Bidar Sultanate and Đinh dynasty) into there correct alphabetical position ? Thanks GrahamHardy (talk) 17:33, 30 May 2016 (UTC)

That's definitely strange. I tried adding {{DEFAULTSORT}} to Bidar Sultanate, but that didn't help, and Đinh dynasty already has one, but it seems to be ignored. nyuszika7h (talk) 17:43, 30 May 2016 (UTC)

I don't have time to investigate further, but I think {{Infobox former country}} is the one to blame for that. --Edgars2007 (talk/contribs) 17:52, 30 May 2016 (UTC)

Right, common_name is required in {{Infobox former country}} and used for category sorting. Fixed in and . It would maybe be better to code the infobox to use {{PAGENAME}} as default but it wouldn't have solved Đ versus D. Do we have a feature to convert letters in a string to similar Latin letters like Đ to D? PrimeHunter (talk) 18:33, 30 May 2016 (UTC)

Do we need it? See Misplaced Pages talk:Categorization#OK to switch English Misplaced Pages's category collation to uca-default?, which should take care of that problem, I think. --Izno (talk) 23:58, 30 May 2016 (UTC)

Nice. I guess we don't need it for category sorting then. It might be used in certain external link templates to automatically convert a title to a url if no url parameter is given, but there are few sites where it would be relevant and if the feature exists then editors may fail to check that the conversion produces a working link. PrimeHunter (talk) 03:03, 31 May 2016 (UTC)

Problem with previewing with the API

I have some code at User:Dudemanfellabra/AssessNRHP.js that I've recently expanded to include a preview function by using the API's "parse" capability. I am and have been able to load the parsed HTML of an existing page rather easily using "action=query&prop=revisions&rvprop=content&rvparse=true", but part of the code I'm writing allows the user to modify a page's wikitext (specifically an infobox) and preview the result. To generate the HTML preview, I use "action=parse&text=..." since the wikitext is not saved anywhere before previewing.

A problem arises for large pages, though, since the URL includes the entire wikitext of the preview, and so in some (all? I'm using Firefox) browsers, an error is thrown. Is it possible to generate a parsed preview of some wikitext without having to include the entire text in the URL?--Dudemanfellabra (talk) 23:26, 30 May 2016 (UTC)

@Dudemanfellabra: This should be possible by using an HTTP POST request instead of HTTP GET (which is the default for $.ajax). Data gets appended to the URL in GET requests but not in POST requests. The following code is untested on any actual long pages, but should do what you need:

var api = new mw.Api();
api.post( {
    action: "parse",
    format: "json",
    contentmodel: "wikitext",
    text: pagetext
} ).done( function ( data ) {
    console.log( data.parse.text );
} );

Best — Mr. Stradivarius 04:33, 31 May 2016 (UTC)

Also, the docs for mw.Api are here. Or you could use the "method" parameter in $.ajax (docs). — Mr. Stradivarius 04:35, 31 May 2016 (UTC)

Thanks for that! I just added "method: 'POST'" to the ajax call (which I wasn't aware of), tested it on a long page, and it worked! I'll keep mw.Api in my back pocket for next time. Thanks again!--Dudemanfellabra (talk) 04:46, 31 May 2016 (UTC)

Having issues with the search function

What were you expecting and what was the actual result of your action?

When I click the search bar, I should be able to type my query in, press the ↵ Enter key and be whisked away like normal. What ended up happening was when I am in the process of typing something in the search bar the cursor sometimes disappears completely, not allowing me to type until I click it again. When clicking on a link that is auto-suggested by search, it should lead me to the link. Instead, it leads me to a blank search results page.

Where did you encounter the problem?

I've had this problem with search for a while (can't remember how long though) and it drives me nuts when it doesn't act normally.

What browser and what version of your browser are you using?

I am using Google Chrome 51. In case it is needed, I have a Windows 10 desktop computer.

Thanks in advance! Best wishes,
TheFallenOneGOTH (Talk) 00:18, 31 May 2016 (UTC)

Check if you have any browser extensions enabled. These things tend to interfere at times with your normal browsing experience. —TheDJ (talk • contribs) 08:09, 31 May 2016 (UTC)

Signature question

I'm wondering if anyone would mind taking a look at User talk:LeonRaper#Signature help etc and see if there's a technical issue with the way this user is signing his posts. I understand there is quite a bit of user error, etc. involved, but I am curious if the editor's settings somehow got accidentally tweaked which is causing his signature not to display properly even when he correctly uses the 4 tilde. Thanks in advance. -- Marchjuly (talk) 02:28, 31 May 2016 (UTC)

That use has been indefinitely blocked since 17MAY. The user would have to fix or reset their signature in Special:Preferences if they return. — xaosflux 03:29, 31 May 2016 (UTC)

Thanks for the response Xaosflux. I understand the user is blocked, but I was just wondering if his problem was more technical or more user error. Also, I didn't know that blocked editors were unable to edit their preferences. Anyway, I'll pass that information along. -- Marchjuly (talk) 05:42, 31 May 2016 (UTC)

From what I can see it is purely user error. FWIW, the "default" signature option is to leave the box blank, and not have the checkbox checked. — xaosflux 11:36, 31 May 2016 (UTC)

Trying again on tech question

I asked about this on another page (got some helpful info but not quite the clarity I was after)..perhaps there are some very technical types here...FOR EXAMPLE: this very page/function/space I'm on right now must not have existed at some point in time...someone had the idea to create it and it was then created....how was it created? Did, perhaps, editors suggest it be created and then somebody at the Misplaced Pages Foundation had to code it/create it? Or are tech-savvy editors with certain permissions able to create it on their own?? Nobody seemed to exactly know when I posted this question at "idea labs" Thanks..68.48.241.158 (talk) 14:17, 31 May 2016 (UTC)

Hi IP, perhaps you were looking for the help desk? Either way, any editor can edit and create* articles on Misplaced Pages - if you check out this guide you can find out how (* unregistered editors (like yourself) cannot create new articles outside of this process)-- samtar 14:25, 31 May 2016 (UTC)

I'm not sure you're understanding my question..I'm talking about an entirely new function/space not an article...68.48.241.158 (talk) 14:31, 31 May 2016 (UTC)

Ah! You mean (for example) Misplaced Pages:Village pump (carrots)? I believe any editor could propose such a creation and, if the idea gained consensus, create it. -- samtar 14:48, 31 May 2016 (UTC)

Anyone can create it without consensus, it would take consensus for it to stay though. -- GB fan 15:00, 31 May 2016 (UTC)

Any logged in editor can create a page in any space including a page similar to this one. It does not take any special permissions other than having a named account. Whether that page will remain or not may require a consensus discussion to take place. If someone believes that the new page is not helpful/does not comply with policy then they can take it to a deletion process. It is usually easier if the discussion takes place before hand rather than building the page and hoping it survives. If you are thinking about a bot to do the task you are talking about elsewhere, that will require approval before it can operate, see Misplaced Pages:Bot policy. -- GB fan 14:38, 31 May 2016 (UTC)

so this entire village pump space/function can be created by just normal editors and doesn't require anything on the end of the Foundation? what about the log of all blocks, for example..that space/function was and can be created by just anyone and placed into Misplaced Pages? and how sure of all this are you? if others could confirm/add anything...68.48.241.158 (talk) 14:46, 31 May 2016 (UTC)

See my response above, but in relation to the logs - these are programmatically generated by the Mediawiki software -- samtar 14:49, 31 May 2016 (UTC)

The entire Village pump are just pages in Misplaced Pages and like any page in Misplaced Pages they can be created by any logged in user. Logs are a different matter and that takes coding in the back end and would require the developers to take action. I am very sure of my answer. -- GB fan 14:58, 31 May 2016 (UTC)

and if a new/different log was desired what then would be the process?? you're saying normal editors couldn't do it, right?68.48.241.158 (talk) 14:54, 31 May 2016 (UTC)

Correct - It would be a 'feature request' made on our phabricator. This guide (shameless plug) helps explain the process -- samtar 14:57, 31 May 2016 (UTC)

Normal editors can not create logs that would show up at Special:Logs. Now if you are looking at a log like is at WP:SPI anyone can manually create it but if they want a bot to create it, then there is an approval process. -- GB fan 14:58, 31 May 2016 (UTC)

well it would be similar to that SPI and maintained automatically by a bot I suppose...so wouldn't have to go through phabricator?? but where would I request the page/bot be created?68.48.241.158 (talk) 15:04, 31 May 2016 (UTC)

You can start at Misplaced Pages:Bot requests. -- GB fan 15:09, 31 May 2016 (UTC)

so if I wanted a new log related to unblock requests the only process would be to go through this phabricator process, is that correct?68.48.241.158 (talk) 15:01, 31 May 2016 (UTC)

It depends on what you want. If you want it to show up as a simple list in Special:Logs then yes. If you want it on a page with additional information like the log at WP:SPI then no it would not go through phabricator. If this is related to the discussion about the unblock transparency, you probably don't need to go through phabricator. -- GB fan 15:04, 31 May 2016 (UTC)

Thought I recognised this train of thought - IP, it's likely what you're after could be solved with a bot as GB fan suggests -- samtar 15:07, 31 May 2016 (UTC)

okay, so it wouldn't require a petition to phabricator, right? the page (log) could be created and then maintained by a bot (and bot only) where would I a. petition someone who knows how to do this...and then b. it would have to be approved..before or after I request it be made??68.48.241.158 (talk) 15:11, 31 May 2016 (UTC)

The bot would have to be approved after it was made, before it started making any edits. If you didn't see it above you can start the bot process at Misplaced Pages:Bot requests. -- GB fan 15:14, 31 May 2016 (UTC)

Okay, I guess that clarifies, thanks.68.48.241.158 (talk) 15:16, 31 May 2016 (UTC)

To clarify, the reason that a bot would be used here rather than a feature in Mediawiki (i.e. a phabricator request) is because unblock request (AFAIK) are not a feature of Mediawiki: they are handled basically just by putting the user talk page into Category:Requests for unblock. Things in Special:logs tend to be special actions, rather than normal edits. —  crh ₂₃  (Talk) 15:48, 31 May 2016 (UTC)

okay, thanks.68.48.241.158 (talk) 15:52, 31 May 2016 (UTC)

Spacing Issues in Infobox

I am new to template creation and I have a few quirky formatting issues in the Template:Infobox_gene that I was hoping to get help fixing. On my talk page User_talk:Julialturner you can see the newest version of the Template:Infobox_gene. If you look at the first gene "RELIN" you will notice under the "Genetically Related Diseases" section the references (ie ) align to the center instead of the top like the name of the disease. This has something to do with the fact that it can be a collapsible list in this section. You can see it happening again in the "Orthologs" section ("5649" and "19699" are centered). The other issue can be seen in the "endothelin receptor type B" gene box under the "Orthologs">"RefSeq (mRNA)" those ids that are displayed are bolded and it would be nice if they weren't. If you have suggestions how to fix these or where to look I would greatly appreciate the help. Thanks Julialturner (talk) 20:43, 31 May 2016 (UTC)

MathML glitch

Display of formulas in composition algebra suddenly came up red though rendering had been successful on Preview. — Rgdboer (talk) 21:48, 31 May 2016 (UTC)

Problems with math display

I'm seeing issues with <math> ... </math> expressions. Apparently there is a separate server to process these expressions? I'm getting messages such as:

Failed to parse (MathML with SVG or PNG fallback (recommended for modern browsers and accessibility tools): Invalid response ("Math extension cannot connect to Restbase.") from server "/mathoid/local/v1/":)

This isn't on a page I'm editing, just one I'm viewing. (Specific example at this point in time: Deconvolution (permalink to failed version). WikiDan61_ReadMe!! 21:39, 31 May 2016 (UTC)

A search on "MathML with SVG or PNG fallback" finds more examples. A purge has fixed all examples I have tested so it seems the problem is either gone or only affects some servers. PrimeHunter (talk) 22:12, 31 May 2016 (UTC)

This is related to T131177 which changes the default of the maths renderer form the 10 year old PNG renderer to a newer SVG system which uses server side mathjax rendering. It was made the default today. You may need to change your preferences to get things to work right, I had "MathML with SVG or PNG fallback" as my preference and I needed to change things to PNG and back again to get things to work. --Salix alba (talk): 23:02, 31 May 2016 (UTC)

Stepped outside, just returned. Formulas rendering well now. Thank you everyone for the information and efforts. — Rgdboer (talk) 01:50, 1 June 2016 (UTC)

Still a lot of messed up pages throughout all wikimedia wikis. I'm searching for Math+extension+cannot+connect+to+Restbase site:wikipedia.org with 78 errors across all languages.--Salix alba (talk): 04:48, 1 June 2016 (UTC)

I did a round of manual purging, so most of these should be fixed now. There was a brief outage related to a Cassandra upgrade not long after the preference switch (which caused a lot of re-renders), which resulted in these errors. Sorry about that. -- GWicke (talk) 15:10, 1 June 2016 (UTC)

Find sources

Could someone change Template:Notability so that the "find sources" external link creates a search query that excludes parenthetical disambiguators.--Prisencolin (talk) 03:53, 1 June 2016 (UTC)

Discussion at Template talk:Notability#Find sources. PrimeHunter (talk) 10:42, 1 June 2016 (UTC)

Visual editor problems

Expected vs observed behavior: "<small>" should be either in the "Style text" menu or should function as expected when typed (like "{{" or "]"). The current reading is:

I propose that it be changed to read:

or:

or something to that effect.

Problem encountered at: https://en.wikipedia.org/search/?title=Wounded_Knee_incident&diff=prev&oldid=723118346 (see the bottom of the diff) (next parenthetical is tangential) (the <nowiki>''</nowiki> in the diff is user error attributable to trying to get the "Wiki markup detected" box to show up again so I could read the instructions for using the "Switch to source editing" feature without realizing that it disappears before the offending markup is deleted (I mistakenly assumed that its disappearing indicated that the markup was gone because I had happened to delete my added markup manually at pretty much the same time as the notification disappeared the first time I saw it); I wasn't being particularly attentive so I neglected to notice the continued presence of the '') (if anyone actually understands this tangential, "<small>"-ified wall of text, they probably deserve a fuckin award for language comprehension skills; I bet I'd have gotten lost and/or glazed over way before getting to the end of it).

Browser: FirefoxDeveloperEdition

Browser version: 48.0a2 (2016-05-31) Goldenshimmer (talk) 04:11, 1 June 2016 (UTC)

Thanks for the feedback! mw:VisualEditor/Feedback is the best place to make sure it is seen. :) --AKlapper (WMF) (talk) 09:47, 1 June 2016 (UTC)

Bottom of VPT is fucked up

The last three threads are all showing up on one line. Could someone fix the page? Thanks :) Goldenshimmer (talk) 04:17, 1 June 2016 (UTC) (It should be evident from my post contents why I'm posting in the wrong part of the page.)

Done. Writ Keeper ⚇♔ 04:42, 1 June 2016 (UTC)

Sweet, thanks @Writ Keeper:. :) (Should I move this to the bottom where it belongs chronologically now?) Goldenshimmer (talk) 04:52, 1 June 2016 (UTC)

I'm going to bed now so I'm gonna be bold and put this section where I think it goes. If that's a problem, feel free to revert. :) Goldenshimmer (talk) 07:02, 1 June 2016 (UTC)

Tony Dean (racing driver)

Hello, I wonder if anyone can shed any light on why the above article I moved into mainspace on 30 April does not appear in my list of articles created? Two others I moved at the same time did so immediately. It's only a small thing, I know, but it was my 50th article and these tiny milestones are the only rewards we can hope for. :) Thanks. Eagleash (talk) 15:46, 1 June 2016 (UTC)

I see it in these search results. Where do you not see it? Fred Gandt · talk · contribs 16:00, 1 June 2016 (UTC)

It does not appear when clicking on 'contributions' (top of any page) and then 'articles created' at the bottom of the page. I.e. here and then here. Thanks. Eagleash (talk) 16:11, 1 June 2016 (UTC)

@Cyberpower678 and MusikAnimal: because I think you're likely to be most useful here (xtools). Fred Gandt · talk · contribs 16:56, 1 June 2016 (UTC)

Edit notice not highlighted

I added a 1RR edit notice to Flag of Northern Ireland but it isn't highlighted and I doubt it will be noticed by many editors. Can this be fixed? Thanks. Doug Weller talk 16:07, 1 June 2016 (UTC)

@Doug Weller: It shows for me. What are you expecting to see, but are not? --Redrose64 (talk) 17:24, 1 June 2016 (UTC)

On Template:Editnotices/Page/Flag of Northern Ireland you could add some styles or colors, see Template:Editnotice/doc for some examples. — xaosflux 17:37, 1 June 2016 (UTC)

Thanks. For some reason I expected to see some color. I've fixed it now so it's more obvious. Doug Weller talk 18:33, 1 June 2016 (UTC)

Finding contributions of a editor who changed names

An editor was told at The Teahouse she was required to change her name. Sinebot signed her name with a link to contributions. Fortunately she replied with her new name and I was able to find her contributions with that name. But shouldn't a link to contributions with the old name somehow give us a clue as to how to find contributions with the new name?

She was asking for more help but in the articles she linked to neither name had contributed. And the other article she needed help with had been deleted.— Vchimpanzee • talk • contributions • 19:40, 1 June 2016 (UTC)

The talk pages redirect because the renaming occurred so I don't know what more do you need. The Recordings username has no contributions which I think is because they were moved. The new on has all the edits. It's the same as for Misplaced Pages:Courtesy vanishing. -- Ricky81682 (talk) 20:53, 1 June 2016 (UTC)

Cite journal filler again

Sorry to bring this up again but the cite journal filler is still not working for me--when I try to use it to fill out a template by entering the doi or pmid, in many cases the template doesn't even load at all when I click on the "cite journal" button on the cite tab on the toolbar. I really hope someone knows what I can do to fix this problem permanently. Everymorning (talk) 20:36, 1 June 2016 (UTC)

I get this too if the doi is invalid, or sometimes it is valid, but it is for a book chapter and not a journal article. It would be good to get feedback if a problem is detected, and what that problem is. Graeme Bartlett (talk) 23:57, 1 June 2016 (UTC)

WP:Comments in Local Time

Hi, Not sure if this is a bug or what,
Thanks to British Summer Time back in April I added the script from Misplaced Pages:Comments in Local Time to my vector.js and it worked fine ... However today I've noticed it's not working or updating itself ?,
When you install the script the timestamp should basically change automatically (and I recall it had a "+1" next to the time/date) (So for me instead of the timestamp here being 11pm it should say 12pm) ... however it's not changed it ...,
Thanks to BST the script made my life alot more easier here so am rather disappointed it's stopped so hoping somewhere can help, Anyway thanks, –Davey2010 23:18, 1 June 2016 (UTC)

Why not post at Misplaced Pages talk:Comments in Local Time instead? ―Mandruss ☎ 00:02, 2 June 2016 (UTC)

I've amended the OP's post. Readers should not have to click the 'British Summer Time|BST' link that was provided, in order to find out what 'BST' means. It may be obvious in the UK but it certainly isn't everywhere else. Akld guy (talk) 00:28, 2 June 2016 (UTC)

Because I'm not sure if it's an actual bug to do with this place or whether it's something minor with the script? .... and that talkpage looks dead anyway. –Davey2010 00:50, 2 June 2016 (UTC)

• Misplaced Pages village pump
• Pages automatically checked for accidental language links