Commons:Village pump/Technical

From Wikimedia Commons, the free media repository
Jump to navigation Jump to search
Community portal
introduction
Help deskVillage pump
copyrightproposalstechnical
Administrators' noticeboard
vandalismuser problemsblocks and protections

Shortcuts: COM:VP/T· COM:VPT

Welcome to the Village pump technical section

This page is used for technical questions relating to the tools, gadgets, or other technical issues about Commons; it is distinguished from the main Village pump, which handles community-wide discussion of all kinds. The page may also be used to advertise significant discussions taking place elsewhere, such as on the talk page of a Commons policy. Recent sections with no replies for 30 days and sections tagged with {{section resolved|1=~~~~}} may be archived; for old discussions, see the archives.

Please note
 
SpBot archives all sections tagged with {{Section resolved|1=~~~~}} after 1 day and sections whose most recent comment is older than 30 days.

overlay[edit]

https://commons.wikimedia.org/wiki/File:Karta_%C3%B6ver_Venedig_p%C3%A5_1920-talet_(ur_Nordisk_familjebok).jpg has a box: "Open this image as an overlay in Google Earth (Google Maps, Bing)"

All 3 links do not work. 2A02:810D:6C0:2FB0:B8BD:D76B:D60C:7311 19:46, 17 May 2020 (UTC)

That link is to display File:Karta över Venedig på 1920-talet (ur Nordisk familjebok).jpg/overlay.kml in Google earth and other services. It seems like [1] service on WMF Labs, run by User:Dschwen is down. @Dschwen: any chance you can bring it back on line? --Jarekt (talk) 04:30, 18 May 2020 (UTC)
Dschwen has not been online for half a year, unfortunately. 2A02:810D:6C0:2FB0:D915:28CA:AC30:270C 18:08, 24 May 2020 (UTC)
Anybody else who can help instead? --2A02:810D:6C0:2FB0:3893:1DC7:E319:A1DC 19:15, 21 June 2020 (UTC)

False warning for png files[edit]

Hi. Please excuse my ignorance if this has been discussed earlier, but it seems to be a recent developement. As a frequent uploader using the "basic upload form" option I have started to run into the problem that Commons stops the upload and gives a warning about the file not being in proper png format. This makes no sense, because the file is ok. Furthermore the same files can be uploaded via the Upload Wizard, so there is certainly nothing wrong with them. It only seems to happen with files over 10 MB, so it could be a time-out thing, that has been given a wrong error message. Hope it can be solved, as the Upload Wizard is rather cumbersome for experienced users. Cheers --Rsteen (talk) 06:51, 27 May 2020 (UTC)

Hi again. Not impressed by the response here. You may think "Okay he found a work-around, so no big deal". But how about a new user being met by this error message: "File extension ".png" does not match the detected MIME type of the file (unknown/unknown)." That user might start questioning the validity of hers or his own files, or of the graphics program - totally unnessesary. As I gather, Wikimedia has a programme for making our community kinder and more easily adaptable, especially for new users. Error messages like this one is not a step in that direction. Cheers --Rsteen (talk) 03:29, 1 June 2020 (UTC)
@Rsteen: Please give an example of a file where this has occurred. --AntiCompositeNumber (talk) 04:18, 1 June 2020 (UTC)
@AntiCompositeNumber: Have just uploaded File:Christian Andreas Schleisner - Børn, der søger ly ved en båd på stranden - 1854.png. Tried first via the "basic upload form" and got exactly that error message. Tried then via the Upload Wizard and it ran smoothly - as you can see the file is there. Cheers --Rsteen (talk) 04:24, 1 June 2020 (UTC)
@Rsteen: And what browser and operating system (including version numbers) are you using? --AntiCompositeNumber (talk) 04:27, 1 June 2020 (UTC)
@AntiCompositeNumber: Firefox 76.0.1 (64-bit) and Windows 10 Home Version 1903. --Rsteen (talk) 04:36, 1 June 2020 (UTC)
@Rsteen: Thanks. I want to double-check that this is not an issue with the file itself. Please:
  1. Open the original file from your computer in Firefox using Ctrl-O or the Open button in the menu
  2. Right-click on the file
  3. Click "View image info"
  4. Click "General"
and let me know what it says next to "Type:" in that window? AntiCompositeNumber (talk) 04:42, 1 June 2020 (UTC)
@AntiCompositeNumber: Type: image/png. --Rsteen (talk) 04:47, 1 June 2020 (UTC)
@Rsteen: Thanks, that confirms that this is probably a bug in MediaWiki, not the file itself. It's most likely to be seen and fixed by a developer if it is reported on Phabricator. You can file the report yourself by following the instructions at mw:How to report a bug, or I can file it for you if you prefer. You should add the MediaWiki-Uploading and Commons project tags to the bug report, and make sure to include the information you gave me. --AntiCompositeNumber (talk) 05:03, 1 June 2020 (UTC)
@AntiCompositeNumber: So grateful if you would do it. Phabricator things are a bit out of my league. Cheers --Rsteen (talk) 05:14, 1 June 2020 (UTC)
┌─────────────────────────────┘
@Rsteen: No problem, I've filed phab:T254177. I noticed that the source for File:Christian Andreas Schleisner - Børn, der søger ly ved en båd på stranden - 1854.png is behind a zoom viewer -- did you use a dezoomify tool to retrieve the full resolution file? If so, what tool did you use, and did you use it for the other problem images? --AntiCompositeNumber (talk) 16:20, 1 June 2020 (UTC)
@AntiCompositeNumber: Thanks for your efforts. For all these files I use the dezoomify tool recommended at Help:Zoomable_images. As stated earlier, the Upload Wizard is content with these files - and smaller files go through without problems - so I still think it is a wrongly worded time-out error because of the file sizes. A bit more lenience by the timer system would be appreciated. Cheers --Rsteen (talk) 16:31, 1 June 2020 (UTC)
@AntiCompositeNumber: Hi again. If you can not replicate this error, you should try it on a slower internet connection. You will first get the message that the servers are busy, and please try again later, and when you do that, you will get the message about the wrong file format. Maybe I should have been more specific about this. Cheers --Rsteen (talk) 02:32, 3 June 2020 (UTC)
Rsteen, This may be connected to the fact that the UploadWizard uses chunked uploads, but the legacy upload form does not. I had similar issues when I was behind a slow connection (weak remembrance, because this was years ago). If you do not like the Wizard and dare to use it you could try a script, instead. All in all cf. Help:Chunked upload. — Speravir – 01:38, 7 June 2020 (UTC)
Speravir, thanks for the info. I need a method where I can put a complete artwork template along with the upload, and the legacy way seems to be the only one. Of course it can be retrofitted when you have gone through the Upload Wizard hoops. What gripes me here is the faulty and misleading error message. I gather that the Foundation employs people on the server side to maintain these messages and it is not rocket science to find an erroneous message and change it. Otherwise, new and inexperienced users will continue to be confused, and that can not be what we want. There, you got me on a rant again, sorry. Cheers --Rsteen (talk) 05:38, 7 June 2020 (UTC)
Rsteen, the script supports this, too. Take a look at the sample image for the upload form. There is the lowest input line containing the text “preparing a screenshot”. This would appear as upload comment (plus a hint to the script). It is in fact nowadays a bit larger, and exactly in this field you could insert the (in your words) “complete artwork template”, also including the license tag. I personally dislike this and handle it different (sometimes with the unfortunate side-effect that the MifterBot tags an image as missing a license faster than I can update the info page), see e.g. history of this file (and this edit from my talk page: Special:Diff/394886792/399769132, see also next edit). — Speravir – 00:00, 8 June 2020 (UTC)
Speravir, just what the doctor ordered. Tried it, and it solved the problem. Now, if only somebody would go to work on the false error message. Cheers --Rsteen (talk) 05:07, 8 June 2020 (UTC)

More than a month has passed since this error was reported. If you look at the Phabricator link, it seems that nobody wants to take responsibility for fixing it. As written, the error tells users with slow internet connections that their files are erroneuos, instead of just telling them that they were timed out again. Do we really have to mislead our new/inexperienced users, who just want to upload? How hard can it be to change the words of an error message? --Rsteen (talk) 05:09, 2 July 2020 (UTC)

If this issue were just about changing the wording of an error message, it would have been fixed already. It is not a simple issue, however, it is a complex, hard-to-reproduce issue with an effective work-around in most cases. It also does not fall under the responsibility of a WMF development team, so you are relying on someone to put in the volunteer hours necessary to figure out what is causing the problem and fix it. That time is a limited resource, especially at the moment. --AntiCompositeNumber (talk) 05:59, 2 July 2020 (UTC)
Of course the WMF development team has every right to allocate its resources however it sees fit, but
a) Yes, it is about "changing the wording". You could use a broader error message that also took in account that the file is not broken, but just aborted because of a time-out.
b) No, the error is not "hard-to-reproduce". Just simulate a slow internet connection (if that is within your powers).
c) Yes, there is "an effective work-around". But before you go there, you have probably tried to correct the "faulty" file, which was in fact not faulty at all. And some users will not get to the work-around.
Sorry to impose on your precious time with this issue, but as stated before, Wikimedia has a programme for making our community kinder and more easily adaptable, especially for new users. Error messages like this one is not a step in that direction. Cheers --Rsteen (talk) 11:07, 2 July 2020 (UTC)

Wikidata watchlist messages no longer showing names[edit]

The past few days, the Wikidata edits in my watchlist have stopped showing descriptions, and instead only showing the codes:

When before it would have said something like

Anyone know what's changed? -mattbuck (Talk) 21:29, 11 June 2020 (UTC)

@Mattbuck: This issue was just mentioned in phab:T255078. There are also more serious issues with inaccessible page histories and diffs, so hopefully it will be fixed soon (including readding the labels). —Tacsipacsi (talk) 23:14, 11 June 2020 (UTC)
Tacsipacsi, it seems to be working again, thanks for the info. -mattbuck (Talk) 07:11, 12 June 2020 (UTC)

Another issue (don’t know whether it’s related): Special:Diff/425576840 says:

File:Derby railway station MMB 94.jpg‎ 20:51 +555‎ ‎Tessa piccolina talk contribs block‎ ‎Created claim: depicts (P180): railway station (Q55488) Tag: Computer-Aided Tagging - manual

But Special:PermanentLink/425576840 (which should look exactly the same) says:

File:Derby railway station MMB 94.jpg‎ 20:51 +555‎ ‎Tessa piccolina talk contribs block‎ ‎Created claim: d:Special:EntityPage/P180: d:Special:EntityPage/Q55488 Tag: Computer-Aided Tagging - manual

(When I posted my comment, I just pasted everything as text, not links, so the same issue won’t occur again.) Brianjd (talk) 09:04, 13 June 2020 (UTC)

@Mattbuck, Tacsipacsi: Pinging users who were involved above. Brianjd (talk) 09:05, 13 June 2020 (UTC)
Interestingly there's also some line spacing differences on the page, just a few pixels here and there but noticable when you click back and forth. -mattbuck (Talk) 09:31, 13 June 2020 (UTC)
I created phab:T255356 to request feature parity on oldid pages. (I wouldn’t expect such fast response as in the previous case, as that was emergency with error messages instead of pages, while there’s nothing like that here.) The pixel differences probably arise from how the browser rounds subpixel sizes. —Tacsipacsi (talk) 23:39, 13 June 2020 (UTC)

"In other projects" links to the very same Commons category[edit]

On Category:Felix Frang there is a side bar link "In other projects", Wikimedia Commons, which then links to the very same category. Obviously a Commons category page should not link to Commons itself as "other project". This situation has happened before (in other categories), but I thougth it was fixed. Any idea why it happens again? MKFI (talk) 06:57, 13 June 2020 (UTC)

  • @MKFI: Confirming that I have the same issue. I know nothing about the history of this issue or why it’s occurring now. Brianjd (talk) 08:58, 13 June 2020 (UTC)

How to upload a large PDF (>100MB)?[edit]

Commons:Maximum file size says "The maximum file size for any file on Commons is 4 GiB (4,294,967,296 bytes). Uploads using the Upload Wizard, other tools that support chunked uploads, and server-side uploads must be smaller than this limit."

However when I try to upload https://archive.org/download/catalogofcopy13libr/catalogofcopy13libr.pdf from the URL given, I consistently get a "Wikimedia Error" page.

My next thought was to use a Chunked upload which had worked previously, however for some reason the script didn't seem to want to install or behave according to the documentation. (It did not appear in my sidebar where it was supposed to have).

It is not unreasonable to expect to be able to upload files from a URL, or using a script , with the instructions provided on Commons without having to play "hunt the bug", on a repeated basis.

Can someone here please provide clear one step at time instructions on how a large PDF is supposed to uploaded to Commons without any errors happening? (Because at present it doesn't seem to possible to do it reliably)

ShakespeareFan00 (talk) 11:07, 13 June 2020 (UTC)

\u200e problem[edit]

See special:permalink/387142460, it's generated by subst:lle . The resultant page contains two extra characters \u200e. I suppose something went wrong with {{Lle}} and probably Module:Languages, but I cannot figure out what's wrong. Can you plz help?--Roy17 (talk) 20:56, 15 June 2020 (UTC)

Tech News: 2020-25[edit]

21:36, 15 June 2020 (UTC)

User:Majora/LicenseReview.js[edit]

User:Majora/LicenseReview.js, a common license reviewing script, appears to be interacting poorly with Vector as of MW 1.35.0-wmf.37 today. Unfortunately, this script is unmaintained after Majora retired. Is there a license reviewer with better JS abilities than me who can maintain this script? --AntiCompositeNumber (talk) 20:19, 16 June 2020 (UTC)

If anyone wanna see an example: File:Error_MGA73_2020-06-16.jpg --MGA73 (talk) 20:30, 16 June 2020 (UTC)
w:en:Wikipedia_talk:Twinkle#Update_to_broken_Vector_menu_for_Twinkle_—_DEVS_READ_HERE should provide enough information to fix this issue. --AntiCompositeNumber (talk) 03:01, 17 June 2020 (UTC)
The gadget MediaWiki_talk:Gadget-LicenseReview.js is also affected. --Mdaniels5757 (talk) 15:59, 17 June 2020 (UTC)
… because it is a copy of Majora's script. — Speravir – 22:13, 26 June 2020 (UTC)

Ungrammatical message[edit]

Hi all - I recently renamed a file on Commons and noticed for the first time that one of the messages displayed during the change process reads: "Replacing usage immediately using your user account. Do not close this window until the process completed." Is there any way someone can get in and tweak it so that there is an "is" before that "completed", please? Grutness (talk) 18:12, 17 June 2020 (UTC)

The text is defined on MediaWiki:Gadget-libGlobalReplace.js, so probably your best chance is writing on its talk page (with an {{Edit request}} template), so that even if your request is fulfilled after a long time, it doesn’t get archived too early. By the way, I think the author wanted to use the active voice (the process itself completes, not some third party completes it), although in that case probably it should be present simple, i.e. “until the process completes”. But I’m not a native speaker, so I may be wrong. —Tacsipacsi (talk) 20:39, 18 June 2020 (UTC)
  • I am a native speaker, and it sounds good enough to me. I have made the edit request.
However, what they really need to do is to move all the strings to a separate file, for easy correction and localisation. Brianjd (talk) 13:57, 19 June 2020 (UTC)
@Grutness: I actually prefer “is complete”. But I have no strong feeling either way. Feel free to change my edit request (or make a new one) if you have a better wording. Brianjd (talk) 14:00, 19 June 2020 (UTC)
✓ Done King of ♥ 14:39, 19 June 2020 (UTC)
  • "...is complete" is fine (as is "...completes"). Thanks all :) Grutness (talk) 16:30, 19 June 2020 (UTC)

App is sending DR notices to the nominator instead of the uploader?[edit]

Take a look at Special:Contributions/Nguyenkhoidoanh99 plz. This user makes a few DR apparently via an app (which app?). All the notices went to this user's rather than uploaders' talk pages.--Roy17 (talk) 23:26, 17 June 2020 (UTC)

  • I have no idea which app this is, but there’s another issue: it’s also generating rationales like “Because it is Logo”. Other users have created DRs like this too, and it drives every DR reviewer nuts. Perhaps we could fix this at the same time. Brianjd (talk) 02:15, 18 June 2020 (UTC)
  • Seems to be the Commons Android app. It has the option of giving three or more deletion rationales, one for scope, one for copyvio and one general. So the "Becouse it is" part is standardized within the app in the translatewiki:Wikimedia:Commons-android-strings-delete_helper_ask_alert_set_positive_button_reason/en message. So, you need to figure out what the expected outcome is supposed to be and report the issue at [6].--Snaevar (talk) 13:08, 8 July 2020 (UTC)
I reported a bug very like this, and it was apparently fixed, in March: https://github.com/commons-app/apps-android-commons/issues/3464 I wonder if the user in this case is simply using an outdated version of the App. --bjh21 (talk) 13:23, 8 July 2020 (UTC)

IA's source of Congressional Research Service reports, and removal of front pages...[edit]

I asked User:Fæ to look into mirroring some of the Congressional Research Service reports on IA to Commons in good faith.

It seems however that some of them may have come to IA via a contentious intermediate source.

An example being: File:95-408 (IA 95-408-crs).pdf.

The concerns are i) The copyright or other status of the underlying report. The 'provenance' of the files given the source, and concerns about the inclusion of embargoed materials. ii) Commons shouldn't promote the contentious intermediate source, thus if the file is still okay to host, the front page of the PDF should be removed.

ShakespeareFan00 (talk) 16:33, 19 June 2020 (UTC)

Reports with an actual title (as opposed to just a number) seem to be without a front-sheet for the contentious intermediate source. ShakespeareFan00 (talk) 16:42, 19 June 2020 (UTC)
Plan on getting on with uploading. Whether to mass remove the cover sheet can be a separate discussion which has has no effect on copyright as any CRS report is by law public domain. You could always notify WMF legal to ensure there are no extra-copyright concerns for their employer. -- (talk) 16:43, 19 June 2020 (UTC)
It was more the 'provenance' of the reports, and whether they contained embargoed material, than the copyright as such. ShakespeareFan00 (talk) 17:01, 19 June 2020 (UTC)
Yes, that's clear. However Commons has no policy which recognizes press embargoes for legally public domain material which has been verifiably published. Note that the case in point is 12 years old, hosted at IA for 5 years so far with no take-downs, and there's no internationally recognized superinjunction as far as we know. -- (talk) 17:09, 19 June 2020 (UTC)
There are also no markings on the report to initially indicate the presence of any "sensitive" material. However, given some of the other material the contentious source has dealt with in the past, I hope you can understand the concern and caution. ShakespeareFan00 (talk) 17:18, 19 June 2020 (UTC)

the Q52 project[edit]

Hi! On File:2012 Latvian referendum.svg I see this text in license template: "... Laurijs at the Q52 project. ..." Hmmm Q52... Is it just me or? --MGA73 (talk) 18:02, 19 June 2020 (UTC)

{{PD-user-w/en}} is calling {{Projectname}} without |lang=, and that template didn't properly fall back to {{int:lang}} without a lang parameter. I've fixed that, everything is working now. Not sure why it broke recently. --AntiCompositeNumber (talk) 00:46, 20 June 2020 (UTC)
Thank you @AntiCompositeNumber: --MGA73 (talk) 08:06, 20 June 2020 (UTC)
Perhaps a bot should fix it because it seems that many files use the old way of using the template. Example File:Rotterdamse ZGT.jpg. And the tools that moves files to Commons may need to be changed too. --MGA73 (talk) 08:11, 20 June 2020 (UTC)

Tech News: 2020-26[edit]

18:48, 22 June 2020 (UTC)

"No categorization" in categorized files[edit]

Dear Wikimedians,

while the upload (Upload wizard) I often copy several categories into the field "other information" in this style: [[Category:XYZ]]. Sometimes I do not enter anything into the categorization field. After doing this, my file page gets a "not categorized" template, but the file is properly categorized. Can somebody fix this issue?

Thanks, --PantheraLeo1359531 😺 (talk) 16:29, 23 June 2020 (UTC)

  • @PantheraLeo1359531: The problem with this is that the categories may not be at the bottom of the wikitext, which is where they should be. Example: Special:PermanentLink/428493807. We have a bot to fix this; perhaps we could fix this in the upload wizard too. Brianjd (talk) 09:31, 24 June 2020 (UTC)

Thank you for the answer :) --PantheraLeo1359531 😺 (talk) 16:57, 24 June 2020 (UTC)

Video2Commons problem[edit]

V2C previously had an error, which stuck at "Converting" for a long time, then I decided to aborted the video and try upload once more. However, the status of V2C remained "Your task is being aborted..." for days. I'm being stuck here and cannot upload any video. --A1Cafel (talk) 10:05, 24 June 2020 (UTC)

Sorry, my understanding is that it will remain offline, possibly indefinitely per Phab:T236446 as can any tool that repeatedly accesses YouTube. -- (talk) 10:27, 24 June 2020 (UTC)

Camera heading discrepancies[edit]

File:Royal Crown embellished Pylon.jpg:

There is a discrepancy of 2160 degrees between the above camera heading (set to 101) and the ones stored at SDC (set to 2261). Please reconcile them.

Two questions:

  1. @PhoenixMaimitiValentine: The original description provided by you claims a heading of 2261 degrees in the template (which was later copied to SDC by a bot); can you explain this?
  2. Where does the 101 come from? I can’t see 101 anywhere else.

Brianjd (talk) 03:04, 25 June 2020 (UTC)

  • At least some of the uploader’s other files have the same issue; so whatever the fix is, it needs to be applied there too. Brianjd (talk) 03:06, 25 June 2020 (UTC)

Aloha, Thank you for asking. Please allow me to explain. Mauna ‘Ala (The Royal Mausoleum) is listed at Location: 2261 Nu’uanu Ave on Wikipedia. When I uploaded 2 years ago (I was new to Wiki Loves Monuments) my camera automatically downloaded information into my submission. The SDC by a bot suggested the address it recognizes as the general area for Mauna ‘Ala at Nu’uanu as listed on Wikipedia and I went with that suggestion. My camera had the accurate coordinate while standing infront of the pylon. That would explain 101- the difference from the actual and the accepted according to Wikipedia.

Please help me to decide what you render best! I have 3 entries for Mauna ‘Ala. They may have similar issues, because as stated earlier, my camera had the exact location from where I stood while taking the shot, however Mauna ‘Ala is generally accepted as 2261 Nu’uanu Ave by Wikipedia. I went with whatever suggestion the SDC bot gave. Kalākaua Crypt at Mauna ‘Ala, Chapel at Mauna ‘Ala and Royal Crown Embellished Pylon are all housed at Mauna ‘Ala. What should I do?

What ever you think is the better description, I’ll leave it up to your expertise in this matter. There’s the one the SDC bot suggested or the actual degree my camera recorded. Mauna ‘Ala is not a large area in comparison to other places, however technology has become increasingly more accurate. I just wanted my photos to be associated with the Royal Mausoleum, Mauna ‘Ala so I went with the SDC bot suggestion.   I hope this satisfies your question. If my response is confusing, I remember my camera downloading directly, then having the computer or SDC bot make suggestions with the general location of Mauna ‘Ala. I don’t know how to fix this discrepancy. I’ll need assistance, please.

Mahalo (thanks) PhoenixMaimitiValentine 04:24, 25 June 2020 (UTC)

  • @PhoenixMaimitiValentine: Commons’ signatures policy requires your signature to contain a link to at least one of: your user page, your user talk page or the page listing your contributions. I have added a link to your signature. Brianjd (talk) 04:30, 25 June 2020 (UTC)
    • Your signature should also contain the time of your comment, which I have added. If you type four tildes (~~~~) at the end of your comment, the software will add a valid signature for you. Brianjd (talk) 04:32, 25 June 2020 (UTC)
  • @PhoenixMaimitiValentine: Regarding your photos, I am not sure what is going on here. I will leave it up to the real experts here. (And I still have no idea where the 101 came from.) Brianjd (talk) 04:30, 25 June 2020 (UTC)

Thank You!PhoenixMaimitiValentine (talk) 04:41, 25 June 2020 (UTC)

  • The {{Location}} template on File:Royal Crown embellished Pylon.jpg has a heading specified as heading:2261, which is more than once around the circle. SDC stores the smallest equivalent of this heading, which is 101, because 2261 - (6 × 360) = 101°. — Sam Wilson ( TalkContribs ) … 06:07, 25 June 2020 (UTC)
    • *smacks head* I should have noticed this.
    @Samwilson: Still confused though. If I understand you correctly, the two values that need “reconciling” actually came from the same place. This makes no sense: why doesn’t the system just change the SDC to 101 automatically? Brianjd (talk) 06:11, 25 June 2020 (UTC)
    • No, one comes from the template and one comes from SDC. It’s starting to make sense. But not quite:
      • Looks like SDC value was copied from the template by a bot, so again, the system should have fixed this automatically.
      • The “structured data” tab actually says 2261, which seems to contract your claim that SDC stores the smallest equivalent value of 101.
    Brianjd (talk) 06:13, 25 June 2020 (UTC)
    • @Brianjd: Good question! I'm not sure. I guess that {{Location}} does the reconciling before checking with SDC, and doesn't realise that it's being confused. … Yes, it looks like Module:Coordinates normalizes the heading first, then checks it against what's in SDC. — Sam Wilson ( TalkContribs ) … 06:24, 25 June 2020 (UTC)
      • @Samwilson: Based on the uploader’s response, this problem only affects three files. So I will make sure everything there is set to 101. I will leave it to others to examine Module:Coordinates. Then we should be done here! Brianjd (talk) 06:27, 25 June 2020 (UTC)
        • @Brianjd: Yep, sounds sensible. It's probably a pretty rare thing for any software to write a heading greater than 360°. — Sam Wilson ( TalkContribs ) … 06:29, 25 June 2020 (UTC)
          • @Samwilson: I have fixed the three files. For each file, I fixed the template first (so I could put an explanation in the edit summary), then the structured data. Two lessons here:
            1. We need edit summaries for structured data (Who was the genius who decided not to allow them?).
            2. After fixing the template, but before fixing the structure data, it continued to show the same warning, consistent with your explanation above.
          Brianjd (talk) 06:33, 25 June 2020 (UTC)
          • Oh, wait, the uploader’s response also suggests that 101° might not be the correct value to begin with. I’m obviously getting tired to contribute to Commons. I’m going away now. Brianjd (talk) 06:39, 25 June 2020 (UTC)

Precautionary log out of all users[edit]

Hi all,

According to the linked mailing list post, everyone on Wikimedia wikis will shortly be logged out and will have to log back in again.

Due to a configuration error, session cookies may have been sent in cacheable responses. Some users had reported that they saw the site as if they were logged in as someone else. The number of affected users is believed to be very small. However, resetting all sessions is done as a prudent measure to ensure that the impact is limited.

See also, the complete mailing list thread.

--Kaartic (talk) 08:20, 26 June 2020 (UTC)

Bug in file moving script?[edit]

Hi, I just moved a couple of files which ended up making some strange edits on the files moved (See edit history of the redirect page):

Is this a known bug with the file moving script that I just haven't run into before or should I report this somewhere? TommyG (talk) 08:06, 29 June 2020 (UTC)

Looks like a timing issue/race condition. I moved two files which were referring to one another and they ended up overwriting each others edits. TommyG (talk) 08:09, 29 June 2020 (UTC)

Tech News: 2020-27[edit]

16:30, 29 June 2020 (UTC)

Tech News: 2020-28[edit]

20:17, 6 July 2020 (UTC)

interwiki links not appearing on certain category[edit]

I'm unable to get interwiki links to show up on Category:Kyburz, California even though the corresponding Wikidata item links to the correct articles elsewhere. I tried to re-link the category to a Wikipedia article but got this message: "The page you wanted to link with is already attached to an item on the central data repository which links to Category:Kyburz, California on this site." I removed the links on Wikidata and re-added them, but this did not solve the problem.

Any idea what's going on? Ixfd64 (talk) 21:15, 6 July 2020 (UTC)

For what it's worth, Commons does show up at en:Kyburz,_California but it still is giving a "can't find Wikidata" error. May just be a server lag. -- Ricky81682 (talk) 03:34, 7 July 2020 (UTC)
The discussion at Template talk:Wikidata Infobox#Box loosing connection is related to this. --Hjart (talk) 05:03, 7 July 2020 (UTC)
Not sure if anyone else is still seeing similar issues, but it appears to be fixed for me. Ixfd64 (talk) 18:59, 7 July 2020 (UTC)

"Wikimedia Error"[edit]

Hello, I receive repeatedly error messages during a normal 20 MB+ upload for days right now. The last additional error message I got was Request from - via cp3054.esams.wmnet, ATS/8.0.8 Error: 408, Inactive Timeout at 2020-07-07 12:03:57 GMT. When does this get better? Best regards, Mosbatho (talk) 12:11, 7 July 2020 (UTC)

Are you using Special:Upload? I also experienced that problem, though it was a month ago. It occurs to me whenever I upload a file greater than 2 or 3 MB in Special:Upload. I had to use User:Rillke/bigChunkedUpload.js so that I won't lose any progress. Special:UploadWizard should also work too, since it uploads in chunks (you don't have to go back to the start if the upload suddenly fails), unlike Special:Upload. pandakekok9 Junk the Philippine anti-terror law! 12:33, 7 July 2020 (UTC)
Thank you for your immediate help! Yes, I use Special:Upload. Hmm, so I try it with Special:UploadWizard, although I do not like this option very much. Nevertheless, pandakekok9, thank you for your help! Best, Mosbatho (talk) 13:03, 7 July 2020 (UTC)

Wikimirror Edit Filter Implementation[edit]

Per the consensus here, could I request that someone who understands the ins and outs of edit filters implement one to prevent wikimirror substitution for people editing from censored areas? I'm not sure the zhwiki one I found is reasonable to import without understanding the underlying mechanism. Thanks, Storkk (talk) 10:02, 8 July 2020 (UTC)