Shortcuts: COM:VP/T • COM:VPT

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

Continuing Commons:Village pump/Technical/Archive/2024/10#Templates in description field cause empty caption in Media Viewer: I write to inform that I reported the problem as https://phabricator.wikimedia.org/T380190. You can add more details if you wish, or interact in some other ways – I'm not familiar with Phabricator savoir vivre and politics.

I would also like to add that I feel demotivated and hopeless by the way the now archived thread linked above was handled. I asked for help and no one even bothered to answer "no, I won't help, do it yourself". The thread was left to die, without anyone giving a helping hand to bring the topic closer to some solution. I don't think that ignoring a problem makes it disappear. This was an unpleasant experience for me to collaborate this way. I hope someone reads this feedback and makes some use of it. Derbeth ^talk 16:15, 18 November 2024 (UTC)[reply]

Maybe User:Sannita (WMF) can help? It's a problem I was wondering how to get around it before.
 ∞∞ Enhancing999 (talk) 14:25, 19 November 2024 (UTC)[reply]

I'll flag it to the devs and see if they can do something about it. I'm sorry that @Derbeth had this unpleasant experience. I'll keep you posted about it, but please be aware that it might take some time. Sannita (WMF) (talk) 14:51, 19 November 2024 (UTC)[reply]

Thank you Sannita. I fully understand fixing bugs takes time. I just wish discussions here were more like "exchanging different opinions -> agreeing what to do -> doing", instead of "dissolving" without any conclusion, as I felt was the case with the topic I started in October. --Derbeth ^talk 16:51, 19 November 2024 (UTC)[reply]

Yeah, I see. As I said, I'll try this time to get you a solution for it, instead of just disappearing. If you don't hear from me, you're free to ping me on my talk page about this bug. Sannita (WMF) (talk) 17:21, 19 November 2024 (UTC)[reply]

I wish that too. I think people did not engage exchanging different opinions -> because it's clear this needs to be fixed and people share the opinion that it needs to be fixed with it not being useful in regards to getting it fixed to write that. -> agreeing what to do for bugs people generally agree that it should be reported and fixed. Somebody should have asked to create a phab issue. -> doing this part is the key problem. Even major bugs like all interactive charts on Wikipedia being broken or Commons categories not showing on mobile are not getting fixed after timescales of 5 years to decades. I don't think complaining about this is enough anymore so I made concrete suggestions on how to fix this here. They could readily be discussed and implemented which would result in all technical issues being addressed more often and more quickly:

Please increase MediaWiki development capacity further.

Prototyperspective (talk) 17:37, 19 November 2024 (UTC)[reply]

The commons category thing is not a case of insufficient resources. The graph thing is partially a resource problem, but that is hardly the only issue there and it would be a gross oversimplification to boil it down to just that. Some problems are resource problems, i would even say many problems on commons are resource problems, but not all problems are resource problems. Bawolff (talk) 21:09, 19 November 2024 (UTC)[reply]

Those were just examples. Meant to add a note that the hiding of categories on mobile doesn't even really require much resources but dropped it; this just makes it even worse. Add them already, what gives WMF the permission to just hide away this core useful data I wonder. It's not a simplification to say things are technical development capacity problems, it would be solved much faster with more thinking/development capacity or are we waiting for a new Internet protocol for it to be invented before it can be addressed? I was not describing "resource" problems, I was describing a lack of technical development...obviously increasing technical development would result in more technical issues getting fixed and faster. Prototyperspective (talk) 21:15, 19 November 2024 (UTC)[reply]

Sure, but i also think some of these problems are deciding what to do problems. No amount of technical resources will fix a problem if the underlying issue is we simply decided not to do it. Like the category thing in particular is pretty clearly not a case of WMF being too busy - its a trivial change. Its a product failure - there is a mismatch between what commons thinks is important and what that particular team thinks is important. If we want to fix that we need better communication not more people fixing bugs (there are other things where more people would be helpful). Bawolff (talk) 09:11, 20 November 2024 (UTC)[reply]

These were examples so ignore this example if it's a bad example. we simply decided not to do it we did not. its a trivial change which is one reason why I don't donate to WMF and think they're doing a bad job what that particular team thinks is important what team? we need better communication there have been Wishlist proposals and phabricator issues and it's the most-supported request in the technical needs survey. All WMF needs to do is listen a bit and/or engage in any of these venues. not more people fixing bugs I see a tiny fraction of usually quite useful proposals in meta:Category:Community Wishlist Survey results have been implemented so far and on phabricator it's an even more desolate situation. We need far more people fixing bugs. Prototyperspective (talk) 19:28, 20 November 2024 (UTC)[reply]

There are always going to be more tasks than people. Having more people does not mean they will neccesarily work on the things you want them to. Like if there is something everyone agrees needs to be worked, but is pushed for something higher priority - then yes, more people will help with that. If there is something nobody seems to intend to fix, more people won't help, because that is not going to change the intention. Bawolff (talk) 14:48, 25 November 2024 (UTC)[reply]

I wasn't saying anything to the contrary.
Anyway, as a note the likelihood of particularly useful or needed issues/proposals getting implemented is higher with more developers working on issues and more development per dev. Moreover, if lots of issues like pesky bugs are worked on then there is more possibility for other devs to work on interesting features since the major bugs are already being taken care of. e.g. we can't innovate much if everyone is only busy fixing bugs. Prototyperspective (talk) 15:05, 25 November 2024 (UTC)[reply]

It appears the problem was identified earlier (phab:T373979), but the ticket closed without actually being solved in general. I doubt we should do the solution suggested there in dozens if not hundreds of templates. @User:Sannita (WMF)
 ∞∞ Enhancing999 (talk) 08:42, 26 November 2024 (UTC)[reply]

Possibly the solution is to change Template:Lang. Identifying the language shouldn't mark the string as a "description". But then, it's not entirely clear what that class implies.
 ∞∞ Enhancing999 (talk) 09:33, 26 November 2024 (UTC)[reply]

Unless someone comes up with a better solution, I'd suggest we remove the "description" class from Template:Lang.
 ∞∞ Enhancing999 (talk) 10:02, 28 November 2024 (UTC)[reply]

@Enhancing999 Thanks for proposing a solution. Is there anything from WMF side that we can do to help? Asking this to see if I can bring it up at the earliest meeting to discuss. Sannita (WMF) (talk) 13:26, 28 November 2024 (UTC)[reply]

Dear fellow Wikimedians, here is one for the template experts, it regards the {{Licensed-FOP}} template. IMHO this edit has introduced two errors into the template by making it create unmatched/unbalanced {{...}} and <div>...</div>. I have tried to fix this in the two last edits ([1], [2]). Could you please check whether the template is now (more or less) correct again, or if I have overlooked or even introduced yet another error (in the latter case please take my apologies!)? Thank you very much for your help! Best, – Aristeas (talk) 20:34, 22 November 2024 (UTC)[reply]

@Aristeas still broken. See, for example, uses at File:Tower of Taipei 101.jpg and File:Singapore Merlion Park, August 2023.jpg. In fact, Michael Barera removed the template I added on the desc page of his image of T-Mobile arena, citing this broken template as the reason (read this). JWilz12345 (Talk|Contributions) 23:27, 24 November 2024 (UTC)[reply]

Thank you for your input, JWilz12345! It’s the same with my own photos which use the template (example): the FoP is still displayed in a wrong way. The question is: Where is the problem in the code of the {{Licensed-FOP}} template? I think my two edits have fixed the syntax errors introduced by this edit. Maybe the current problems were not related to that, but to some other changes, e.g. to this one?

This is why I left this message, and I can only beg our real template experts to look into this problem. – Aristeas (talk) 09:07, 26 November 2024 (UTC)[reply]

@Labant FYI
 ∞∞ Enhancing999 (talk) 09:09, 26 November 2024 (UTC)[reply]

Reverted it for now. When editing it, please preview it with some of the files mentioned here.
 ∞∞ Enhancing999 (talk) 09:35, 26 November 2024 (UTC)[reply]

Thank you very much, Enhancing999! Now the template works perfectly again. The current (reverted) version is identical to the revision as of 21:16, 8 August 2024 by Jarekt. This confirms that the recent problems were introduced by this edit. In addition to the problems this edit introduced I also doubt whether the layout change made by that edit was really necessary – the additonal left margin may look nice in some contexts, but looks irritating in some other contexts. Therefore I would ask that everybody who wants to change the layout of such widespread templates should discuss this before with other users and then tests the changes first befor deploying them. Thank you – Aristeas (talk) 10:04, 26 November 2024 (UTC)[reply]

Hello everyone, first of all, sorry for the inconvenience. The reason for my contribution was that {{Licensed-FOP}} looks the same as {{Licensed-PD}}. Unfortunately, I could not use the solution there because it would cause problems with {{Self}}. I thought I had found the solution with the <div>-function. But apparently not. I have also reset {{Licensed-TOO}}. I have put the process on my to-do list and will be continue working on it in my user-namespace. --Labant (talk) 14:36, 27 November 2024 (UTC)[reply]

I think I found the error. In any case, the files in question are now displayed correctly. Labant (talk) 13:18, 28 November 2024 (UTC)[reply]

Hi!

Especially when it comes to uploading larger files, the error "Could not acquire lock. Somebody else is doing smth. with that file." occurs. It is frustrating when there are many attempts needed to upload a larger file. The error occurs with the Upload Wizard and th chunked upload. It's been already around for several days.

--PantheraLeo1359531 😺 (talk) 13:32, 24 November 2024 (UTC)[reply]

You might want to add it to phab:.
 ∞∞ Enhancing999 (talk) 08:29, 26 November 2024 (UTC)[reply]

 Done Thanks, added :) --PantheraLeo1359531 😺 (talk) 16:02, 26 November 2024 (UTC)[reply]

@Sannita (WMF): would you check?
 ∞∞ Enhancing999 (talk) 22:33, 26 November 2024 (UTC)[reply]

Added the tag to put it on the dev's radar. I'll see at the next estimation what can we do about it. Sannita (WMF) (talk) 12:33, 27 November 2024 (UTC)[reply]

@Sannita (WMF) thanks. "Lock" suggests database issues. Together with phab:T379035, this might get upload issues finally resolved.
 ∞∞ Enhancing999 (talk) 09:49, 28 November 2024 (UTC)[reply]

Is there a parser function for checking if the file is of a specific media-type like image or video?

Could not find find a Commons version for Help:Conditional expressions and thus did not find a way for mediatype conditions.

Some templates seem to need this. Prototyperspective (talk) 14:59, 26 November 2024 (UTC)[reply]

@Prototyperspective: This is not a good solution, but I found {{File type en}} that does it by an ugly means. --bjh21 (talk) 14:25, 2 December 2024 (UTC)[reply]

Thank you! This solves it. I think there were also some templates that display image despite that the file is an audio but I can't find them anymore and think some of these change once structured data is added to the file which can take some time (but not all of them). So this may also be useful it various places. Prototyperspective (talk) 15:04, 2 December 2024 (UTC)[reply]

You can get the mime type via Lua reference manual - File metadata. But it doesn't seem that MediaWiki's internal concept of mediatype (image/video/application etc, that the search etc depend for categorising these) is exposed through that endpoint. Then again, this is a very internal definition and concept. —TheDJ (talk • contribs) 14:31, 5 December 2024 (UTC)[reply]

How remove sodipodi:nodetypes attribute on a file ( File:Drapeau de Vaudreuil-Soulanges.svg) ? YanikB (talk) 20:45, 26 November 2024 (UTC)[reply]

You could open the file in Inkscape and "save as optimized SVG", or open the file in a text editor and do it manually/with find and replace. —CalendulaAsteraceae (talk • contribs) 21:04, 26 November 2024 (UTC)[reply]

@YanikB: I took the comment as the file would not display. I added the sodipodi and inkscape namespace declarations, so the file now displays. The file should have had the namespace declarations, it used to display on Commons, but in April 2024 the Commons SVG renderer started rejecting noncompliant SVG files. There are probably thousands of such files on Commons. Glrx (talk) 02:29, 28 November 2024 (UTC)[reply]

Hi there, the original content producer of these videos has noticed a deterioration in the sound quality of the videos there, both old and new. I can hear a drop in the audio quality from the files uploaded.

Has there been a change in the compression levels on sound within the .webm files? JimKillock (talk) 18:22, 2 December 2024 (UTC)[reply]

MediaWiki message delivery 22:19, 2 December 2024 (UTC)[reply]

Category:Blue ISO 639 icons with double parentheses looks like this:

Is this a a known issue? Bad old PNG does NOT suffer from this bug. Taylor 49 (talk) 16:34, 3 December 2024 (UTC)[reply]

Looking at File:ISO 639 Icon gwi.svg shows the line

<text x="300" y="141" font-size="150" fill="navy" font-family="Helvetica,Arial,sans-serif" font-weight="bold" transform="scale(0.67 1)" text-anchor="middle">gwi</text>

IIRC, the current renderer has a problem when the scale is not uniform: scale(0.67 1).

Glrx (talk) 20:02, 3 December 2024 (UTC)[reply]

OK ... I can't find it on Phabricator. Should one create a BUG report there? Taylor 49 (talk) 23:19, 3 December 2024 (UTC)[reply]

These images should be fixed rather than the software. Sjoerd de Bruin (talk) 23:23, 3 December 2024 (UTC)[reply]

My SVG spec (admittedly not very good) says:

scale(<sx> [<sy>]), which specifies a scale operation by sx and sy. If <sy> is not provided, it is assumed to be equal to <sx>

Given that, the images are valid. Anyone has an authoritative SVG spec saying that different scaling factors for X and Y are invalid? Taylor 49 (talk) 23:31, 3 December 2024 (UTC)[reply]

The files are legitimate, so they should not need to be fixed. Fixing them is also problematic because the support for font-stretch="condensed" (the practical effect of the nonuniform scaling) is poor. Also, Commons does not support textLength.

There was an involved discussion about this problem a long time ago, but I could not find it. I also did not find something on Phabricator, so a Phabricator issue should be started. Someone can check whether this bug is already fixed in later versions of librsvg.

Glrx (talk) 23:42, 3 December 2024 (UTC)[reply]

• Topic is still present at Commons:Graphics village pump#Issues with E-road shields (Tabliczka set). TilmannR diagnosed the issue. Phab:T370044. Glrx (talk) 23:54, 3 December 2024 (UTC)[reply]

Previously reported at https://en.wikipedia.org/wiki/Wikipedia:SVG_help/Archive_10#Text_misaligned_(not_previous_bug) cmɢʟee ⋅τaʟκ 13:13, 4 December 2024 (UTC)[reply]

When I upload and download a JPG file with the XMP.Attribution Name set to First Last <first.last@provider.tld>, Wikimedia Commons, for some reason, omits the space char between Last and < in the "When re-using this work, please credit" field in the Metadata section. This is the only name/email address combination that renders incorrectly in this section. So a bit odd really.

The given thumbnail provides an example. A small but not insignificant bug. I also searched the Village Pump archives but could not find any reference to this particular problem. Best, RobbieIanMorrison (talk) 21:22, 4 December 2024 (UTC)[reply]

I can confirm that this very minor bug exists. In the file in the field "author" there is ordinary space $20 followed by ordinary less-than-sign $3C. However in the field "please credit" there is ordinary space $20 folowed by a HTML-encoded less-than-sign. Taylor 49 (talk) 21:58, 4 December 2024 (UTC)[reply]

As it happens, my Thunderbird mail client adds back the missing space char when the current value is copy/pasted in. RobbieIanMorrison (talk) 09:15, 5 December 2024 (UTC)[reply]

it's probably because it can be html, and it does some sort of normalisation on it. These parts of the MediaWiki code tend to be rather obscure. —TheDJ (talk • contribs) 14:13, 5 December 2024 (UTC)[reply]

Speaking as a programmer, it is usually worth fixing bugs. An artifact that is brushed aside as trivial may well indicate a more significant problem. And I would also argue that image metadata should be faithfully replicated in all cases. RobbieIanMorrison (talk) 07:33, 7 December 2024 (UTC)[reply]

Hi all

I'm trying to help UN FAO upload some maps to Commons but I'm getting an error I've never seen before, the error happens when I try to upload the SVG files, does anyone know what the issue is and can someone suggest steps to fix them? I'm not very technical so a vague answer isn't really going to help a lot :)

The error message is maybe 20 pages long so I'll just copy the start of it in below.

  Found href to unsafe data: URI target <image http://www.w3.org/1999/xlink:href=@data:;base64,

Thanks so much

. John Cummings (talk) 15:56, 5 December 2024 (UTC)[reply]

@John Cummings:

The ...xlink:href=@data:mimetype;base64,.. is a data URL. https://developer.mozilla.org/en-US/docs/Web/URI/Schemes/data

A data URL allows arbitrary content. MediaWiki wants to limit that content, so it only accepts a limited number of data URL mimetypes. The mimetype is not specified in the data URL, so MediaWiki will reject the upload.

The element is probably trying to include a bitmap image. Inserting the appropriate mimetype between the colon and semicolon should fix the problem. Acceptable mimetypes are image/jpeg or /image/png.

Glrx (talk) 18:47, 5 December 2024 (UTC)[reply]

Hi Glrx thanks very much for the technical explanation, unfortunately I'm far too much of a muggle to work out how to use it. Do you have a suggestion of which program to use and what buttons to press to resolve this? Thanks again, John Cummings (talk) 08:34, 6 December 2024 (UTC)[reply]

@John Cummings:

Use a text editor. Search for href="@data:. then add the appropriate mimetype after the colon and before the semicolon. Save the file. Then open the file in a browser to see that it displays correctly (Windows: locate file in the File explorer; then right click and open with Chrome/Edge/Firefox/whatever). If the file is good, then upload the file to Commons.

Glrx (talk) 16:13, 6 December 2024 (UTC)[reply]

I'd like to sort audio files not by recency or relevance but by duration (maybe filesize would also work as a proxy for that). Is that possible somehow? I'd like to use it in a category of spoken Wikipedia audios for example to be able to choose between a very long or a shorter audio. It would probably be useful also for many other kinds of applications. Prototyperspective (talk) 16:39, 5 December 2024 (UTC)[reply]

Image duration is not an indexed field in the database I believe. It's only in the db's metadata structure of a file's record, which makes it difficult to query over a collection of files. —TheDJ (talk • contribs) 10:42, 6 December 2024 (UTC)[reply]

I figured maybe it was in the searchindex, but I think it isn't in those indexes either. —TheDJ (talk • contribs) 10:47, 6 December 2024 (UTC)[reply]

But you can sort by filesize from quarry: https://quarry.wmcloud.org/query/88499 —TheDJ (talk • contribs) 10:49, 6 December 2024 (UTC)[reply]

Thanks, that's helpful. However, that's just the filesize, not the duration and I'm looking for something that can be used in the UI (integrated into MediaSearch or SpecialSearch). Strange if it's not in the database since on the file page there is a field "Dimensions" which shows both the file-size and the duration (except for files with this bug). Prototyperspective (talk) 11:11, 6 December 2024 (UTC)[reply]

The file page is just one page, it can descend into the metadata relatively cheaply. Sorting is a 140+ million row operation and for that we need to pre-extract the information and put it into a separate column of the database and keep an index. We do this for width, height and file size, but not for duration. —TheDJ (talk • contribs) 15:54, 10 December 2024 (UTC)[reply]

An extra column for duration like for media width would be very useful then. It would also enable finding & fixing more of the files that display a duration of 0 (and by now I also found a mp3 and an ogg file with that). Prototyperspective (talk) 16:07, 10 December 2024 (UTC)[reply]

Hello, you are invited to participate in the discussion at Template_talk:Mbox#Shift_to_Lua —Matrix(!) _{ping one}^{when replying} {user - talk? - _uselesscontributions} 20:40, 5 December 2024 (UTC)[reply]

Hello, I noticed this file File:Bihar district location map Bhojpur.svg, the image is not loading, and opening the image shows message

error on line 3 at column 43: xmlns:ns: '&ns_sfw;' is not a valid URI

I hope somebody can fix it. Thanks, ExclusiveEditor (talk) 20:50, 5 December 2024 (UTC)[reply]

Fixed namespace declaration. File should display in a couple hours. Glrx (talk) 22:01, 5 December 2024 (UTC)[reply]

Is anyone else getting this message on the file pages when using the custom license option on the Upload Wizard? Example at File:(CHN-Shanghai) Pudong Yanggao W0K-114 沪A31192D 581 2024-12-08.jpg. 沪A 05683D_S5A-0043 14:08, 8 December 2024 (UTC)[reply]

Tracked in Phabricator
Task T364150

Someone should batch-remove all 142 instances of {{self|subst:Custom license marker added by UW}} after phab:T364150 is fixed. See Template:Custom license marker added by UW for historical context. Dexxor (talk) 12:56, 18 December 2024 (UTC)[reply]

MediaWiki message delivery 22:12, 9 December 2024 (UTC)[reply]

I've slowly been requesting overwriting of various files from the IWM. They've been so gracious in correcting exposure on some of those (as I write this, I begin to wonder whether the modifications are enough to warrant copyright protection...), but there being multiple versions of a file seems to confuse Dezoomify, who only pulls the second version with lighting issues. With the help of ChatGPT, I could extract the exposure-corrected one, albeit at a reduced-resolution (1000x1300, compared to the 2400x3000 unedited) version of the edited image. Is there something I'm doing wrong in terms of extracting the edited image in all of its glorious pixels?

The IWM file in question is https://www.iwm.org.uk/collections/item/object/205022125

Here's the ChatGPT convo: https://chatgpt.com/share/67577715-c474-8003-a35e-2456499c0a64

Thanks. JayCubby (talk) 23:12, 9 December 2024 (UTC)[reply]

Similarly, there appears to be a better version of File:John Finnis (captain) 2.jpg (source: https://collections.slsa.sa.gov.au/resource/B+343) at https://collections.slsa.sa.gov.au/resource/B+343/tiles.json

but Dezoomify isn't working on the code as I'd expect:

JayCubby (talk) 17:07, 10 December 2024 (UTC)[reply]

Hi. If Dezoomify does not yield the desired result, then we have other methods ... First, look at the code for the page. On the page mentioned in IWM, press Shift + Ctrl + i (works in Firefox) to see the code window. In the code window, you should use the "Network" tab. Then click on the desired picture (the one to the left?). You will see three lines of code, one with the "info.json" file that is used by Dezoomify, and two with jpg files that result in thumbs of the picture. If you click on the bottom jpg codeline, you will see this code: https://media.iwm.org.uk/cantaloupe/iiif/2/171%7C%7C950%7C%7Csuper_000000.jpg/full/251,/0/default.jpg

Now substitute "251" with "2400" and Voila! You get a picture in 2400 x 3111 (at least that is how it worked for me). You might try with larger values than "2400", but the system at IWM would block that option. Hope this helps. Cheers Rsteen (talk) 03:27, 11 December 2024 (UTC)[reply]

Great, I can do that going forward and many thanks! Often images that have been retouched aren't accessible beyond the 2400px, or so I've unreliably figured out after further digging in the source code. JayCubby (talk) 03:53, 11 December 2024 (UTC)[reply]

Interesting. I use the Dezoomify extension on Chrome, and I only get 1536 x 1990 pixels. Please note that this may not be in the public domain. They say "Press agency", not a government picture. Yann (talk) 09:59, 11 December 2024 (UTC)[reply]

Background: I am not new to coding and data processing, but to the Wikimedia Commons sphere. I am developing a batch uploading process for the object photographs of a community archive of everyday material culture in Singapore as image sources for their Wikibase Cloud instance (NGO "My Community, Data Partner of Wikimedia Germany, see here). I was sent here by my post on the general Help Desk: https://commons.wikimedia.org/wiki/Commons:Help_desk#OpenRefine_Upload_to_Wikimedia_Commons_failing_without_notice_(abuse_filter_triggered?).

Problem: I have prepared and reconciled all relevant metadata, filenames and filepath in OpenRefine for a test batch of 5 images, including schema preparation with "add media" to Wikimedia Commons. When I did a first technical trial run of the pipeline a month ago, my images successfully uploaded to Wikimedia Commons even though the metadata was far from perfect at the time. Now that I have worked on the data transformation, following the Wikimedia best practices as closely as I could, I have the same thing happening to me as this user here: https://forum.openrefine.org/t/no-errors-reported-and-the-percentage-completed-went-through-but-no-upload-done/899. I get a "100% percent completed" notification from OpenRefine but no uploads have been made (I checked under my user profile as well as searched for the file names).

For reference, see the permalink to my OpenRefine project (hopefully this works!).

What could be the issue? I'd gladly provide more information once I know what is needed here. Thanks! Esxx24 (talk) 22:54, 11 December 2024 (UTC)[reply]

MediaWiki message delivery 22:21, 16 December 2024 (UTC)[reply]

If you install m:User:Tol/RealSVG.js and go to Category:Icons8 flat-icons, you'll see that a ton of the SVGs disappear. Why? According to the W3C checker, their content type is text/plain! Is there some way to (perhaps check all and) change SVGs content types in bulk? Aaron Liu (talk) 01:02, 17 December 2024 (UTC)[reply]

Validate offline and re upload. Or if they are valid and can be identified easily (by prefix for instance) it might be worth it to run a server side script, but this requires a Phabricator ticket. The cause might be that there is no XML DOCtype declared for these files. —TheDJ (talk • contribs) 12:21, 17 December 2024 (UTC)[reply]

Being more concrete with two example files.

• File:Dam.svg (27 March 2015) does not have an XML processing instruction.

  SVG 1.1 validation gives one error (version="1").

  https://validator.w3.org/check?uri=https%3A%2F%2Fcommons.wikimedia.org%2Fwiki%2FSpecial%3AFilepath%2FDam.svg&doctype=Inline&ss=1

• File:Icons8 flat headset.svg (7 March 2016) does not have an XML processing instruction.

  SVG 1.1 validation link fails with text/plain.

  https://validator.w3.org/check?uri=https%3A%2F%2Fcommons.wikimedia.org%2Fwiki%2FSpecial%3AFilepath%2FIcons8_flat_headset.svg&doctype=Inline&ss=1

  The file URL produces text/plain

  https://upload.wikimedia.org/wikipedia/commons/9/95/Icons8_flat_headset.svg

  Request header

  :authority: upload.wikimedia.org
  :method: GET
  :path: /wikipedia/commons/9/95/Icons8_flat_headset.svg
  :scheme: https
  accept: text/html,application/xhtml+xml,application/xml;q=0.9,image/avif,image/webp,image/apng,*/*;q=0.8,application/signed-exchange;v=b3;q=0.7
  accept-encoding: gzip, deflate, br, zstd
  accept-language: en-US,en;q=0.9
  

  https://commons.wikimedia.org/w/api.php?action=query&titles=File:Icons8+flat+headset.svg&prop=imageinfo&iiprop=url%7Cmime%7Cmediatype%7Cmetadata%7Ccommonmetadata%7Cbadfile → image/svg+xml

• File:Icons8 flat assistant.svg (7 March 2016) does not have an XML processing instruction.

  text/plain failure.

  Did an essentially null edit (change version="1" to version="1.1") and the file now validates and displays.

Glrx (talk) 18:33, 17 December 2024 (UTC)[reply]

These videos (1, 2) are a few seconds long, but they show a length of more than 2 hours. How could this be fixed? — Draceane ^talk_contrib. 15:29, 17 December 2024 (UTC)[reply]

This generally happens when the files have not been properly muxed. Passing them through ffmpeg (in copy mode) will fix them. —TheDJ (talk • contribs) 17:31, 18 December 2024 (UTC)[reply]

done —TheDJ (talk • contribs) 09:19, 19 December 2024 (UTC)[reply]

Rebecca Moore (en:Rebecca Moore (scientist)) is a friend of mine. When I told her what her picture was used in Wikipedia (because she never looked at her own page - haha), she was appreciative of the guy who uploaded it, but wished he had uploaded one she felt better represented her and her work. (Yes, the Rachel Carson Award was a great honor, but she thinks the work in Brazil with helping Chief Almir and the Surui tribe save their rainforest was more meaningful.) She gave me the original photo that they used in Time Magazine article April 15, 2016,(https://time.com/4295351/rebecca-moore-google-earth-outreach/) to replace it. I cropped the original 1600 x 1062 to be square, but then realized I couldn't upload it. Can someone please do that for me if I get you the photo? And how would I do that? My real email is martha.legare@gmail.com. Thanks much for your help, Martha MarleeRobertson (talk) 05:58, 19 December 2024 (UTC)[reply]

@MarleeRobertson: Hi, We need a written permission from the photographer, unless he/she uploads it her/himself. And it would be much better to have the original image first, it can always be cropped later. Please see COM:VRT for the procedure. Yann (talk) 09:41, 19 December 2024 (UTC)[reply]

Thanks. To make sure I'm clear: we (and thank you!) can replace the current photo as long as we get the Brazilian photographer's permission, not the guy who posted the current photo? The photo I have was taken for Google - I'm 99% sure they paid her for it. (I think the photographer was from Brazil - will check with Rebecca.) I appreciate your help. MarleeRobertson (talk) 04:09, 20 December 2024 (UTC)[reply]

This image, File:Papua New Guinea relief map.svg, is failing to load globally, and I don't see any indication as to why. The image hasn't been modified in a few years, and the image loads from the direct URL ([16]) and from the link on the description page, but doesn't load when it's placed inline. Is this some kind of database error? Ivanvector (talk) 13:55, 19 December 2024 (UTC)[reply]

Bad ns: namespace declaration fixed. Image should appear in a couple hours. Glrx (talk) 19:03, 19 December 2024 (UTC)[reply]

Same problem as #Error with a file above. Glrx (talk) 23:05, 20 December 2024 (UTC)[reply]

I imported {{Q+}} and Template:Q+/doc from this project into Wikispecies, but the latter is behaving very oddly, and the former not working as expected, and I cannot figure out why. Wikispecies is a small project with few technical editors; can someone assist there, please? Andy Mabbett (Pigsonthewing); Talk to Andy; Andy's edits 16:07, 19 December 2024 (UTC)[reply]

Hi! It seems that there is a problem during File-uploading here on commons. The page was created for my picture, all descriptions and categories can be seen, but the picture itself is missing. Instead I get following message: "Die Datei „mwstore://local-multiwrite/local-public/1/15/Bargischow_Kirche_lub_2024-07-27_img01.jpg“ befindet sich, innerhalb des internen Speicher-Backends, in einem inkonsistenten Zustand." Is this a known issue, is the issue being resolved, and is there a chance I can add my images to the page without having to go through all the work of describing and categorizing again? Thanks in advance Lukas Beck (talk) 20:03, 23 December 2024 (UTC)[reply]

Hi, I got an error while uploading a big video with Chunked Uploads, and many errors while deleting files. It seems there is some issue on the servers today. Yann (talk) 21:22, 23 December 2024 (UTC)[reply]

I used {{US state by city}} to create further subcats of Category:Alaska by city by year. Three days later, those cats are still empty. I don't know much about template programming, but looking over the code, the various by city templates should populate this cat automatically. Please help me out with what missteps may have occurred. RadioKAOS / Talk to me, Billy / Transmissions 23:08, 23 December 2024 (UTC)[reply]

To the best of my knowledge, the by city templates were created via copypasta, so they should have the same syntax and behave the same. Digging further, I wonder if the problem is actually with the above-linked template. Category:2009 in Alaska by city is not populated by the subcats, but does populate Category:2009 in the United States by city by state. OTOH, Category:2010 in Alaska by city is populated by the subcats, but does not populate Category:2010 in the United States by city by state. The former was created by me the other day, while the latter was part of a series created by another editor over three years ago. I haven't examined the breadth of this tree, but the "by city by state" cats for each year appear to be devoid of subcats which should be in there. RadioKAOS / Talk to me, Billy / Transmissions 23:54, 23 December 2024 (UTC)[reply]

The revision history shows it's been edited by @Ricky81682: , @Verdy p: , @AnRo0002: and @SecretName101: . Perhaps you should double-check your edits, as it's apparent the template originally worked correctly but is now broken. I looked over other states' trees in the meantime and the same problem exists. RadioKAOS / Talk to me, Billy / Transmissions 16:09, 24 December 2024 (UTC)[reply]

Looks like a cache issue to me. Category:2010 in the United States by city by state did not have "Category:2010 in Alaska by city" this morning but does now, try doing an edit without any changes on those catgories that are not linked. The edit will not show up in edit history. Snævar (talk) 23:43, 24 December 2024 (UTC)[reply]

File:Liban, Broumana, Vue aérienne oblique (MédiHAL 2557874).jpg is supposed to be deleted per Commons:Deletion requests/Medihal-IFPO duplicate files. Deletion does not work from the DR however, and the file page does not offer me an option for deletion, nor an option to view the history. What is going on here? --Rosenzweig τ 00:21, 24 December 2024 (UTC)[reply]

Never mind, apparently there was no file description page. As soon as I had created one with the content test, I could delete the file. --Rosenzweig τ 00:26, 24 December 2024 (UTC)[reply]

When you look at Category:Amastra, you'll find categories of which the name has changed by a vandal, e.g.

• Ancient Amastra should be Amastra antiqua
• Amastra Abbey should be Amastra badia
• Amastra Baldwiniana should be Amastra baldwiniana
• Amastra horny should be Amastra cornea
• Hulled Amastra should be Amastra decorticata
• Amastra fossil should be Amastra fossilis
• Fraternal Amastra should be Amastra fraterna
• Amastra Grayana should be Amastra grayana
• Amastra Johnsoni should be Amastra johnsoni
• Amastra Lahaina should be Amastra lahainana

and many more. When I press F5 on my keyboard, the proper name appears for a second or two and then changes again into the vandalised names. I have tried to find a solution for this, but I'm at a loss. Can someone put this right ? JoJan (talk) 10:16, 24 December 2024 (UTC)[reply]

I don't see any of these names. When I look at the history for Category:Amastra badia, for example, I also see no edits to it. If it was moved, that would show in the history. The Squirrel Conspiracy (talk) 01:06, 25 December 2024 (UTC)[reply]

I show you a partial clipboard of what I see on my computer (the arrows are mine):

. Perhaps this will help solving this problem. JoJan (talk) 14:15, 25 December 2024 (UTC)[reply]

@JoJan It looks like you have Google Translate attempting to translate these. Try clicking the icon (next to the bookmark star in the address bar), then select Italian (or whatever it detects the source language as). —‍Mdaniels5757 (talk • contribs) 16:46, 25 December 2024 (UTC)[reply]

Thank you very much. I would never have thought of this as a solution. JoJan (talk) 16:50, 25 December 2024 (UTC)[reply]

Hi! It is common to smooth edges in raster images to make them look more aesthetic to the eye. But sometimes, it is desired not to apply this anti aliasing (for example for small 8-bit graphics). Otherwise it looks blurred. Is there a way to change the display style?

A pixelated arrow looks blurred, which is undesired in this case.

Thanks! --PantheraLeo1359531 😺 (talk) 10:34, 25 December 2024 (UTC)[reply]

The best solution for such cases would be to just use SVG instead. GPSLeo (talk) 13:31, 25 December 2024 (UTC)[reply]

Yeah, I thought about it, too, but I guess there are several (unexperienced) users, who may not take the SVG conversion into account (and batch converting may be complicated, too)... --PantheraLeo1359531 😺 (talk) 14:51, 26 December 2024 (UTC)[reply]

I raised a similar issue previously and was told the code involved is intricate and quite possibly quirky and that the problem I described is relatively minor — in short, creating a fix is not especially likely. That earlier example involved ␣< sequences in email addresses.

For context, I specify my JPG metadata using YAML — a language with its own idiosyncrasies — and write that information to file using Python and ExifTool.

My latest upload (see thumbnail) used single quotes preceded (or followed) by spaces in the EXIF::Image Description metadata field, namely ␣'. This sequence was rendered faithfully to my terminal by Python and reported correctly on upload and download by both ExifTool and the gThumb image viewer. So I assume that the metadata is stored correctly in the JPG file.

But Wikimedia omits the leading (or trailing) space char in that sequence in the Description field and in the Metadata table. I duly edited the Description field to correct the corrupted string. But the faulty Metadata table rendering cannot be so easily fixed by users.

This presumed bug might not seem important but I can imagine use‑cases where confusion could result. In any case, I am raising the matter in the hope that a fix might be given some increased priority. Best, RobbieIanMorrison (talk) 22:46, 25 December 2024 (UTC)[reply]