Commons:Village pump/Technical

Shortcuts: COM:VP/T • COM:VPT

• Community portal
  • introduction
• Help desk
• Village pump
  • copyright
  • proposals
  • technical
• Administrators' noticeboard
  • vandalism
  • user problems
  • blocks and protections

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/2025/11 /Archive/2025/12.

COMMONS DISCUSSION PAGES

• Commons Help desk
• Village pump (general discussion)
  • Copyright
  • Proposals
  • Technical
• Graphics and photography discussion
  • Photography critiques
  • Image improvement
    • Illustration workshop
    • Map workshop
    • Photography workshop
    • Video and sound workshop
• Categories for discussion
• Undeletion requests
• Deletion requests
• Volunteer Response Team/Noticeboard
• Translators' noticeboard
• Work requests for bots

---

• Contact administrators
  • Vandalism
  • User problems (Dispute resolution)
  • Blocks and protections
• Bureaucrats' noticeboard
• CheckUser requests
• Oversight requests

---

• Telegram
• IRC ^webchat
• Commons mailing list (archive)
• Commons' bugs on Phabricator

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.

How to move (rename) many categories?

How can one rename many categories at once? This would be similar to VisualFileChange or massrename but for categories, not files. For example, all categories starting with something / that are in the search results of some search query. Prototyperspective (talk) 16:40, 13 October 2025 (UTC)

This really isn't possible?

Is it possible to edit the content of many categories at once similar to how VisualFileChange can be used to edit many file pages?
See MediaWiki talk:Gadget-VisualFileChange.js#VisualFileChange for category text content changes?.
Prototyperspective (talk) 23:51, 3 November 2025 (UTC)

I am also curious if you find out something here. I'm less interested in mass-renaming of categories, but if there is a better way to mass-categorize many categories (like Cat-a-lot?), I am still unaware of possibilities. The only way I know is HotCat and Edit. --Enyavar (talk) 09:54, 4 November 2025 (UTC)

but if there is a better way to mass-categorize many categories (like Cat-a-lot?) you can use cat-a-lot for that. Prototyperspective (talk) 12:57, 4 November 2025 (UTC)

So it doesn't seem to be possible and I'll create a wish for it. Please correct if I'm wrong and there is a bot one could readily use for this or a tool. Prototyperspective (talk) 16:41, 2 December 2025 (UTC)

Flickr2commons “The file you submitted was empty.”

I have this issue “The file you submitted was empty.”, How to fix? 6D (talk) 07:15, 15 October 2025 (UTC)

Does Anyone else have this issue? 6D (talk) 09:13, 16 October 2025 (UTC)

Not recently, no. I don’t know the cause of it, but I remember when I had this issue, I just kept resubmitting the files until they went through. Tvpuppy (talk) 02:28, 17 October 2025 (UTC)

And the Flickr2Commons are struck at Running....., may be the F2C API key got ratelimited. 6D (talk) 15:21, 22 October 2025 (UTC)

And it now working again!!!’ 6D (talk) 23:53, 22 October 2025 (UTC)

So are your two issues both solved now? Prototyperspective (talk) 10:23, 29 October 2025 (UTC)

The Flickr2Commons are struck at Running..... is fixed, but Flickr2commons “The file you submitted was empty.” is not fixed, when I moved about ~600-800 images, this issue pop up for 30 Minutes-1 Hour. 6D (talk) 02:50, 30 October 2025 (UTC)

I'm also still experiencing the same “The file you submitted was empty.” with the tool. Also checked, and I am able to manually transfer these files, so it is a tool related issue. Respublik (talk) 23:09, 28 November 2025 (UTC)

Path to merging multi-part audiobooks?

Commons contains a sizable fraction of free-licensed audiobooks. However, many are split into multiple parts. This makes it cumbersome to download them and to listen to them conveniently and without interruptions.

It's also not well-suited for adding the file to Wikidata items or Wikipedia articles or Wikisource pages if it's split up into many parts. There also are further issues.

Is there any way that many or all of the multi-part audiobooks could be feasibly bundled up into one file each?

For example, there's many in Category:LibriVox recordings and I just merged one of them with 8 parts (just 45 min; 83 MB) using one ffmpeg command. But it can't be done manually for all the audios there. Prototyperspective (talk) 00:01, 17 October 2025 (UTC)

Created Commons:Bots/Work requests#Merging audio files of audiobooks. Prototyperspective (talk) 14:42, 6 November 2025 (UTC)

One reason is that only one part audio files can be featured as Media of the Day and that instead of cluttering a Wikipedia page with lots of audio parts, it should be just one file (and some templates may only allow for one or a few audios). It also makes it easier to correct/update/improve the description, metadata and categories and to add it to Wikidata items. Prototyperspective (talk) 16:42, 2 December 2025 (UTC)

NASA videos imported at low quality

I noted Kesäperuna recently reuploaded this old video that was recently featured on the frontpage where I remember I was a bit surprised about the sometimes blurry resolution: File:Measuring Elevation Changes on the Greenland Ice Sheet.webm (thanks for that!)

When going to the video source (the sourced linked in the first link is 404 by now so the source of the webm reupload) and clicking on the Download button, the only webm available there is 62 MB, not 110 MB like in the new file uploaded to Commons.

So it seems like sometimes or often NASA doesn't make videos available in full resolution as webms and it's been these videos that have been imported here. Kesäperuna probably downloaded another file and then converted it.

I then also noticed the new video File:At Land's Edge - Tracking Coastal Ecosystem with Landsat (SVS14903).webm imported by OptimusPrimeBot operated by Don-vip looks quite blurry and tested whether I'd get a better version if I download the mp4 file and convert it to webm locally on my machine using ffmpeg. As you can see in the File history of that file, the new video is of much better resolution and about 5 times the size (click on the prior version to see the difference). Thus, I think many NASA or even PD-US-gov videos may have been imported at submax resolution.

I think many of these videos are some of the most educational, most useful and partly most-used videos we have on Commons, so I think they should probably be on Commons at full resolution where if necessary and as adequate only the default playback quality is changed but not the max-resolution kept low. At the very least the fraction of NASA videos that are featured in MOTD or in use on any other Wikimedia project like Wikidata or Wikipedia (but probably all of them).

How do you think would be the best way to fix the low-resolution of these videos? That would be a two-step process of 1. identifying which videos have been imported at submax resolution and 2. importing a higher-resolution video (directly if available or via downloading the maxres video and converting it to webm locally. Could somebody implement this?

I don't know if the max-resolution video is by now usually available as mp4 but if so it may also make sense to wait until mp4 files get accepted on Commons if that's just a few more years(?) If somebody could import highres versions of these files, that would be great either way! Prototyperspective (talk) 17:55, 17 October 2025 (UTC)

Yes, this is a problem. The original WebM file is remarkably small. Then there is a standard quality version in an unfree codec, and a MOV (ProRes 444 or so) file with astronomical file size. If it is a managable amount of files, I can help converting and reuploading, as my machine can roar like a lion :) (works very fast). As we don't have videos beyond 8192 pixels wide or tall, this is no problem :) --19:05, 17 October 2025 (UTC) PantheraLeo1359531 😺 (talk) 19:05, 17 October 2025 (UTC)

For the encoding from other formats, video2commons should now (since yesterday) be able to upload videos with a good size/quality ratio (thanks to Amdrel contribution). To identify the videos that need a reupload however, I have no idea. vip (talk) 22:42, 17 October 2025 (UTC)

Good that you noticed and started this thread, better to have more eyes on this issue.

Firstly, NASA svs website changed url format from https://svs.gsfc.nasa.gov/goto?4022 to https://svs.gsfc.nasa.gov/4022.

I did couple more videos that were used in articles with most views in category Videos from NASA, that were in poor quality and had better versions available.

Highest quality "master" format in NASA website is very varied, sometimes it's mp4 file, mpeg2 file, or prores mov, I used best version available and encoded to AV1/Opus format with reasonable settings(depending on video in question, as most videos have visible mpeg2 artifacts in prores master files for some reason) to keep file sizes smallish.

What should be done to videos uploaded in different format such as ogv that are promoted to MOTD or have other "awards" associated with them, can they be just redirected to better webm version? Kesäperuna (talk) 00:01, 18 October 2025 (UTC)

I think, yes. OGV is outdated, probably not the most suitable codec for UHD content, and WebM (with AV1) is state-of-the-art. I can imagine there is a "replace" voting system for featured media, too. --PantheraLeo1359531 😺 (talk) 16:36, 18 October 2025 (UTC)

Thanks for the info. It may be useful if somebody replaced all those links with the new format using VisualFileChange. Good idea to replace the ones with most views first and right away. I think the old file can simply be deleted and redirect to the new webm file per F8. Twinkle has something about the file format but the actual policy doesn't require it to be it of the same file format. However, I'm not sure if it can technically be done currently – maybe it's only possible for files of the same file format. I'll tag the low-res file at a later point – would like to have it stay as is for a while so people can still see the file in the context of this issue/thread. I think many files are affected by this so I think it was best if this wasn't done manually but via some script or so. One of the difficulties with that though is that it doesn't seem like one can download the highest quality file with some standardized url like e.g. appending ?dl=hd https://svs.gsfc.nasa.gov/4022?dl=hd. Prototyperspective (talk) 22:11, 20 October 2025 (UTC)

F8 says “exact or scaled-down duplicate of an older existing file”. If the scaled-down duplicate is the older one, it does not apply; the OGVs should not be deleted in order not to break external usage (which we cannot track down and fix). Please add {{Superseded}} to the description pages of the OGVs instead of getting them deleted. —Tacsipacsi (talk) 16:08, 7 November 2025 (UTC)

Thanks; maybe that phrase should be changed then: the old file could be turned into a redirect to the higher-quality file so the uses would not break. Prototyperspective (talk) 16:40, 7 November 2025 (UTC)

Some of them do break: hotlinking to the https://upload.wikimedia.org files doesn’t follow redirects, so it’s the external, non-wiki usage (i.e. usage that doesn’t come from first- or third-party MediaWiki installs) that suffers the most. —Tacsipacsi (talk) 22:15, 7 November 2025 (UTC)

Template:Shortcut not showing

The {{Shortcut}} box isn't showing on any of the pages it's being used. Could somebody please fix this? Prototyperspective (talk) 13:52, 29 October 2025 (UTC)

Moved to this new page for template requests: Commons:Template requests#Make template Shortcut show again. Prototyperspective (talk) 14:34, 2 November 2025 (UTC)

I don't see what the use of that template even is if it's not showing. Note that many of the policy pages using this don't have an additional {{Shortcut2}} template that is showing so the shortcuts aren't visible to the readers. Prototyperspective (talk) 16:43, 2 December 2025 (UTC)

FlickreviewR 2 sometimes struck

Sometimes when I moving images from Flickr, the FlickreviewR 2 can take up to ~30 Minutes to review the license, see this [1]. 6D (talk) 02:44, 30 October 2025 (UTC)

@6D: It appears that the problem occurs occassionally. Using this file as an example, it takes around 1 hours and 15 minutes for the bot to review my file. At the time of my upload, there were around 200 backlog for the bot, though they are all resolved now.廣九直通車 (talk) 13:07, 1 November 2025 (UTC)

Noting here that due to a toolforge outage, the bot will take longer than normal to review files for a few hours once back online. The maintainers are aware, and Chuckbot is on standby if needed. All the Best -- Chuck ^Talk 05:45, 5 November 2025 (UTC)

Empty files in Flicker2Commons

I successfully uploaded some hundreds of files by F2C today, but then the infamous empty file error started to appear (The file you submitted was empty.) [ 1, 2, 3, 4, 5, 6, 7 ] I know that {{Magnus is not here}}, but Magnus Manske isn't anywhere, not at his talkpage, not at bitbucket... Does anyone know, what can I do to make F2C to upload photos. (Logging off/clearing the cache didn't help.) Otherwise I think, that in these case someone (?some WM branch/WMF) should intervene, as the maintainer isn't willing to maintain his own tools (same for U2C, WikiShootMe...). — Draceane ^talk_contrib. 14:30, 3 November 2025 (UTC)

@Οἶδα, 6D, Karl Gruber, and Thyj: FYI. — Draceane ^talk_contrib. 14:31, 3 November 2025 (UTC)

Here, it also affect the FlickreviewR 2 bot. 6D (talk) 15:21, 3 November 2025 (UTC)

So, some API problem at Flickr side? (Commons_talk:Flickypedia#Cannot_login) — Draceane ^talk_contrib. 17:22, 3 November 2025 (UTC)

I wish I knew the workaround to this recurring issue. The only solution that has ever worked for me is to wait it out, and occasionally wait much longer I would like. Οἶδα (talk) 23:16, 3 November 2025 (UTC)

That sounds to me as if flickr is blocking the api request to deal with an influx of data at their end (aka rate limiting) —TheDJ (talk • contribs) 19:01, 18 November 2025 (UTC)

It is not only affect you, it is everyone who use Flickr2commons bot. 6D (talk) 06:27, 9 November 2025 (UTC)

Tech News: 2025-45

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

Updates for editors

• Administrators will now find that Special:MergeHistory is now significantly more flexible about what it can merge. It can now merge sections taken from the middle of the history of the source (rather than only the start) and insert revisions anywhere in the history of the destination page (rather than only the start). [2]
• For users with "Automatically subscribe to topics" enabled in their preferences, starting a new topic or adding a reply to an existing topic will now subscribe them to replies to that topic. Previously, this would only happen if the DiscussionTools "Add topic" or "Reply" widgets were used. When DiscussionTools was originally launched existing accounts were not opted in to automatic topic subscriptions, so this change should primarily affect newer accounts and users who have deliberately changed their preferences since that time. [3]
• Scribunto modules can now be used to generate SVG images. This can be used to build charts, graphics and other visualizations dynamically through Lua, reducing the need to compose them externally and upload them as files. [4]
• Wikimedia sites now provide all anonymous users with the option to enable a dark mode color scheme, featuring light-colored text on a dark background. This enhancement aims to deliver a more enjoyable reading experience, especially in dimly lit environments. [5]
• Users with large watchlists have long faced timeouts when editing Special:EditWatchlist. The page now loads entries in smaller sections instead of all at once due to a paging update, allowing everyone to edit their watchlists smoothly. As part of the database update, sorting by expiry has been removed because it was over 100× slower than sorting by title. A community wish has been created to explore alternative ways to restore sort-by-expiry. If this feature is important to you, please support the wish! [6]
• View all 31 community-submitted tasks that were resolved last week. For example, the fixing of the persisting highlighting when using VisualEditor find and replace during a query. [7]

Updates for technical contributors

• Since 2019 the Wikimedia URL Shortener at https://w.wiki is available for all Wikimedia wikis to create short links to articles, permalinks, diffs, etc. It is available in the sidebar as "Get shortened URL". There are 30 wikis that also install an older "ShortUrl" extension. The old extension will soon be removed. This means /s/ URLs will not be advertised under article titles via HTML class="title-shortlink". The /s/ URLs will keep working. [8]
• On Thursday, October 30, the MediaWiki Interfaces and SRE Service Operations teams began rerouting Action API traffic through a common API gateway. Individual wikis will be updated based on the standard release groups, with total traffic increased over time. This change is expected to be non-breaking and non-disruptive. If any issues are observed, please file a Phabricator ticket to the Service Ops team board.
• MediaWiki Train deployments will pause for the final two weeks of 2025: 22 December and 29 December. Backport windows will also pause between Monday, 22 December 2025 and Thursday, 2 January 2026. A backport window is a scheduled time to add things like bug fixes and configuration changes. There are seven deployment trains remaining for 2025. [9]
• Detailed code updates later this week: MediaWiki

In depth

• In 2025, the Wikimedia Foundation reported that AI systems and search engines increasingly use Wikipedia content without driving users to the site, contributing to an 8% drop in human pageviews compared to 2024. After detecting bots disguised as humans, Wikimedia updated its traffic data to reflect this shift. Read more about current user trends on Wikipedia in a Diff blog post.

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

MediaWiki message delivery 19:30, 3 November 2025 (UTC)

Any way to interlink other versions for many files?

At Special:ListFiles/Distribution Wissen SRF you can see that the same 15 useful explainer videos were uploaded in German, French, and Italian. However, they don't link to each other in file description in the other_versions field of {{Information}}. Is there a way to add this to many files at once or have it somehow be automatically added?

See also {{Otherversion}} and this idea for UploadWizard. Is the only way to add it by manually going through each file to add the interlinking? This is of course not the only case of files in multiple languages not linking to each other. If a person not understanding language X well or at all doesn't see it linked at the file but would understand language Y well, they likely won't notice/learn that this video also exists. Prototyperspective (talk) 17:34, 6 November 2025 (UTC)

The same problem also exists for files Special:ListFiles/RTS Radio Télévision_Suisse.

Moreover, most of these would probably be good to add to the Wikidata item about the subject – can this be done in bulk somehow? (I mean at least the 3 language version files at once per item.) Prototyperspective (talk) 15:37, 17 November 2025 (UTC)

I am not sure that it is exactly what you are looking for because there is not so much automation but there are galleries. Example DustDFG (talk) 05:54, 3 December 2025 (UTC)

@Prototyperspective and do not overlook Template:Edit_other_versions in the example DustDFG (talk) 06:02, 3 December 2025 (UTC)

I've also just found that gallery syntax maybe is not only possible... There is also Template:Other_versions and now I am confused... DustDFG (talk) 06:06, 3 December 2025 (UTC)

Way to mark files that got a new revision but still have same date?

Many data graphics like charts or choropleth map get updated via new revisions. However, the value in the date field usually stays the same.

This is problematic to users who look at the file information template and then see another date than the year the data graphic was released. This is confusing and especially so if the date there is not before the latest data point (which would make that date impossible). Apps and tools could also use this false information and display (or otherwise use) it, for example the Commons app, scrapers, or Web search engines. The structured data would also still have the false data.

Is there a way to display for example a warning next to the value in the date field when the file has multiple revisions and that date wasn't changed?

Maybe one could also prompt the user whether the date changed after a new revision was uploaded to reduce the number of these cases in the future? Another way would be to identify the files with a likely false date due to new revision uploads and correct these. But even if that was done, having a small warning display next to the date would be good: for example, a warning icon that when hovered over says "A new revision of the file was uploaded, this date may be outdated" (and it would be best if users could make the warning go away if the date is still correct or was updated).

Many and ultimately most of the files affected by this may be in Category:Charts by year of latest data and Category:Maps by year (the corresponding subcat is changed when a new revision has newer data).

It may be best and easiest to understand this with some examples:

• File:Mean-seawater-ph.png was updated in 2023 with data for 2021 but it still has the date of the release of the chart of the first revision, 2019
• File:Chick culling laws world map.svg has 2020 in the date field but the latest revision is from 2025, including probably legal changes made after 2020
• File:World laws pertaining to homosexual relationships and expression.svg gets frequently updated via new revisions and has it solved by appending (upload date) to the date in the date field. Similar for this.

Prototyperspective (talk) 00:19, 7 November 2025 (UTC)

It's not just datagraphics but sometimes also other images – I think most often screenshots. Example:

• File:Abe lincoln on app.jpg (comment for the new revision upload: Updated, interface of app changed a lot since 2017/2019 and so has the article.) – it has 2017 in the date field but is a 2025 screenshot.

Prototyperspective (talk) 16:39, 2 December 2025 (UTC)

Commons:Copyright rules by territory/Belgium

Could someone take a look at Commons:Copyright rules by territory/Belgium? It looks like there's a level-2 section heading (==Copyright tags==) in Commons:Copyright rules by territory/Belgium#General rules that's not displaying properly. -- Marchjuly (talk) 07:30, 7 November 2025 (UTC)

@Marchjuly, I think I fixed it, just need to wait for a TA to mark this for translation, so it updates the other language versions as well. Thanks. Tvpuppy (talk) 12:58, 7 November 2025 (UTC)

Thank you for doing that Tvpuppy. I didn't catch it was an added line break causing the problem. -- Marchjuly (talk) 20:33, 7 November 2025 (UTC)

This section is resolved and can be archived. If you disagree, replace this template with your comment. Prototyperspective (talk) 11:05, 3 December 2025 (UTC)

Lots of Wikipedia articles using low-quality superseded files …but glamorgan & glamorous fail

For many files, a new version has been uploaded as a separate file. It usually is of substantially higher resolution, more translatable / editable, and of the better filetype SVG. However, often the Wikipedia articles that use the old file have not been edited. In addition, some users may still use of the now legacy file because a note about it was missing earlier or they didn't/couldn't read it.

Here's an example:

• 
  New SVG version with high resolution and very translatable
• 
  Old version still used in 9(!) mainspace Wikipedia articles

Usually, one could do a scan of uses of files in a category with the glamorgan or glamorous tools. It would be very useful for Category:Superseded or Category:Vector version available which are added to files like the second one above via a template.

However, for these two categories where either tool would be most useful, they don't work.

Does somebody know why or how to get either or both to work for a report of file uses of superseded files?

--Prototyperspective (talk) 23:39, 7 November 2025 (UTC)

Deepcat search

Tracked in Phabricator
Task T410440

What's going on with deepcat search recently? It stops showing the results when scrolling with "Deep category search SPARQL query failed" message under the search box. Qbli2mHd (talk) 10:36, 8 November 2025 (UTC)

Could you give some example category/ies? See also phab:T395348. Prototyperspective (talk) 11:42, 8 November 2025 (UTC)

It's any scrollable search really, like [10]. The behaviour is unpredictable, you could manage to have the results loaded several times or get an error on the next screen. Qbli2mHd (talk) 02:19, 9 November 2025 (UTC)

Could you create an issue on phabricator? I could scroll down and it did load more images and I could click on the Load more button but eventually after scrolling just a bit it shows "No more results found" at the bottom and the error message you wrote at the top (it didn't show when only the first set of images showed) before the 1,842 files of that example deepcat search were shown. Thanks for reporting this problem here. Prototyperspective (talk) 20:58, 9 November 2025 (UTC)

phab:T410440 Qbli2mHd (talk) 18:38, 18 November 2025 (UTC)

Flickr2Commons sometimes struck

For some reason, the Flickr2Commons have been struck for few hours now. 6D (talk) 10:57, 10 November 2025 (UTC)

Resumed, and then got stuck again. Zhuyifei1999, who runs this bot, has not been heard from in months. Is there anyone who can restart the bot? - Jmabel ! talk 06:06, 12 November 2025 (UTC)

And now it is running again. - Jmabel ! talk 06:32, 12 November 2025 (UTC)

And it is struck again!!!!!!!! 6D (talk) 06:30, 13 November 2025 (UTC)

Do you mean stuck or struck? If the latter, what do you mean. Misspelling makes it difficult for others to quickly understand what you mean and this is also in the title. In any case this seems like something to report at Commons talk:Flickr2Commons. The recent threads that could be about this there describe the problem as it showing The file you submitted was empty. – is this a new separate problem or the same problem? The issue tracker seems to be https://bitbucket.org/magnusmanske/flickr2commons If nothing helps, a wish in the m:Community Wishlist could be created if this is deemed important to fix and nothing much is happening already to solve this. Prototyperspective (talk) 10:41, 13 November 2025 (UTC)

Tech News: 2025-46

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

Updates for editors

Example of a talk page with the new design, in French.

• Starting November 12, users will see a change in the appearance of talk pages on some Wikipedias. Almost all wikis have received this design change; English Wikipedia will get these changes later. You can read more on Diff. Users can opt out of these changes in their user preferences in "Show discussion activity". [11]
• MediaWiki can now display a page indicator automatically while a page is protected. This feature is disabled by default. It can be enabled by community request. [12]
• Using the "Show preview" or "Show changes" buttons in the wikitext editor will now carry over certain URL parameters like 'useskin', 'uselang' and 'section'. This update also fixes an issue where, if the browser crashed while previewing an edit to a single section, saving this edit could overwrite the entire page with just that section’s content. [13][14][15]
• Wikivoyage wikis can use colored map markers in the article text. The text of these markers will now be shown in contrasting black or white color, instead of always being white. Local workarounds for the problem can be removed. [16]
• The Activity tab in the Wikipedia Android app is now available for all users. The new tab offers personalized insights into reading, editing, and donation activity, while simplifying navigation and making app use more engaging. [17]
• The Reader Growth team is launching an experiment called "Image browsing" to test how to make it easier for readers to browse and discover images on Wikipedia articles. This experiment, a mobile-only A/B test, will go live on English Wikipedia in the week of November 17 and will run for four weeks, affecting 0.05% of users on English wiki. The test launched on November 3 on Arabic, Chinese, French, Indonesian, and Vietnamese wikis, affecting up to 10% of users on those wikis. [18]
• View all 27 community-submitted tasks that were resolved last week. For example the inability to lock accounts on mobile sites has been fixed. [19]

Updates for technical contributors

• Nominations are open on Wikitech for new Toolforge standards committee members. The committee oversees the Toolforge Right to fork policy and Abandoned tool policy among other duties. Nominations will remain open through 2025-11-28.
• The JWT issuer field in OAuth 2 access tokens for SUL wikis has been changed to https://meta.wikimedia.org. Old access tokens will still work. [20]
• The JWT subject field in OAuth 2 access tokens will soon change from <user id> to mw:<identity type>:<user id>, where <identity type> is typically CentralAuth: (for SUL wikis) or local:<wiki id> (for other wikis). This is to avoid conflicts between different user ID types, and to make OAuth 2 access tokens and the sessionJwt cookie more similar. Old access tokens will still work. [21]
• MediaWiki's block messages (blockedtext, blockedtext-partial, autoblockedtext, systemblockedtext, blockedtext-tempuser, autoblockedtext-tempuser) now support additional parameters indicating whether the user is blocked from editing their own user talk page $9 or emailing other users $10. [22]
• A REL1_45 branch for MediaWiki core and each of the extensions and skins in Wikimedia git has been created. This is the first step in the release process for MediaWiki 1.45.0, scheduled for late November 2025. If you are working on a critical bug fix or working on a new feature, you may need to take note of this change. [23]
• The process for generating CirrusSearch dumps has been updated due to slowing performance. If you encounter any issues migrating to the replacement dumps, please contact the Search Platform Team for support. [24][25]
• Detailed code updates later this week: MediaWiki

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

MediaWiki message delivery 20:35, 10 November 2025 (UTC)

I think the automatic protection icon feature can be useful here in Commons. This means we don't have to manually place {{Protected}} in protected pages anymore. Tvpuppy (talk) 22:46, 10 November 2025 (UTC)

Palacios en la Comunidad de Madrid

Palacios en la Comunidad de Madrid has no images - what's wrong? --~2025-33091-77 (talk) 15:56, 12 November 2025 (UTC)

I think I fixed the first image but I do not have time to fix all of them now. Ymblanter (talk) 16:22, 12 November 2025 (UTC)

As the page says This list is periodically updated by a bot. Manual changes to the list will be removed on the next update! so please don't manually edit the contents. Prototyperspective (talk) 12:11, 13 November 2025 (UTC)

My edits were indeed overwritten by a bot, so that I am not going to edit it again.--Ymblanter (talk) 15:42, 13 November 2025 (UTC)

Tracked in GitHub
magnusmanske/listeria_rs/issues/82

This is the problem described at /Archive/2025/03#Can the Listeriabot be fixed? which was just archived without being solved.

The outcome of that discussion so far mostly is that this is caused by bug https://github.com/magnusmanske/listeria_rs/issues/82 […] reported in 2021. ListeriaBot does not produce correct wikitext when row_template is used. Since this depends on somebody fixing this in the listeria code, the route to get it solved may be devs here doing so or asking Manske about it and/or supporting wish m:Community Wishlist/Wishes/Continue development of the Listeria bot that creates dynamic tables using Wikidata (0 supporters so far, thanks).

Looks like 45 galleries are affected by this in the same way. Prototyperspective (talk) 12:21, 13 November 2025 (UTC)

Special name space redirect

Tracked in Phabricator
Task T410518

There used to be a page in the special name space called OAuthConsumerRegistration/propose. It no longer exists, as OAuth Consumer Registration proposals are now dealt with on Media Wiki for all Wikimedia projects. The current version of Open Refine isn't up-to-date, and it points to https://commons.wikimedia.org/wiki/Special:OAuthConsumerRegistration/propose. That's not helpful, as you get told that "you have requested an invalid special page". What would be more useful is for there to be a redirect that points to the relevant page on Media Wiki instead, which is here. I wonder whether admins, or whoever else has the right privileges, could edit the Special:OAuthConsumerRegistration/propose page and set up a redirect that points to the right spot on Media Wiki. Schwede66 00:39, 16 November 2025 (UTC)

No, pages (including redirects) cannot be created in the Special: namespace at all, regardless of permissions. You could request that a redirect be added at meta:Phabricator; however, given that this link only appears in one place, having it corrected there may be more productive. Omphalographer (talk) 21:12, 16 November 2025 (UTC)

I've never provided feedback to OpenRefine before. I've done so now. No idea how often they update their software. Schwede66 22:39, 16 November 2025 (UTC)

Not sure but I think this might be caused by gerrit:1191860. Nemoralis (talk) 04:31, 17 November 2025 (UTC)

Filed as T410518. Tgr (WMF) (talk) 15:27, 19 November 2025 (UTC)

Category missing in all of a cat's subcats

I noticed at Category:Electricity production trends in the United Kingdom that the category is missing the category Category:Charts of the United Kingdom.

The Electricity production trends categories don't have a template so all their categories are set not via template but separately on all the categories.

Is there a way to add [[:Category:Charts of ''name of country'']] (where name of country is simply whatever comes after "Electricity production trends in" in the category title)) to all of these categories without having to go through all the categories and adding it manually?

If not, is there a tool to which this functionality could possibly be added? Prototyperspective (talk) 11:41, 17 November 2025 (UTC)

Tech News: 2025-47

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

Updates for editors

• The Reader Experience team is experimenting with reading lists on mobile web, allowing logged-in readers with no edits to save private lists of articles for later. The experiment is running on Arabic, Chinese, French, Indonesian, and Vietnamese Wikipedias since the week of 10 November, and will begin on English Wikipedia the week of 17 November.
• Users who can’t receive their email verification code during login can now get help by submitting a form on a new special page. This update is part of the Account Security initiative. If your account has an email address, please make sure you still have access to it. When logging in from a new device or location without 2FA, you may be asked to enter a 6-digit code sent by email to finish logging in. Learn more.
• One new wiki has been created: a Wikisource in Minangkabau (s:min:) [26]
• View all 23 community-submitted tasks that were resolved last week.

Updates for technical contributors

• As part of the Parser Unification project, the Content Transform Team rolled out Parsoid as the default parser to many low-traffic Wikipedias and is preparing the next step to high traffic ones. This message is an invitation for you to opt-in to Parsoid, as described in the Extension:ParserMigration documentation, and identify any issues you might encounter with your own workflow using bots, gadgets, or user scripts. Please, let us know through the "Report Visual Bug" link in the Tools sidebar or create a phab ticket and tag the Content Transform Team in Phabricator.
• Unsupported Tools: Several issues with Video2Commons have been fixed, including filename-related upload failures, black-video imports, and retry handling. AV1 support has also been added. Ongoing work focuses on backend stability, ffmpeg errors, subtitle imports, metadata handling, and playlist uploads. To track specific tasks, check the Phabricator board.
• Detailed code updates later this week: MediaWiki

Meetings and events

• Save the date for the next Wikimedia Hackathon happening in Milan, Italy from May 1–3, 2026. Registration will open in January 2026. Scholarship applications are currently open, and will close on November 28, 2025. If you have any questions, please email hackathon@wikimedia.org.

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

MediaWiki message delivery 17:23, 17 November 2025 (UTC)

Unsupported Tools: Several issues with Video2Commons have been fixed That's great news! Thanks to everyone involved. However, I think this belongs into section "Updates for editors", not "Updates for technical contributors". To track specific tasks, check the Phabricator board. As explained on the talk page of the meta page about this ongoing effort, the phabricator board doesn't contain most v2c tasks – those are on GitHub here. So if that issue tracker isn't linked, its issues I think need to be imported to phabricator. Prototyperspective (talk) 18:45, 17 November 2025 (UTC)

File uses at Wikiradio not showing

m:Wikiradio (tool) is for playlists of audio-files. It only links to files via wikilinks instead of embedding the audios.

Is there a way for the used tracks to show the use at Wikiradio in the File use sections of the audios here? This would enable way more people to learn about this tool and to find wikiradio stations of similar audios as the one they're interested in. Audios on Commons are usually short and stop after you played them, with wikiradio you can listen to playlists that continue to play. Prototyperspective (talk) 23:19, 17 November 2025 (UTC)

No this is not possible. That tool essentially works the same way as downloading to your desktop works and we cant show that either. —TheDJ (talk • contribs) 18:56, 18 November 2025 (UTC)

The only thing we can know about, is the linking to its description page, which is registered via WhatLinksHere as is standard. Example: Special:WhatLinksHere/File:Pachelbel's Canon.ogg —TheDJ (talk • contribs) 18:58, 18 November 2025 (UTC)

Yes so I think it's technically possible but maybe not with how things currently are. There could be some relevant change to Wikiradio (e.g. embed files instead of linking to them on the page or specify the files on Commons instead of on meta) or to MediaWiki.

WhatLinksHere doesn't show the places where it's wikilinked from other projects, only those wikilinks on Commons. Prototyperspective (talk) 19:10, 18 November 2025 (UTC)

@Prototyperspective: I think one approach might be to change the playlist pages to use <gallery> to list the files. That would cause them to show up through the usual mechanism for showing pages that are in use on other wikis. This might need some changes to Wikiradio itself so that it can read galleries. --bjh21 (talk) 20:09, 21 November 2025 (UTC)

That would be an idea but I think it would make the playlist page less readable than plain hyperlinks to the files which e.g. for music are usually artist name - song name. On the other hand, one could still see these by clicking the edit button and looking at the wikitext and having these playlists very readable isn't quite important. Navigating to the file would become more difficult. I'll create an issue in the repository for WikiRadio. However, it doesn't seem like there's any developer actively looking into these and developing it further. The bigger problem is that it can't play mp3 files (anymore?) and that didn't get fixed so far despite this being the most common audio format nowadays. This is probably the larger reason why I was looking for an alternative solution if one is possible. Prototyperspective (talk) 20:21, 21 November 2025 (UTC)

"Geograph from structured data" template doesn't work for derivative files via CropTool

I've run into this problem before. I used CropTool on an image originally imported from the Geograph project- File:Crompton Parkinson Factory Clock - Netherfield Road - geograph.org.uk - 3207039.jpg- but the cropped/derivative version- File:Crompton Parkinson Factory Clock - Netherfield Road - geograph.org.uk - 3207039 (cropped).jpg- doesn't copy and display the file information correctly.

The original doesn't use a regular {{Information}} template and instead relies on {{Geograph from structured data}}. This is then copied to the derivative/cropped version, but doesn't work there, the problem presumably because the structured data it relies upon isn't automatically transferred?

Cutting and pasting the information manually would be enough of a nuisance in itself, but even figuring out how to do so in the first place is far from straightforward since {{Geograph from structured data}} gives no indication of that. The onus should *not* be on the end user to do so, at least not without prior warning.

At the risk of stating the obvious, this situation clearly isn't satisfactory. Ubcule (talk) 12:49, 18 November 2025 (UTC)

@Ubcule I agree with you that some SDC data should be copied when cropped, but unfortunately CropTool currently doesn't have this feature.

In the meantime, you can use Commons:MoveClaim Tool to copy SDC data from one file to another, which should save a lot of time by not having to manually do it. Note that the tool doesn't appear to work if there is no SDC data, so you may have to begin by adding at least one SDC claim (e.g. caption). Thanks. Tvpuppy (talk) 19:50, 18 November 2025 (UTC)

@Tvpuppy: - That seems to mostly work, so thank you for your help!

While the implied criticism below certainly isn't aimed at you (you were helpful and did your best with the current setup and the onus isn't on you to provide a proper solution to someone else's problem), this is still a clunky semi-manual workaround that, while a helpful improvement and usable for more technical users like ourselves, still isn't really a proper, acceptable solution for general use.

I'm not sure whose responsibility this problem is; CropTool's for not copying over the structured data (is it required or expected to?) or the {{Geograph from structured data}} template's, and those who forced the use of that template for Geograph imports rather than the standard infobox.

Given the Geograph template also has the problem that- as far as I can tell- it's not editable directly (only via the structured data) and thus doesn't- and can't- integrate properly with things that *would* normally go in the infobox (e.g. {{Image extracted}} has been simply plastered below), I'm not inclined favourably towards it or its use, as it seems to be the primary cause of the problem.

Ubcule (talk) 13:20, 19 November 2025 (UTC)

I don't have experience with this tool but isn't it the case that not always the SD should be copied as the crop could display something else (say just a pencil in a photo of a building where location is set)? So it would have to prompt the user whether (or which?) SD should be copied. If it's still adequate to set this in CropTool, please create a code issue for CropTool in its issue tracker, thanks. Prototyperspective (talk) 11:14, 3 December 2025 (UTC)

Technical issue

Tracked in Phabricator
Task T393287

On the Special:ListFiles pages, can we add selection buttons for choosing a specific date range? such as from 12 December 2012 to 11 November 2013, which makes it easier to view the photos the uploader uploaded. Huangdan2060 (talk) 02:16, 20 November 2025 (UTC)

phab:T393287. Nemoralis (talk) 11:03, 21 November 2025 (UTC)

Some recent improvements to Video2Commons

As some of you may know, the WMF allocated a small budget for a contractor to address some Commons tool issues. This is less than a lot of us would have hoped for, but it is definitely more than nothing. I was among the small group who were consulted as to where this should be allocated. We and they chose Video2Commons was chosen because, as against the other likely possibilities, there seemed to be a fair chance of a contractor making progress without needing a deep, broad understanding of Commons in general. Status is at meta:Product and Technology Advisory Council/Unsupported Tools Working Group. - Jmabel ! talk 16:18, 21 November 2025 (UTC)

Truly great to see the progress there. And that's solid reasoning regarding the decision-making. I hope more improvements to Commons-related tech will be made also in similar ways. Prototyperspective (talk) 20:24, 21 November 2025 (UTC)

Potential changes to MediaWiki:Protectedpagewarning

I'd like to propose that we replace the contents of that interface message with User:JJPMaster/MediaWiki:Protectedpagewarning. The current version describes any non-semi-protection--template, autopatroller, or full protection--as "only administrators can edit." My version accounts for the multiple protection levels. I also added wikilinks for all the relevant user groups, which were absent in the original. JJP_Master (she/they) 05:40, 24 November 2025 (UTC)

@JJPMaster: Your version doesn't seem to handle semi-protection and cascading protection. Is that intentional? NguoiDungKhongDinhDanh 06:12, 24 November 2025 (UTC)

@NguoiDungKhongDinhDanh: Yes. Semi- and cascading protection are handled by MediaWiki:Semiprotectedpagewarning and MediaWiki:Cascadeprotectedwarning respectively. JJP_Master (she/they) 06:16, 24 November 2025 (UTC)

Tech News: 2025-48

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

Updates for editors

• Last week, the Wikimedia Search Team recreated the "DWIM" (Do What I Mean) gadget functionality server-side, for Russian and Hebrew Wikipedias. This feature adds cross-keyboard suggestions to the standard search-box suggestions. For example, searching for cxfcnmt on Russian Wikipedia will now add suggestions for счастье ("happiness") that the user probably intended. They plan to enable this feature for other Russian and Hebrew wikis this week. [27]
• Later this week, users of the "Improved Syntax Highlighting" beta feature will have syntax highlighting available in DiscussionTools. This requires that the "Enable editing tools in source mode" preference be set. [28]
• Campaign events extension – the set of tools for coordinating events and other on-wiki collaborations has now been deployed to all Wikimedia wikis. A new feature known as Collaborative contribution to help organizers and participants see the impact of activities has also been added. Join the upcoming learning session to see the new feature in action and share your feedback.
• View all 24 community-submitted tasks that were resolved last week. For example, the bug which stopped CodeReviewBot from working, has now been fixed. [29]

Updates for technical contributors

• Users of Wikimedia API can join a usability study to help validate the new design of Wikimedia REST API sandboxes. Interested participants should fill the recruitment survey. [30]
• The MediaWiki Interfaces team is deprecating XSLT stylesheets within the Action API. Support for format=xml&xlst={stylesheet} will be removed from Wikimedia projects by the end of November, 2025. In addition, it will soon be disabled by default in MediaWiki release versions: v1.43 (LTS), v1.44, and v1.45. Support for XSLT stylesheets will be fully removed from MediaWiki v1.46 (expected to release between April and May 2026). [31]
• The WDQS legacy endpoint (query-legacy-full.wikidata.org) will be decommissioned at the end of December 2025, and finally closed down on 7th January 2026. After this date, users should expect requests to query.wikidata.org that require the full graph to fail or return invalid results if they are not rewritten to use SPARQL federation. The team encourages users to ensure that tools and workflows use the supported WDQS endpoints (https://query.wikidata.org/ - Main graph or https://query-scholarly.wikidata.org/ - Scholarly graph). For support with migrating use cases, please review the Data Access and Request a Query pages for details and assistance on alternative access methods.
• Detailed code updates later this week: MediaWiki

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

MediaWiki message delivery 15:53, 24 November 2025 (UTC)

Template bug on crops of deleted copyvios

There appears to be a bug in the {{Extracted from}} template that's causing cropped images to wrongly describe their source image as having been "deleted for reasons that do not affect this image", when that source file has been deleted. The cropped image is presented to the user as if it has no problems at all, and can still be used.

For example, File:Prince Hamzah.jpg, a photo taken from social media, was deleted for lacking permission a few days ago. But File:Prince Hamzah (cropped).jpg, a crop of it that links back to the original, still exists and now confidently says:

This image has been extracted from another file: Prince Hamzah.jpg. The source file was deleted for reasons that do not affect this image, like a derivative work which is not a part of this cropped image.

(I've now manually flagged this crop as also lacking permission.)

This appears to be a mistake in the {{Extracted from}} template that was introduced in 2021, flagged on the template talk page in 2022 and is still unfixed. It seems to be assuming that all missing source files were deleted "for reasons that do not affect this image", when the template can't actually know that: the only information the template has is that the source no longer exists.

Can somebody with a better understanding of templating and the deletion process take a look at this? Belbury (talk) 12:42, 25 November 2025 (UTC)

It's not always the case that a crop is a copyvio if the parent image is; it may be that one half was a copyvio and the crop removed that.

The presumption is that cropped images that are still copyvios will be deleted when the parent image is deleted; and thus that the template only applies to crops without copyvios. Andy Mabbett (Pigsonthewing); Talk to Andy; Andy's edits 14:18, 25 November 2025 (UTC)

I suppose the question is how often admins delete images without checking if any cropped versions also need to be deleted.

Is it safe to assume it's rare enough that we're saving admins a significant amount of work by having this template automatically mark all surviving crops as source file was deleted for reasons that do not affect this image, even if that's giving us some false positives? Belbury (talk) 16:04, 25 November 2025 (UTC)

It seems to be assuming that all missing source files were deleted "for reasons that do not affect this image" Why should it not. If the extracted images is still there and hasn't also been deleted, then one can assume this. I think it would be better to ask about / work on / raise awareness about copyvio file deletions also checking for extracted files. Prototyperspective (talk) 17:10, 25 November 2025 (UTC)

It's not lining up if we're assuring users that the stated licence is valid because the source was deleted for reasons that do not affect this image, but we're also categorising them into the backlogged Category:Extracted images with broken file links and asking experienced editors to check them all.

If we're confident that admins check for linked crops every time and best practice is to let the template handle the switch from {{Extracted from}} to {{Extracted from deleted}} automatically, we shouldn't be filing these into a heavily backlogged "priority to check" category, should we? Belbury (talk) 09:16, 26 November 2025 (UTC)

One could also have a parameter in the template that can get changed when the image got checked. However then I think it needs some change to a gadget that allows reviewing files with the click of a button. The template edit request could be made at Commons:Template requests. Prototyperspective (talk) 13:53, 26 November 2025 (UTC)

Rename

Can you rename File:Wohnhaus_Kirchplatz_1.jpg please to File:Tauchritz Kretscham mit Hauptbau, Saalbau und Nebengebäude Kirchplatz 20.jpg. Regards, Sanisconokow (talk) 14:38, 29 November 2025 (UTC)

@Sanisconokow: Done. In future you can mark your own uploads for renaming using the "Move" link. See COM:FR for details. --bjh21 (talk) 15:41, 29 November 2025 (UTC)

Ah ok, it is missing at mobile page... Thank you Sanisconokow (talk) 18:48, 29 November 2025 (UTC)

Is it really missing in the mobile Web version of Commons? If so, please create a code issue on phabricator to show the hyperlink also on mobile (and then link it here using {{Tracked}}). Prototyperspective (talk) 11:25, 3 December 2025 (UTC)

Display bug for usernames in "File history" section of file pages

Tracked in Phabricator
Task T411304

I just noticed in the "File history" section of file pages (example: File:Hungry Howie's on Pensacola Street, Tallahassee, Florida.jpg, but it's doing it on all pages that I can see), that it's now doing this with my username. I'm pretty sure it didn't used to break like this, and it looks like there should be plenty of room for it in the box without breaking. I'm guessing something got changed in the backend somewhere? - The Bushranger (talk) 23:26, 29 November 2025 (UTC)

I have the same problem for my uploaded files. Also a break before the last letter. It looks like there is same sort of nbsp in the space --PantheraLeo1359531 😺 (talk) 09:51, 30 November 2025 (UTC)

Image thumbnail problem

Could take anyone a look at File:Vittore Carpaccio - Young Knight in a Landscape - Google Art ProjectFXD.jpg. For some reason the image doesn't show up in any page, where it's used. Armbrust (talk) 17:07, 30 November 2025 (UTC)

All i see in the logs i have access to is a bunch of "first byte timed out" errors. Would probably need to file a bug on phabricator to get it more investigated. If the file is a progressive jpeg, try uploading as a baseline jpeg. Bawolff (talk) 20:03, 30 November 2025 (UTC)

Fixed by Yann (thanks!) with the following comment/explanation: c:User:Rillke/bigChunkedUpload.js: baseline instead of progressive. How to see more files affected by this issue so they can be fixed as well or alternatively is there a code issue about making also such progressive files show up properly? Prototyperspective (talk) 11:28, 3 December 2025 (UTC)

Tech News: 2025-49

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

Updates for editors

• The Wikipedia Year in Review 2025 will be available on December 2 for users of iOS and Android Wikipedia apps, featuring new personalized insights, updated reading highlights, and refreshed designs. Learn more on the review's project page.
• The Growth team is working on improving the text and presentation of the Verification Email sent to new users to make them more welcoming, useful and informative. Some new text have been drafted for A/B testing and you can help by translating them. See Phabricator.
• Add a link will now be deployed at Japanese, Urdu and Chinese Wikipedias on December 2. Add a link is based on a prediction model that suggests links to be added to articles. While this feature has already been available on most Wikipedias, the prediction model could not support certain languages. A new model has now been developed to handle these languages, and it will be gradually rolled out to other Wikipedias over time. If you would like to know more, please contact Trizek (WMF).
• View all 34 community-submitted tasks that were resolved last week. For example, the issue where search boxes on some Commons pages showed no results due to switch from SpecialSearch to MediaSearch, has now been fixed. [32]
• Two new wikis have been created:
  • a Wikipedia in Toki Pona (w:tok:) [33]
  • a Wikiquote in Nigerian Pidgin (q:pcm:) [34]

Updates for technical contributors

• Detailed code updates later this week: MediaWiki

In depth

• The Wikimedia Foundation is in the early stages of exploring approaches to Article guidance. The initiative aims to identify interventions that could help new editors easily understand and apply existing Wikipedia practices and policies when creating an article. The project is in the exploration and early experimental design phase. All community members are encouraged to learn more about the project, and share their thoughts on the talk page.

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

MediaWiki message delivery 18:54, 1 December 2025 (UTC)

File:British Punjab 1909.svg

What's wrong with this map, it doesn't load at all?-- Htm (talk) 20:31, 1 December 2025 (UTC)

That happens for a small fraction of SVG files and was fixed for this file by Glrx. @Glrx: Could you also fix this one? Moreover, is there a way to list all of the SVG files with this bug so they can all be fixed? Prototyperspective (talk) 10:40, 3 December 2025 (UTC)

Sorting files in a category by the number of categories the files have?

Is this possible somehow?

It would also be useful for Wikipedia articles.

Here, in the case of Category:NIH BioArt, I'd like to either filter for files with only the (currently) 2-3 meta-categories set or sort the files by number of categories to add categories to those files that miss them.

Most of these files don't have categories set and currently one can't filter away the ones that already got some. Categorization request here. Prototyperspective (talk) 00:47, 3 December 2025 (UTC)

Does https://quarry.wmcloud.org/query/99622 work? Bawolff (talk) 02:48, 3 December 2025 (UTC)

Proposal about changing VisualFileChange.js

Not sure that I need to put it here but don't know where else but there was warning make post in village pump too...

Pressing enter inside input field should be equal to pressing compare button

https://commons.wikimedia.org/wiki/MediaWiki_talk:Gadget-VisualFileChange.js#Pressing_enter_inside_input_field_should_be_equal_to_pressing_compare_button DustDFG (talk) 05:48, 3 December 2025 (UTC)