Commons:Village pump/Technical

Welcome to the Village pump technical section

Technical discussion
Village pump/Technical
Bug reports
Code review
Tools
Tools/Directory
Idea Lab

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; recent archives: /Archive/2023/10 /Archive/2023/11.

Please note

Feature or bug reports should be filed on Phabricator (see how to report a bug). Bugs with security implications should be reported differently (see how to report security bugs).
Have you read the FAQ?

Start a new discussion

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

Request to add Tai Ahom Unicode to Commons[edit]

Moved to MediaWiki_talk:Titleblacklist#Whitelist Tai Ahom alphabet

Template:No source since[edit]

Needs to be replaced in regexp so that the output is Template:File source. NBS (talk) 06:31, 5 October 2023 (UTC)Reply[reply]

Not really, because "No source since" is used on the file page, and "File source" is used on user chat pages. Snævar (talk) 15:25, 5 October 2023 (UTC)Reply[reply]

Snævar, then what do you propose to replace? NBS (talk) 20:27, 10 October 2023 (UTC)Reply[reply]

@NBS Please elaborate: What exactly seems to be the problem with Template:No source since? El Grafo (talk) 10:06, 11 October 2023 (UTC)Reply[reply]

@El Grafo The template requires installing the same template on the talk page - example. NBS (talk) 21:51, 27 October 2023 (UTC)Reply[reply]

Broken text-anchor:end in SVG renderer[edit]

Tracked in Phabricator
Task T97233

What/when has happened with text alignment in the SVG renderer? I've tried to replace sloppy hyphens with real minus signs in File:Butterworth filter bode plot.svg, where it should have been trivial, as all these labels are already right-aligned (using style="... text-anchor:end"), but instead the new rendered SVG file got all the labels left-aligned, breaking everything. Moreover, when I've reverted the file to its previous version, it also became completely broken, even though previously it was rendered with correct text alignment. It there something wrong with that particular file (which is marked "Valid SVG", BTW), or the renderer here indeed broke recently? — Mikhail Ryazanov (talk) 00:02, 12 October 2023 (UTC)Reply[reply]

@Mikhail Ryazanov:

The damage happened in April 2023 when WMF switched from the approximately 3-year-old librsvg 2.40 to the approximately 5-year-old librsvg 2.44.10 in Buster. That lost some bug fixes, so middle and right aligned text elements may now fail. See Phab:T336894 and Phab:T97233.

Frequently accessed files that have not changed since April 2023 display correctly if the pre-April 2023 PNG comes out of the cache. If the image is re-rendered, then the defects show up. That is why reverting did not restore the correct rendering -- the changes flushed the cache of the correct rendering.

Glrx (talk) 00:39, 12 October 2023 (UTC)Reply[reply]

OK, probably related, but doesn't really match the description. Namely, the entire code chunks look like this:

  <g style="fill:none; color:black; stroke:currentColor; stroke-width:1.00" id="g630">
    <path d="M140,348 L158,348 M1197,348 L1179,348 " id="path631"/>
    <g transform="translate(123,357)" style="stroke:none; fill:black; font-family:Times; font-size:28.00; text-anchor:end" id="g632">
      <switch><text id="text633">
        <tspan id="tspan634">−50</tspan>
      </text></switch>
    </g>
  </g>

There is only one <tspan> element within each <text>, and no x/y at all (only transform="translate(...)" in the parent group). Or this bug has a broader scope and also appears when text-anchor:end is inherited rather than applied directly to <text>? Or it doesn't like <switch>?

In any case, is there any reasonable solution for now? (I can edit the file as would be required but don't want to do so by trial and error and clutter the history.) — Mikhail Ryazanov (talk) 01:07, 12 October 2023 (UTC)Reply[reply]

BTW, why did <syntaxhighlight> insert these colons at each line in my comment above? — Mikhail Ryazanov (talk) 01:10, 12 October 2023 (UTC)Reply[reply]

@Mikhail Ryazanov:

You have a #text node before and after the tspan element. Under the rules, leading and trailing spaces should disappear unless you have xml:space="preserve". Try this:

  <g style="fill:none; color:black; stroke:currentColor; stroke-width:1.00" id="g630">
    <path d="M140,348 L158,348 M1197,348 L1179,348 " id="path631"/>
    <g transform="translate(123,357)" style="stroke:none; fill:black; font-family:Times; font-size:28.00; text-anchor:end" id="g632">
      <switch>
        <text id="text633"><tspan id="tspan634">−50</tspan></text>
      </switch>
    </g>
  </g>

The colons were there because you added them. Colons inside a syntaxhighlight element are not wikimarkup.

Glrx (talk) 01:23, 12 October 2023 (UTC)Reply[reply]

I didn't add the colons myself, but the strange editor that appears after clicking "[reply]" apparently did. I guess, it's also a bug (and I probably should use the regular old code editor instead of these broken "modern" tools...)

Which "#text node before and after" do you mean? The file doesn't use white-space:preserve, so all the line breaks and leading spaces in the SVG source code shouldn't matter. I also don't see any extra elements in the DOM inspector. — Mikhail Ryazanov (talk) 01:37, 12 October 2023 (UTC)Reply[reply]

@Mikhail Ryazanov:

So librsvg 2.44.10 is more broken than I thought — it does not trim. I tried the fix on two "-30" labels in the graph, and it worked.

Glrx (talk) 02:04, 12 October 2023 (UTC)Reply[reply]

Thanks! I've "corrected" the rest, and now it seems to render as expected. Could you please update the bug tracker accordingly (add the case description/workaround or open another bug report, if appropriate)? — Mikhail Ryazanov (talk) 02:23, 12 October 2023 (UTC)Reply[reply]

The reply tool doesn’t support <syntaxhighlight> tags yet (phab:T251633), so yes, you need to use the old editor to use them in replies. —Tacsipacsi (talk) 07:06, 18 October 2023 (UTC)Reply[reply]

File:Pluto-01 Stern 03 Pluto Color TXT.jpg[edit]

This file should be rolled back to the correct version. But which one? 0x0a (talk) 09:12, 15 October 2023 (UTC)Reply[reply]

Leave as is The current version is the one that was assessed at Commons:Featured picture candidates/File:Pluto-01 Stern 03 Pluto Color TXT.jpg, so I'd say leave it at that version. The Squirrel Conspiracy (talk) 09:22, 15 October 2023 (UTC)Reply[reply]

Even if it's a scaled-up version? No more details were provided? 0x0a (talk) 09:32, 15 October 2023 (UTC)Reply[reply]

8000x8000px is the size of the original image as released by NASA, per https://www.planetary.org/articles/09241425-lose-yourself-in-this-pluto. Nosferattus (talk) 00:44, 3 November 2023 (UTC)Reply[reply]

Pdf files not appearing correctly in Commons and not linking to Wikisource[edit]

I appreciate that I have raised this before but the situation seems to be getting worse rather than better. Two recent examples are:

1. [File:The life of and character of Marcus Portius Cato Uticensis - collected from the best ancient Greek and Latin authors; and designed for the readers of Cato, a tragedy (IA lifeofcharactero00theo).pdf], a new version of which was uploaded today:

There was a file of this work on Commons, in the 'File history' section it showed a thumbnail and all file details. I linked this file to a Wikisource Index page and everything worked fine. As I began the transcription of it, it became apparent that the file was incomplete (missing pages) so I obtained another copy and uploaded it to Commons. At first it showed a thumbnail in the 'file history' section and all file details. However, this section subsequently collapsed, with the thumbnails of the original and replacement files disappearing. Oddly, the page size information on the new file has become 0 x 0, while the old file's page sizes are still showing correctly. On the file's page on Wikisource there is no thumbnail at top left and the 'file history' section is incomplete/incorrect as it is on Commons. On the Wikisource index page there is no thumbnail, just a file name. The correct number of pages is showing in the 'Pages' section (the new version has more pages than the original). On creating 'pages', no page image appears. The new file was created and processed using legitimate, licensed PDF software (Foxit PDF editor) and if the file is downloaded from Commons or Wikisource, it opens and displays properly in various PDF readers / browsers.

2. [File:First book of the Iliad; Battle of the frogs and mice; Hymn to the Delian Apollo; Bacchus, or, the Rovers; second book of the Iliad (IA firstbookofiliad00home).pdf]. The following changes were carried out on 5th October 2023.

This file was already on Commons and was being transcribed at Wikisource. However, it was problematic there due to one page rendering as 'black mush' rather than text, despite the page displaying properly in PDF readers, etc. when downloaded. To try and fix this, I rebuilt the file from individual page images (using the same software as for (1) above) and uploaded it. After initial apparent success, the 'file history' for both the original and new files collapsed and the thumbnails disappeared. No thumbnail appears on the Wikisource index page and when attempting to create or edit pages, no page image appears. In this case, the 'file history' information gives the page size as 0 x 0 for both files. To allow work to continue on the transcription, I decided to revert the change, expecting that as the original file worked (mostly) properly, the situation in Wikisource would revert back to working. Only it didn't, and still doesn't. The 'file history' information in Commons and Wikisource shows the page size of the reverted file as 0 x 0, and there is no thumbnail, likewise no thumbnail in WS and no page image when editing.

One thing these two files have in common is rather long given filenames. Is this a potential source of the problem? Chrisguise (talk) 14:04, 17 October 2023 (UTC)Reply[reply]

These files are corrupt and report "Syntax Warning: Invalid least number of objects reading page offset hints table" when checked with the pdfinfo tool. —TheDJ (talk • contribs) 19:11, 17 October 2023 (UTC)Reply[reply]

That warning should not be fatal however. I do wonder if perhaps this is because the new file was resized and has page dimensions that are in decimal numbers.. Dimensions are reported as "Page size: 519.68 x 644.91 pts". Someone will have to experiment a bit to figure out what is really going on. —TheDJ (talk • contribs) 19:19, 17 October 2023 (UTC)Reply[reply]

Here links to the mentioned files:

Also as gallery:

Enhancing999 (talk) 14:32, 17 October 2023 (UTC)Reply[reply]

This may be phab:T297942. Yann (talk) 08:27, 24 October 2023 (UTC)Reply[reply]

New x old file version[edit]

On the 13th October I uploaded a new version of File:The Czechoslovak Review title page without inscriptions4.jpg, differing in quality and colour. The thumbnail shows the new version, but when I click on it, the old version is displayed instead, and when I download it, the old version is downloaded. Also, when displayed in Wikisource, the old version is displayed there too, see e.g. s:Page:The Czechoslovak Review, vol3, 1919.djvu/41. I tried purging the cache, but it did not help. Any advice how to push the new version through? -- Jan Kameníček (talk) 12:59, 20 October 2023 (UTC)Reply[reply]

All of a sudden it works well, so I suppose somebody pushed it through somehow. Thanks. --Jan Kameníček (talk) 22:37, 22 October 2023 (UTC)Reply[reply]

table formatting on mobile[edit]

How can I get the table at https://commons.m.wikimedia.org/wiki/Template:Sheets_Swisstopo_25000#All to not change the width of cells on mobiles?

Tables with text only don't re-scale cells.

I tried adding style="width:.." and style="height:.." on the first cells, but that didn't help. The problem isn't limited to Commons. Enhancing999 (talk) 08:04, 21 October 2023 (UTC)Reply[reply]

I changed the image size to "|frameless|upright=0.2", but that didn't really fix it. Enhancing999 (talk) 16:05, 21 October 2023 (UTC)Reply[reply]

POTD - Interwiki transclusion[edit]

Hello! Is there any bot operator willing to help in achieving this idea here? - Klein Muçi (talk) 15:46, 22 October 2023 (UTC)Reply[reply]

There is Commons:Bots/Work requests, you may have more luck there. —Tacsipacsi (talk) 23:40, 22 October 2023 (UTC)Reply[reply]

Log in via phone[edit]

I'm unable to log into Commons via my phone. No problems on the computer. Anyone know why? APK (talk) 04:17, 23 October 2023 (UTC)Reply[reply]

Tech News: 2023-43[edit]

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

Recent changes

There is a new Language and internationalization newsletter, written quarterly. It contains updates on new feature development, improvements in various language-related technical projects, and related support work.
Source map support has been enabled on all wikis. When you open the debugger in your browser's developer tools, you should be able to see the unminified JavaScript source code. [1]

Changes later this week

The new version of MediaWiki will be on test wikis and MediaWiki.org from 24 October. It will be on non-Wikipedia wikis and some Wikipedias from 25 October. It will be on all wikis from 26 October (calendar).

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

MediaWiki message delivery 23:14, 23 October 2023 (UTC)Reply[reply]

File:Francis of Assisi Basilica Katowice Panewniki 2010.jpg[edit]

What's wrong with this photo? Can someone turn this around? Best regards and thank you in advance! Abraham (talk) 19:00, 24 October 2023 (UTC)Reply[reply]

Abraham Absolutely no idea, but I uploaded a new version that was manually rotated and it looks like it's working. The Squirrel Conspiracy (talk) 20:12, 24 October 2023 (UTC)Reply[reply]

Wikimaps warper not working?[edit]

Hi! I cannot access this link to a georeferenced version of a map from Wikimedia Commons today, using the blue button on page c:File:MNHN_1892.png: it says "502 Bad Gateway. nginx/1.18.0". It worked in July and when I tried to find information about this problem in the Village pump archives a few minutes ago, looking for "wikimap", "wikimaps" or "warper", I did not find anything. Any idea on what the problem is and how to solve it? Thanks in advance!

--FreeCorp (talk) 07:10, 26 October 2023 (UTC)Reply[reply]

Warper is part of wikitech:Nova Resource:Maps, which has quite a few members. I don’t know who’s actually responsible for it. —Tacsipacsi (talk) 19:16, 26 October 2023 (UTC)Reply[reply]

Thanks, I'm not sure I did the right thing but I tried to post a phabricator ticket here: https://phabricator.wikimedia.org/T349865

-- FreeCorp (talk) 19:37, 26 October 2023 (UTC)Reply[reply]

I reported a different problem at Commons:Village_pump/Technical#Wikimaps_Warper_(can't_save,_defaults). Eventually I found Commons_talk:Wikimaps and a workaround. Also there was a github or something, but the project doesn't seem that active anymore.

In generally, the tool works quite well. I was wondering about bulk importing points .. Enhancing999 (talk) 19:55, 26 October 2023 (UTC)Reply[reply]

Deletions of batch uploads[edit]

Not being very familiar with Commons, I am not sure how visible is the discussion I have started at Commons_talk:Deletion_requests#Deletions_of_batch_uploads, so I hope it's okay if I advertise it here too. In short, I would like to make it possible for Commons admins to easily delete all files that were batch uploaded via tools like OpenRefine, and request your feedback and help to figure out how to do it right. − Pintoch (talk) 09:48, 26 October 2023 (UTC)Reply[reply]

sitelink to zh-yue appears twice[edit]

Tracked in Phabricator
Task T350163

In Category:Iao Hon, the same sitelink to zh-yue appears twice in the sidebar. I had a look using Special:ExpandTemplates and it seems to say that {{Wikidata Infobox}} gives one sitelink to [[yue:]] and another to [[zh-yue:]], which does cause this to happen (e.g. User:HTinC23/Sandbox). Is it possible to fix the template/module to avoid this, or is the problem somewhere else? Thank you! —HTinC23 (talk) 00:04, 28 October 2023 (UTC)Reply[reply]

yes i think it's Wikidata Infobox giving two links.

@Mike Peel: could you please take a look?--RZuo (talk) 12:36, 28 October 2023 (UTC)Reply[reply]

@HTinC23 and RZuo: Please could you ask this at Template talk:Wikidata Infobox, and probably also Phabricator? There is an exception in place for zh-yue, but removing that didn't seem to help, this needs further investigation. It should be asked on the template talk page and phabricator so it's in the relevant worklists. Thanks. Mike Peel (talk) 19:53, 28 October 2023 (UTC)Reply[reply]

@HTinC23 and Mike Peel: The zh-yue link is coming from Module:Wikidata Infobox, while the yue link is coming from Module:Interwiki from P460. Removing the latter from the Infobox is overdue but it won't help since a yue is automatically inserted from the connected Wikidata item (the interwiki link is there even if you blank the page). We could add a special case to Module:Wikidata Infobox, making it insert yue links instead of zh-yue, but IMO MediaWiki should just treat both "yue" "zh-yue" equally, see phab:T350163. --LennardHofmann (talk) 16:05, 31 October 2023 (UTC)Reply[reply]

Thanks Lennard, let's see how the bug report goes. Thanks. Mike Peel (talk) 10:26, 4 November 2023 (UTC)Reply[reply]

Captions migration[edit]

Tracked in Phabricator
Task T250114

some files might have captions in the langcode zh-yue. they should be migrated to langcode yue.

how to find all the zh-yue captions?--RZuo (talk) 12:36, 28 October 2023 (UTC)Reply[reply]

Gadget or script that adds a convenience link to use WikimediaOCR？[edit]

is there already one such thing that adds a link to the sidebar (like croptool) to one click feed an image to https://ocr.wmcloud.org ? RZuo (talk) 12:39, 28 October 2023 (UTC)Reply[reply]

I found only a template ({{Transcribe here}}). However, it’s relatively easy, I think this should work (based on the crop tool gadget):

'use strict';
if (mw.config.get('wgNamespaceNumber') === 6 &&
	mw.config.get('wgIsArticle') &&
	/(PNG|GIF|JPE?G|TIF?F|WEBP)$/i.test(mw.config.get('wgTitle'))) {
	$(function () {
		var file = document.getElementById('file');
		if (file) {
			mw.util.addPortletLink(
				'p-tb',
				new mw.Uri('https://ocr.wmcloud.org/').extend({image: file.querySelector('a').href}).toString(),
				'OCR',
				't-ocr',
				'Transcribe text in the image'
			);
		}
	});
}

Maybe worth turning it into a gadget. —Tacsipacsi (talk) 13:05, 29 October 2023 (UTC)Reply[reply]

File:Large format camera lens.jpg (solved)[edit]

I wanted to undo my file upload, but I can't ("The edit appears to have already been undone.") Could somone pl. do that? Thanks, --Mateus2019 (talk) 15:13, 28 October 2023 (UTC)Reply[reply]

@Mateus2019: You need to use "revert" under "File history" rather than "undo" to undo the effect of overwriting a file. --bjh21 (talk) 15:26, 28 October 2023 (UTC)Reply[reply]

it worked, another kind of "undo" just called "revert" --Mateus2019 (talk) 15:32, 28 October 2023 (UTC)Reply[reply]

Tech News: 2023-44[edit]

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 Structured Content team, as part of its project of improving UploadWizard on Commons, made some UX improvements to the upload step of choosing own vs not own work (T347590), as well as to the licensing step for own work (T347756).
The Design Systems team has released version 1.0.0 of Codex, the new design system for Wikimedia. See the full announcement about the release of Codex 1.0.0.

Changes later this week

The new version of MediaWiki will be on test wikis and MediaWiki.org from 31 October. It will be on non-Wikipedia wikis and some Wikipedias from 1 November. It will be on all wikis from 2 November (calendar).
Listings on category pages are sorted on each wiki for that language using a library. For a brief period on 2 November, changes to categories will not be sorted correctly for many languages. This is because the developers are upgrading to a new version of the library. They will then use a script to fix the existing categories. This will take a few hours or a few days depending on how big the wiki is. You can read more. [2][3]
Starting November 1, the impact module (Special:Impact) will be upgraded by the Growth team. The new impact module shows newcomers more data regarding their impact on the wiki. It was tested by a few wikis during the last few months. [4]

Future changes

There is a proposed plan for re-enabling the Graph Extension. You can help by reviewing this proposal and sharing what you think about it.
The WMF is working on making it possible for administrators to edit MediaWiki configuration directly. This is similar to previous work on Special:EditGrowthConfig. A technical RfC is running until November 08, where you can provide feedback.

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

MediaWiki message delivery 23:19, 30 October 2023 (UTC)Reply[reply]

POLISH – https://commons.wikimedia.org/wiki/Creator:...[edit]

Hi! There is a linguistic error in the Polish version of the message: "Ten szablon Kreator opiera się na stronie Wikidata, której brakuje deklaracji szablon autora w Commons (P1472). Kliknij powyższą ikonę , aby dodać tą deklaracje." The last two words should be: tę deklarację. Thank you very much for correcting it. Abraham (talk) 12:57, 31 October 2023 (UTC)Reply[reply]

@Abraham:

Done. You may have to purge the creator page for it to appear. Anon126 (✉ ⚒) 16:51, 31 October 2023 (UTC)Reply[reply]

Upload Errors[edit]

I'm trying to upload a new version of File:October 2023 Gaza−Israel conflict.svg and it has continuously thrown errors. Either it says "Could not acquire lock. Somebody else is doing something to this file." or it gives an error screen that reads: "Request from 71.166.43.40 via cp1083 cp1083, Varnish XID 220586446 ; Error: 503, Backend fetch failed at Fri, 03 Nov 2023 00:09:46 GMT"

I'm getting pretty frustrated. -- Veggies (talk) 00:12, 3 November 2023 (UTC)Reply[reply]

Yes, I had similar errors yesterday evening. But now it looks like it works smooth again, so you may try again? --PantheraLeo1359531 😺 (talk) 15:59, 3 November 2023 (UTC)Reply[reply]

悉請熟悉過濾器的人協助[edit]

正如User_talk:そらみみ#您好所述，過濾器對於道路相關的分類是非常敏感，造成顯示紅色訊息：An automated filter has identified this edit as potentially unconstructive, and it has been disallowed. If this edit is constructive, please report this error. 然而，照片確實是有顯示道路標誌或道路有關的標示牌，若是因為過濾器問題而阻止添加分類，可能會給讀者找尋照片時，錯失可以使用的照片。有鑑於此，悉請熟悉過濾器的人協助，看能否更改設定或修復故障。謝謝。--125.230.90.21 14:52, 5 November 2023 (UTC)Reply[reply]

一張圖片不能編輯而已，算了吧。除非有更多的疑似誤判，否則編輯過濾器並非必須修改。 RZuo (talk) 15:11, 5 November 2023 (UTC)Reply[reply]

不是一張，而是很多張。因為只要是照片有拍攝到道路相關的標示牌及標誌，甚至是圓環設施，所有的分類都會被過濾器給阻擋。這些分類僅止於道路相關的分類，比如圓環夜景、禁止標誌、道路龍門架，而且還有更多分類，未能一一列舉，我已經算不清被擋了多少個分類。我只能說太多照片會受到影響。可是，按照そらみみ回答來看，似乎只有非註冊帳號的IP才會受到阻擋。此外，我連照片名稱寫在這裡也會受到過濾器阻擋 (使用維基file連結會被阻擋)，包含User_talk:そらみみ也是會被阻擋。因此，我懷疑是過濾器有問題。--125.230.90.21 18:08, 5 November 2023 (UTC)Reply[reply]

RZuo，你可以前往Special:Contributions/125.230.90.21查看，我對照片是如何添加分類，如此就能清楚知道我反映的過濾器問題是否屬實。--125.230.90.21 18:13, 5 November 2023 (UTC)Reply[reply]

上次圓環是在這張照片遇到，我是取最後一次編輯給你看。關於更多的編輯，可以前往Special:Contributions/125.230.87.246查看。--125.230.90.21 18:19, 5 November 2023 (UTC)Reply[reply]

有沒有人可以幫忙？我又被過濾器阻擋了。「國六埔里端.jpg」這張照片不能添加道路有關的分類。--125.230.90.219 18:26, 14 November 2023 (UTC)Reply[reply]

Help with a file[edit]

Hi. The file File:MetroPantitlanTerminalLAandL9.JPG was a street file originally. The file can be seen here subtitled "Exterior de la estación en Línea 9, donde cuenta con un CETRAM". For some reason, the file now displays the interior of another station, originally found at File:MetroLazaroCardenasLine9Platform.jpg. Can an admin restore the files as they were before September 2023? Thanks. Tbhotch™ 18:15, 5 November 2023 (UTC)Reply[reply]

I had a look at the deleted file. It is the same as the one you linked. I can not find any other file there. GPSLeo (talk) 18:28, 5 November 2023 (UTC)Reply[reply]

Commons app - Map views would work only with v4.2.1[edit]

Hello all,

I just wanted to spread the word regarding a recent change in the Commons app with respect to map views. Due to some unforeseen circumstances, we had to revoke the Mapbox API key that we were using to render maps in the app. As a consequence all map views in v4.2.0 and below would fail to load i.e., they would get stuck with a blank screen. Kindly upgrade the app to version 4.2.1 in order to fix this issue and continue using features that need a map view. This update is available via Play Store and F-droid.

We regret the inconvenience that this may cause. Feel free to open an issue in our issue tracker or leave a message in our app's talk page for any assistance. We could be glad to help with any issues you may face.

Related thread in commons-l.

cc @Syced

-- Kaartic ^[^talk^] 18:38, 6 November 2023 (UTC)Reply[reply]

Log In Error[edit]

When attempting to log in to Wikimedia Commons via non-incognito mode Google Chrome I receive the error: "No active login attempt is in progress for your session." I can still log in to Wikipedia via regular mode or Wikimedia Commons via incognito mode fine. I tried disabling all of my extensions in regular mode, but that didn't help. I had just updated Google Chrome before attempting to log in, so it would seem to be somehow related to changes made as part of the update. Any ideas what could be causing this and how to fix it? –Noha307 (talk) 20:03, 6 November 2023 (UTC)Reply[reply]

Tech News: 2023-45[edit]

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

In the Vector 2022 skin, the default font-size of a number of navigational elements (tagline, tools menu, navigational links, and more) has been increased slightly to match the font size used in page content. [5]

Problems

Last week, there was a problem displaying some recent edits on a few wikis, for 1-6 hours. The edits were saved but not immediately shown. This was due to a database problem. [6]

Changes later this week

The new version of MediaWiki will be on test wikis and MediaWiki.org from 7 November. It will be on non-Wikipedia wikis and some Wikipedias from 8 November. It will be on all wikis from 9 November (calendar).
The Growth team will reassign newcomers from former mentors to the currently active mentors. They have also changed the notification language to be more user-friendly. [7][8]

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

MediaWiki message delivery 21:03, 6 November 2023 (UTC)Reply[reply]

Bad changes to the upload wizard[edit]

When I used the upload wizard today, I encountered some changes that must've been made recently to the license release section. Before, if I remember correctly, it just assumed I wanted to use CC BY-SA 4.0 unless I specified otherwise, but now it asks me to actively choose between three different licenses. I cannot manage to find discussion of this (the "leave feedback" button leads to a page marked as inactive, which is something we probably want to fix); was it discussed centrally?

I think it's a terrible change. Choice paralysis is a huge thing, so to improve the upload wizard we want people to have to make as few choices/fill out as little as possible while still getting all the data/assurances we need. The old version did that very well: It offered CC BY-SA 4.0, which is a great license, by default, while still allowing people to choose a different one if they so desired. The new version, by contrast, requires an extra click and forces people to choose between three options that all look very similar (especially to someone inexperienced in copyright). Some number of newcomers are going to be confused enough by that choice that they're going to decide not to bother continuing their upload, and we're going to lose contributions. {{u|Sdkb}} ^talk 04:18, 7 November 2023 (UTC)Reply[reply]

OK, looking at the tech news above, this appears related to phab:T347756. I'll put pointers to here from there and other relevant places. {{u|Sdkb}} ^talk 04:22, 7 November 2023 (UTC)Reply[reply]

I believe it's part of Commons:WMF support for Commons/Upload Wizard Improvements. I see a lot of copyvio files where the uploader just goes with the default license even though it's obviously incorrect, so I'm glad to see something that forces users to actually make a decision. I do understand it may be an inconvenience for experienced users; perhaps a setting could be made for users over a certain threshold to select a default. Pi.1415926535 (talk) 04:28, 7 November 2023 (UTC)Reply[reply]

Yeah, there's absolutely some element of productive friction we'd like to reduce copyvios. But this ain't it. People who are encountering this choice have already declared that the file is their own work, so this is a next step that doesn't really add anything.

Regarding the inconvenience, I'm more concerned about inconvenience for new users than I am about inconvenience for experienced folks, since we're going to upload no matter the hassle, but they won't. More broadly, I object to the "just add friction until we get rid of copyvios" mentality (not saying your comment is this, Pi, just that I've observed it more generally here). At Wikipedia, as awful as the experience is for newcomers, there's at least a recognition that the project needs all the help it can get, so it's a good thing that they're present. But here, where the community is mostly patrollers of one sort or another, we too often make choices that add big hurdles for uploaders with zero awareness of the cost we're paying in terms of abandoned contributions. To retain our position as a centralized repository of images, we need to make it easy enough for people to upload that they choose to upload here and we maintain a strong collection. If we don't, people looking for free images will just go to Flickr instead. And needless hurdles like this one are not how we make it easy to contribute. {{u|Sdkb}} ^talk 04:56, 7 November 2023 (UTC)Reply[reply]

The default license that is setup in the preferences is also used in the new dialogue. So this is still a one click step of those who changed the default to be asked every time. The difference to Wikipedia is that if people do not read the guidelines there it is only an editorial problem, here it can have serious legal implications. GPSLeo (talk) 06:44, 7 November 2023 (UTC)Reply[reply]

@Sdkb: Thanks for involving us in this discussion, and we definitely thank you for raising this issue.

We did this change to increase intentionality in users in choosing a particular license when uploading medias to Commons. Also, while we run the usability tests for the changes we made, users didn't seem to get confused when it came to choose a license. We acknowledge there might be still some possibility for users to get confused, but the estimate seems to be small.

Maybe, to reduce friction, we can evaluate a possibility for people to know how to input a default license for own works in their preferences or giving some extra links to Commons guidelines for licenses. Would it help, in your opinion, reduce the issue you're suggesting? Sannita (WMF) (talk) 13:39, 7 November 2023 (UTC)Reply[reply]

@Sannita (WMF), can you describe/point me more specifically to the user research you did on this issue? I'd find it persuasive if e.g. you did an A/B test of having a default own work license vs. not and found it made no difference in the rate at which newcomers completed uploads. But I would be surprised, since everything I know about UX indicates that when you make a form longer, fewer people fill it out.

Regarding the suggestion of something in user preferences, that wouldn't hurt, but again, that doesn't help newcomers, who will be starting with the default preferences. I'm not coming at this from the angle of being annoyed for myself at having to make an extra click; I'm concerned about it reducing the number of contributions we get from new users. I've had multiple experiences of suggesting to non-Wikipedian friends who have taken photos that they upload them to Commons, only to have them come back and say "well, I tried, but the upload form was so complex, how about I just send it to you instead". Ensuring that uploaders mean it when they declare something their own work is absolutely essential, but I'm not convinced that this particular change does that (again, did an A/B test indicate it resulted in fewer copyvios?), or that there are not other things we could introduce for the price of one click that'd be far more effective at that goal. And overall, the "let's throw friction at the wall until it sticks" approach without concern for the impact it has on contributions is a dangerous path. If we end up at the point where we're increasing intentionality by requiring uploaders to take a lie detector test and then sign a notarized form and then submit to a 30-minute Zoom interview where an AI grills them about their work,^[hyperbole] we're no longer going to have contributors. {{u|Sdkb}} ^talk 15:47, 7 November 2023 (UTC)Reply[reply]

@Sdkb I asked the designer to give me the data you requested, and I hope to follow soon with the answer. Anyway, our scope is try to strike a (very delicate, indeed) balance between increasing intentionality in users and not discouraging them from uploading because of too many options to tick, so we do share your point. Sannita (WMF) (talk) 16:37, 8 November 2023 (UTC)Reply[reply]

@Sdkb I just came out of a meeting with the designer, and I have some answers for you: we conducted two separate tests, one on the old UI (you can find a summary of the findings at pages 14 to 17 of this report) and another one on the new UI that we introduced with the latest changes. While I cannot share with you publicly (yet) the full findings of the second test, I can tell you that all of the participants to the test were able to select the license of their liking without hesitation, and the UI didn't influence their choice. As soon as there is a public report on this test, I'll ping you.

Anyway, our plans are to rework the whole experience of uploading medias on Wikimedia Commons, always with having in mind the objective of striking the balance I told you about in my last message. While I can't make any precise promise about what will change, one of the hypothesis we're working on is to make other steps of the process easier for new users, in order to rebalance the slight improvements we made on the "release rights" step. I hope this sounds sufficient as an answer for you. Sannita (WMF) (talk) 18:01, 8 November 2023 (UTC)Reply[reply]

A problem I have with the new Upload Wizard is that I can no longer add license information to every upload at once if it deviates from the three options you're given at the start. Even if I use the "Copy information to all uploads" function and then check the box "Copy other information" it doesn't apply copyright information to all the files. ReneeWrites (talk) 11:13, 8 November 2023 (UTC) EDIT: The option is still there, it shows up if I pick the option that I'm uploading someone else's work. I should've just looked around for a bit longer, disregard my complaint. ReneeWrites (talk) 01:02, 9 November 2023 (UTC)Reply[reply]

@ReneeWrites Thanks for reporting this, have you already opened a Phabricator ticket for this? If not, I can do it, but then I might ask you some more details about the problem you're having with uploads, in order to help the developers understand what's going on. Sannita (WMF) (talk) 16:38, 8 November 2023 (UTC)Reply[reply]

Where can I open the ticket? I'm fine with you doing it for me and me then answering questions, though. ReneeWrites (talk) 16:39, 8 November 2023 (UTC)Reply[reply]

@ReneeWrites I'll contact you on your talk page with the necessary questions, so that we don't occupy too much space here. Sannita (WMF) (talk) 18:06, 8 November 2023 (UTC)Reply[reply]

Template:Wdib/doc[edit]

There's some error in the example usages in Template:Wdib/doc that is causing categories of the example items to be added to the categories of the template. I've temporarily commented it out at Special:Diff/819452047, but a proper solution is needed. Pi.1415926535 (talk) 20:30, 7 November 2023 (UTC)Reply[reply]

Lost access to structured data[edit]

I seem to have lost access to structured data. When I look at an image, I no longer see the caption, or the tab to view and edit the other structured data. As far as I can tell I havn't accidentally changed any of my settings. This happened in the last couple of hours, as I was happily seeing and editing them earlier today. Is this an expected change, or can anybody suggest what I might have snafued. -- Chris j wood (talk) 12:40, 8 November 2023 (UTC)Reply[reply]

Same with me, and the edits where I added structured data are still shown on my contribution list (and I can undo them). Ymblanter (talk) 12:58, 8 November 2023 (UTC)Reply[reply]

And bots are still adding the structured data. Ymblanter (talk) 13:17, 8 November 2023 (UTC)Reply[reply]

appears normal for me (firefox win10).

can you give an example where you dont see the sdc tab? RZuo (talk) 13:24, 8 November 2023 (UTC)Reply[reply]

I am on Firefox Ubuntu, do not see it on my recent uploads (checked a few of them). Ymblanter (talk) 13:31, 8 November 2023 (UTC)Reply[reply]

It is back now, may be it was a glitch. Ymblanter (talk) 13:31, 8 November 2023 (UTC)Reply[reply]

Yes, back for me too. And I was using Chrome, so not browser related. -- Chris j wood (talk) 15:58, 8 November 2023 (UTC)Reply[reply]

Other versions[edit]

The template {{Artwork}} is used on the file File:Edvard_Munch_-_Pikene_på_broen.jpg. The parameter "other_versions" is empty but three images are shown anyway. When adding an image to that parameter so it is no longer empty, then all other images disappear (at least in the preview). The documentation about the parameter "other_versions" does not describe which (or why) images are displayed when the parameter has no value. --Bensin (talk) 20:35, 8 November 2023 (UTC)Reply[reply]

@Bensin: When the parameter has no value, the default is to use information from Wikidata (item for this work: The Girls on the Bridge (Q18891073)). There are several Wikidata properties used for this parameter, and I've added a few of them to the table in the documentation under the "Default" column. Anon126 (✉ ⚒) 10:41, 10 November 2023 (UTC)Reply[reply]

Thank you! That is helpful. --Bensin (talk) 19:47, 10 November 2023 (UTC)Reply[reply]

Upload bug[edit]

Tracked in Phabricator
Task T350917

The file has uploaded with a strange gray stripe at the bottom. It seems that it hasn't uploaded completely. Anyone has the same problem? Юрий Д.К 17:34, 9 November 2023 (UTC)Reply[reply]

Yes, it happens sometimes. The second upload always was successful in my case. Ymblanter (talk) 20:11, 9 November 2023 (UTC)Reply[reply]

how wonderful... now we will have a new category to work on after Category:Incomplete JPG files (5 MB interruption), yeah!--RZuo (talk) 20:59, 9 November 2023 (UTC)Reply[reply]

Mobile-frontend-return-to-page[edit]

this seems to be a system message, from https://translatewiki.net/wiki/Special:PrefixIndex/MediaWiki:Mobile-frontend-return-to-page . somehow it's not displaying correctly anymore, as you can see if you use MediaWiki:Gadget-Cat-a-lot.js or MediaWiki:Gadget-Restore-a-lot.js. anyone knows why and how to fix it? or if we can find another system message to put in place of this? RZuo (talk) 08:34, 12 November 2023 (UTC)Reply[reply]

Watchlists[edit]

Is there a way to set up a commons category page on your watchlist so that when someone adds a new image to the category, you can see that on your watchlist?

I keep an eye on the climbing area and have lots of climbing category pages on my watchlist, but when a new image is added under a climbing category I won't know unless I explicitly visit that category page and see it? thanks. Aszx5000 (talk) 12:04, 12 November 2023 (UTC)Reply[reply]

Special:Preferences#mw-prefsection-watchlist untick "Hide categorization of pages".

then watch the cats you want to monitor. RZuo (talk) 15:32, 12 November 2023 (UTC)Reply[reply]

Thank you so much for that! Aszx5000 (talk) 22:13, 12 November 2023 (UTC)Reply[reply]

Tech News: 2023-46[edit]

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

Four new wikis have been created:
- a Wikipedia in Moroccan Amazigh (w:zgh:) [9]
- a Wikipedia in Dagaare (w:dga:) [10]
- a Wikipedia in Toba Batak (w:bbc:) [11]
- a Wikiquote in Banjar (q:bjn:) [12]

Problems

Last week, users who previously visited Meta-Wiki or Wikimedia Commons and then became logged out on those wikis could not log in again. The problem is now resolved. [13]
Last week, some pop-up dialogs and menus were shown with the wrong font size. The problem is now resolved. [14]

Changes later this week

The new version of MediaWiki will be on test wikis and MediaWiki.org from 14 November. It will be on non-Wikipedia wikis and some Wikipedias from 15 November. It will be on all wikis from 16 November (calendar).

Future changes

Reference Previews are coming to many wikis as a default feature. They are popups for references, similar to the PagePreviews feature. You can opt out of seeing them. If you are using the gadgets Reference Tooltips or Navigation Popups, you won’t see Reference Previews. Deployment is planned for November 22, 2023.
Canary (also known as heartbeat) events will be produced into Wikimedia event streams from December 11. Streams users are advised to filter out these events, by discarding all events where meta.domain == "canary". Updates to Pywikibot or wikimedia-streams will discard these events by default. [15]

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

MediaWiki message delivery 23:49, 13 November 2023 (UTC)Reply[reply]

Flickr2Commons[edit]

F2C stucking to "Loading..." when I just open the tool. Only I have the problem? Юрий Д.К 22:14, 15 November 2023 (UTC)Reply[reply]

Commons:Village pump/Technical

Contents

Request to add Tai Ahom Unicode to Commons[edit]

Template:No source since[edit]

Broken text-anchor:end in SVG renderer[edit]

File:Pluto-01 Stern 03 Pluto Color TXT.jpg[edit]

Pdf files not appearing correctly in Commons and not linking to Wikisource[edit]

New x old file version[edit]

table formatting on mobile[edit]

POTD - Interwiki transclusion[edit]

Log in via phone[edit]

Tech News: 2023-43[edit]

File:Francis of Assisi Basilica Katowice Panewniki 2010.jpg[edit]

Wikimaps warper not working?[edit]

Deletions of batch uploads[edit]

sitelink to zh-yue appears twice[edit]

Captions migration[edit]

Gadget or script that adds a convenience link to use WikimediaOCR？[edit]

File:Large format camera lens.jpg (solved)[edit]

Tech News: 2023-44[edit]

POLISH – https://commons.wikimedia.org/wiki/Creator:...[edit]

Upload Errors[edit]

悉請熟悉過濾器的人協助[edit]

Help with a file[edit]

Commons app - Map views would work only with v4.2.1[edit]

Log In Error[edit]

Tech News: 2023-45[edit]

Bad changes to the upload wizard[edit]

Template:Wdib/doc[edit]

Lost access to structured data[edit]

Other versions[edit]

Upload bug[edit]

Mobile-frontend-return-to-page[edit]

Watchlists[edit]

Tech News: 2023-46[edit]

Flickr2Commons[edit]

Navigation menu

Commons:Village pump/Technical

Request to add Tai Ahom Unicode to Commons[edit]

Template:No source since[edit]

Broken text-anchor:end in SVG renderer[edit]

File:Pluto-01 Stern 03 Pluto Color TXT.jpg[edit]

Pdf files not appearing correctly in Commons and not linking to Wikisource[edit]

New x old file version[edit]

table formatting on mobile[edit]

POTD - Interwiki transclusion[edit]

Log in via phone[edit]

Tech News: 2023-43[edit]

File:Francis of Assisi Basilica Katowice Panewniki 2010.jpg[edit]

Wikimaps warper not working?[edit]

Deletions of batch uploads[edit]

sitelink to zh-yue appears twice[edit]

Captions migration[edit]

Gadget or script that adds a convenience link to use WikimediaOCR？[edit]

File:Large format camera lens.jpg (solved)[edit]

Tech News: 2023-44[edit]

POLISH – https://commons.wikimedia.org/wiki/Creator:...[edit]

Upload Errors[edit]

悉請熟悉過濾器的人協助[edit]

Help with a file[edit]

Commons app - Map views would work only with v4.2.1[edit]

Log In Error[edit]

Tech News: 2023-45[edit]

Bad changes to the upload wizard[edit]

Template:Wdib/doc[edit]

Lost access to structured data[edit]

Other versions[edit]

Upload bug[edit]

Mobile-frontend-return-to-page[edit]

Watchlists[edit]

Tech News: 2023-46[edit]

Flickr2Commons[edit]

Navigation menu

Search