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

RSVG rendering preview on user:Rillke/MwJSBot.js not working[edit]

Tracked in Phabricator
Task T345972

When I preview any SVG using User:Rillke/MwJSBot.js, I don't get the RSVG rendering preview to work. It just shows the default File:Bug blank.svg as if the SVG is broken, but they aren't. Am I the only one having this problem? Jonteemil (talk) 16:48, 23 July 2023 (UTC)Reply[reply]

Anyone? Jonteemil (talk) 14:48, 28 July 2023 (UTC)Reply[reply]

@Glrx: Can you confirm or disconfirm this? Jonteemil (talk) 19:11, 2 August 2023 (UTC)Reply[reply]

@Jonteemil and Rillke:

I've been using User:Rillke/SVGedit.js for a time, but I have not paid much attention to the RSVG rendering. I usually do not hit the preview button. When I do, I'm happy to see a local SVG rendering. RSVG departs from the SVG specification in a few places.

The RSVG preview has not worked in a long time. For example, using SVGedit on File:IPv6 header-en.svg (which specifies a width and height) does not produce an RSVG preview.

If I look at the SVGedit code, line 396 does a fetchPreview(val). I presume that obtains the RSVG rendering. That method probably fails, so line 413 substitutes a PNG rendering of File:Bug blank.svg. (An alternative explanation is the preview method succeeds but line 399 image/jpeg is incorrect and causes a failure. I expect RSVG to return an image/png rather than an image/jpeg. Data URL claims JPEG but is PNG. Another possibility is the line 411 timeout is too short.)

Looking further, fetchPreview sends its request to //convert.toolforge.org/svg2png.php. If I go to that website and issue a request for a large (2199×1477) SVG file, I get a 500 Internal Server Error. If I give it a small file, my computer receives a appropriate PNG. I will guess the endpoint functions for at least some files.

That leads me back to guessing something goes wrong inside of line 397 .done.

Glrx (talk) 20:51, 2 August 2023 (UTC)Reply[reply]

@Glrx: Okay, I don't probably use the tool as often as you do but I do it from time to time and I always preview so I don't happen to save anything erroneous. This problem is something that I haven't experienced before so it must be some new change to the code, or the code of another program that the SVGedit tool uses. Do you know of anyone who'd be willing to take a look at fixing this? Jonteemil (talk) 04:46, 3 August 2023 (UTC)Reply[reply]

@Jonteemil and Cmglee:

You load SVGedit from Meta:User:Jonteemil/global.js, but you use Cmglee's version at User:Cmglee/SVGedit.js. That's fortunate because Cmglee is still active; Rillke has not edited in some time. You can ask Cmglee to try changing line 401 to use image/png to see if that fixes preview.

Glrx (talk) 05:32, 3 August 2023 (UTC)Reply[reply]

Thanks for your clear instructions and analysis, @Glrx: I've changed "jpeg" to "png" but the problem persists. I think rsvg previews are broken as with commons:commons_SVG_Checker. Would you be able to debug why commons:commons_SVG_Checker also gives the bug image? Thanks, cmɢʟee ⋅τaʟκ 15:34, 3 August 2023 (UTC)Reply[reply]

@Cmglee:

Thanks for running the test. I'll try looking at the HTTP transfer and see if there are cross origin issues.

The code backing the SVG Checker also uses line 451 image/jpeg:

MediaWiki:CommonsSvgChecker.js

Thanks again.

Glrx (talk) 17:58, 3 August 2023 (UTC)Reply[reply]

image/jpeg likely isn't the issue as it worked before around 2019. Don't know if Commons_talk:Commons_SVG_Checker#is_it_down? is a useful lead. Thanks too for trying, cmɢʟee ⋅τaʟκ 19:23, 3 August 2023 (UTC)Reply[reply]

@Cmglee and Jonteemil:

I go to Commons SVG Checker, select an SVG file, and then execute the SVG check.

The request to convert.toolforge.org/svg2png.php fails.

The request origin is https://commons.wikimedia.org
The host origin is https://convert.toolforge.org
The host returned the appropriate image/png
simple request, multipart/form-data, no preflight required

Console reports

Referrer Policy: Ignoring the less restricted referrer policy “origin-when-cross-origin” for the cross-site request: https://convert.toolforge.org/svg2png.php index.php:322:8

Cross-Origin Request Blocked: The Same Origin Policy disallows reading the remote resource at https://convert.toolforge.org/svg2png.php. (Reason: CORS header ‘Access-Control-Allow-Origin’ missing). Status code: 200.

The request fails in the browser because the svg2png does not supply an appropriate Access-Control-Allow-Origin header.

Cannot find tool on toolforge.org.

Guess this is the source

https://github.com/Toollabs/convert

This URL should return the version:

https://convert.toolforge.org/svg2png.php?version → JSON rsvg-convert version 2.44.10

svg2png.php line 35 calls matchOrigin($origin) and emits appropriate CORS access headers if there is a match. I'm confused. The access headers were not emitted, but if no match then no PNG should be emitted (exit is called before calling RSVG). A PNG was emitted. Is there another source? Is PHP or something else suppressing the CORS headers?

I cannot find matchOrigin; I expect it to be in shared/commons.php, but that links to Rillke (which is not 2 dirs up).

Interesting GitHub issue re toolforge and wmflabs (apparently fixed by renaming wmflabs URLs to toolforge URLs around 2020).

line 8 uses old URL:

$url = $prot . "://tools.wmflabs.org/$tool_user_name/";

but does not seem to be used for matching the origin.

Glrx (talk) 20:36, 3 August 2023 (UTC)Reply[reply]

@Jonteemil and Cmglee:

I suspect that is not the current source. I can convert SVG to PNG from a non-WMF origin, so I suspect the current source has deleted not only the origin matching test but also the CORS headers.

Glrx (talk) 21:19, 3 August 2023 (UTC)Reply[reply]

@Glrx: Thanks again for investigating. I must admit that your findings are far beyond what I'm familiar with. Pinging @Redrose64: and @JoKalliauer: (may not be active recently) for their opinions, cmɢʟee ⋅τaʟκ 02:22, 4 August 2023 (UTC)Reply[reply]

@Cmglee and JoKalliauer:

Turns out that Johannes cloned convert to make his SVG workaround bot. His clone has the matchOrigin code:

https://github.com/JoKalliauer/convert

I still cannot explain the failure to supply the CORS headers.

Glrx (talk) 04:12, 4 August 2023 (UTC)Reply[reply]

@Glrx and Jonteemil: I do not know why Rillke's rendering does not work, maybe consider reopening phab:T217362.

I assume that Commons:Commons_SVG_Checker might use the same code, which recommends since 2019 to use @Jarry1250: tool: https://svgcheck.toolforge.org/ which works imho flawlessly. (But you have to manually upload the image.)

I assume that

webservice stop
webservice --backend=gridengine start

would fix it, see wikitech:Help:Toolforge/Web. I also sometimes have to restart webservice for https://svgworkaroundbot.toolforge.org/ to work again.

github.com/JoKalliauer/convert doesn't help in this case, it only converts svg to (less buggy) svg, it does not render svg to png, and the issue with User:Rillke/MwJSBot.js is imho independent on the SVG, therefore it won't help. I use Rillke's code basically as black-box without understanding JavaScript, so I won't be helpful in bug fixing the code, or finding the issue.

I'm basically inactive, and stopped following treads, however I'm happy to get pinged to help. :-)

— Johannes Kalliauer - Talk | Contributions 07:50, 4 August 2023 (UTC)Reply[reply]

There should be a Phabricator issue (or equivalent) about this toolforge app. It is used in several places, but the behavior of the installed tool does not match the existing (and incomplete) GitHub source. Furthermore, a modification to the tool source (make the web page display the PNG rather than download it: Content-Disposition header) could avoid a lot of uploads at File:Test.svg. Glrx (talk) 23:40, 18 August 2023 (UTC)Reply[reply]

Submitted Phab:T345972 Glrx (talk) 04:27, 9 September 2023 (UTC)Reply[reply]

Similar issue at Commons_talk:Commons_SVG_Checker#Previews_aren't_generated. Glrx (talk) 16:57, 8 October 2023 (UTC)Reply[reply]

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]

Missing files after file move[edit]

Hi, during moving files earlier this morning, it seems that I and User:TKsdik8900 moved a number of files at the same time. I'm not sure that this is the cause or if there's some other reason why the actual files has gone missing after moving the following files:

Would anyone be able to locate where the actual files went and get them reattached to the respective file pages? TommyG (talk) 09:09, 7 October 2023 (UTC)Reply[reply]

I have tried to restore them from the original Flickr sources or Wayback Machine, but failed to find. I'm sorry for not realising you were working on them. --TKsdik8900 (talk) 09:21, 7 October 2023 (UTC)Reply[reply]

Yeah, there's a number of bugs in the file moving scripts with regards to race conditions and concurrency issues, but I don't think I've encountered this specific issue before. Most others are easily fixable but I have no idea where the files went in this case :-) TommyG (talk) 09:59, 7 October 2023 (UTC)Reply[reply]

Blanking coused by file renaming[edit]

When I renamed File:Blason Louis Nicolas d'Avout (1770-1823).svg to File:Blason Louis Nicolas d'Avout (1770-1823) duc d'Auerstaedt.svg, the automatic edit to replace usage has blanked all the contents of w:Armorial of the First French Empire in w:Special:Diff/1179001857. Was this a bug or something? It might have been caused by our moving files at the same time as above. --TKsdik8900 (talk) 09:43, 7 October 2023 (UTC)Reply[reply]

Internal error when uploading audio file[edit]

I received an error that prevents me from updating the upload of my fileː here. It says [176da193-efc3-43bd-862a-27affe7961fe] 2023-10-07 13:33:01: Fatal exception of type "Wikimedia\Rdbms\DBUnexpectedError". This is the second time this has happened.

I've researched online, and as far as I know don't see the specific factor that triggered this server issue. I use the Brave browser, only have one extension (Google Translate), and the upload is 6.91MB, which isn't that big for an OGG file. Requesting assistance. SuperWIKI (talk) 14:34, 7 October 2023 (UTC)Reply[reply]

Yes, there are some recurrent uploading errors. Did you try it again? --PantheraLeo1359531 😺 (talk) 15:31, 17 October 2023 (UTC)Reply[reply]

Tech News: 2023-41[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

One new wiki has been created: a Wikipedia in Fon (w:fon:) [1]

Changes later this week

The new version of MediaWiki will be on test wikis and MediaWiki.org from 10 October. It will be on non-Wikipedia wikis and some Wikipedias from 11 October. It will be on all wikis from 12 October (calendar).
Starting on Wednesday, a new set of Wikipedias will get "Add a link" (Swahili Wikipedia, Walloon Wikipedia, Waray Wikipedia, Wolof Wikipedia, Kalmyk Wikipedia, Xhosa Wikipedia, Mingrelian Wikipedia, Yiddish Wikipedia, Yoruba Wikipedia, Zhuang Wikipedia, Zeelandic Wikipedia, Min Nan Wikipedia, Zulu Wikipedia). This is part of the progressive deployment of this tool to more Wikipedias. The communities can configure how this feature works locally. [2]
At some wikis, newcomers are suggested images from Commons to add to articles without any images. Starting on Tuesday, newcomers at these wikis will be able to add images to unillustrated article sections. The specific wikis are listed under "Images recommendations" at the Growth team deployment table. You can learn more about this feature. [3]
In the mobile web skin (Minerva) the CSS ID #page-actions will be replaced with #p-views. This change is to make it consistent with other skins and to improve support for gadgets and extensions in the mobile skin. A few gadgets may need to be updated; there are details and search-links in the task.

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

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

Flip image in Commons[edit]

I know there are tools in Commons to rotate images (CropTool and {{Rotate}}). However, I can't find similar tools or templates to flip (mirror) an image.

Is there a tool or template to flip an image? Or do we need to download the image to flip it in our computer and upload the flipped version again? Pere prlpz (talk) 20:40, 9 October 2023 (UTC)Reply[reply]

I've never encountered such a tool in my 18 years here. The few times I've needed this, I've done it on my computer and uploaded the new version from there too. --Rosenzweig τ 20:23, 17 October 2023 (UTC)Reply[reply]

rendering of images in high res sometimes fails[edit]

File:Hietzinger friedhof hass 2023-07-18.jpg does display correctly, but in higher resolutions the rendering fails:

3.888 × 5.184 Pixel not properly rotated and cropped.
sometimes there is even an error Error: 503, Backend fetch failed and the file does not render at all (as of yesterday).

Yesterday File:Brunnen Bad Weiherburg Detail b.JPG showed similar behavior, but now everything is ok.

&action=purge does not help. Any help appreciated. (see also de:Wikipedia_Diskussion:WikiDaheim/Jury#Anzeigeproblem_im_Vorjurytool - German). Is there a background job with a huge lag that cares for rerendering of such cases? --Christian Philipp (WMAT) (talk) 06:38, 11 October 2023 (UTC)Reply[reply]

We have some similar issues for uploading Commons:Village_pump#Large_number_of_fails, maybe there is a connection between these errors --PantheraLeo1359531 😺 (talk) 19:06, 12 October 2023 (UTC)Reply[reply]

File a task in phab: with the projects "SRE-swift-storage" and "Thumbor". Your commons account will work there. As for statistics, see https://grafana.wikimedia.org/d/Pukjw6cWk/thumbor?orgId=1 . Note that the 200 and 400 HTML errors are normal, it is just the thumbnail storage (swift) talking with the thumbnailer (thumbor). Snævar (talk) 20:53, 15 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]

Broken JPEG[edit]

Is this image broken, or not? I cannot see any content, even after purging all caches. But when I tried to reupload the image, it's consider as duplicate. — Draceane ^talk_contrib. 18:45, 12 October 2023 (UTC)Reply[reply]

I can see it. The Squirrel Conspiracy (talk) 19:04, 12 October 2023 (UTC)Reply[reply]

+1 --PantheraLeo1359531 😺 (talk) 19:05, 12 October 2023 (UTC)Reply[reply]

Thanks. It seems that it have been some deep server cache-related problem. — Draceane ^talk_contrib. 20:17, 12 October 2023 (UTC)Reply[reply]

upload wizard fail[edit]

File:Ruichi_250V2A_EMI_filter_02(DXO).jpg - upload form said An unknown error occurred in storage backend "local-swift-eqiad"., can't see any images thumbnails. What's up? Retired electrician (talk) 19:56, 12 October 2023 (UTC)Reply[reply]

Apparently working now, I see the image and also thumbnails. --Rosenzweig τ 13:23, 13 October 2023 (UTC)Reply[reply]

File not found[edit]

What's happening to these files? 0x0a (talk) 12:35, 13 October 2023 (UTC)Reply[reply]

It seems like there are heavy problems right now with uploading and publishing files, let's hope the error will be solved soon --PantheraLeo1359531 😺 (talk) 17:07, 13 October 2023 (UTC)Reply[reply]

Problems renaming WEBM files[edit]

I've been working on the requested renaming queue, and have run into problems using the renaming script (when people use the {{Rename}} template). When I try to rename them, it throws an error like this:

Error while moving the page. A detailed description of the error is shown below:
API request failed (internal_api_error_DBUnexpectedError): [c57a5b9c-26ab-44e7-8e59-1309c8248527] Caught exception of type Wikimedia\Rdbms\DBUnexpectedError at Fri, 13 Oct 2023 19:29:06 GMT served by mw2352

This only seems to happen with WEBM files (these two specifically, so far: File:DOD 105858664.webm and File:(Archivo 1969) Mónica en los preparativos del lanzamiento del Apolo 11.webm). I've been able to rename other files without issue. Has anyone else encountered this? ···日本穣 ^{Talk to Nihonjoe} 19:32, 13 October 2023 (UTC)Reply[reply]

This one, too. ···日本穣 ^{Talk to Nihonjoe} 19:33, 13 October 2023 (UTC)Reply[reply]

This file and this file, too. ···日本穣 ^{Talk to Nihonjoe} 19:45, 13 October 2023 (UTC)Reply[reply]

File a task in phab: with the projects "MediaWiki-File-management" and "MediaWiki-Page-rename". Snævar (talk) 12:49, 14 October 2023 (UTC)Reply[reply]

Done. ···日本穣 ^{Talk to Nihonjoe} 18:06, 17 October 2023 (UTC)Reply[reply]

This seems to have been fixed now. ···日本穣 ^{Talk to Nihonjoe} 23:28, 17 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]

Upload image error: "local-swift-eqiad"[edit]

When I upload the image, it shows "儲存庫後端 "local-swift-eqiad" 發生了不明的錯誤。" and the image cannot display properly, how can solve this problem？ Thank You! Wpcpey (talk) 15:49, 15 October 2023 (UTC)Reply[reply]

Yes, this error occurs since a few days. Sometimes reuploading helps. A similar discussions was held here: Commons:Village_pump#Large_number_of_fails. I hope the error is fixed soon, as it affects many cases --PantheraLeo1359531 😺 (talk) 16:34, 15 October 2023 (UTC)Reply[reply]

File a task in phab: with the projects "SRE-swift-storage" and "MediaWiki-Uploading". Your commons account will work there. "Local-swift-eqiad" is the server thumbnail cache. Snævar (talk) 20:41, 15 October 2023 (UTC)Reply[reply]

Tech News: 2023-42[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 Unified login system's edge login should now be fixed for some browsers (Chrome, Edge, Opera). This means that if you visit a new sister project wiki, you should be logged in automatically without the need to click "Log in" or reload the page. Feedback on whether it's working for you is welcome. [4]
Edit notices are now available within the MobileFrontend/Minerva skin. This feature was inspired by the gadget on English Wikipedia. See more details in T316178.

Changes later this week

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

Future changes

In 3 weeks, in the Vector 2022 skin, code related to addPortletLink and #p-namespaces that was deprecated one year ago will be removed. If you notice tools that should appear next to the "Discussion" tab are then missing, please tell the gadget's maintainers to see instructions in the Phabricator task.

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

MediaWiki message delivery 23:44, 16 October 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. [5]

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]

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. [6][7]
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. [8]

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]

Commons:Village pump/Technical

Contents

Request to add Tai Ahom Unicode to Commons[edit]

RSVG rendering preview on user:Rillke/MwJSBot.js not working[edit]

Template:No source since[edit]

Missing files after file move[edit]

Blanking coused by file renaming[edit]

Internal error when uploading audio file[edit]

Tech News: 2023-41[edit]

Flip image in Commons[edit]

rendering of images in high res sometimes fails[edit]

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

Broken JPEG[edit]

upload wizard fail[edit]

File not found[edit]

Problems renaming WEBM files[edit]

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

Upload image error: "local-swift-eqiad"[edit]

Tech News: 2023-42[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]

Navigation menu

Commons:Village pump/Technical

Request to add Tai Ahom Unicode to Commons[edit]

RSVG rendering preview on user:Rillke/MwJSBot.js not working[edit]

Template:No source since[edit]

Missing files after file move[edit]

Blanking coused by file renaming[edit]

Internal error when uploading audio file[edit]

Tech News: 2023-41[edit]

Flip image in Commons[edit]

rendering of images in high res sometimes fails[edit]

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

Broken JPEG[edit]

upload wizard fail[edit]

File not found[edit]

Problems renaming WEBM files[edit]

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

Upload image error: "local-swift-eqiad"[edit]

Tech News: 2023-42[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]

Navigation menu

Search