Wikipedia:Village pump (technical)

 Policy Technical Proposals Idea lab WMF Miscellaneous 

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

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. Questions about MediaWiki in general should be posted at the MediaWiki support desk.

« Archives, 120, 121, 122, 123, 124, 125, 126, 127, 128, 129, 130, 131, 132, 133, 134, 135, 136, 137, 138, 139, 140, 141, 142, 143, 144, 145, 146, 147, 148, 149, 150, 151, 152, 153, 154, 155, 156, 157, 158, 159, 160, 161, 162, 163, 164, 165, 166, 167, 168, 169, 170, 171, 172, 173, 174, 175, 176, 177, 178, 179, 180, 181, 182, 183, 184, 185, 186, 187, 188, 189, 190, 191, 192, 193, 194, 195, 196, 197, 198, 199, 200, 201, 202, 203, 204, 205, 206, 207, 208, 209, 210, 211, 212, 213, 214, 215, 216

stats.grok.se broken yet again?

• There have been no updates since the 24th. For example, this. Narutolovehinata5 ^tccsdnew 03:34, 28 July 2015 (UTC)

• http://stats.grok.se Stats from June 16 and all dates beginning on July 25 are missing even though the raw data exists.--TonyTheTiger (T / C / WP:FOUR / WP:CHICAGO / WP:WAWARD) 03:58, 28 July 2015 (UTC)
  • July stats are up, but June 16 is still missing.--TonyTheTiger (T / C / WP:FOUR / WP:CHICAGO / WP:WAWARD) 04:35, 30 July 2015 (UTC)

Cannot reach stats.grok.se, name cannot be resolved. DNS lookup failed. — Preceding unsigned comment added by Dstone1029 (talk • contribs) 16:41, 3 August 2015 (UTC)

Search links not appearing

I just discovered that all my search links that are limited to searching the article text (eg. {{search link|text="buggy"}}) stopped rendering sometime in the past 48 hours past week (apparently my earlier conversation on this very board and with John of Reading on his userpage didn't use the text parameter). I've checked instances logged-in and logged-out, on Chrome and on Firefox, and I get the glitch in all cases. This does not seem to affect instances of {{Search link}} that do not have that limitation. I have not had a chance to test various alternates. Test matrix:

plaintext using <nowiki> tag – regular wikitext

{{search link|text="buggy"}} – "buggy"‎ [restored as of 22:34 (UTC)]

{{search link|"buggy"}} – "buggy"

Insights will be welcome! —jameslucas (" " / +) 21:20, 28 July 2015 (UTC)

User:Cpiral changed the parameter names in [1] without allowing the old names as aliases. That's problematic for an old template with many uses. I see Cpiral updated some uses of the old names. Was that all of them or are there still many? In either case I suggest allowing the old names. PrimeHunter (talk) 21:35, 28 July 2015 (UTC)

Was problematic. With {{Template usage}} now anyone can now find all template usage and directly removing obsolete parameter usage from the wikitext, avoiding the need for backward compatible code. — CpiralCpiral 23:03, 28 July 2015 (UTC)

What does {{Template usage}} have got to do with breaking existing transclusions of another template? Alakzi (talk) 23:40, 28 July 2015 (UTC)

Cpiral has been doing some strange things recently, see their edits to Help:Template over the last two weeks. --Redrose64 (talk) 21:51, 28 July 2015 (UTC)

It was necessary to evolve {{search link}} for {{regex}} which was necessary for Help:Searching/Searching - DRAFT. My work on the {{Val}} family got me to create {{Template usage}}, which got me interested in improving Help:Template. — CpiralCpiral 23:03, 28 July 2015 (UTC)

Replacing parameter names is a common newbie mistake. What about their edits to Help:Template? Alakzi (talk) 22:38, 28 July 2015 (UTC)

@Alakzi: They have been rewriting whole sections, much of their new text is barely comprehensible. In this edit, for example, terms like "parameter" and "argument" are used almost interchangeably; and although they state early on that there are two kinds of parameter: named and unnamed. Soon after, we find that there is a third kind, the positional parameter, which is apparently not the same as an unnamed parameter. Have a look at each edit individually - they really are difficult to follow. The most recent large edit produced the paragraph

To improve readability many programming languages ignore much of the whitespace, so programmers can add newlines and indent almost at will. Because of the nature of transcluding text in place, seemlessly, MediaWiki software is very sensitive to whitespace, only allowing it around some places, but in most places newlines for code-readability are treated by the software as content, so the template code uses <!-- comments --> as a work around, adding <!-- before each newline character and --> after it.

which really is not an improvement in readability. --Redrose64 (talk) 23:32, 28 July 2015 (UTC)

Right, I see what you mean. The documentation of {{Template usage}} is difficult to follow as well. Alakzi (talk) 23:40, 28 July 2015 (UTC)

Awh, let's go ahead and sully the talk page at Help:Template. I've started a conversation there about the changes. You can refer to me in first person now. Thanks. — CpiralCpiral 00:16, 29 July 2015 (UTC)

There's another big issue with updating parameter names: Many other projects rely on the template infrastructure of the English Wikipedia. Breaking stuff makes it much harder to adopt updates. All the best: Rich Farmbrough, 19:58, 29 July 2015 (UTC).

I think I understand your concerns, but can you specify? I am not convinced that template infrastructure need develop differently than the way I am developing it. I can achieve new-feature parity for any template and avoid the need for carrying any backward compatible code, by directly changing every instance of obsolete parameter usage on the wiki, then changing the template. The documentation was updated. Was I supposed to change these few on the wiki in User space? — CpiralCpiral 02:36, 3 August 2015 (UTC)

AfD Statistics

The AfD Statistics tool ([2]) shows my vote at WP:Articles for deletion/Bob Girls discography as "keep", abut in fact I proposed the article for deletion. Why is that? Vanjagenije (talk) 09:21, 30 July 2015 (UTC)

You commented below someone else's support, which the tool probably picked up as "support". It should not do that, someone commenting on someone else's !vote is usually not a vote, or a contestation. Not sure why it ignored the nomination, though. Jo-Jo Eumerus (talk, contributions) 10:03, 30 July 2015 (UTC)

Is there somebody who can fix that? The author (Scottywong) is retired. I don't know whom to ask. Vanjagenije (talk) 10:55, 30 July 2015 (UTC)

I was bold and have tweaked the page. What's probably going on is that you used the incorrect list type to start your comment (please read WP:Accessibility#Lists). Check in a day or two to see if that fixed it. --Izno (talk) 11:58, 30 July 2015 (UTC)

@Izno: Thanks a lot for your time, but it is still the same. The problem is not fixed. Vanjagenije (talk) 00:29, 3 August 2015 (UTC)

Made a couple more tweaks. Wait a couple more days. --Izno (talk) 01:33, 3 August 2015 (UTC)

@Izno: Thank you very much. I think I found what's wrong. User:4minute lover signed his "keep" vote with a signature that contains a link to my talk page ([3]). That's very weird. He probably didn't know how to sign, but copied my signature. I changed it, and the AfD Statistic is now OK. I took a look into 4minute lover's edits, and I found that here he signed his post with a signature of User:Gene93k. Very strange behavior. Vanjagenije (talk) 11:30, 3 August 2015 (UTC)

WP:SIGFORGE. --Redrose64 (talk) 11:44, 3 August 2015 (UTC)

That one with Gene looks like he was moving the deletion sorting notice, not signing the page with a new comment. Which it's weird, but separately weird. --Izno (talk) 13:56, 3 August 2015 (UTC)

This is what is so ugly about talk pages. They are messy and unstructured. WP:Flow would be much easier for tools like this to work with. But a lot of reactionary people wants it to fail.--Anders Feder (talk) 11:08, 30 July 2015 (UTC)

What does a Healthy Community look like to you?

Hi,
The Community Engagement department at the Wikimedia Foundation has launched a new learning campaign. The WMF wants to record community impressions about what makes a healthy online community. Share your views and/or create a drawing and take a chance to win a Wikimania 2016 scholarship! Join the WMF as we begin a conversation about Community Health. Contribute a drawing or answer the questions on the campaign's page.

Why get involved?

The world is changing. The way we relate to knowledge is transforming. As the next billion people come online, the Wikimedia movement is working to bring more users on the wiki projects. The way we interact and collaborate online are key to building sustainable projects. How accessible are Wikimedia projects to newcomers today? Are we helping each other learn?
Share your views on this matter that affects us all!
We invite everyone to take part in this learning campaign. Wikimedia Foundation will distribute one Wikimania Scholarship 2016 among those participants who are eligible.

More information

• All participants must have a registered user of at least one month antiquity on any Wikimedia project before the starting date of the campaign.
• All eligible contributions must be done until August 23, 2015 at 23:59 UTC
• Wiki link: Community Health learning campaign
• URL https://meta.wikimedia.org/wiki/Grants:Evaluation/Community_Health_learning_campaign
• Contact: María Cruz / Twitter: WikiEval #CommunityHealth / email: evalwikimedia · org

Happy editing!

MediaWiki message delivery (talk) 23:42, 31 July 2015 (UTC)

A healthy community is definitely one where people get blocked for hate speech.Codeofdusk (talk) 07:18, 3 August 2015 (UTC)

Image metadata, here v. Commons

I just moved File:Putter Green.jpg to Commons under the same filename because it was a simple process: PD-self claim and no hiccups. Moving it there, however, I observed that the metadata were a lot fuller (we have an image title, for example), and some of them appear to indicate a copyvio: for example, it's listed as being a work of The Augusta Chronicle, and through it I discovered that author Andrew Davis Tucker is a newspaper photographer who was with the Chronicle at the date of the photograph, not a Clemson golfer as suggested by the uploader's username.

Judging by the metadata I could see here, the image is fine, but judging by the metadata I could see at Commons, it's not. Why do files here display less metadata? Click the extended metadata link at the bottom of the filepage here, and the result is 37 metadata fields; click the extended metadata link at the bottom of the filepage at Commons for the same image, and the result is 55 metadata fields. Is there a way to adjust what metadata fields are displayed? If so, why don't we adjust it so that files display more fields? Nyttend (talk) 21:13, 1 August 2015 (UTC)

I suspect there is a difference between how Wikipedia and Commons treat metadata information. There is this page and this page but they are the same so likely not. I'll dig further. Jo-Jo Eumerus (talk, contributions) 21:29, 1 August 2015 (UTC)

I don't think those specific pages are relevant, since the names don't appear when you view with ?uselang=qqx. I've left a note at the Commons village pump asking people there to offer input here. Nyttend (talk) 21:37, 1 August 2015 (UTC)

It might be a "metadata.js" thing as described on Wikipedia:Catalogue of CSS classes. Or in other words, a difference between site settings in Commons and Wikipedia. This might be the case for a Phabricator topic. Jo-Jo Eumerus (talk, contributions) 22:01, 1 August 2015 (UTC)

I wondered whether the displayed metadata is extracted at upload time or some other past time and depends on the MediaWiki software at the time so I uploaded an identical copy at File:Putter Green copy.jpg. It displays the same metadata as commons:File:Putter Green.jpg so that must be the explanation. File:Putter Green.jpg was uploaded in 2006 and displays less metadata. PrimeHunter (talk) 22:45, 1 August 2015 (UTC)

(edit conflict) Its an old file. Maybe the software didnt detect these metadata at that time (see mediawikiwiki:Manual:Image table). Try upload it to enwiki again. Christian75 (talk) 22:50, 1 August 2015 (UTC)

I found mw:Manual:$wgUpdateCompatibleMetadata which is false by default and remains false in Wikimedia wikis. PrimeHunter (talk) 22:57, 1 August 2015 (UTC)

Files get their metadata extracted when they are uploaded, or anytime someone does ?action=purge on the image description page. Support for IPTC metadata was added to MediaWiki as part of my GSOC project in 2010. Since this image was uploaded prior to that way back in 2006, it only has exif data extracted, not the other types of metadata. Uploading to commons allowed caused all the metadata we now support to be extracted. If one purges the image page here on enwikipedia, then the missing metadata should show up. Bawolff (talk) 20:26, 4 August 2015 (UTC)

Right, I have purged File:Putter Green.jpg and it now displays the same as the others. PrimeHunter (talk) 21:12, 4 August 2015 (UTC)

Module:Citation/CS1 incorrectly adding pages using edition=revised to tracking category

Module:Citation/CS1 automatically adds "ed." after the value of the edition parameter. Citations that explicitly use something like "2nd ed." are added to the hidden maintenance category Category:CS1 maint: Extra text to allow fixing these values more easily. However, the module probably just checks whether the value ends with "edition", "ed" or similar. This leads to issues on pages like Pi, where a reference (No. 79, The Penguin Dictionary of Curious and Interesting Numbers) gets incorrectly marked as erroneous because it uses "edition=revised", which ends with "ed". Is this a bug? —Maths314 (talk) 20:04, 2 August 2015 (UTC)

Yes, a bug that has been fixed in the sandbox. Questions and concerns about this module are best addressed at Help talk:Citation Style 1.

—Trappist the monk (talk) 20:32, 2 August 2015 (UTC)

Citations are weird

I just added a citation to same-sex marriage in Mexico for Puebla:

In November 2014 a lesbian couple filed for an amparo and were granted an injunction to marry. The state appealed the decision. 10 July, 2015, the Appellate Court upheld the ruling in favor of the couple. Their wedding, which was the first same-sex marriage in the state of Puebla<ref name="1st marriage">{{cite news|last1=Hernández Alcántara|first1=Martín|title=Mañana se celebrará el primer matrimonio gay en la historia de Puebla|url=http://www.lajornadadeoriente.com.mx/2015/07/31/manana-se-celebrara-el-primer-matrimonio-gay-en-la-historia-de-puebla/|accessdate=31 July 2015|publisher=La Jornada de Oriente|date=31 July 2015|location=Puebla, Mexico|language=Spanish}}</ref> took place on 1 August 2015.<ref name="1st marriage">{{cite news|last1=Fernández|first1=Tuss|title=Se celebra en Puebla la primera boda de personas del mismo sexo|url=http://ladobe.com.mx/2015/08/se-celebra-en-puebla-la-primera-boda-de-personas-del-mismo-sexo/|accessdate=3 August 2015|publisher=La Dobe|date=2 August 2015|location=Puebla, Mexico|language=Spanish}}</ref> As you can plainly see the text is different, but the numbers are the same: 254 is the citation number for both. Edit was made at 19:03 and it is still the same at 19:18? SusunW (talk) 00:18, 3 August 2015 (UTC)

@SusunW: This has happened because you've given both the references the same name, "1st marriage", so MediaWiki thinks your second reference is actually a reuse of the first one rather than a totally new reference. If you change the name of one of the references, it'll be fixed. Hope that helps. --(ʞɿɐʇ) ɐuɐʞsǝp 00:24, 3 August 2015 (UTC)

Thank you. Some days one can't see the forest for the trees ;) SusunW (talk) 00:27, 3 August 2015 (UTC)

Wikimedia email

Is Wikimedia email currently working? I sent an email to another user about an hour ago, ticked the box to receive a confirmation copy to my registered email address, got the on-screen confirmation that the email had been sent, but never received the confirmation email. Can this be independently checked? Dirtlawyer1 (talk) 02:37, 3 August 2015 (UTC)

The easiest way to check would be to have a different account with a different email address, and try to email that account. עוד מישהו Od Mishehu 02:50, 3 August 2015 (UTC)

Good idea, OM. I should have thought of that. I have three alternative accounts that I use to maintain separate large watch lists. I will try emailing one of those accounts. Cheers. Dirtlawyer1 (talk) 02:57, 3 August 2015 (UTC)

@Od Mishehu: About 45 minutes ago, I tried to send an email from my alternate account, Dirtlawyer2: Olympics, to my primary user account, Dirtlawyer1. I have not received either the email sent to the recipient account, or the confirmation email that the email system is supposed to generate for the sender account. About 10 minutes ago, I also sent a test email to you through the Wikipedia email system. Please let me know if you do or don't receive it. Thanks. Dirtlawyer1 (talk) 03:39, 3 August 2015 (UTC)

Some mail providers block Wikimedia mail due to the way it is sent. See for example Wikipedia:Village pump (technical)/Archive 136#Email is not working and phab:T66795. PrimeHunter (talk) 03:47, 3 August 2015 (UTC)

Better to direct people to a thread that has less of Technical 13's scary misinformation, like Wikipedia:Village pump (technical)/Archive 129#Is "Email this user" on the blink? and the threads linked back from there. --Redrose64 (talk) 10:23, 3 August 2015 (UTC)

In my opinion, it would be better to direct people to http://www.ietf.org/mail-archive/web/ietf/current/msg87153.html with a brief explanation that Yahoo mail is broken and that there is little we can do about it except possibly block Yahoo mail. --Guy Macon (talk) 12:51, 3 August 2015 (UTC)

As I've suggested a few times since this problem presented itself, we could resolve this issue by correctly and accurately identifying the sender (albeit by proxy) of the email as Wikimedia and provide the email address of the Wikipedia user who requested Wikimedia send the email in the reply-to field.

Alternatively, each user with email enable could be assigned virtual email address that Wikimedia would route to their actual email. xeno@users.wikimedia.org, for example. –xeno^talk 13:00, 3 August 2015 (UTC)

Upload file from WikiEditor...to Commons

Hi there, Wikipedians!

First, this is not a very polished script, so forgive the omissions and thrown-together UI.

At Wikimania, I wrote a gadget that uploaded from enwiki beta to Commons beta. And it worked. And it was brilliant.

Now, the code required for that gadget is on enwiki proper. So I ported the script over to enwiki.

All you need is the following line in your common.js to enable it:

importScript( 'User:MarkTraceur/editPageUploadTool.js' );

After that, a second "insert file" icon will appear in WikiEditor after a second or two, and its title text will be "upload file" or something.

Note, this is going to Commons, under a CC-BY-SA 4.0 license, so by reading this and installing my script you're agreeing to those terms when you upload...see, I told you it was unpolished. In the Future, it will have a license disclaimer.

This is going to be the very rough basis for our upcoming tools, which will live both in WikiEditor and in VisualEditor. They will definitely have proper license disclaimers.

In this grand tradition, you can create subclasses of my mw.Upload object(s), and my mw.UploadDialog object(s), and write specialized upload tools for various purposes. Want to add a special category to images in a class of articles that you edit often? Easy! Subclass mw.CommonsUploadForEditDialog to return a subclass of mw.CommonsUploadForEdit which adds the category in automatically on creation. This is only one example of the cool, specialized stuff you can do.

See the documentation for mw.Upload on doc.wikimedia.org: https://doc.wikimedia.org/mediawiki-core/master/js/#!/api/mw.Upload

Happy hacking! --MarkTraceur (talk) 15:07, 3 August 2015 (UTC)

Wikitables - unable to disambiguate links

Wikitables on the following articles Athletics at the 1962 British Empire and Commonwealth Games – Women's 100 yards, Athletics at the 1968 Summer Olympics – Women's 400 metres, Athletics at the 1962 British Empire and Commonwealth Games – Women's 220 yards, and Australia at the 1962 British Empire and Commonwealth Games generate links to Joyce Bennett, but they should link to Joyce Bennett (athlete) (a legitimate redlink). I cannot see how to edit the wikitable to make them generate the correct links. Help please! DuncanHill (talk) 15:27, 3 August 2015 (UTC)

Like so, per the Template:Sortname documentation. --Izno (talk) 15:31, 3 August 2015 (UTC)

You can also do this using |dab=athlete as opposed to my solution for each of the template uses. I think my solution is marginally easier to understand. YMMV. --Izno (talk) 15:33, 3 August 2015 (UTC)

Many thanks - I went with the first method. DuncanHill (talk) 15:46, 3 August 2015 (UTC)

Resolved

Tech News: 2015-32

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

• The ContentTranslation extension has been updated:
  • You can now type in list paragraphs on wikis with right-to-left scripts. [4]
  • Some user interface updates changed how details in the ContentTranslation extension look. [5] [6] [7] [8]
• The error page you see when the sites are not working is now simpler and easier to read. It also shows the Wikimedia logo. [9]
• MediaWiki now supports redirects for CSS pages. [10]
• Bots can't guess captchas unlimited times anymore. [11]

Problems

• There was a problem with thumbnails on wikis with local images on July 24 and 25. It was due to a code error. [12]
• We can't search by file type on Wikimedia wikis now. [13]

Changes this week

• The new version of MediaWiki will be on test wikis and MediaWiki.org from August 4. It will be on non-Wikipedia wikis from August 5. It will be on all Wikipedias from August 6 (calendar).

Meetings

• You can join the next meeting with the VisualEditor team. During the meeting, you can tell developers which bugs are the most important. The meeting will be on August 4 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.

15:51, 3 August 2015 (UTC)

Wikidata: Access to data from arbitrary items is coming

(Sorry for writing in English)

When using data from Wikidata on Wikipedia and other sister projects, there is currently a limitation in place that hinders some use cases: data can only be accessed from the corresponding item. So, for example, the Wikipedia article about Berlin can only get data from the Wikidata item about Berlin but not from the item about Germany. This had technical reasons. We are now removing this limitation. It is already done for many projects. Your project is one of the next ones. We will roll out this feature here on August 18.

We invite you to play around with this new feature if you are one of the people who have been waiting for this for a long time. If you have technical issues/questions with this you can come to d:Wikidata:Contact the development team.

A note of caution: Please be careful with how many items you use for a single page. If it is too many pages, loading might get slow. We will have to see how the feature behaves in production to see where we need to tweak and how.

How to use it, once it is enabled:

• Parser function: {{#property:P36|from=Q183}} to get the capital from the item about Germany
• Lua: see mw:Extension:Wikibase Client/Lua

Cheers Lydia Pintscher MediaWiki message delivery (talk) 17:51, 3 August 2015 (UTC)

Let's see if this works in two weeks: The capital of Germany is: Berlin.--Anders Feder (talk) 18:01, 3 August 2015 (UTC)

Hooray! I've been waiting for this for a long time. — Mr. Stradivarius ^{♪ talk ♪} 13:19, 4 August 2015 (UTC)

Blank thumbnail with upright

Would anybody have any idea why upright produces a blank thumbnail with the example below? Alakzi (talk) 12:57, 4 August 2015 (UTC)

[[File:Parodie.svg|thumb]]	[[File:Parodie.svg|thumb|upright]]

Silly me, I'm using a 300px default, so upright should be 230px for everybody else (on the right). Alakzi (talk) 13:11, 4 August 2015 (UTC)

Whatever, this works for me (but is not wanted, right?)

[[File:Parodie.svg|thumb|300px]]

--Gerda Arendt (talk) 13:14, 4 August 2015 (UTC)

Why are only my mobile web edits ever tagged as mobile edits?

Even my edits right now are mobile edits, but they are only tagged as mobile edits when I make them using the mobile version of the website. What's the problem here? Dustin (talk) 17:42, 4 August 2015 (UTC)

Not sure if there is a problem. Have you run into a use case where it was problematic that edits made with the desktop site from a mobile device was not tagged as a mobile edit?--Anders Feder (talk) 19:13, 4 August 2015 (UTC)

What is the point of a tag if it doesn't work properly? Dustin (talk) 20:16, 4 August 2015 (UTC)

What leads you to conclude that the function is not "proper"? The point of the tags is filtering and analytics.--Anders Feder (talk) 20:38, 4 August 2015 (UTC)

Yes, it works as intended as far as I know. The mobile version works differently and displays some things differently or not at all. When evaluating edits it can be helpful to know they were made with the mobile version. When discussing with a user it can be helpful to know what they see (it's certainly very helpful at the help desks where I answer questions). The developers may use it to investigate software issues. If a user edits with the desktop version then I don't see good reason to know whether they did it on a mobile device. If a user edits with the mobile version on a desktop computer then the edit is tagged with mobile and that makes sense to me. Special:Tags displays MediaWiki:Tag-mobile edit-description for "Mobile edit", and MediaWiki:Tag-mobile web edit-description for "Mobile web edit". This change seems wrong but the former version was also inaccurate. The default "Edit made from mobile (web or app)" should probably be restored. I think "Mobile edit" is for all edits with either the mobile version or some app, while "Mobile web edit" is only for the mobile version, and "Mobile app edit" is only for apps. PrimeHunter (talk) 21:05, 4 August 2015 (UTC)

It's a more complicated tag than I originally though, isn't it? In any case, thanks for the in-depth response. Dustin (talk) 02:02, 6 August 2015 (UTC)

Black berry app is down

So https://appworld.blackberry.com/webstore/content/105171/ seems to be the official Wikipedia app for BlackBerry. However I'm getting this error:

Unknown item

The requested item does not exist or is not available. (EC)

Please check it. I made a talk page entry on List of Wikipedia mobile applications yet nobody replied. Also I Help:Mobile access was notified of this in January 2014 yet nobody replied so far.

Not sure where else to report this. I now took the app off those articles.

--Fixuture (talk) 17:47, 4 August 2015 (UTC)

As you can see here: Help:Mobile_access#Official_application, there is no longer and official supported BlackBerry application. There used to be one, but it was removed from the BlackBerry AppWorld store. Wherever you find that URL still listed, you are encouraged to remove it or at least mark it as no longer valid. —TheDJ (talk • contribs) 21:31, 4 August 2015 (UTC)

@TheDJ: Yes it's not there anymore as I just removed it as written above. Note that the black berry app was still linked on both sites for at least 1,5 years after the first notice on the talk page about it being down. I guess it's not really problematic or anything but sometimes I'm really confounded by Wikipedia's organisation - one would expect there to be some major notice (a minor comment on some talk page to confirm it actually being down would have sufficed as well) somewhere about it being taken down / not being supported anymore with the developers themselves taking it off all articles the same day that it's not supported anymore... --Fixuture (talk) 18:09, 5 August 2015 (UTC)

Issue reported at Theodore Roosevelt

Hello technical folk,

User:Smykytyn reports: This page does not currently display correctly on iPad, unlike all other President pages. It shows up in single column form appropriate for iPhone, not iPad. This seems to be a fairly recent development. My guess is this is a user-side settings issue, but I'm passing on the message in case someone with better technical knowledge can take a look at the page to see if there's something there messing things up, or maybe can offer help to this user on how to get things working. Thanks. Ivanvector 🍁 (talk) 21:29, 4 August 2015 (UTC)

This is due to the usage of stack begin/end templates, which cause the infobox to be in a single file column, instead of right floated. —TheDJ (talk • contribs) 21:35, 4 August 2015 (UTC)

Dabbing in a cathead navy patrol vessels template

Category:Patrol vessels of the Georgian Navy uses Template:Cathead navy patrol vessels. Is there any way to dab the link from Georgia to Georgia (country) but make it display as Georgia? DuncanHill (talk) 21:32, 4 August 2015 (UTC)

Can you now? No. Could one after changing the template? Ostensibly. --Izno (talk) 00:18, 5 August 2015 (UTC)

Content Translation scourge

I'm venting, but I've had it with fixing articles created with the Content Translation scourge

An example is this mess. Original article is here. Majority of the problems I've seen is contained in this article.

1. Why does the scourge add wikilinks to dates on enwiki?
2. Why does it not always translate dates? The above article translated [[2009년 3월]] to [[March 2009|2009년 3월]]. Others do 12 de noviembre de 2014 to 12 de noviembre de 2014.
3. Why does it add random [[?
4. Why does it add random wikilinks?
5. Why does it add color in random spots that the original doesn't have?
6. Why does it add random <span> </span>?
7. Why does it add random span tags around text, especially if the text was in a template on the original article? For example, <span>1995 April 12</span><span> (20)</span>
8. Why does it screw up tables. I'm not talking about the copious id="666" tags, but messing things up. For example in this section, everywhere there was a blank cell, it droped the cell. Instead of a blank cell where the person was born, they now ended up being born on Protoss or Zerg. It can't handle blank cells.
9. Why does it not translate a cite template correctly? Atleast I know what "titel", "autor" and "título" means, but not Content Translation tool. Another example.
10. Why does it translate somethings in a list/table/section, but not others?
11. Report a problem to Content Translation and they say to report it to Parsoid. Content Translation uses Parsoid. Parsoid says it is fixed, but Content Translation uses a different version of Parsoid.
12. Content Translation uses Apertium for translating. It doesn't support Japanese, Korean and many others. According to the Apertium's wikipage, only 7 languages can be translated to English. This probably explain why the above article was only half way translated.
13. Majority of people using Content Translation don't cleanup the mess.

Anyone want to cleanup, little alone understand 2nd generation Intel core global StarCraft II league March? Bgwhite (talk) 23:12, 4 August 2015 (UTC)

Then nominate the articles for deletion like we always do with bad quality stuff. It's a tool, not pixie dust. —TheDJ (talk • contribs) 07:21, 5 August 2015 (UTC)

Try mw:Talk:Content translation. Eman235/talk 15:13, 5 August 2015 (UTC)

May also be good to get the thoughts of the person who created these two articles, Dakarias. — Rhododendrites ^talk \\ 19:35, 5 August 2015 (UTC)

Not sure what all these weird happenings are- I just try to translate the text, and nothing else. -Kurousagi 23:38, 5 August 2015 (UTC)

Something I can also add is that the highlighting happens automatically for some reason. The partly translated problem was because I'm still trying to translate the names for various leagues and such using outside sources. -Kurousagi 23:42, 5 August 2015 (UTC)

It looks like only the first revision was done with Content Translation, and the rest was done by hand. Judging from this diff, we have Dab Solver to thank for the colours. Some things, like the table cell problem, look to be bugs in Content Translation, but others, like the [[ thing, look to be good old-fashioned user error. As for Apertium, if people are submitting purely (or mostly) machine-translated stuff, then it should be nominated for deletion. I don't think Apertium's machine translation was used at all in this case, however; it just looks like the translation was a little too literal. I know from experience that it's surprisingly hard to generate coherent text when translating things from Japanese, and I imagine the same thing holds true for Korean. — Mr. Stradivarius ^{♪ talk ♪} 02:45, 6 August 2015 (UTC)

Things that are totally messed up are getting deleted. The above article was just one example of the crap this produces. Dab Solver has nothing to do with some of the random colours. How can a sentences in a plain paragraph be translated to have it's background go red? Majority of people using the tool are not fixing the issues or they don't know how too. Other people on French Wikipedia want it disabled. Bgwhite (talk) 07:06, 6 August 2015 (UTC)

I have no idea of the highlights other than the fact that it 'temporarily' highlights text when copying over from one side of the Content Translation tool. And yes, the machine translation was supposedly 'unavailable'. -Kurousagi 10:36, 6 August 2015 (UTC)

Module:OSM

Hi,

I created a module to link to objects on Openstreetmap and visualise them. To accomplish this a few conditions have to be met:

• the OSM object needs wikidata tag(s)
• Overpass API needs to be able to retrieve them
• Turbo Overpass is needed to show them on a dynamic map
• somebody had to write some Lua code to glue it all together

So I did. You can see the result in the Leuven article. Hopefully this is useful to link to geographical objects.--Polyglot (talk) 23:35, 4 August 2015 (UTC)

I guess it's kind of cool, but...

1. the link has no text associated with it
2. when I click on it, I get a mostly grayed out page with no indication that anything is happening
3. eventually I get a warning about large amounts of data
4. when the map does show up, it's a world map with a bunch of red circles and no obvious information
5. clicking on a circle brings up some OSM metadata that is not immediately useful
6. clicking on some random number finally zooms in to the street

So I like it but the UI is not obvious. Kendall-K1 (talk) 01:16, 7 August 2015 (UTC)

Can't leave edit summaries

I haven't been able to leave edit summaries or other fillable forms like section headers since July 31st. If I do it only registers random letters which I don't even see until I save. I am running Chrome OS 45 (beta). Mark Schierbecker (talk) 06:58, 5 August 2015 (UTC)

Sounds like a broken browser extension/addon or something. And you can always check if the stable version of Chrome works for you of course. —TheDJ (talk • contribs) 07:18, 5 August 2015 (UTC)

Image properly rotated and not properly rotated

What's going on with File:La Grange Civil War monument.jpg? When I view it in IE11, I get different results at different resolutions — at https://commons.wikimedia.org/wiki/File:La_Grange_Civil_War_monument.jpg it's properly upright, but at https://upload.wikimedia.org/wikipedia/commons/3/39/La_Grange_Civil_War_monument.jpg (what I get when I click the image), it's sideways. Nyttend (talk) 00:08, 6 August 2015 (UTC)

https://upload.wikimedia.org/wikipedia/commons/3/39/La_Grange_Civil_War_monument.jpg (wikilink Media:La Grange Civil War monument.jpg) is the actual file that was uploaded. The result of viewing it depends on the used software. I see it sideways in IE9 and upright in Firefox 39.0. If you click "Show extended details" at File:La Grange Civil War monument.jpg#metadata then it says "Rotated 90° CCW". The photographer probably rotated the camera due to the height to width ratio, and the camera or the photographer registered this in the metadata. When the image is scaled by our servers, they register the metadata says rotated and they rotate it back before sending it to your browser, so the result no longer depends on the browser. The only way to display the original Media:La Grange Civil War monument.jpg right in all browsers is to download it, rotate it with some software, and upload the new version. PrimeHunter (talk) 00:24, 6 August 2015 (UTC)

Weird. I wonder how the camera rotated it (I'm the photographer), because I didn't tell it to do any rotation. I'll file a WP:GL request. Nyttend (talk) 00:32, 6 August 2015 (UTC)

If you haven't cropped the photo them I'm fairly certain you tilted the camera 90° when you took the photo. The camera must have a way to detect this. The Commons file page commons:File:La Grange Civil War monument.jpg has a "request rotation" link. I haven't tried clicking such links. PrimeHunter (talk) 00:38, 6 August 2015 (UTC)

I rotated the camera 90°, indeed, but I routinely do this when getting images of taller subjects. I don't remember encountering this situation before, although now to my surprise I'm finding that the same is true of File:Main across from courthouse, Jackson.jpg, and File:Emporium First UMC.jpg from some months ago, and even File:Pauley Bridge pier.jpg from when the camera was really new for me. I haven't a clue how to disable this...Nyttend (talk) 00:44, 6 August 2015 (UTC)

@PrimeHunter: The "request rotation" link (which doesn't appear on all image types) fires a JavaScript thing (see c:Help:RotateLink) which displays a dialog; when you pick an angle (e.g. 90°) and click confirm rotate request, it does this, which displays a message and puts the image in c:Category:Images requiring rotation by bot, for Rotatebot (talk · contribs) to notice and act on. So if you don't have JavaScript (or don't like dialog boxes) it's very easy to do it manually; and it's also easy to undo if you change your mind. --Redrose64 (talk) 09:59, 6 August 2015 (UTC)

Taking a cursory look at the Exif specification, I can't even decide whether it is a bug in the camera or our server. The tag allows one to express how the image is "oriented", but crucially leaves it an open question at which orientation one would normally want to display the image.--Anders Feder (talk) 01:23, 6 August 2015 (UTC)

I can't view or access the large-size version, but I can access the "original", which downloads to my PC is being rotated 90 degrees counterclockwise. ←Baseball Bugs ^{What's up, Doc?} carrots→ 05:15, 6 August 2015 (UTC)

Reverting category moves

The category Category:FC Astana players was moved to Category:Astana F.C. players by ChelseaFunNumberOne. The move was then reverted by GiantSnowman, but Category:FC Astana players must be deleted first. Category moves should be able to be reverted without having to first delete the soft redirected category as long as it has only revision in its history (like reverting any other move). GeoffreyT2000 (talk) 03:33, 6 August 2015 (UTC)

@GeoffreyT2000: There is a significant difference by moving categories. The remaining page will contain the {{Category redirect}} template instead of the usual content of redirects. Armbrust ^{The Homunculus} 14:52, 6 August 2015 (UTC)

The Sajax library will be removed from MediaWiki next week

I've just found out from phab:T55120 that the Sajax JavaScript library will be removed from MediaWiki next week (12 August for non-Wikipedias and 13 August for Wikipedias). This means that all of the 739 scripts that use it, 451 of which are on this wiki, are going to break. Most of those are not important, but I am sure that quite a few of them are still in use. I've made a list of all the affected scripts at User:Mr. Stradivarius/Scripts using Sajax. Now would be a good time to have a look through them and determine the ones that we need to prioritise fixing. — Mr. Stradivarius ^{♪ talk ♪} 05:20, 6 August 2015 (UTC)

Good riddance, I say! Sajax should have been killed off years ago.

It's great that you've prepared this list. Do you think it would be worth sending a mass message to all the concerned users?

Also, would you object if I sorted the list? It would make it a little more useful to identify users with several affected scripts in their userspace. — This, that and the other (talk) 09:41, 6 August 2015 (UTC)

Yep, it would definitely be worth a mass-message. Let me prepare it - with some module coding we should be able to make a personalised message for all the affected users, on all wikis, in one shot. And yes, feel free to sort the list however you want, and especially to remove false positives or scripts that have been fixed. :) I've done a preliminary sort, but if that's not what you were looking for, feel free to tweak it. — Mr. Stradivarius ^{♪ talk ♪} 13:53, 6 August 2015 (UTC)

Actually, it's pretty late here now, so mass-messaging will have to wait until tomorrow. If anyone wants to write a message in the meantime, be my guest. — Mr. Stradivarius ^{♪ talk ♪} 15:49, 6 August 2015 (UTC)

Another thing that is coming, is that you can no longer use document.write() to load a script. See also T107399 and T108139. The fallback will try to asynchronously append to the end of the document, but if your script/gadget after 7 years of deprecation, still requires synchronous execution, then expect it to break. For the rest of us, we get faster page rendering !!! —TheDJ (talk • contribs) 11:12, 6 August 2015 (UTC)

I was going to put this in the mass message as well, but it looks like I'll have to update my searcher script to use the API timeout properly, as on this wiki alone I get 11,447 hits. This really worries me - did no-one at the WMF think to check how many users would be affected by this change? — Mr. Stradivarius ^{♪ talk ♪} 13:53, 6 August 2015 (UTC)

Hmm. If Jimbo is still using Monobook at all, then his scripts are going to be broken too... — Mr. Stradivarius ^{♪ talk ♪} 14:15, 6 August 2015 (UTC)

I'm really hoping there's a non-Sajax script for closing featured picture candidates. The ones I know about require it. Adam Cuerden ^(talk) 14:14, 6 August 2015 (UTC)

...Oh, dear: this appears to break WP:TWINKLE. Adam Cuerden ^(talk) 14:20, 6 August 2015 (UTC)

Twinkle shouldn't be affected: the only gadgets affected by the removal of Sajax are MediaWiki:RefToolbarLegacy.js and MediaWiki:Gadget-dropdown-menus-nonvector.js. If people have old copies of Twinkle around that use Sajax, then they would stop working, however. — Mr. Stradivarius ^{♪ talk ♪} 14:27, 6 August 2015 (UTC)

(edit conflict) @Adam Cuerden: Probably not, but the ones that require it can be updated. Fixing a script to stop it depending on Sajax isn't hard, but it's also not a no-brainer, so it will require us to prioritise what should be fixed. Scripts like the ones you mention will be high up the list - which ones are they? — Mr. Stradivarius ^{♪ talk ♪} 14:22, 6 August 2015 (UTC)

User:Adam_Cuerden/closeFPC.js (I'm not that good at Javascript, I should say: I just made a small change to fix some rearrangements of the Featured pictures system), and whichever of the many results for twinkle in User:Mr._Stradivarius/Scripts_using_Sajax are part of the core gadget are big ones, I'd say. There may be others. There is no alternative for FPC closure besides reinstituting a manual process that, as I remember, took about 15-30 minutes per closure. I'm trying to arrange a few weeks' grace. Adam Cuerden ^(talk) 14:27, 6 August 2015 (UTC)

None of those search results are part of the main Twinkle gadget - the main script is at Mediawiki:Gadget-Twinkle.js, and you can find the others at Special:PrefixIndex/Mediawiki:Gadget-twinkle. — Mr. Stradivarius ^{♪ talk ♪} 15:49, 6 August 2015 (UTC)

Navigation popups is not on the list of broken scripts, but it appears to be broken on my end. Dunno if it is related to this issue or not, just wanted to bring it up in case it is. --I am k6ka ^{Talk to me!} _{See what I have done} 00:54, 7 August 2015 (UTC)

K6ka see [[Wikipedia talk:Tools/Navigation popups#Anyone else getting recent breakage? for the current failure of popups. DuncanHill (talk) 01:34, 7 August 2015 (UTC)

Assorted changes mentioned and unmentioned above, have resulted in a measurable performance improvement of 500ms for every page view and every single user: phab:F679897. —TheDJ (talk • contribs) 06:27, 7 August 2015 (UTC)

That's a great goal, and it's to be applauded. However, how many thousands of people's scripts have we had to break to get there? Do we even know? We didn't know how many scripts were using Sajax until after its removal was approved, and as far as I can tell we have no idea who's actually using them. — Mr. Stradivarius ^{♪ talk ♪} 14:13, 7 August 2015 (UTC)

Rendering of Bold and Italic in Chrome and Firefox Browsers

I run Chrome and Firefox in Windows 7. I noticed that Chrome browser does not render BOLD text as bold - it looks like normal. And that ITALICS render as boldish text. In Firefox, text looks as expected. Please repeat the experiment and report your results. I have reported the bug to Phabricator. They want more info. Thanks Codwiki (talk) 15:05, 6 August 2015 (UTC)

Works fine for me in both browsers and IE. Eman235/talk 15:24, 6 August 2015 (UTC)

Win7 Chrome OK. 2601:601:0:25:9C04:C9A2:64CB:125C (talk) 16:45, 6 August 2015 (UTC)

Strange global login behavior and bugs with Gecko based browsers

Tracked in Phabricator
Task T108196

Beginning yesterday I have been having very frustrating problems relating to global or single-user login across Wikimedia sister projects. For example, on the latest attempt, logging in via Wikipedia logs me into most sister projects, but not Wikisource and Commons and a few odd others like the test Wikipedias and a couple random Wikimedia sites. Logging in via login.wikimedia.org logs me into Commons but none of the rest. Similar problems affect logging out. I could log out of Wikipedia and still be logged in and able to access preferences and everything else in Wikiquote. I have tried clearing my cache and clearing cookies, and this doesn't help. I've tried creating a new profile in Firefox, and this doesn't help. I've tried using Seamonkey, and this doesn't help. Chrome seems to work fine with global login. djr13 (talk) 16:12, 6 August 2015 (UTC)

Bug filed here. Ironholds (talk) 16:16, 6 August 2015 (UTC)

There's a thread at Wikipedia:Administrators' noticeboard#Login problems (started by Friendly Seven) on what appears to be a similar matter. --Redrose64 (talk) 16:29, 6 August 2015 (UTC)

For reference, I have not so far had any error messages as the user in that thread reported. Of course it's possible it could be related somehow. djr13 (talk) 16:41, 6 August 2015 (UTC)

Just wanted to note I confirmed this with latest stable Firefox:

1. signed into Wikipedia and noticed I wasn't signed into any other project;
2. signed in on Wiktionary and found I was logged into Commons, Meta, and Wikidata;
3. signed out on Wikipedia, and found I wasn't signed out of any other project;
4. signed out on Wiktionary, and found I was signed out of all projects

I couldn't reproduce with Chrome. Logging into and out of Wikipedia logged me in and out of all the other projects. -- Consumed Crustacean (talk) 16:34, 6 August 2015 (UTC)

Djr13 and Consumed Crustacean, could you try again and see if the issues are still happening? I think they should be fixed now. Legoktm (talk) 20:40, 6 August 2015 (UTC)

Appears to work so far. Successfully went to some of the sister projects that worked before with no issue. When I went to Wikisource the notice that I am now centrally logged on and need to refresh appeared, after which I was logged on as normal on all the rest of the sister projects I continued to try. I'll check back here if I have any further issues including spontaneous logouts. djr13 (talk) 23:29, 6 August 2015 (UTC)

• I use Firefox 39, and over the last few hours, up to about a minute ago, I've noticed that I keep getting spontaneously logged out (entirely within Wikipedia), typically when I go to preview or save an edit. --Tryptofish (talk) 20:50, 6 August 2015 (UTC)
• I'm also experiencing spontaneous logouts. I'm using Iceweasel 24.4.0 (a Debianized version of Firefox). My current connection also seems to be losing packets (apparently network congestion), though this has not previously affected my WP logins. ~ J. Johnson (JJ) (talk) 21:55, 6 August 2015 (UTC)

Firefox have just sent out an update, raising the version from 39.0 to 39.0.3, maybe it's related. --Redrose64 (talk) 23:42, 6 August 2015 (UTC)

Or maybe it's the fix. Akld guy (talk) 01:41, 7 August 2015 (UTC)

That's what I meant... I can't have been too clear --Redrose64 (talk) 08:21, 7 August 2015 (UTC)

• I use the latest stable Google Chrome 44 and I had the problems that Redrose64 mentioned above. Before having those problems, Commons recognized my account and I was able to upload an image from German wikipedia, then few hours later I wasn't logged in automatically and whenever I tried to log in, it gave me always the output message:

Login error
Incorrect password or confirmation code entered. Please try again.

Even at Wiktionary I had the same problem. I tried Google Chrome 44 and Firefox 39 on Android 5.1.1 (Google Nexus 9), Microsoft Edge and Google Chrome 44 on Windows 10, and I had the same problem. Now it does automatically log me in and it doesn't output the password error when trying to log in, maybe because I did a password reset within 30 min ago. I will write back if the issue happens again. Cheers (and thank you Redrose64), Friendly Seven (talk) 10:21, 7 August 2015 (UTC)

CSS misbehaving

Just for documentation, if this turns out not to be a real problem, I looked at a history today and every time there was a place to undo another person's edits, there was a "Thank". I also went to a diff and the added information did not show up in green which makes it easier for me to identify what's different. Eventually, a diff did change to green.— Vchimpanzee • talk • contributions • 21:26, 6 August 2015 (UTC)

Surely there normally is a "thank" link? --Redrose64 (talk) 23:24, 6 August 2015 (UTC)

@Vchimpanzee: It's now part of Wikipedia layout, you can now thank other editors for an edit they made. Showing appreciation to others it's a good point in my point of view. Cheers, Friendly Seven (talk) 10:28, 7 August 2015 (UTC)

Lua

Does anybody know how to use various symbols and scripts as self.args. i.e. args. in Lua? For example, if I want to use self.args.ћирилица (cyrillic script) I get redirected to Debug console and don't know what to do... I guess there're some extra signs before and after the text self.args.он отхер сцрипт ор витх вариоус сумболс. --Obsuser (talk) 00:57, 7 August 2015 (UTC)

@Obsuser: Use self.args['ћирилица']. You can only use the dot syntax with names that only consist of a-z, A-Z, 0-9, and _, and that don't start with a number. If you try to use it with any other string, it's a syntax error. — Mr. Stradivarius ^{♪ talk ♪} 02:16, 7 August 2015 (UTC)

@Mr. Stradivarius: Thank you! --Obsuser (talk) 02:28, 7 August 2015 (UTC)

@Mr. Stradivarius: Actually, it's not working. I get Script error: Lua mistake at line --: unexpected symbol near '['. I have also problem with self:renderPerЋИРИЛИЦА(builder, 'Ћирилица', 'ћирилица'). Any way to solve these? --Obsuser (talk) 02:40, 7 August 2015 (UTC)

@Obsuser: self:renderPerЋИРИЛИЦА(builder, 'Ћирилица', 'ћирилица') is another syntax error. You need to write self['renderPerЋИРИЛИЦА'](self, builder, 'Ћирилица', 'ћирилица') (see here for an explanation of how the colon operator works). As for the other error, I think I will need to see your script. Can I have a link? — Mr. Stradivarius ^{♪ talk ♪} 03:04, 7 August 2015 (UTC)

@Mr. Stradivarius: Here. You can compare English version and the one from link to see what I've changed (you can check differences here). I need cyrillic script for all of those words (Strana, strane, datum, lokacija, akcija etc.) so they can be used as parameters in the template. You can change module on .sr project to see if it is working (if you want) because with self.args['ћирилица'] style I get error. Thank you! --Obsuser (talk) 03:53, 7 August 2015 (UTC)

@Obsuser: Hmm, it looks like the best way of doing that would be to use the argument translation feature in Module:Arguments. @Jackmcbarn: I see that argument translation isn't documented at Module:Arguments/doc - is there a particular reason for this, or is it ok to encourage people to use it? — Mr. Stradivarius ^{♪ talk ♪} 04:30, 7 August 2015 (UTC)

Legacy gadgets are disabled

See also: mw:ResourceLoader/Migration guide (users), gerrit:230014, and phab:T107399

There is a thread about current problems with Navigation popups at Wikipedia talk:Tools/Navigation popups#Anyone else getting recent breakage? DuncanHill (talk) 01:21, 7 August 2015 (UTC)

It's being explicitly blocked from loading with the console message "Gadget "Navigation_popups" was not loaded. Please migrate it to use ResourceLoader. See <https://en.wikipedia.org/wiki/Special:Gadgets>. ". There must have been a very recent change that blocked it. Nakon 01:22, 7 August 2015 (UTC)

Not just popups - wikEd and a couple of other tools are offline as well. Nikkimaria (talk) 01:35, 7 August 2015 (UTC)

Does this include the "Change UTC-based times and dates, such as those used in signatures, to be relative to local time." gadget? --NeilN ^{talk to me} 01:58, 7 August 2015 (UTC)

This is likely affecting any gadget that wasn't updated recently. See this commit. Nakon 02:00, 7 August 2015 (UTC)

"The time has come to stop useful things working, without warning people or offering them viable alternatives". DuncanHill (talk) 02:03, 7 August 2015 (UTC)

"The time has come to stop having a development staff which has no accountability to the users it purportedly supports." --NeilN ^{talk to me} 02:22, 7 August 2015 (UTC)

"The time has come to stop whining about every miniscule change in Wikimedia infrastructure."--Anders Feder (talk) 02:35, 7 August 2015 (UTC)

The gadgets should be loaded by ResourceLoader (the "new" method since in 2011), by updating their definition at MediaWiki:Gadgets-definition, and explicitly declaring any dependencies they might have. Helder 02:25, 7 August 2015 (UTC)

I *think* wikEd shouldmight work now? At least, it'll try to load. I also fixed ExternalSearch and CategoryAboveAll. Legoktm (talk) 03:07, 7 August 2015 (UTC)

wikEd is loading for me, and so is popups (on enwiki only) --I am k6ka ^{Talk to me!} _{See what I have done} 03:11, 7 August 2015 (UTC)

I've fixed popups by merging MediaWiki_talk:Gadget-popups.js#ResourceLoader. Nakon 03:21, 7 August 2015 (UTC)

thank you VERY much indeed --Snotty (talk) 03:30, 7 August 2015 (UTC)

@Nakon: Thank you for finding Mxn's fix for popups. I was going through severe withdrawal. -- Gogo Dodo (talk) 06:22, 7 August 2015 (UTC)

Article assessment not appearing

This gadget (available in preferences) is not working. What it does is color-code the article title and provide a little blurb with the article rating (featured article, good article, etc) so the logged-in user can see at a glance the current assessment. It quit working today, so it might be related to the thread directly above. The documentation for the gadget is at User:Pyrospirit/metadata. Thanks to anyone who can help get this useful tool working again. (User:Pyrospirit has not edited since 2012) -- Diannaa (talk) 03:36, 7 August 2015 (UTC)

I've updated the gadget's configuration and it should now be working. Nakon 03:40, 7 August 2015 (UTC)

Yes it is. Thank you, Nakon. -- Diannaa (talk) 03:57, 7 August 2015 (UTC)

Help with css

Is there a way to turn links to dab pages a different color, say orange? (blue, red, and green have already been taken.) Eman235/talk 04:18, 7 August 2015 (UTC)

Dab pages do not cause MediaWiki to emit special HTML, so without Javascript loading every link on a particular page to check whether that page is a dab, the answer is no. Such Javascript would probably be fairly expensive, so I don't think that's an option either. So, probably not regardless. Popups, which loads a page dynamically as you browse over the page, would probably be the best solution to your probable need. --Izno (talk) 04:27, 7 August 2015 (UTC)

@Izno: They do, actually; links to dab pages have the mw-disambig class for me when logged out. Unlike the disambiguation class added by Anomie's linkclassifier linked below, mw-disambig is not applied to links to redirects to dab pages (such as Abc), so the script does do a better job at marking dab links. SiBr₄ (talk) 09:33, 7 August 2015 (UTC)

@Eman235: Your best bet would be to use User:Anomie/linkclassifier with custom css A.disambiguation { background-color:#ffa500; } - NQ (talk) 04:32, 7 August 2015 (UTC)

Wikipedia:Help_desk/Archives/2015_August_2#Wikiproject_Watchlist

Hi, is there any tool or why to do this again?--ԱշոտՏՆՂ (talk) 06:07, 7 August 2015 (UTC)

zh.wiki needs some help about google indexing

Currently, Google is unexpectedly indexing /zh/ language variant URLs instead of /wiki/ links for wikipedia.

A quick example is: https://www.google.com/#q=汉语

As you can see, the first link's URL is https://zh.wikipedia.org/zh/汉语 . But if you open it and check its source, it says

<link rel="canonical" href="https://zh.wikipedia.org/wiki/%E6%B1%89%E8%AF%AD" />

So since the "canonical" version is /wiki/ links, Google should follow and index it instead. But at the moment it's not for some reasons.

The most weird part is, if you search with "site:wikipedia.org": https://www.google.com/#q=汉语+site:wikipedia.org

Almost all the links in the first page suddenly became /wiki/ links (correct behavior).

The problem of /zh/ links is that they ignore user's language variant settings. I need to manually change to /zh-cn/ or /zh-tw/ variants after clicking a link from Google (which is a very common scenario). For /wiki/ links, they would automatically jump to the variants according to user's' preference.

It has been like this for months if not years. I have no idea if it's on Google or Wikipedia. I asked several times on zh.wiki but none takes responsibility or has the ability to fix it. There is some discussion on phab:T54429 but please notice this ticket itself it actually irrelevant with this bug.--fireattack (talk) 10:29, 7 August 2015 (UTC)

What's wrong with this article and its link on Wikidata?

Hello,

Article London and Paris Conferences is linked to a Wikidata item (d:Q450503), but this item and the attached interwiki links do not seem to appear on the page of the article, as they should. I looked at case, changed browser and other obvious answers, and found no reason for this behaviour. Any idea? Place Clichy (talk) 14:05, 7 August 2015 (UTC)

I purged the en.wp page and that fixed it. --Izno (talk) 14:12, 7 August 2015 (UTC)

Thanks! Place Clichy (talk) 14:15, 7 August 2015 (UTC)

Secret semi - protection of talk pages

A number of talk pages present a "you cannot edit" message to IP editors although the history shows that nobody has applied semi - protection to them. Is somebody hacking into the system here, and if this is the cause is there any way to revert them to normal? 92.27.57.70 (talk) 08:46, 7 August 2015 (UTC)

Which pages and which IP editors? Jo-Jo Eumerus (talk, contributions) 08:48, 7 August 2015 (UTC)

Greenwich Mean Time, Hijra (Islam), Universal Time, Islamic calendar, Julian calendar. Also Template talk:Year in other calendars and Template:Jewish and Israeli holidays. All IP editors (and presumably non - autoconfirmed registered editors) are affected. 92.27.57.70 (talk) 08:53, 7 August 2015 (UTC)

Curiouser and curiouser. A semi -protection edit has suddenly appeared in the history. 92.27.57.70 (talk) 09:01, 7 August 2015 (UTC)

For those who are bemused by the comings and goings here, this is the Muhammad images cabal at work. When by consensus pictures of the Prophet are taken down those doing the cleanup are branded "banned users". It's not difficult to see why - it's a no - brainer for them. They can just revert - revert - revert without having to worry about 3RR.

NQ reported 92.27.57.70 at AIV for "disruption at VPT". This was a straightforward technical query. It's a standard modus operandi - make up a false story which will get your opponent blocked. If you run the editorinteract tool on NeilN and NQ you'll see they interact quite a bit. NeilN is the leader of the Muhammad images cabal.

Up to now the ringleaders have been quite good at hiding the abuse from the community but no more. I see that NeilN's attack dog JoeSperrazza has been getting into trouble for removing other people's posts from community noticeboards. When challenged he claims a "misclick" on his part. Perhaps his real target was the comment immediately above:

And a point on the much- loved ROPE essay. Under "When not to use" it says "If a user has already been blocked numerous times for the same behavior, they've already gotten all the rope they need; the hangman is just asleep at the switch" and *Banned users – users blocked by community discussion or ArbCom"...

80.44.163.80 (talk) 14:17, 7 August 2015 (UTC)