Wikipedia:Village pump (technical)

From Wikipedia, the free encyclopedia
Jump to navigation Jump to search
 Policy Technical Proposals Idea lab Miscellaneous 
The technical section of the village pump is used to discuss technical issues about Wikipedia. Bug reports and feature requests should be made in Phabricator (see how to report a bug). Bugs with security implications should be reported differently (see how to report security bugs).

Newcomers to the technical village pump are encouraged to read these guidelines prior to posting here. If you want to report a JavaScript error, please follow this guideline. Questions about MediaWiki in general should be posted at the MediaWiki support desk.

Frequently asked questions (FAQ) (see also: Wikipedia:FAQ/Technical)
Click "[show]" 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.
Font size changed unexpectedly?
You may have accidentally changed the font size on your browser for a particular website by pressing a shortcut key or scrollwheel without realising it. Try resetting the zoom with Ctrl+0 (typing the digit zero while holding down the control key) or adjusting the zoom with Ctrl++ or Ctrl+-. Alternatively, look for the View option on your browser's menu and reset it to 100%.
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 bug 1864. There is an accesskey property on it (default to accesskey="f" in English), and for logged in users there is a gadget available in your 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 Wikipedia: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.
Numbers listed in parentheses in the "Recent changes" section, on history pages and in your watchlist are the number of added or removed bytes.
For server or network status, please see Public Website Health Status for Wikimedia Foundation - Core services.
Questions and suggestions related to the portal should go to Meta.
« Older discussions, 146, 147, 148, 149, 150, 151, 152, 153, 154, 155, 156, 157, 158, 159, 160, 161, 162, 163, 164, 165, 166


Remex: My page is recently broken and I can't figure out why[edit]

A new parsing tool called Remex is now cleaning up the HTML output for a webpage. It may cause some pages to display in undesirable ways. Be patient while we work out the kinks, and feel free to report problems in a new subsection here:

Visible bullets in infobox[edit]

FYI: Pointer to discussion elsewhere

See Template talk:Infobox musical artist#Visible bullets at Limp Bizkit. --Redrose64 🌹 (talk) 20:58, 5 July 2018 (UTC)

Post-Tidy fix may be needed at Template:Infobox NFL team[edit]

This link currently shows me different rendering of the bullets under "Playoff appearances (10)" and "Home fields" in {{Infobox NFL team}}. The Tidy version on the left renders normally, with bullets inside the infobox and aligned with the bulleted lists above these bottom sections. The post-Tidy version, which is currently live, shows the bullets for these two sections sitting just outside the box that outlines the infobox. I don't see an obvious cause of this problem. – Jonesey95 (talk) 03:04, 6 July 2018 (UTC)

I hacked the {{Infobox NFL team/sandbox}} with div tags wrapping the problematic list items. Is that terrible? It seems to work. If I put /sandbox into the edit above and preview it, everything looks fine. I wonder if a similar fix would work for Infobox musical artist, or if there is a more general fix that is needed. It seems like it would be a challenge to do something like this to every infobox field that might have bullets in it.
And it doesn't explain why the "Team nicknames" section renders just fine. Is it because the header and data use different numbers in the broken sections? I don't know enough about how infoboxen work to know what effect that numbering has. – Jonesey95 (talk) 03:18, 6 July 2018 (UTC)
Jonesey95: See my response at Template_talk:Infobox_musical_artist#Visible_bullets_at_Limp_Bizkit. The same reasoning applies to this infobox. Presumably, fixing that module would fix this too. SSastry (WMF) (talk) 09:13, 6 July 2018 (UTC)

Peculiar html rendering issue[edit]

As of just the last little while, most of the html-defined fields I am currently using on my user page are suddenly rendering a vertical bar (|) that is not in the supplied text; this occurs only in fields which possess some degree of text however. I'm not even sure what the namespace is to which the "{|" syntax points, so I can't investigate further, but I assume that the problem is not isolated to my user page (if I made some kind of error which cause this rendering, it would have had to have been a while back and I can't imagine I went that long without noticing). I've been off project for a few days, so the alteration may have occurred at any point during as far as I know. Anyone have some thoughts? I'm not too concerned about the user page, but I do wonder if there are content or policy pages affected. Thanks in advance for any insight. Snow let's rap 01:23, 8 July 2018 (UTC)

@Snow Rise: You have 4 dozen lint errors and Remex was just enabled. (I have consequently moved your section.) --Izno (talk) 02:30, 8 July 2018 (UTC)
I believe the cause is <span style="border: 1px solid">, which is unclosed. Is it your intent to have that span? I think I got them all (and it was indeed that). There might be still remaining lint errors. --Izno (talk) 02:46, 8 July 2018 (UTC)
I have cleaned the rest of the page a good bit. There are still some remaining lint errors that I don't want to fight with right now. I think they are due to some unclosed span tags bumping into block elements like the horizontal rules. Let me know if I didn't quite get some set of stylings right on the page. --Izno (talk) 04:26, 8 July 2018 (UTC)
It all looks good to me, Izno. I had no idea about the Tidy->Remex shake-up and didn't realize the number of lint errors I had that would no longer get the benefit of Tidy. Thank you for clarifying the matter and for taking the time to clean up so many of the errors--it was a very generous use of your time! Snow let's rap 06:14, 8 July 2018 (UTC)

Unclosed tag in a user message template[edit]

I just realized the user message template {{Pending changes reviewer granted}} (formerly {{Reviewer-notice}} and {{Reviewer granted}}) had contained the code <tt>reviewer<tt> with an unclosed <tt> for good 4 years and have affected over four thousand User talk pages. It looks like the code had no effect on appearance but with the recent installment of the Remex parser it has broken all the pages the template was substed onto. Can someone fix them with a bot? (Or is someone already?) And I wonder if there is any other similar case where a subst template has plagued pages with unclosed tags... Nardog (talk) 15:47, 8 July 2018 (UTC)

I'll request a bot task here for High/Medium Linter cleanups for Fluxbot - our review and approval process can be somewhat lengthy. — xaosflux Talk 15:51, 8 July 2018 (UTC)
See Wikipedia:Bots/Requests for approval/Fluxbot 7. — xaosflux Talk 16:00, 8 July 2018 (UTC)
As an FYI, in this use, we should probably use {{subst:tt|reviewer}} rather than fixing the unclosed tag.
As for bot tasks, I think you should probably use separate tasks for this rather than a Fluxbot 7, regardless of bureaucracy. Not all changes can be automated and even those that can will have different approaches (especially e.g. obsolete elements). --Izno (talk) 16:39, 8 July 2018 (UTC)
@Izno: these will mostly not be automated, just explicit batches if approved. As for the error and fix described above, fixing the bad tt close is the "obvious" fix for this error, and the one most normal editors would make, why would you not want to see it fixed that way? — xaosflux Talk 21:57, 8 July 2018 (UTC)
Because it is not just unclosed, it is obsolete. Kill a second bird with the stone. --Izno (talk) 22:32, 8 July 2018 (UTC)
But why subst {{tt}}? That adds extraneous code in the source. If you're suggesting substitution so as not to increase the transclusion count, then I'd rather see the <tt> tag removed entirely. Nardog (talk) 22:44, 8 July 2018 (UTC)
The writer wanted special markup for this text, making there be no markup is a big step. I'll probably withdraw my BRFA on this, I expect this type of argument over every cause of each error to take place and I'm not going to deal with tracking a consensus build for each use case. — xaosflux Talk 23:00, 8 July 2018 (UTC)
I guess you can just throw your hands up. :) I'd welcome these bot tasks--I just think it would be better to take them one at a time--otherwise people will argue that a certain change isn't in the scope of the task, or if it is they'll argue that the scope of the task was too broad, and then you're stuck pausing an entire task. --Izno (talk) 23:11, 8 July 2018 (UTC)
The text was in quotes in addition to <tt> anyway... I'm fine with any option (closing, removing, or {{tt}}) except subst. Nardog (talk) 23:24, 8 July 2018 (UTC)
@Izno: some of these pages are a mess, with variances of CODE, TT, SAMP, etc causing the entire page formatting to break - but there is no way I'm going to track a complicated series of fixes, if I come across these in normal editing the only thing I'm probably ever going to do is add/repair the closing tag - I'm well aware of the bureaucracy around here and that editors are passionate about different methods of markup. If there is consensus that making the pages "better" was fine this would be a non-issue, but trying to get a strong consensus for what the "best" is and changing pages from bad to "the best" in one step is way beyond my patience to manage. Feedback is still welcome of course! — xaosflux Talk 00:41, 9 July 2018 (UTC)
I agree with Xaos about making the jump from "tt was used only for convenient styling" to "we should remove the styling entirely" as well. And yes, mostly just to not deal with the transclusion count. Our current template should probably subst/use the markup directly for that as well (or decide whether one of the tt replacements is better; maybe samp?). --Izno (talk) 23:11, 8 July 2018 (UTC)

Horrible colour and font on article talk page[edit]

On Talk:King George V-class battleship (1939) most of the text is in a horrible colour and font. I can't see what is causing this. Can anyone fix it please? DuncanHill (talk) 15:11, 9 July 2018 (UTC)

 Done. An old signature from Ed had a couple unclosed <font>...</font> tags. –Deacon Vorbis (carbon • videos) 15:23, 9 July 2018 (UTC)
Undoubtedly related to MediaWiki's new HTML parser attempting to fix broken HTML differently than Tidy did. I've fixed them. SiBr4 (talk) 15:31, 9 July 2018 (UTC)
How odd, I swear I made the exact same changes you did at the same time (in 2 separate edits even), and it didn't even tell me that there was a conflict. Sorry if it seemed like I was trying to take credit or something. –Deacon Vorbis (carbon • videos) 15:33, 9 July 2018 (UTC)
  • Thank you, looks a lot better now. DuncanHill (talk) 15:41, 9 July 2018 (UTC)
  • Talk:USS Nevada (BB-36) has the same issue, I think I fixed some of it, but there's a lot of that signature... Chris857 (talk) 18:20, 11 July 2018 (UTC)
    The level of my annoyance knows no bounds. --Izno (talk) 18:36, 11 July 2018 (UTC)

Location Map Template Issues[edit]

Hi - hopefully someone can help me with this issue. I regularly edit English rugby union league pages on Wikipedia and use location map templates to show the teams in each league. I have not had any real issues until recently when I noticed that using position=top or position=bottom started to create an unusually large space between the location marking and the team in question (see examples below - Whitchurch, Longton, Dudley K). This has caused many of the pages to become very cluttered and make it difficult to work out where teams are. Would appreciate any feedback. Thanks. Jgjsmith006 (talk) 09:37, 10 July 2018 (UTC)

@Jgjsmith006:This is due to an incorrect usage of {{location map~}} made visible by the recent changeover from Tidy to remexHTML. You shouldn't be wrapping the labels in divs to change their size. There is a dedicated parameter named "label_size" which should be used. I've corrected the Whitchurch label in your example, so that you may compare. —TheDJ (talkcontribs) 11:59, 10 July 2018 (UTC)
@Jgjsmith006: Also, 70% is way too small, it is very much against MOS:ACCESS#Font size. I can't read it, so I doubt that one or two other people I could name (RexxS for instance) can read it either. --Redrose64 🌹 (talk) 07:13, 11 July 2018 (UTC)
Thanks Redrose. I will try and make it bigger but the problem is that there is often not enough space for all the times. Perhaps if the maps had more options when to place text (e.g. top left, bottom right etc) it might be easier. I wouldn't mind someone doing a proper West Midlands map (not just the county) so I could fit more of these teams in with bigger text. I had a go at creating maps but couldn't make head or tails of them. Do you know anyone who might be able to help me with this? Cheers. Jgjsmith006 (talk) 19:56, 11 July 2018 (UTC)
Have you considered a dynamic map do achieve that goal? See mw:Help:VisualEditor/Maps for the easy way to do it (in the visual editor). A basic one is easy enough that even I can do it.  ;-) Whatamidoing (WMF) (talk) 02:06, 12 July 2018 (UTC)
Nilfanion (talk · contribs) has created lots of SVG maps like this one. --Redrose64 🌹 (talk) 10:04, 12 July 2018 (UTC)
Thanks guys will try your advice. The maps look better with the new labels and are much clearer at size 75. Nilfanion has done a map before for me but I had forgotten their details - I will get in touch - thank you all once more. Jgjsmith006 (talk) 19:45, 13 July 2018 (UTC)

HTML formatting issues in archived talk pages[edit]

I don't know if this has anything to do with Linter, Tidy, or Remex, but I have only begun noticing this since these changes were implemented. Specifically, I have recently been encountering what appears to be HTML errors in talk page archives, usually having to do with unclosed tags that cause the rest of the page to be formatted with that HTML markup. For example, I just came across this: Wikipedia:Administrators' noticeboard/IncidentArchive962#Edit-warring at AIV (permanent link). Unless this is a problem on my end, the rest of the page from that point on is stricken due to <s>added<s> lacking a slash in the closing tag. It appears that the unclosed tag HTML error was added and never fixed (even though a bolding issue was noticed and fixed in the very next edit) before being archived, but the fact that nobody fixed it despite being live for days before archival suggests to me that the endless strikethrough formatting was not rendering at that time. Now it is, though.

This is not the only incident. I have seen similar formatting issues in other archived talk pages, but only recently, such as signature formatting being applied to the rest of the page due to the absence of closing HTML tags. I do not have links to those other particular incidents, since they are rare and I initially did not think much of them. I am beginning to wonder if there might be a connection here, though, since I have been perusing archived talk pages for years and do not recall once ever encountering such issues until the past month.

Might this have anything to do with the new parsing changes? Maybe this is related to mw:Help:Extension:Linter/multiple-unclosed-formatting-tags? Or is this old news and I have only just recently been encountering it?

Lastly, I recently fixed missing closing tags at Wikipedia talk:Courtesy vanishing. I don't know if this is at all related, either. Given how it was clearly causing rendering issues for the entire page after those closing tags were removed in August 2012 during improper signature refactoring by the user subsequent to their post being autosigned in previous edit, I find it difficult to believe that it has gone unnoticed for nearly six years by 38 users over 76 edits. But who knows, maybe it was and this is just all coincidence. —Nøkkenbuer (talkcontribs) 05:53, 15 July 2018 (UTC); revised 08:18, 15 July 2018 (UTC)

@Nøkkenbuer: Yes, this is because of Remex. I've run into these formatting problems at least once. I don't know if there's any plan to fix them right now (you could ask at WT:Linter or WP:BOTREQ), but errors in articles have been given higher priority than old signatures. Jc86035 (talk) 06:54, 15 July 2018 (UTC)
Thanks for the information and confirmation, Jc86035. Should I, or any other editor, manually fix these formatting errors in talk page archives whenever we encounter them? Or should they remain untouched? I understand that talk page archives are almost never edited outside of occasional bot edits, categorization, and manual archival, so I assume a hard no. That is why I have not attempted to fix any of these errors. Assuming we should not, is it worthwhile to report instances here or somewhere? Or would that not be useful information? Any further instruction on this matter is appreciated. —Nøkkenbuer (talkcontribs) 07:10, 15 July 2018 (UTC)
@Nøkkenbuer: I don't know and I can't tell you what to do, but I think that if it's fixable by a bot (i.e. stuff like <s>…<s> → <s>…</s>), it's probably not worth your time. There are thousands upon thousands of them in any case. Jc86035 (talk) 07:16, 15 July 2018 (UTC)
I suppose so, especially since this may just become routine cleanup work for some near-future bots, anyway. If anyone reading this has any input, please give it. Until further notice, I'll just ignore these errors. Actually, what is stated at Wikipedia:Linter § How you can help (permanent link) basically answers my questions. I may not actively seek them out, but I might as well manually fix them whenever they are encountered.Nøkkenbuer (talkcontribs) 07:35, 15 July 2018 (UTC); revised 07:48, 15 July 2018 (UTC)
I would advise against changing archives unless you feel like a glutton for punishment and time wasting, unless you're trying to read something and the styles are causing the text to be difficult to read or are unintelligible. Active talk pages, it might be valuable to clean up. Maybe someone can put together a query for talk pages (any talk pages or those with new section edit link magic word outside mainspace) with errors which do not have "archive" and a / in the page name. --Izno (talk) 23:41, 15 July 2018 (UTC)
I have fixed the WP:VPT archives numbered above 145 insofar as fixing the few unclosed <code> tags and similar that most strikingly broke readability. But the pages have plenty of other lint errors remaining. --Pipetricker (talk) 10:25, 16 July 2018 (UTC)

image widths that respond to page width[edit]

Is there a way to format a wide image that fits the image as a percentage of the page width or box width, so that it responds to screen width without overflowing or cropping the display?

Please ping with reply, Thanks, · · · Peter (Southwood) (talk): 08:00, 6 July 2018 (UTC)

Try Upright, see here WP:EIS - X201 (talk) 08:23, 6 July 2018 (UTC)
@Pbsouthwood: forgot to ping - X201 (talk) 08:23, 6 July 2018 (UTC)
X201, Upright scales the image as a proportion of default thumbnail size. I am looking for a way to scale as a proportion of page width or box width. Cheers, · · · Peter (Southwood) (talk): 09:41, 6 July 2018 (UTC)
Although this is possible in HTML with a little CSS, as in:
<img src="Example.svg" style="width:50%;" />
the MediaWiki software does not allow this. The main reason is that image scaling is done server-side, and our servers have no way of knowing how wide your device is. --Redrose64 🌹 (talk) 10:54, 6 July 2018 (UTC)
The software can find the viewport width of the device with CSS media queries, and respond accordingly. This functionality just isn't exposed to editors. TemplateStyles will change that though, and it's due to be enabled soon (phab:T197603), since this wiki was just switched from Tidy to RemexHTML. — AfroThundr (u · t · c) 12:08, 6 July 2018 (UTC)
@Pbsouthwood: I'm guessing your question is related to the mainpage images at the wikimania wiki (context/examples always helps!). I think I've fixed them, so that they no longer cause horizontal scrollbars on small windows. I did so by adding an ID to the site's CSS for the mountain image, and an inline layout hack for the logo images. Cheers, Quiddity (talk) 21:01, 8 July 2018 (UTC)
Indirectly, I guess. That came up after the original issue with portals which use relatively wide images for various purposes, includng page banners. · · · Peter (Southwood) (talk): 05:56, 9 July 2018 (UTC)
Quiddity, what you did on Wikimania main page does not appear to work on mobile view for the mountain, but the fix for the logos seems good.· · · Peter (Southwood) (talk): 06:02, 9 July 2018 (UTC)
Pbsouthwood Fixed for mobile :) Quiddity (talk) 15:58, 9 July 2018 (UTC)
Thanks, · · · Peter (Southwood) (talk): 18:51, 9 July 2018 (UTC)

I've got consensus to merge two pages - now what do I do?[edit]

Back in December 2017 I put in a merge request using Copy and Paste easy merge templates. Consensus to merge was established 2 June 2018 see: Requests answered in June 2018 and discussion but I don't know how to do mergers (please don't point me to the instructions). Is there a place I can go to request a "volunteer merger editor" to actually carry it out, or do I simply wait? I thought there would just be a "done" or "not done" reply, I hadn't bargained on a "working - you may now proceed" answer! --The Vintage Feminist (talk) 17:19, 6 July 2018 (UTC)

@The Vintage Feminist: there is nothing magic or automatic about the merge process, see Wikipedia:Merging#How_to_merge - I know you asked not to see the instructions but they are there for a reason. The major next step is editorial, not technical: what actual content from the FROM article to you want to show in the TO article? You need to put that content in to the article by editing. — xaosflux Talk 17:26, 6 July 2018 (UTC)
(edit conflict)You can request so at Requests for merge assistance and feedback, although that place is perpetually backlogged due to cumbersome nature of merging. Moreover, after you list it, it will be helpful for you to be bold and learn how to merge pages yourself. There's a chance, you'll learn the merger process and even merge the pages before the volunteer from heaven attended to your request. –Ammarpad (talk) 17:40, 6 July 2018 (UTC)
The Vintage Feminist, It really is not difficult. Just follow the instructions step by step and the actual merge will be done after very few steps, none difficult. It looks more complicated than it is, and you can't break anything irreversibly. As an extra suggestion. put an {{in use}} template into each before you start to reduce the chance that someone or a bot will edit while you are busy. Give it a go and ping me if you have any trouble. (I am in UTC+2 time zone, and often not available between 10pm and 7am, due to a habit of sleeping at night). The cleanup after the merge usually takes longer. · · · Peter (Southwood) (talk): 18:59, 6 July 2018 (UTC)
The thing about merging, is that the proposer often has the best idea of where the merged text should go, and how to clean up the merged article after pasting in the added content. · · · Peter (Southwood) (talk): 06:11, 9 July 2018 (UTC)
Okay done, thanks everybody. --The Vintage Feminist (talk) 16:14, 11 July 2018 (UTC)

Feature request: backlink hover from citations in Template:Sfn[edit]

This request emerged here during a Featured Article Review for research quality of Second Australian Imperial Force in the United Kingdom.

In Template:sfn in body text one can hover over the reference, [1] {{sfn|Reid|2003|p=3}} and gain the information, "Reid 2003, p. 3." It would be correspondingly useful in the citations to be able to hover over caret in "1. ^ Reid 2003, p. 3." and gain the information, "At the time of the two world wars, Australia and the United Kingdom (UK) had a very close relationship. Australia was a self-governing dominion within the British Empire, and its foreign and defence policies were strongly influenced by those of the British Government. Most Australians were either descended from Britons or had been born in the UK, leading to a widespread perception that Britain was the "Mother Country"."

This feature is envisaged to improve review editing and editing around sourcing in general. It is also envisaged to help reader experience when reading for research purposes. It would cut a considerable time cost in reviewing which an appreciable benefit for the encyclopaedia.

The suggested rule for hover text is:

  • For a bloc of sfn type citations
    • Display the preceding body text back to:
      • The next bloc of sfn type citations, or
      • The paragraph break

Such that for "¶Foo. [1] Bar. [2(a)][3(b)]" in the citations hovering over 1 renders "Foo.", 2(a) renders "Bar.", and 3(b) renders "Bar."

Could other editors assist with their ideas of the usefulness of moving this forward, and if viewed as useful the manner of doing so? Fifelfoo (talk) 03:20, 8 July 2018 (UTC)

It probably won't be done. It's technically complex and it would be fairly difficult to automatically tell what text an inline citation is being used for. The people at the WMF are also likely to think this isn't very important, especially since you could always… click the caret, and would probably prefer to put their resources into other things (they barely put enough resources into developing software based on volunteer input as it is). Jc86035 (talk) 05:33, 8 July 2018 (UTC)
I think a gadget or another user script could probably make this work to some degree, but I otherwise agree that WMF would not spend time on this. --Izno (talk) 13:13, 9 July 2018 (UTC)

Request: Add one "show all" button to expand at once all collapsible lists inside a template[edit]

Moved to Wikipedia:Village pump (proposals) § Request: Add one "show all" button to expand at once all collapsible lists inside a template: This page is for technical issues with what exists, not proposals for what doesn't exist. Not to say that this distinction is widely understood and observed. ―Mandruss  00:13, 9 July 2018 (UTC)

License for templates?[edit]

Wikipedia and other wikis have lots of templates running under the MediaWiki software. Are these templates licensed under the same Creative Commons license as used by wiki page content by default? Or are they GPL'd like the MediaWiki software? SharkD  Talk  06:39, 9 July 2018 (UTC)

Same license as every other page on wikipedia, unless otherwise indicated at the top of the page in comments or something. —TheDJ (talkcontribs) 07:31, 9 July 2018 (UTC)

Consultation on the creation of a separate user group for editing sitewide CSS/JS[edit]

On the contrary, I think this is a fairly huge change that more administrators and the enwiki community at large should take an interest in. Killiondude (talk) 19:57, 9 July 2018 (UTC)
Eh, I don't know about that. I read the page (and the talk page), and the gist seems to be that the local bureaucrats will be able to assign the "delete the Main Page" button separately from the "install malware" button. We might choose to have an "WP:RFJS" to go alongside WP:RFA, but we're still the ones deciding who gets which rights. It doesn't seem like a big deal to me. WhatamIdoing (talk) 02:38, 12 July 2018 (UTC)

User:Filpro's Indian English script[edit]

Why doesn't this script work anymore? This is the one in question: importScript( 'User:Filpro/script/IE.js' ); // Backlink: User:Filpro/script/IE.js --Kailash29792 (talk) 11:16, 9 July 2018 (UTC)

The user was recently renamed, that is probably what broke the script. –Ammarpad (talk) 11:35, 9 July 2018 (UTC)
So is there a way to fix this? --Kailash29792 (talk) 04:59, 10 July 2018 (UTC)
The actual script is now at User:फ़िलप्रो/script/EN-IN.js, so
importScript( 'User:फ़िलप्रो/script/EN-IN.js' ); // Backlink: [[User:फ़िलप्रो/script/EN-IN.js]]
should work. The other titles form a weird chain of redirect-like pages: User:Filpro/script/IE.js points to User:फ़िलप्रो/script/IE.js, which points to User:Filpro/script/EN-IN.js, which finally points to User:फ़िलप्रो/script/EN-IN.js. This makes the first two double redirects of sorts (not sure if there's such a thing when it comes to JS pages), which might be why the script you've changed it to fails. SiBr4 (talk) 08:59, 10 July 2018 (UTC)
After trying to install the various aliases, it appears even the "single redirect" User:Filpro/script/EN-IN.js fails, so the problem may not be the redirect chaining, but some of the redirects themselves. The raw JS files for User:Filpro/script/EN-IN.js and User:Filpro/script/IE.js give a "Forbidden" error, saying "For security reasons JavaScript, CSS and JSON user subpages cannot be loaded for unregistered users". User:फ़िलप्रो/script/IE.js successfully imports User:Filpro/script/EN-IN.js, which then fails as above. The actual script User:फ़िलप्रो/script/EN-IN.js seems to work, though. SiBr4 (talk) 09:15, 10 July 2018 (UTC)
@Kailash29792, Ammarpad, and SiBr4: The #REDIRECT [[...]] directive is a MediaWiki thing, for use on pages containing Wiki markup. .js pages are not intended to be written in Wiki markup (although certain templates and links are processed, silently). This directive is not valid JavaScript, so when your browser is served such a page, it will not be processed. One of several things could happen, depending upon your browser and its configuration: it might ignore the page entirely; it might throw a clear and helpful error message; it might throw a cryptic and unhelpful error message; it might crash the page. --Redrose64 🌹 (talk) 23:11, 10 July 2018 (UTC)
So, what is the resolution? What should I do? I've amended the script on my common.js to User:फ़िलप्रो/script/EN-IN.js. Kailash29792 (talk) 04:00, 11 July 2018 (UTC)
@Redrose64:: the #REDIRECT is within a /* */ comment on each page, so it shouldn't break the JS (that MediaWiki actually correctly processes that as a redirect without a link in square brackets, at least for User:फ़िलप्रो/script/IE.js, was new to me, though). I'd tried copying the contents of User:Filpro/script/EN-IN.js into my JS and it worked, it's just that importing the script doesn't.
@Kailash29792: If User:फ़िलप्रो/script/EN-IN.js works, nothing. The "redirects" might need to be edited to work (both Filpro aliases are still used by a few users), but I'm not yet sure how, and JS pages can only be edited by admins and the owner of the userspace. SiBr4 (talk) 09:38, 11 July 2018 (UTC)
फ़िलप्रो, your attention is needed here. Kailash29792 (talk) 09:53, 11 July 2018 (UTC)
The users of the script have been notified. I think it's best to delete all those redirects and so they've been nominated for deletion. फ़िलप्रो (talk) 17:06, 11 July 2018 (UTC)
फ़िलप्रो, nothing has changed. Can you please enter my common.js page and see if I put it correctly? Kailash29792 (talk) 04:37, 12 July 2018 (UTC)
Kailash29792, your common.js seems to be correct. Try pressing Ctrl + F5 or clearing your cache. If that doesn't work try replacing "User:फ़िलप्रो/script/EN-IN.js" with "User:%E0%A4%AB%E0%A4%BC%E0%A4%BF%E0%A4%B2%E0%A4%AA%E0%A5%8D%E0%A4%B0%E0%A5%8B/script/EN-IN.js". Let me know if the problem still persists. Thanks. फ़िलप्रो (talk) 05:03, 12 July 2018 (UTC)
Still nothing. It briefly worked in a draft article, but never again. On User:फ़िलप्रो/script/EN-IN.js, I find one instance of User:Filpro/EN-IN. Maybe that's the code? Or Chrome and Firefox (my primary browsers) no longer support your script? Kailash29792 (talk) 05:21, 12 July 2018 (UTC)

Bug in citation toolbar feature[edit]

Animated GIF demonstrating the bug

I'm using Monobook on Firefox. There's a bug in the citation widget, the one that's in the toolbar that appears above the editing area, the one that's triggered by clicking a button that looks like {{CITE}}. When doing a book citation and you change the date format, the value of the access date increments by one day, as shown in the animated GIF here. Not only that, but if you're at the end of the month, it will create invalid date values (e.g., July 32). I would fix it myself except I don't know where this code lives. Thanks. howcheng {chat} 17:29, 9 July 2018 (UTC)

Your file shows a feature of RefToolbar 1.0 at Wikipedia:RefToolbar, so you must have disabled "Enable enhanced editing toolbar" at Special:Preferences#mw-prefsection-editing. It's enabled by default. I tried to disable it but I cannot reproduce your problem. The date format changes without changing the date for me. I also use Firefox and tried in MonoBook. Can you try with a blank User:Howcheng/monobook.js? Logged out users have another toolbar so you cannot test it by logging out. Do you have any time-manipulating browser add-ons in Firefox? PrimeHunter (talk) 21:07, 9 July 2018 (UTC)
@PrimeHunter: Thanks for pointing me in the right direction. This is what I found in MediaWiki:RefToolbarLegacy.js in the function formatDate:
  else if (/^\d\d? \w+ \d\d\d\d$/.test(datein) || /^\w+ \d\d?, \d\d\d\d$/.test(datein)) {
    var DT = new Date(datein);
    year = DT.getUTCFullYear();
    month = DT.getUTCMonth()+1;
    date = DT.getUTCDate()+1;
It looks to me like when the date format is dmy or mdy, the script is adding one to the date value, which corresponds with the behavior I'm seeing. howcheng {chat} 06:53, 10 July 2018 (UTC)
It's a time zone issue. DT.getUTCDate() apparently assumes DT is local time for the browser (not the Wikipedia preference) at midnight and converts it to UTC. I'm at UTC+2. 28 September 2000 in your example is assumed to be 28 September 2000 00:00:00 local time. For me that means 27 September 2000 22:00:00 UTC, so DT.getUTCDate()+1 returns 27+1 = 28 which is correct. Your user page says California so your browser time is probably UTC−9. 28 September 2000 00:00:00 local time converted to UTC is 28 September 2000 09:00:00. DT.getUTCDate()+1 returns 28+1 = 29 which is wrong. The script was made by Kaldari who is also in California so I'm not sure why it says +1. Using getFullYear, getMonth and getDate instead of the UTC functions and dropping +1 for date should fix the bug. getUTCMonth and getMonth always return 0 to 11 so +1 is still needed for month. PrimeHunter (talk) 12:21, 10 July 2018 (UTC)
I suspected time zone. Yeah it's weird because the if block for ymd format (right above this one) just uses regex to parse the numeric values as-is without any time zone conversion. I've also never understood why the month value is zero-based. Just creates headaches for developers IMHO. Is there a sandbox version of this file I can apply the fix to? I also may not have access to edit the actual file given the new permissions limitations (as per a post below). howcheng {chat} 15:44, 10 July 2018 (UTC)
The planned edit limitation on sitewide CSS/JS is probably around four weeks away. PrimeHunter (talk) 20:15, 10 July 2018 (UTC)
@Howcheng and PrimeHunter: I think it should be fixed on Can you try it there and make sure everything's working correctly? If so, ping me, and I'll copy it over to English Wikipedia. Kaldari (talk) 21:19, 10 July 2018 (UTC)
@Kaldari: I can't figure out how to disable reftoolbar 2.0. howcheng {chat} 03:58, 11 July 2018 (UTC)
See Wikipedia:RefToolbar#Versions and change testwiki:Special:Preferences#mw-prefsection-editing. You can also disable both toolbars at "Show edit toolbar" and try to load your own JavaScript instead. I haven't tried this for a toolbar. testwiki:MediaWiki:RefToolbarLegacy.js can only be edited by local administrators. See testwiki:Wikipedia:Administrators#Becoming an administrator. PrimeHunter (talk) 10:38, 11 July 2018 (UTC)
@PrimeHunter: Thanks for that. I had been looking in the Gadgets section and couldn't find it. @Kaldari: Confirmed to be working now. Thanks! howcheng {chat} 15:54, 11 July 2018 (UTC)
@Howcheng: Should be fixed now. Thanks for the report! And thanks PrimeHunter for the help debugging! Kaldari (talk) 16:59, 11 July 2018 (UTC)

Transcluding userpages[edit]

Yesterday at ANI, I happened upon an edit where instead of pinging someone, a user accidentally transcluded an entire userpage onto the noticeboard. Searching the archives (at ANI and here) reveals that this is far from the first time this has happened. Is there someway we could try to make it a habit to include <noinclude> and similar code in userpages to prevent this from happening as often? Home Lander (talk) 19:37, 9 July 2018 (UTC)

@Home Lander: how "often" are you seeing this? We could make a filter to at least warn if adding {{User: to a non(user/usertalk) page. — xaosflux Talk 19:44, 9 July 2018 (UTC)
@Xaosflux: Not particularly often, per se, but when it does happen, it tends to break up a noticeboard and can spawn all sorts of pings to users (particularly when lots of barnstars, etc, are on a userpage), who then generally end up here or somewhere else wondering why they were pinged about something that has nothing to do with them. An edit filter sounds like a great idea. Home Lander (talk) 19:48, 9 July 2018 (UTC)
Could display a message like Special:Permalink/849552699. Home Lander (talk) 19:50, 9 July 2018 (UTC)

Bug in Special:BlockList?[edit]

Special:BlockList appears to be synthesizing various bits together from the block log and getting incorrect reads. According to this, Ian.thomson made a checkuser block on July 2 but from the block log, it may be seen that the active block is my CU block made on July 8. Is Special:BlockList borked?
 — Berean Hunter (talk) 19:48, 9 July 2018 (UTC)

Seeing as I'm not a CU, I'd say so. Maybe it's because I'm the original blocking admin and everything since has been changing the reason for the block (rather than starting a new block)? Ian.thomson (talk) 19:56, 9 July 2018 (UTC)
Think you're onto something. Not too familiar with this, but if one of you can find another "changed block settings" instance, where one admin blocked and another changed the settings, it may be the same. Home Lander (talk) 20:00, 9 July 2018 (UTC)
Yes. This block is another incorrect one that has Zzuuzz revoking talk page access but clearly it was Kuru's block. Zzuuzz did the former active block.
 — Berean Hunter (talk) 20:10, 9 July 2018 (UTC)
It looks like this has been broken since 2014 when someone made reblocks update the existing block and no one thought to update the blocker when doing so. Someone should file a task in Phabricator. Anomie 22:32, 9 July 2018 (UTC)
 Done It is T199174. Cheers,
 — Berean Hunter (talk) 01:22, 10 July 2018 (UTC)

Connection issues[edit]

Is anyone else having connectivity issues, particularly when trying to submit an edit? Windows 10 Home, Chrome. Amaury (talk | contribs) 20:39, 9 July 2018 (UTC)

Same setup here, no issues as of now. Home Lander (talk) 20:47, 9 July 2018 (UTC)
@Home Lander: Meant to follow up on Monday. Oops. The problems soon went away. Just to note that any other website was fine while Wikipedia was giving me these issues. Amaury (talk | contribs) 19:27, 11 July 2018 (UTC)

Inverting CSD log[edit]

Hello all, A bit ago I posted at the help desk regarding the possibilty of inverting my CSD log. Nothing came of it, so I did some search on my own and came up dry. What I wish to do is make it so my CSD log displays backwards, e.g.-->: August 2018 then July 2018 then june 2018 etc and also have backwards integers; 70-69-68-67-66 etc. I did some search for mediawiki code, and couldn't find anything, on wiki searches netted useless stuff like this rotation template, but I want the text to be displayed normally. Most logs like the daily AFD and DelReview load this way, and the TeaHouse also did it for a while back. Also, can this be done in such a way as to make Twinkle compliant, rather have TW try to make a new month at the bottom every time I tag something? Thanks, L3X1 ◊distænt write◊ 20:52, 9 July 2018 (UTC)

Need it to display like that for everyone, or just for you? —Cryptic 21:17, 9 July 2018 (UTC)
For me would work, as I am probably the only person who looks at it often, unless politeness or ease of execution would dictate otherwise. Thanks, L3X1 ◊distænt write◊ 21:26, 9 July 2018 (UTC)
The real answer is to make Twinkle support this natively. But since that's unlikely to happen, and at the risk of making real web developers who actually know what they're doing cringe, here's a first approximation: put #mw-content-text ol { display: flex; flex-direction: column-reverse; }
in User:L3X1/common.css to reverse the per-month lists (and break the numbering). Put
$(function(){ if (mw.config.get('wgPageName') == 'User:L3X1/CSD_log') $('#mw-content-text > .mw-parser-output').append($('#mw-content-text > .mw-parser-output > div, #mw-content-text > .mw-parser-output > h3, #mw-content-text > .mw-parser-output > table, #mw-content-text > .mw-parser-output > ol').get().reverse()); });
in User:L3X1/common.js to reverse the order of collapse boxes (both kinds), headers, and lists on the page (and make the headers appear at the ends of their sections instead of the start).
Fixing the numbering and headers isn't impossible, but is a good deal more complex. —Cryptic 22:11, 9 July 2018 (UTC)
Thanks! It worked. Thanks, L3X1 ◊distænt write◊ 22:19, 9 July 2018 (UTC)
@L3X1: More functional (but even more cringe-inducing) version at User:Cryptic/reverse-csd.js. You should remove the above css if you use this. —Cryptic 00:06, 10 July 2018 (UTC)
I swapped to that version because it put the section headings on top which is more helpful. Thanks again for making this code, I appreciate it. Thanks, L3X1 ◊distænt write◊ 01:40, 10 July 2018 (UTC)

Context not appearing on archive talk despite code being present[edit]


Can someone please look at Wikipedia talk:AutoWikiBrowser/Archive 30 particularly the difference between special:diff/836484104 and special:diff/836825128. My edit special:diff/849573836 might also be worth looking at. --Emir of Wikipedia (talk) 22:56, 9 July 2018 (UTC) P.S.: Please ping me in your reply. Thank you.

@Emir of Wikipedia: <nowiki>...</nowiki> was missing around open ref tags. Fixed in [1]. PrimeHunter (talk) 23:11, 9 July 2018 (UTC)
The code worked in the original context, because there was no closing </ref> tag on that page, but broke in the archive when much later a </ref> tag appeared in another comment. So I guess this wasn't a Tidy/Remex thing. --Pipetricker (talk) 10:38, 10 July 2018 (UTC)
Well thanks for your help anyway. I used that archive as a reference for some regex code. --Emir of Wikipedia (talk) 17:40, 11 July 2018 (UTC)

Tech News: 2018-28[edit]

23:09, 9 July 2018 (UTC)

Global preferences came to the Wikipedias today[edit]

See the "Set your global preferences" link on your Preferences page.


This was announced in the Tech News of 29 May to arrive to the Wikipedias later that week, but didn't happen until today. --Pipetricker (talk) 23:50, 9 July 2018 (UTC)

Yeah, it was delayed – there'll be a notice in next Tech News about this. /Johan (WMF) (talk) 23:53, 9 July 2018 (UTC)
There's also a plan for a separate announcement tomorrow. /Johan (WMF) (talk) 23:55, 9 July 2018 (UTC)
Indeed, announcements are going out now. After the delays in getting this released to all wikis, the Community Wishlist team wanted to make sure global preferences would not have to be reverted again before announcing. Keegan (WMF) (talk) 19:27, 10 July 2018 (UTC)

Visual Editor (beta "New wikitext mode") forced on?[edit]


Some time between last night and this morning VE came on as the default editor (talk and non-talk pages) for me, for no apparent reason. I have not logged out or back in again, nor did I change any preferences. Not sure how to turn it off again.  — SMcCandlish ¢ 😼  20:19, 9 July 2018 (UTC)

Special:Preferences#mw-prefsection-editing has options. PrimeHunter (talk) 21:17, 9 July 2018 (UTC)
The only applicable one seems to be "Temporarily disable the visual editor while it is in beta", which I have checked. Having no effect. I did a logoff-login routine. Still getting VE everywhere. I wouldn't mind it except for the gross inefficiency of having to to top-right to click on "Publish changes" to do anything.  — SMcCandlish ¢ 😼  21:55, 9 July 2018 (UTC)
You don't actually have the VisualEditor but the 2017 wikitext editor. Disable "New wikitext mode" and "Automatically enable all new beta features" at Special:Preferences#mw-prefsection-betafeatures. PrimeHunter (talk) 22:26, 9 July 2018 (UTC)
Ah. I had to go to Special:Preferences#mw-prefsection-betafeatures, turn on "Set a local exception for this global preference" at page top, then turn off "New wikitext mode". Something seems to have changed in how the global prefs are managed. I haven't made any changes to mine in over a week.  — SMcCandlish ¢ 😼  22:35, 9 July 2018 (UTC)
I guess you have to change Special:GlobalPreferences#mw-prefsection-betafeatures if you don't want "New wikitext mode" at any wiki. PrimeHunter (talk) 22:52, 9 July 2018 (UTC)
Hmmm if true, that is not likely to be intentional. Someone should file a ticket about that asap. —TheDJ (talkcontribs) 03:25, 10 July 2018 (UTC)
SMcCandlish, is it possible that you may have set the global "New wikitext mode" from another wiki such as Wiktionary or Test Wiki at an earlier time? --Pipetricker (talk) 07:53, 10 July 2018 (UTC)
Yes, I may have monkeyed around with global user prefs stuff, over at Meta, but it shouldn't have an unexpected effect a week or two later.  — SMcCandlish ¢ 😼  08:09, 10 July 2018 (UTC)
Oh, that would explain it.  — SMcCandlish ¢ 😼  08:11, 10 July 2018 (UTC)
@TheDJ: I only meant that SMcCandlish had probably changed Special:GlobalPreferences#mw-prefsection-betafeatures and if he doesn't want to make a local exception at each wiki he edits then he should change it back. I didn't mean that the local exceptions don't work. They do work. PrimeHunter (talk) 10:26, 10 July 2018 (UTC)

Sec Warning coming up on Chrome[edit]

I am having the sec warning: coming up when using Chrome. I have cleared all my data to see if it is being triggered by a cookie. Also have the newest update of Chrome. It is only from this one machine/user profile. — Preceding unsigned comment added by (talk) 13:59, 10 July 2018 (UTC)

Company firewall or other type of proxy service installed somewhere perhaps ? —TheDJ (talkcontribs) 14:21, 10 July 2018 (UTC)

Other users are able to access it from the same network segment so does not appear to be firewall or proxy. — Preceding unsigned comment added by (talk) 14:45, 10 July 2018 (UTC)

(edit conflict) Running Chrome here without issues on Windows 10 Home. IP, what version of Windows is that machine running? Home Lander (talk) 14:46, 10 July 2018 (UTC)

Chrome version 67 (32bit) — Preceding unsigned comment added by (talk) 14:47, 10 July 2018 (UTC)

That's my Chrome version too, but I'm on the 64-bit. Which version of Windows are you running? Home Lander (talk) 14:51, 10 July 2018 (UTC)

For this particular group of users, Windows 7 32-bit. From the same group, other users are not getting the warning, only one user. Which leads me to believe it is something in her profile, however, i have cleared all her IE/Chrome settings/cookies. Short of resetting her entire user profile (not optimal), not sure what could be causing it. — Preceding unsigned comment added by (talk) 14:55, 10 July 2018 (UTC)

It did end up being a firewall issue for that particular user. They were getting the wrong certificate. Thanks for all the help. — Preceding unsigned comment added by (talk) 15:03, 10 July 2018 (UTC)

Self-links not bolded in certain viewing configurations[edit]

It's come to my attention that self-links aren't displayed in bold in some viewing configurations. For me, if I go to Saurophaganax in mobile mode (using Firefox on a desktop computer), in the taxobox line for genus, Saurophaganax is in non-bold black text, and when I hover the cursor over it, it gets underlined, but is not clickable. I've tested this a little and have seen similar behavior with other self-links in mobile mode. I know self-links aren't very common, but they are generated when {{Speciesbox}} or {{Automatic taxobox}} is used with a monotypic taxon. Another editor brought this to my attention, but they experienced it in non-mobile mode with Firefox, but not with Chrome.Plantdrew (talk) 19:12, 11 July 2018 (UTC)

What skin are you using? Besides that, the task for this is phab:T192033. --Izno (talk) 19:25, 11 July 2018 (UTC)
I've got Vector in my preferences. I don't typically view Wikipedia in mobile mode, but I guess I'm using Vector there as well (or whatever the default is). Plantdrew (talk) 19:39, 11 July 2018 (UTC)
@Plantdrew: If you're viewing the mobile website, you're probably using mw:Skin:Minerva Neue. The mobile website ignores your non-mobile skin preferences. --Ahecht (TALK
) 20:23, 11 July 2018 (UTC)

Can't delete page[edit]

I've been having some trouble with the bar (don't know the name of it) across the near top of a page, the one to the left of the Search Wikipedia box. Certain items don't show up at all, or the drop-downs don't have certain items. In this instance, the Page drop-down doesn't have Delete or delete page or whatever it normally says. I've tried refreshing. I've tried logging out and back in. While I'm here, is there another way to delete the page besides that drop-down? Thanks.--Bbb23 (talk) 01:31, 12 July 2018 (UTC)

Copy the url for the history page and replace "action=history" with "action=delete". —Cryptic 01:34, 12 July 2018 (UTC)
If you have a Page drop-down then I guess you enabled MoreMenu at Special:Preferences#mw-prefsection-gadgets. What is your skin at Special:Preferences#mw-prefsection-rendering, and what is your browser? Did you check whether Delete is under a "More" tab? Do you get Delete under a "More" tab if you disable MoreMenu? PrimeHunter (talk) 02:05, 12 July 2018 (UTC)
Thank you Cryptic; that worked. @PrimeHunter: Vector and Chrome. Delete is not under More. I disabled MoreMenu and delete is now under More. I'm still puzzled why the Page item disappeared.--Bbb23 (talk) 02:21, 12 July 2018 (UTC)
MoreMenu is JavaScript and scripts often have problems, sometimes causing other scripts to fail. It works for me. Does MoreMenu work if you preview a blank version of User:Bbb23/vector.js? PrimeHunter (talk) 02:40, 12 July 2018 (UTC)
Sorry for the late response, PrimeHunter, but I had to get off-wiki last night and couldn't continue this dialog. I'm not sure what you want me to try. I remove all the material from vector.js, click on Show preview, and then see if the Page drop-down has a delete item? Maybe I'm misunderstanding.--Bbb23 (talk) 12:01, 12 July 2018 (UTC)
Exactly. I'm wondering whether one of your user scripts is interfering. This way you can test it without having to actually save another version of your vector.js. If you preview a user js or css page then the previewed version runs instead of the saved version. You can also save an empty js page if you want but the test doesn't require it. PrimeHunter (talk) 12:13, 12 July 2018 (UTC)
No delete item in Page drop-down after Show preview. I know Chrome updates frequently. Could an update have caused the problem? I can tell you the latest version if that helps.--Bbb23 (talk) 12:44, 12 July 2018 (UTC)

────────────────────────────────────────────────────────────────────────────────────────────────────This sounds like Wikipedia:Village pump (technical)/Archive 164#Lost the delete button. I'm baffled how this can happen. Bbb23 I know this is a lot to ask, but could you please do the following:

  • In Chrome, go to View > Developer > JavaScript console
  • Run the code localStorage.mmUserRights.contains("delete"). This should return true
  • Also run localStorage.mmCacheDate and let me know what it says.

Doing this will help me figure out what's going wrong, and hopefully fix this bug once and for all. Many many thanks MusikAnimal talk 18:19, 12 July 2018 (UTC)

@MusikAnimal: There is no View in my Chrome.--Bbb23 (talk) 18:27, 12 July 2018 (UTC)
@Bbb23: Oh sorry. To get to the JavaScript console, try step #6 at WP:JSERROR. The keystroke for you is probably Ctrl+⇧ Shift+J MusikAnimal talk 18:29, 12 July 2018 (UTC)
  • @MusikAnimal: When I do that, I get: ... (removed) ... I couldn't format it nicely, so I did the best I could, which ain't great. I didn't do anything after that because all of those incomprehensible error messages made me very nervous. I have no clue what we're doing.--Bbb23 (talk) 18:40, 12 July 2018 (UTC)
    @Bbb23: Hehe no worries, sorry to make you do this! I actually need you to run this code, individually:
  • localStorage.mmUserRights.contains("delete")
  • localStorage.mmCacheDate
And let me know what those say. Thank you so much! MusikAnimal talk 18:55, 12 July 2018 (UTC)
  • @MusikAnimal: Don't think this is what you were expecting:
    VM136:1 Uncaught TypeError: localStorage.mmUserRights.contains is not a function at <anonymous>:1:27 (anonymous) @ VM136:1
    --Bbb23 (talk) 19:00, 12 July 2018 (UTC)
    @Bbb23: Okay one more thing, run: localStorage.mmUserRights.indexOf("delete") !== -1. It should return true. Also, what version of Chrome are you using? MusikAnimal talk 19:04, 12 July 2018 (UTC)
    @MusikAnimal:. Do the returns on these commands or whatever they are really help you in this instance? Doesn't seem to work at all. But:
    localStorage.mmUserRights.indexOf("delete") !== -1
    VM126:1 Uncaught TypeError: Cannot read property 'indexOf' of undefined at <anonymous>:1:27
    Chrome Version 67.0.3396.99 (Official Build) (64-bit). I am now off to eat at a Chinese restaurant. May not be what NYC has to offer, but it's what we've got here in the hinterlands, and it's surprisingly good. Bon appetit to me.--Bbb23 (talk) 19:12, 12 July 2018 (UTC)
    They are sort of helpful, but indeed they are not returning what is expected. Do you still have MoreMenu turned on? If not, please turn it on, and run localStorage.mmUserRights.indexOf("delete") !== -1 once more. The result from the last command you ran doesn't make sense. In short, clearing your cache should resolve your issue, but I was trying to figure out what was stored in the cache before you cleared it. Oh well. I'll do some more investigation on my own and let you know if I figure anything out. Enjoy your dinner! :) MusikAnimal talk 19:31, 12 July 2018 (UTC)
    I had MoreMenu enabled. Lunch. Thank you for trying to help. I'm hoping it does what inexplicable software problems often do: go away on its own.--Bbb23 (talk) 20:44, 12 July 2018 (UTC)
    So let it be written, so let it be done.--Bbb23 (talk) 02:06, 13 July 2018 (UTC)
    @Bbb23: So it is working for you now? :) If not, WP:BYPASS should fix it. Cheers MusikAnimal talk 16:56, 13 July 2018 (UTC)
    @MusikAnimal: I didn't do a thing. It just started working again yesterday evening and continues to work now.--Bbb23 (talk) 17:04, 13 July 2018 (UTC)
    Well as you reported above, the cache expiry (mmCacheDate) was 1531427563594 in Unix time, which equates to 8:32, 12 July 2018 (UTC) -- around the time you said it magically started working again. That tells me the issue must be cache-related. This is very helpful. I now have some theories as to what might have happened. I'll get to work! Thank you again MusikAnimal talk 17:30, 13 July 2018 (UTC)

Help me Bypass my cache[edit]

I added some userscripts recently in my common.js but I saw no effect on my experience. There I saw one notification stating:

Note: After saving, you may have to bypass your browser's cache to see the changes.
Firefox / Safari: Hold Shift while clicking Reload, or press either Ctrl-F5 or Ctrl-R (⌘-R on a Mac)
Google Chrome: Press Ctrl-Shift-R (⌘-Shift-R on a Mac)
Internet Explorer: Hold Ctrl while clicking Refresh, or press Ctrl-F5
Opera: Go to Menu → Settings (Opera → Preferences on a Mac) and then to Privacy & security → Clear browsing data → Cached images and files.

I use Google chrome for the purpose but I'm on a mobile ! So these notifications proved useless to me.

One of my wiki friends mentioned me to put my query here. So I'm here to ask for your help. Please see!

ARKA (talk) 06:33, 12 July 2018 (UTC)

See this for iOS and this for android. Ruslik_Zero 06:36, 12 July 2018 (UTC)
Thanks but I did it earlier and now as well! No change!

ARKA (talk) 07:08, 12 July 2018 (UTC)

@Dr. Sroy: Many interface features are only in the desktop version of the site. Click "Desktop" at the bottom of a page to switch. PrimeHunter (talk) 10:48, 12 July 2018 (UTC)
@PrimeHunter:Ok trying!

ARKA (talk) 10:51, 12 July 2018 (UTC)

Oh man great! It works! Thanks PrimeHunter! — Preceding unsigned comment added by Dr. Sroy (talkcontribs) 10:53, 12 July 2018 (UTC)

Installation of Twinkle[edit]

Hi there again!

Another problem I seem to have is that I can't install Twinkle to my preference. I had checked the box for Twinkle in my User Preferences(in the Gadget tab, under the Browsing section the checkbox for Twinkle) long ago! But I see no change.

Help me with please!

ARKA (talk) 06:33, 12 July 2018 (UTC)

@Dr. Sroy: Is Javascipt enabled for your browser? If not, see instructions here. Abecedare (talk) 06:59, 12 July 2018 (UTC)
@Abecedare:Yes!ARKA (talk) 07:02, 12 July 2018 (UTC)
@Abecedare:Problem solved! Twinkle enabled!

It only works in the desktop site! — Preceding unsigned comment added by Dr. Sroy (talkcontribs) 11:32, 12 July 2018 (UTC)

Reminder: No editing 06:00–06:30 AM (UTC), 18 July[edit]

As previously stated here in June, English Wikipedia will be read-only for up to 30 minutes (06:00 AM to 06:30 AM UTC) on 18 July because of maintenance work. Everyone will be able to read it, but you can’t edit. If everything goes well, this should just take a few minutes, but prepare for 30 minutes to be on the safe side. I'd suggest some kind of banner to warn all editors, but I think it's up to the English Wikipedia community to decide.

You can read more in the tasks linked to from phab:T197134. /Johan (WMF) (talk) 07:46, 12 July 2018 (UTC)

Alternatively (or in addition) to a banner for logged in users, in the past, some wikis decided to put a warning/reminder on the recentchanges page. Up to you. JCrespo (WMF) (talk) 08:25, 12 July 2018 (UTC)
Maybe list this at CENT for a day? I have no idea how hard it is to cook up a banner, but personally I think something official doesn't need community rubber stamping for a helpful notice. Thanks, L3X1 ◊distænt write◊ 01:40, 13 July 2018 (UTC)
I just reread CENT, it seems they don't want this put there, and recommend P:WP, however that looks fairly dead, so if no one else has been bold, I will put up a {{centralized discussion}} tomorrow morning.Thanks, L3X1 ◊distænt write◊ 01:43, 13 July 2018 (UTC)
I didn't even know P:WP existed. Natureium (talk) 19:19, 13 July 2018 (UTC)
That's the trouble with Portal space - not enough awareness. That is, other than the little boxes that get added to certain places, such as the "See also" sections of articles; the top of category pages; and inside WikiProject banner templates. --Redrose64 🌹 (talk) 09:12, 14 July 2018 (UTC)
P:WP is a redirect to Wikipedia:Community portal which is not a Wikipedia:Portal. It's linked in the left pane and had 346,486 views in the past 30 days. PrimeHunter (talk) 10:26, 14 July 2018 (UTC)
Not all portals are the content-related types found in Portal: space. There are also a handful of project-related portals in both the Portal: and the Wikipedia: namespaces. — AfroThundr (u · t · c) 19:07, 14 July 2018 (UTC)
  • I would be happy for this to be put up publically for logged-in users for the 24 hours before it occurs. Nosebagbear (talk)
    • For users in the United States, that’s 2:00A–2:30A Eastern and 11:00P–11:30P Pacific. — pythoncoder  (talk | contribs) 19:58, 13 July 2018 (UTC)

Per the Cent instructions, this discussion being listed on Centralized discussion looks like it is perhaps a (misplaced) notification of this discussion, and not a notification of the upcoming read-only event.

But any way, I think the proper way to announce the read-only time to everyone who is editing this wiki (including those not logged in), and not just to those who read Cent or the Community portal, would be a MediaWiki:Sitenotice. (Examples: one of the more recent uses on this wiki, use on testwiki.)

I think it would make sense to put up a final warning maybe 15 minutes before going read-only, and an earlier warning a couple of hours before that. --Pipetricker (talk) 01:09, 16 July 2018 (UTC)

Hmm, looks like CentralNotice inhibits the use of MediaWiki:Sitenotice:
mw:Manual:Interface/Sitenotice says:
1. If the CentralNotice extension is enabled, it is displayed (even if not defined); see below.
The CentralNotice extension supersedes all other notices.
Do I understand that correctly? And if so, can CentralNotice be used? --Pipetricker (talk) 07:45, 16 July 2018 (UTC)
I asked at the phabricator task whether there will be a $wgReadOnly message displayed during the read-only time. --Pipetricker (talk) 09:22, 16 July 2018 (UTC)
At Phabricator, Marostegui wrote:
It will show: Scheduled maintenance on enwiki from 06:00-06:30 UTC. Database in read-only mode.
(And now I'm going off-line for a couple of weeks.) --Pipetricker (talk) 09:48, 16 July 2018 (UTC)

While you've all got your calendars out[edit]

Please make a note that there will probably be another round of server switch testing in a few months, with the attendant read-only time. Current best guess is "switch to" in mid-to-late September and "switch back" three weeks later, in October. There will naturally be about a hundred reminders between now and then. Face-wink.svg Whatamidoing (WMF) (talk) 23:03, 13 July 2018 (UTC)

PNGs don't scale? Or am I doing something wrong?[edit]

If I write [[File:Westminstpalace.jpg|300px]]/[[File:Zeta_bootis_short_exposure.png|300px]], I get

Westminstpalace.jpg Zeta bootis short exposure.png

Everything is peachy. But if I write [[File:Westminstpalace.jpg|300px|thumb]]/[[File:Zeta_bootis_short_exposure.png|300px|thumb]] I get

Zeta bootis short exposure.png

What gives? Headbomb {t · c · p · b} 12:26, 12 July 2018 (UTC)

Thumbnails cannot be scaled above the original size. File:Zeta bootis short exposure.png is 98 × 92 pixels. [[File:Zeta_bootis_short_exposure.png|300px]] is not a thumbnail so it works there but thumb features cannot be used. PrimeHunter (talk) 12:54, 12 July 2018 (UTC)
Well that's dumb. Frame doesn't work either. Headbomb {t · c · p · b} 18:34, 12 July 2018 (UTC)

Watchlist problems again[edit]

When I bring up my watchlist, it shows articles changed in the past 3 days by default. But the "Period of time to display" drop-down is populated with "1 hour" by default, so that if I click the "Show" button on my watchlist page to refresh it, I only get 1 hour's worth of changes unless I specifically change the drop down. It always resets to 1 hour, even though my preferences are set to 3 days. (IE 11 (sorry -- required by work!), MonoBook skin) WikiDan61ChatMe!ReadMe!! 15:13, 12 July 2018 (UTC)

Error deleting file: inconsistent state within the internal storage backends[edit]

I'm getting the following error when trying to delete File:Mariko Silver Portrait 2014 1.jpg under F8. Anyone know how to fix this? Thanks, FASTILY 19:18, 12 July 2018 (UTC)

  • FWIW, I've just tried to delete it as well, and still get the same message, so it's not something temporary. Black Kite (talk) 23:16, 12 July 2018 (UTC)
  • Thanks for taking a look. I've filed a bug report: phab:T199499. -FASTILY 04:47, 13 July 2018 (UTC)

Central login[edit]

Why is central login not working for Wikidata too? And could someone connect Translatewiki in central login projects (it should be[come] part of Wikimedia, currently is only designated as MediaWiki project)? --Obsuser (talk) 00:14, 13 July 2018 (UTC)

Not sure what you mean by Central login not working for Wikidata since Special:CentralAuth/Obsuser shows Wikidata connected and in fact you edited there few hours ago. Translatewiki is also running on MediaWiki software but it is not part of Wikimedia Foundation projects hence not part of SUL wikis. –Ammarpad (talk) 04:14, 13 July 2018 (UTC)
Sometimes the system don't log in you to all of its projects for some reason. And in some projects it logs you out automatically. Stryn (talk) 06:52, 13 July 2018 (UTC)
Try to delete cookies for PrimeHunter (talk) 10:58, 13 July 2018 (UTC)

Issues uploading audio files to Wikipedia[edit]

I'm trying to upload samples of audio recordings to add to an article I'm working on and am having technical issues.

I've encountered this problem using both the and the

I'm using Chrome version 67.0.3396.99 (Official Build) (64-bit), which it tells me is up to date, and Windows 10.

The problem is, whenever I try to upload an .mp3 file or .ogg file, wikipedia does not recognise them as those extension types. When I try to upload a .mp3 file, it says "".mpga" is not a permitted file type. Permitted file types are tiff, tif, png, gif, jpg, jpeg, webp, xcf, pdf, mid, ogg, ogv, svg, djvu, oga, flac, opus, wav, webm, mp3." When I attempt to upload a .ogg file, it says "".ogx" is not a permitted file type. Permitted file types are tiff, tif, png, gif, jpg, jpeg, webp, xcf, pdf, mid, ogg, ogv, svg, djvu, oga, flac, opus, wav, webm, mp3."

Now, I've triple checked my files and windows lists them on my screen as .mp3 and .ogg, even when you right click and look at the properties, they say .mp3 and .ogg, NOT .mpga and .ogx

So my computer is telling me they are the right type of file, but when I attempt to upload them to Wikipedia, Wikipedia believes they are a different type of file. If anyone has any advice for me on how to upload these file, it would be very much appreciated and I'm beginning to go crazy. NicklausAU (talk) 04:18, 13 July 2018 (UTC)

I transferred the exact same files from my laptop to my android phone (still using chrome) and the upload worked without any issues. I guess it's no longer as important, but would still be helpful to know about in the future. NicklausAU (talk) 04:33, 13 July 2018 (UTC)

Infoboxes erroneously wrapped in bold tags[edit]

While investigating some error logs for the mobile web site, I noticed that 170 pages have incorrect formatting which wraps the infobox in a bold or italic tag. e.g.

'''{{Infobox venue... }}
'''Subject title'' is defined in this line.

I'm not sure what's causing this problem (maybe a result of new pages being copy and pasted or edit conflicts?). I've made a few fixes myself (see Special:Contributions/Jdlrobson but obviously me manually fixing these isn't the most sustainable of ideas!

Can we get this fixed via a bot?

You can use this query] to find pages with the problem.

Jdlrobson (talk) 15:18, 13 July 2018 (UTC)

@Jdlrobson: Wallace Wade Stadium was the first page that showed up in the search, and I cleaned it up. My guess is the infobox on some articles may have been inserted after the bulk of the articles may have already been written and it was accidentally inserted after the bold string for the title. Not all of the articles listed seem to visually have issues - Brisbane, California looks normal, for example. Home Lander (talk) 15:54, 13 July 2018 (UTC)
I don't think it's quite straightforward to fix these with a bot, as many have other underlying formatting issues as well that didn't show up until the switch from html4-tidy to RemexHtml earlier this month. A lot of them do seem like they were articles started by copying and pasting another (especially the ones on ethnic groups and on rugby and football teams), and the errors are just showing up now due to Remex. I've started going through them with AWB, but each one needs a bit of manual processing. --Ahecht (TALK
) 16:17, 13 July 2018 (UTC)
Fixed. These are all fixed now, if the insource search is working. – Jonesey95 (talk) 19:01, 13 July 2018 (UTC)

Edits are lost when changing from VisualEditor to regular editor[edit]

It seems like when I start editing an article in VisualEditor (e.g to add citations) and then change in source editor mode, the changes don't carry over between the edit windows. Jo-Jo Eumerus (talk, contributions) 17:11, 13 July 2018 (UTC)

It works fine for me, in both directions.. -- RoySmith (talk) 19:11, 13 July 2018 (UTC)
What browser, operating system, skin? --Izno (talk) 19:56, 13 July 2018 (UTC)
Firefox latest, Windows 10 and Vector. Jo-Jo Eumerus (talk, contributions) 21:51, 13 July 2018 (UTC)
Jo-Jo Eumerus, does this happen every time? If you make multiple changes (e.g., to different parts of the article), do you lose all of your work, or just some of it? Whatamidoing (WMF) (talk) 23:09, 13 July 2018 (UTC)
It seems like the issue happens when I try to change through the header buttons (these next to the "view history" button). Formerly then the page changed over with a you have changed the editing mode flag and kept previous edits. Now instead I get the "some changes may not be saved if you leave this page" popup and the edits done in the previous editing mode don't stay. Jo-Jo Eumerus (talk, contributions) 12:24, 14 July 2018 (UTC)
Thanks. I've filed a bug. Since your first edits are from 2012, I'm going to assume that you are using the 2010 wikitext editor. Whatamidoing (WMF) (talk) 21:26, 15 July 2018 (UTC)

Templates do not show up in mobile view Suggestion[edit]

Hi! I've recently noticed that templates that are at the bottom of articles like this one Template:Woman's club movement, don't show up in mobile view. Is there any way that we can correct that? I find the templates useful for navigation and would like to use it on my phone. (I have an Android.) Megalibrarygirl (talk) 22:18, 13 July 2018 (UTC)

Navigational templates have class="navbox" and are deliberately omitted from the mobile version. You can click "Desktop" at the bottom of mobile pages to see the desktop version. PrimeHunter (talk) 00:53, 14 July 2018 (UTC)
Time we put this in Wikipedia:Village pump (technical)/FAQ. --Redrose64 🌹 (talk) 12:57, 14 July 2018 (UTC)
Hi! PrimeHunter! I know I can switch to Desktop to see the template, but I think that the mobile view should encompass a view for templates, too. What can we do about that? Redrose64 do you think there is a way to make a proposal to fix this? I think it's important to do since more and more people access Wikipedia in mobile version nowadays. :) Megalibrarygirl (talk) 18:42, 14 July 2018 (UTC)
It's done on purpose to reduce bandwidth usage and page size for mobile users. Many articles have a lot of losely connected navigation templates. They wouldn't be collapsible in mobile, and their width is not designed for narrow screens. Maybe there should be an option to display them without switching to desktop but they are currently not transmitted at all in mobile so it would require a change in the software for the mobile version. This is outside control of the English Wikipedia. phab:T124168 ("Show Navbox templates in mobile skins") has a proposal. I don't know whether it's the primary discussion. PrimeHunter (talk) 19:06, 14 July 2018 (UTC)
Thanks for the answer, PrimeHunter! That makes sense and I understand better why templates wouldn't show up. Megalibrarygirl (talk) 22:37, 15 July 2018 (UTC)

Transparent png files[edit]

Is there a limit to the dimensions of a png file above which transparent pixels are rendered as white? I've created a lot of png 'cut-outs' over the years, normally small logos and such for use in infoboxes, but recently I've had a couple of fairly large png files that don't render as transparent. The most recent one is File:Trump baby balloon.png (975 × 1,000 pixels, file size: 775 KB). I can't remember the other, but it was fairly large IIRC. nagualdesign 04:44, 14 July 2018 (UTC)

@Nagualdesign: There is a bug that was recently introduced into the mediawiki software that breaks PNG transparency in thumbnails. It's been reported at T198370, but no developers have responded to even triage it, and fixing it seems to not be a priority. --Ahecht (TALK
) 14:11, 14 July 2018 (UTC)
@Ahecht: Okay, thanks for the reply. I was going to reduce the dimensions of the image but I'll just leave it be. Cheers. nagualdesign 14:36, 14 July 2018 (UTC)

Script problem[edit]

I was recently developing a script at User:FR30799386/Actiontog.js based on MediaWiki:Gadget-MobileCategories.js (I have some experience very limited experience with coding). I tried the whole script out on my browser console and the script worked perfectly, but when I try to run it on-wiki the script does not produce any result. Can anybody help out ?12:49, 14 July 2018 (UTC)

User:FR30799386/common.js says:
//importScript('User:FR30799386/MOSDDT.js'); //Linkback: [[User:FR30799386/Actiontog.js]] Added by Script installer
Everything on a line after // is a JavaScript comment. The line should say:
importScript('User:FR30799386/Actiontog.js'); //Linkback: [[User:FR30799386/Actiontog.js]] Added by Script installer
The imported page is determined by importScript. The linkback comment is just a way to affect Special:WhatLinksHere/User:FR30799386/Actiontog.js. To avoid confusion, importScript and a linkback comment should always refer to the same page. The different page names were made by you [15] and not Script installer. PrimeHunter (talk) 13:03, 14 July 2018 (UTC)
PrimeHunter, I loaded the script into my User:FR30799386/minerva.js, anticipating that the mobile skin would override my common.js (Which I believe it does) — FR+ 13:08, 14 July 2018 (UTC)
P.S. I am aware about that anomaly in my common.js, but I don't think that is causing the issue right now.Face-smile.svg — FR+ 13:13, 14 July 2018 (UTC)

Template transcluding articlespace categories onto userpages, Vol. 458[edit]

User:Just granpa/Atomic volume and User:Just granpa/Atomic volume (Alternate) are both showing up in Category:Properties of chemical elements by virtue of an artificial transclusion — but I can't find what template is pushing the category in order to get them out, because none of the obvious candidates seem to have that category declaration on them either. Can somebody look into this so the category can be properly cleaned up under WP:USERNOCAT rules? Thanks. Bearcat (talk) 14:26, 14 July 2018 (UTC)

Fixed. The categories were coming from documentation subpages. The subpages were actually holding template code not transluding them. Hence the categories coming from here and here; which are subpages of the categorised subpages. –Ammarpad (talk) 14:59, 14 July 2018 (UTC)
You can enter wikitext at Special:ExpandTemplates and search the result for the category to see where in the page it occurs. Some things are namespace or page name sensitive so you sometimes have to fill out "Context title". PrimeHunter (talk) 16:04, 14 July 2018 (UTC)

\w and \d equivalents in Mediawiki regex?[edit]

I've been trying to wrap my head around how to deal with the lack of \w or \d support in our regex functions. \d is fairly easy to deal around [0-9], but \w is nearly impossible to get around. If you use [A-Za-z], you miss out all the diacritics, as well as all non-Latin characters. What's an equivalent way of replacing \w. Better yet, why don't we support \w or \d? Headbomb {t · c · p · b} 16:07, 14 July 2018 (UTC)

Nevermind, found this. It was buried 230 layers deep in documentation, but it was there. Headbomb {t · c · p · b} 16:10, 14 July 2018 (UTC)
it's not mediawiki regex, it's Lua patterns :) I think I'm not the only one, who was confused by what you asked till I got to reading link title --Edgars2007 (talk/contribs) 15:13, 15 July 2018 (UTC)

Least edited pages[edit]

Is there a database report, or some other place, where one can locate articles (or any pages, for that matter) that have gone the longest time without being edited? Home Lander (talk) 18:07, 14 July 2018 (UTC)

@Home Lander: Special:AncientPages might help, although it mostly lists disambiguation pages. Jc86035 (talk) 18:16, 14 July 2018 (UTC)
Disambiguation pages dominate the list because there's less reason to edit them than articles proper. –Ammarpad (talk) 19:38, 14 July 2018 (UTC)
Wikipedia:WikiProject Abandoned Articles has deliberately edited all the oldest articles at Special:AncientPages. Wikipedia:Database reports/Forgotten articles ignores disambiguation pages. PrimeHunter (talk) 19:46, 14 July 2018 (UTC)

"Some parts of the edit form did not reach the server; double-check that your edits are intact and try again."[edit]

We've just had this question posted by TheTechnician27 at the Teahouse. Can't find anything in recent VPT talk or the archives, so could someone offer a suggestion, please? The text of the question is "Whenever I switch from visual to source editing mode, I get this error message at the top of the page. Additionally, there is no chart showing the difference between the current version and my edit. This had never happened to me, but recently it's happened every time. I get this on two separate computers, and I can't seem to find any information about it. I'd like to find a way to stop this error message from showing up and to get the side-by-side comparison to show up again." Many thanks, Nick Moyes (talk) 20:28, 14 July 2018 (UTC)

@Nick Moyes: The same message generates when using WP:REFILL. I verified this just now on War bride. Load the article, click on Refill, then click "Preview/Save on Wiki" and the message will appear. I left the bare URLs alone on that article so this will continue to work. Home Lander (talk) 20:38, 14 July 2018 (UTC)
I see this message as well when I switch from visual to source editing mode and I also miss the side-by-side comparison. Jo-Jo Eumerus (talk, contributions) 20:40, 14 July 2018 (UTC)
I reported this 2 days ago in phab:T199554. Stryn (talk) 20:03, 15 July 2018 (UTC)
Stryn, or someone, can you add in Phabricator that Refill triggers this also? Home Lander (talk) 20:28, 15 July 2018 (UTC)
I did. Also, the message is MediaWiki:Edit form incomplete, which appears to belong to preview (in the older wikitext editors). Whatamidoing (WMF) (talk) 21:21, 15 July 2018 (UTC)

Can't get pages to show in my template[edit]

I just created a new citation template, Template:BLKO, but I can't seem to get the page or pages parameters to work, and I can't figure out why, so I need some additional eyes on it. Thanks in advance. howcheng {chat} 23:36, 14 July 2018 (UTC)

I don't think that it's your template but rather is a problem with {{cite wikisource}}. This example from the documentation page has |pages=100–110 but that isn't displayed:
{{cite wikisource |last=Bloggs | first=Fred |editor-first=John| editor-last=Doe |plaintitle=Big Book With Many Chapters and distinct chapter authors|publisher=Book Publishers |date=2001-01-01 |pages=100–110 |chapter=Chapter 2: The History Of The Bloggs Family |isbn=123456789X}}
Bloggs, Fred (2001-01-01). "Wikisource link to Chapter 2: The History Of The Bloggs Family". In Doe, John. Big Book With Many Chapters and distinct chapter authors. Book Publishers. Wikisource. pp. 100–110. ISBN 123456789X. 
{{cite wikisource}} uses {{citation/core}} and feeds that template's |At= parameter with a complicated mess of code that includes |page= and |pages= among a whole bunch of other parameters. You might raise the issue at Template talk:cite wikisource; perhaps there is someone there who knows what that mess of code is supposed to do and can see where is is loosing |page= and |pages=.
Trappist the monk (talk) 00:08, 15 July 2018 (UTC)
Just fixed the isbn error at the Template:cite wikisource/doc and did some playing around with the other examples. In the above example, changing |plaintitle= to |title= makes the template render with the pages:
Bloggs, Fred (2001-01-01). "Wikisource link to Chapter 2: The History Of The Bloggs Family". In Doe, John. Wikisource link to Big Book With Many Chapters and distinct chapter authors. Book Publishers. Wikisource. pp. 100–110. ISBN 123456789X. 
Trappist the monk (talk) 00:15, 15 July 2018 (UTC)
I went back and checked my previous usages of {{cite wikisource}} (e.g., Ferdinand III, Holy Roman Emperor § Notes) and you are correct: the page numbers aren't included, so I'll have to take it up at the template talk page. Thanks. howcheng {chat} 03:39, 15 July 2018 (UTC)

Tool idea[edit]

I was just thinking about using Template:Copyvios to build a tool that you can click on each article to see if the article has been copied from other sources, but I don’t have the technical knowledge to do it myself. I was wondering if a tool like that already exists and if not, someone will take it upon themselves to develop one?--▸ ‎épine talk 13:27, 15 July 2018 (UTC)

@Épine: See User:Ahecht/Scripts/CVD. --Ahecht (TALK
) 15:14, 15 July 2018 (UTC)
@Ahecht: thanks but it has issues that I described on the talk page, can you please take a look?--▸ ‎épine talk 18:39, 15 July 2018 (UTC)
I fixed the script so that it defaults to "wikipedia" if the site name is something other than mediawiki, wikibooks, wikidata, wikimedia, wikinews, wikipedia, wikiquote, wikisource, wikiversity, wikivoyage, or wiktionary. See the script's talk page. --Ahecht (TALK
) 20:52, 15 July 2018 (UTC)

Problems with the edit window when there is WikiMarkup color-shading[edit]

Referring to this thread, I still have a problem when I copy and paste text and delete it at the same time. The text doesn't get deleted, I get sent to the start of the edit window, and somehow this happened. Actually, that was my attempt to correct the mistake, and I did it wrong too.— Vchimpanzee • talk • contributions • 17:06, 15 July 2018 (UTC)

Did you notice this error on Chrome or in Firefox or in both? -- Magioladitis (talk) 11:12, 16 July 2018 (UTC)

InternetArchiveBot is malfunctioning[edit]

InternetArchiveBot (v2.0beta2) is malfunctioning and making edits like this. I've reported but the edits continue. --Auric talk 12:22, 16 July 2018 (UTC)