Wikimedia Commons

Commons:Village pump/Technical

< Commons:Village pump

Shortcuts: COM:VP/T • COM:VPT

Welcome to the Village pump technical section

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

COMMONS DISCUSSION PAGES (index)
Please note
 

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.

Broken Convert to SVG scriptEdit

When I have User:Perhelion/fixconverttosvg.js turned on, it hides me Edit button from pages in File NS. (I've comfirmed it by test edit). What could be done with the script to work well? It's very useful tool otherwise. Pinging some users with script linked from their .js @1234qwer1234qwer4, Sarang, and Minorax: — Draceane talkcontrib. 07:39, 16 June 2022 (UTC)

​This script I did not know, but I will give it a look -- sarang♥사랑 07:46, 16 June 2022 (UTC)
What skin are you using? This works for me on Vector; as far as I remember this and SVGcheck do not appear on Monobook at all. 𝟙𝟤𝟯𝟺𝐪𝑤𝒆𝓇𝟷𝟮𝟥𝟜𝓺𝔴𝕖𝖗𝟰 (𝗍𝗮𝘭𝙠) 19:32, 16 June 2022 (UTC)
@1234qwer1234qwer4: I use Vector, today it's working again. Kind of strange... But thank you for responses. — Draceane talkcontrib. 07:44, 17 June 2022 (UTC)

Another problem?Edit

@Sarang: On some files, the script wouldn't run resulting only to redirect to "File:abc#ToSVG". It happens only on some pages (not working; random image – working). The console output: [1]; the correct output for working file should be [2]. I assume that there is a mistake in the JS, but IDK. — Draceane talkcontrib. 10:31, 23 June 2022 (UTC)

@Draceane: That error probably means the jquery.ui module was not loaded as one of the dependencies. Try running mw.loader.load('jquery.ui') in your browser console before using the script. NguoiDungKhongDinhDanh 13:10, 23 June 2022 (UTC)
@NguoiDungKhongDinhDanh: Yes, it helps, thank you. Is there any option how to change e.g. my common.js in order to load the script properly? — Draceane talkcontrib. 13:30, 23 June 2022 (UTC)
@Draceane: This issue should normally be fixed in the script itself; however, since Perhelion is inactive, you can add this to your common.js (don't use the deprecated importScript):
mw.loader.using('jquery.ui', function() {
    mw.loader.load('//commons.wikimedia.org/w/index.php?title=User:Perhelion/fixconverttosvg.js&action=raw&ctype=text/javascript');
});
NguoiDungKhongDinhDanh 13:37, 23 June 2022 (UTC)
Great, it works, thanks! I've moreover replaced all importScript with mw.loader.load. — Draceane talkcontrib. 14:15, 23 June 2022 (UTC)

Error: An exception occurred: FileNotFoundError: b"[Errno 2] No such file or directory: '/data/project/video2commons/video2commons/frontend/static/uploads/fc25beb8-ed71-11ec-921f-82d0630f66a4'"Edit

Every time I try to upload a video to Video2Commons it shows me the error "Error: An exception occurred: FileNotFoundError: b"[Errno 2] No such file or directory: '/data/project/video2commons/video2commons/frontend/static/uploads/fc25beb8-ed71-11ec-921f-82d0630f66a4'" ". How can I upload videos? --Donald Trung 『徵國單』 (No Fake News 💬) (WikiProject Numismatics 💴) (Articles 📚) 12:45, 16 June 2022 (UTC)

As far as I know this is an error many people experience. Unfortunately, the only way (I know right now) is converting the video by yourself (with FFMPEG for example) and uploading it on the UploadWizard or other upload protocols. --PantheraLeo1359531 😺 (talk) 13:20, 9 July 2022 (UTC)

Crop Tool failures - "! Command not found"Edit

The Crop Tool has failed to crop .pdf and .djvu files for the last 9 to 15 days. See this Crop Tool error message from this file File:Lucky Bag (IA luckybag1926unse).pdf today :

! Command not found: "gs -sDEVICE=jpeg -dNOPAUSE -dBATCH -dSAFER -dFirstPage='1' -dLastPage='1' -r300 -dUseCropBox -sOutputFile='/data/project/croptool/public_html/files/5f8384c2c799e3f0aef79d965242ea9450abbba6.pdf.page1.jpg' '/data/project/croptool/public_html/files/5f8384c2c799e3f0aef79d965242ea9450abbba6.pdf' 2>&1"

I have never had a problem before with this tool. Can it be fixed?

Thank you, -- Ooligan (talk) 20:10, 19 June 2022 (UTC)

It's also returning errors when an attemt is made to crop a jeg. Andy Mabbett (Pigsonthewing); Talk to Andy; Andy's edits 14:56, 16 July 2022 (UTC)

Thumbnails have become tinyEdit

Tracked in Phabricator
Task T311119

@Jon (WMF): , whenever I use "Desktop mode" on my mobile device (Google Pixel 4A using the Ecosia browser) I get this weird scaling. Licenses have become very wide which isn't an issue, per se, but the thumbnails of images have become microscopic. If you want I can include a screenshot.

I've only been experiencing these issues since a couple of minutes but according to Tech News this is a new display style for mobile devices. --Donald Trung 『徵國單』 (No Fake News 💬) (WikiProject Numismatics 💴) (Articles 📚) 09:14, 22 June 2022 (UTC)

Having similar problem with iPad and iPhone. Commons pages are shrunk, type is super-small in desktop mode. Page looks okay on laptop. Thought it was a problem with page size in Google Chrome but there is no setting for page size on mobile device or tablets. Raquel Baranow (talk) 22:20, 22 June 2022 (UTC)
@Jon (WMF): , I have had a similar problem with extremely small font size and vast areas of blank space between text. Is that "scaling?" Whatever the term, it makes Wikimedia.commons virtually unusable. I cannot read the text without zooming in on every single page.
I tried the "accessibility" feature on my device and the text is heavily pixilated as well as terrible to navigate with a "zoom window" showing only part of the text, which has to be moved constantly in order to read. This issue makes it more difficult for Users with visual impairment or visual disability. Can this be fixed soon?
Thank you -- Ooligan (talk) 02:54, 23 June 2022 (UTC)
I reported it on Phabricator, with a link to this discussion. https://phabricator.wikimedia.org/T311195 Raquel Baranow (talk) 04:21, 23 June 2022 (UTC)
@Raquel Baranow: Thank you for helping to fix this issue. -- Ooligan (talk) 04:36, 23 June 2022 (UTC)

  • File page showing better scaling of copyright licenses, but worse scaling of everything else.

  • Categories have become unusable.

  • No more "quick glances" for files either. You actively have to zoom in to see what a file looks like.

  • Sub-categories are even worse. Note that HotCat is also largely un-useable on "Desktop mode".

Well, a picture says a thousand (1000) words, so here is how I experience these new changes. Overal a lot is improved regarding some templates, but also the way texts are scaled is bad now. --Donald Trung 『徵國單』 (No Fake News 💬) (WikiProject Numismatics 💴) (Articles 📚) 09:31, 22 June 2022 (UTC)

  •   Comment Yes, pages have 'zoomed out' to such an extent they are unreadable. I’m using desktop mode with Vector legacy skin in Safari on Ipad 5th gen (P.S. the same issue arises on Wikidata). --Malcolmxl5 (talk) 12:36, 23 June 2022 (UTC)

They closed my bug report as a duplicate of this one, I changed tracking number above. If your change your Preference>Appearance to Monobook, it’s better but formatting is still a little bit screwed up on some pages. https://phabricator.wikimedia.org/T311119 Raquel Baranow (talk) 13:35, 23 June 2022 (UTC)

We are aware of the issue and will be fixing that this morning as soon as possible. I'll report back here when that's done to check in. Thank you for your patience. Jdlrobson (talk) 13:41, 23 June 2022 (UTC)
Hi we just synced a change that should improve this situation. Note you may need to apply ?action=purge to the URL if you are viewing anonymously.
Please let me know if you are continuing to still see problems. If you are be sure to let me know your browser, the page URL and the device you are using. Jdlrobson (talk) 14:13, 23 June 2022 (UTC)
Vector skin (default) works like before, thanks! Raquel Baranow (talk) 17:51, 23 June 2022 (UTC)
Vector legacy (2010) looks like before. Thanks for fixing this issue. -- Ooligan (talk) 19:37, 23 June 2022 (UTC)
Thank you both for taking the time to confirm the fix. I appreciate it! Jdlrobson (talk) 20:34, 23 June 2022 (UTC)

Template:Derived from unexpectedly displays a link to MTR stationsEdit

See Template:Derived from, and an invocation of the template here: File:Penrhyn Bay.jpg. Delta 51 (talk) 12:11, 25 June 2022 (UTC)

  Fixed here Delta 51 (talk) 14:27, 25 June 2022 (UTC)

Wrong video dimensionsEdit

File:Boeing OFT-2 Landing - 05 - Hatch opening.webm is only 49s long but "dimensions" says it's 33 h 49 min 52 s. RZuo (talk) 15:16, 25 June 2022 (UTC)

File a bug at phab: with "TimedMediaHandler" as the tag.--Snævar (talk) 11:45, 26 June 2022 (UTC)
No, it’s not a software bug. I opened the video in Firefox, and analyzed it with exiftool; both say it’s 33:49:52 long. Something’s fishy with the video, but that won’t be resolved by a bug report on Phabricator. I don’t know what it means, but it may help: james-heinrich/getid3 (which TimedMediaHandler uses under the hood) emits three warnings: 
Unhandled seekhead element [module.audio-video.matroska.php:627] (5036::SeekPosition [1 bytes]) at 71
Unhandled seekhead element [module.audio-video.matroska.php:627] (5036::SeekPosition [2 bytes]) at 85
Unhandled seekhead element [module.audio-video.matroska.php:627] (5036::SeekPosition [2 bytes]) at 100
Unhandled seekhead element [module.audio-video.matroska.php:627] (5036::SeekPosition [3 bytes]) at 115
—Tacsipacsi (talk) 15:20, 26 June 2022 (UTC)

Enable VideoCutTool gadget by default on video pages of CommonsEdit

VideoCutTool is a video editing tool that helps to edit videos on Wikimedia Commons, users can also upload new videos to the tool, edit and upload the same to Commons on the fly! The tool is currently deployed on Wikimedia's Cloud VPS and in live as a gadget! Cropping, Trimming, Audio Disabling, and Rotating are the current features of the tool. VideoCutTool works similarly to the Commons:CropTool. Also as of today total of 711 users enabled VideoCutTool as a gadget, Source: https://commons.wikimedia.org/wiki/Special:GadgetUsage, So it would be nicer if we make the VideoCutTol enable as a default gadget for videos on Wikimedia Commons.

Tool: https://videocuttool.wmcloud.org/ Commons: https://commons.wikimedia.org/wiki/Commons:VideoCutTool Link to script of Gadget: https://commons.wikimedia.org/wiki/MediaWiki:Gadget-VideoCutTool.js Gopavasanth (talk) 10:58, 26 June 2022 (UTC)

@Gopavasanth: "Default" means every single one of us 11,137,143 users, in which 38,473 are active, will have to load it on every page load. I, for example, never know that this exist, nor have I ever work with videos; my sidebar has already been filled with other stuffs and I'd like not to have another one which I cannot take advantage of. On the other hand, if I ever need it, I can simply go to videocuttool.wmcloud.org by typing it directly into the address bar. That being said, I see no reason to enable the gadget by default, but thanks for your tool anyway. NguoiDungKhongDinhDanh 14:04, 26 June 2022 (UTC)
Hi @NguoiDungKhongDinhDanh, Thanks for your thoughts, Oops! my bad if its conveyed incorrectly. I was proposing this tool to enable by default for all the users on commons only on the video pages. Similar to CropTool as its enabled by default on all the Image pages of Commons. So users who are not aware of the tool can easily find the tool and edit videos on the fly using VideoCutTool. Gopavasanth (talk) 14:26, 26 June 2022 (UTC)
@Gopavasanth: CropTool is not a default gadget. As far as I know, there is no way to set such a condition outside the gadget itself, which means we will still have to load it anyway. Feel free to advertise it at appropriate venues though. NguoiDungKhongDinhDanh 14:30, 26 June 2022 (UTC)
@NguoiDungKhongDinhDanh Current gadget - VideoCutTool works in the same way, if its enabled on the user account VideoCutTool appears on the side panel of the commons on video pages alone. Gopavasanth (talk) 17:07, 26 June 2022 (UTC)
@Gopavasanth: Not everyone of our 11 million users, that is, including me and you, works with videos, and not everyone who works with videos needs this tool to the extend that a portlet link is necessary. I'm grateful that you code the tool – definitely useful, thank you – but enabling this gadget by default is simply excessive. NguoiDungKhongDinhDanh 17:16, 26 June 2022 (UTC)
@NguoiDungKhongDinhDanh, Thanks for sharing your point of view, As you told not all of our 11 million users uses all of the options that are currently there on commons, So I/other users will generally get to know about some tool existence only if they look at tool or read about it somewhere as you got to know about the tool now. So as in this case VideoCutTool gadget only appears on Commons sidebar if the users are on the video pages, Also the users who visits the video pages may be dealing with the videos (high chances) and this tool might help them in some ways. so I strongly support my nomination in making the VideoCutTool a default gadget. Gopavasanth (talk) 16:44, 27 June 2022 (UTC)

Text extends beyond the surrounding rectangleEdit

Recently I uploaded six different SVG files using Upload Wizard - Wikimedia Commons:
MAP of PARO 11 (Phitsanulok) EN.svg to MAP of PARO 15 (Chiang Rai) EN.svg
The original SVG files have text such as "Protected Areas Regional Office XX (city name)" in the center of surrounding rectangles.
These maps printed with a regular color printer also indicate these text exactly in the middle of the rectangles.
But the text of uploaded SVG files extends beyond the surrounding rectangle. SietsL (talk) 08:53, 27 June 2022 (UTC)

Tech News: 2022-26Edit

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

Recent changes

Changes later this week

  •   The new version of MediaWiki will be on test wikis and MediaWiki.org from 28 June. It will be on non-Wikipedia wikis and some Wikipedias from 29 June. It will be on all wikis from 30 June (calendar).
  •   Some wikis will be in read-only for a few minutes because of a switch of their main database. It will be performed on 28 June at 06:00 UTC (targeted wikis). [3]
  • Some global and cross-wiki services will be in read-only for a few minutes because of a switch of their main database. It will be performed on 30 June at 06:00 UTC. This will impact ContentTranslation, Echo, StructuredDiscussions, Growth experiments and a few more services. [4]
  • Users will be able to sort columns within sortable tables in the mobile skin. [5]

Future meetings

  • The next open meeting with the Web team about Vector (2022) will take place tomorrow (28 June). The following meetings will take place on 12 July and 26 July.

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

20:00, 27 June 2022 (UTC)

"Load More" at top?Edit

Tracked in Phabricator
Task T310984

When did the "load more" button get moved to the top of the screen for image search? It's now quite inconvenient when I'm scanning through images from a search with hundreds or thousands of results. I have to repeatedly scroll back to the top to load more. Can the old functionality be restored? RobertAldenRubin (talk) 02:09, 28 June 2022 (UTC)

@RobertAldenRubin: I don't know why, but I do know a way to fix. Add this to your personal .css page:
body.page-Special_MediaSearch .sdms-search-results__list-wrapper {
	display: flex;
	flex-direction: column;
}
body.page-Special_MediaSearch .sdms-search-results__list-wrapper .sdms-load-more,
body.page-Special_MediaSearch .sdms-search-results__list-wrapper .sdms-spinner {
	order: 2;
}
Note that this may not work on very old browsers: Internet Explorer 6-10, Firefox 2-19, Chrome 4-28, Safari 3.1-8 and Opera 12. NguoiDungKhongDinhDanh 09:50, 28 June 2022 (UTC)
It was not intentional and has already been fixed in software; the fix will likely be deployed tomorrow. —Tacsipacsi (talk) 15:40, 28 June 2022 (UTC)

Categories in wiki appEdit

Hello I 99% use the wikicommons app. The past few weeks I have not been able to add categories either during upload or after on the photo page in the app.

I am surprised it has not been reported given the popularity of the app. When you arrive at the 'add category' page, the icon/curser just spins round and round. It is like it cannot access the database.

I also uploaded a file outside the app for "wiki love wales" and the category worked fine.

Anyway, hope this helps

Peter Glyn (talk)

See https://github.com/commons-app/apps-android-commons/issues/5002 . All reported bugs on the commons app are in the bugtracker in the link.--Snævar (talk) 23:38, 2 July 2022 (UTC)

File "lost" after a renaming and edit conflictEdit

I uploaded a file yesterday under the (wrong) filename File:Portrait de femme artiste-crop - Copie.jpg so I put a rename request for File:Portrait of a female artist painting a flower.jpg. Then I edited the file for some minutes (bad idea - now I know it) until I got an edit conflict when a file mover quickly complied with my request... and the image (*.JPG) "disappeared" from the file description page (File:*) (cf "No file by this name exists..."). I tried to upload again the image (from the page File:Portrait of a female artist...) and as a new file, but both times I got the warning "The upload is an exact duplicate of the current version of File:Portrait of a female artist painting a flower.jpg." So the image (*.JPG) is still "somewhere" on Commons, but without "link" to the file description page (File:*). Can someone retrieve it ?

Plan B : I could upload a slightly different version as a new file, but the older one (and the associated file description page) should then be deleted. BeatrixBelibaste (talk) 10:04, 29 June 2022 (UTC)

And now the file is back... BeatrixBelibaste (talk) 10:40, 29 June 2022 (UTC)

New file type for 3D filesEdit

Hey dear Wikimedians,

I wanna ask if there are plans to integrate new file types for 3D files next to STL. Afaik STL files cannot store information about the mesh surface like textures, transparency or shader information. For some objects, this isn't a problem, but for works with windows or jello for example, it would be very helpful :).

Thanks and greetings, PantheraLeo1359531 😺 (talk) 15:22, 2 July 2022 (UTC)

Not really. There is not an maintainer currently for the thumbnails, so a new file format will not be added in that situation. There is only an working group which sole purpose is to update the system, which is allready years out of date. Maybe sometime next year. Snævar (talk) 10:00, 7 July 2022 (UTC)
Okay thanks :) --PantheraLeo1359531 😺 (talk) 13:12, 9 July 2022 (UTC)f

Tech News: 2022-27Edit

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

Changes later this week

  •   The new version of MediaWiki will be on test wikis and MediaWiki.org from 5 July. It will be on non-Wikipedia wikis and some Wikipedias from 6 July. It will be on all wikis from 7 July (calendar).
  •   Some wikis will be in read-only for a few minutes because of a switch of their main database. It will be performed on 5 July at 07:00 UTC (targeted wikis) and on 7 July at 7:00 UTC (targeted wikis).
  • The Beta Feature for DiscussionTools will be updated throughout July. Discussions will look different. You can see some of the proposed changes.
  •   This change only affects pages in the main namespace in Wikisource. The Javascript config variable proofreadpage_source_href will be removed from mw.config and be replaced with the variable prpSourceIndexPage. [6]

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

19:30, 4 July 2022 (UTC)

What are the requests mean on the Media views Analysis page?Edit

Hello, I wanted to ask a question about the Media views Analysis page. I was curious what do the Requests mean? On the side and at the bottom it says Requests I can't figure out what that means and the 2 different numbers either Requests and Daily Numbers why are they so different as in one is higher than the other. I look at my page and am curious what that means as far as my page on Wikimedia commons. Hope this is clear thanks. Flapper the turtle (talk) 12:32, 6 July 2022 (UTC)

Any nice toolsEdit

Hi, I usually use Twinkle Global to CSD any file but sadly I don't think it is completely compatible with Commons. It does not help us to warn/notify the users. Do we have any nice tools here that I could use for this? Manual warnings are a headache. PermissionVRTS works nicely but we need something outside that realm. ─ The Aafī (talk) 09:18, 7 July 2022 (UTC)

@TheAafi: This one? NguoiDungKhongDinhDanh 20:57, 14 July 2022 (UTC)

BotMultichillT Bots not respecting Bots-denyEdit

At Special:Diff/672127507 BotMultichillT seemed to not respect a {{Bots}}/deny request. When questioned bot owner Multichill seemed uninterested and wished to place the Special:Diff/672194033 blame back on me. (Although not mentioned specifically I have some concern that back from the diff's that BotMultichillT, and perhaps others, are not respecting the precision of co-ordinates I am indicating when loading information to Wikidata and additionally that BotMultichillT may on occasion be truncating precision by removing trailing zeros from specified co-ordinates. I am not currently fully up to speed on all the various co-ordinate systems and usages currently in use which have some complexity so I don't which to get involved in a massively detailed exploration of that at this time due to RL commitments). I would however expect a Bot to respect a Bots/deny request and am very concerned if this is not happening. Thankyou. Djm-leighpark (talk) 18:17, 7 July 2022 (UTC)

This is ridiculous. I do not see any syntax problems. The bot shouldn't have edited the file page given the deny request. @Multichill Could you please explain why did this happen? I don't see this being anywhere explained at COM:OWN. ─ The Aafī (talk) 05:13, 8 July 2022 (UTC)
Technically not per template:bots. If you read the template documentation Bots are not bound to observe the nobots tag, it will depend on their functionality, their owners and their terms of approval. The bots which currently support exclusion are listed at exclusion compliant bots. However, it is good practice to follow the tag. -- Zache (talk) 05:51, 8 July 2022 (UTC)
Disappointed the bots template was not respected, but I suppose it doesn't have to be. I think I likely have some valid concerns in the precision area, and requesting a bot deny is perhaps reasonable, and I understand I think there is a general caution in place about the harvesting of structured information in case it upsets good faith ordinary users, but I doubt anyone would accept I fall into that set. Pragmatically I've chosen to proceed in the short term by deferring adding co-ordinate information which avoids the problem and COM:OWN issues. I thought adding the prec parameter to {{Location}} would be helpful but see it is not particularly respected so I need to start doing haversine stuff while talking a ten-thousandth of an arc-second walk (<3.1mm?) to understand things a little better first before getting the wet trout and a RPN calculator on an auction site - my last one was wiped out with me at 50°44'34.4"N 1°58'34.1"W. Thankyou. Djm-leighpark (talk) 00:35, 9 July 2022 (UTC)
You are trying to solve different things. I can't talk for Multichill or his bots, but I can say something about how I am handling the data by myself. The target is to get harvesting the data from templates/categories etc which information heavily varies to some standardized format. In that scope, importing the coordinates in the first place at some predictable and useful level is the primary target. The second, after that, is to find obvious errors in the data from random photos. In that sense, truncating trailing zeroes is a trivial problem as the quality differentiation of the input data is much bigger. This includes in example prec=10 values too which would mean that coordinate accuracy would be sub-millimeter level which is impossible even when there are so many decimals. The rounding errors and lack of input device accuracy gives us much bigger variation to the results. So, the problem is how to handle that kind of data? Most common way is to either store the number as it is and truncate when the number is shown (as 10 decimals are hard to read) OR truncate the number alltogether. (In example if you use float datatype for storing coordinates it supports only 6 decimals, ~10cm accuracy) which truncates numbers but it is still much higher than realistic input accuracy by user. -- Zache (talk) 04:13, 10 July 2022 (UTC)
@Zache: I'm a little worried that you might have a mistaken understanding of the prec parameter to the {{Location}} template. It doesn't specify a number of decimal places, but a number of metres. So prec=10 means a location with 10-metre precision. I apologise if you were aware of this and were referring to a different prec. --bjh21 (talk) 11:41, 10 July 2022 (UTC)

I think I have managed to locate the instance where trailing zeros were truncated and it looks like on review they were omitted on page creation rather than subsequently by a bot. So either I entered -0.9900 (degress) to the upload wizard which rendered it as -0.99, or perhaps I simply entered -0.99 in the first place. It's likely the bots are using the number of decimal places (of degrees) to estimate the precision stored to Wikidata. This appears on the diff, with units not specified but arcdegrees implied. The structured data tab does not seem to give the precision in view mode but will give a drop for in in edit mode, with 1/1000 of an arcsecond as the first in the dropdown list, decimal places of degrees visible further down. A lot of the time things are conveniently translated to from decimal (arcdegree) to arcdegree/arcmin/arcsec format which adds a little confusion. I think I am beginning to get an understanding but very easy to get something wrong. I might pose a specific question later, but short term I'll likely generally continue to defer adding co-ordinates as bots-deny won't be respected. Although I might have a test case which can perhaps shed more light. Thankyou. Djm-leighpark (talk) 23:18, 10 July 2022 (UTC)

I'd like to confirm one image I loaded this morning that 50.869, -0.99, 240 entered into the position/location boxes to the upload wizard programmed as parameters 50.869,-0.99 & heading:240 to {{Location}}. The {{Object location}} call was created at the same time by entering in directly to the "other location" box. I am minded the should not be truncating the trailing zero's if stuff is using the number of decimal places as a precision indicator for loading structured information. Its not easy to see this as the rederend page uses DMS (Degre, Minute, Second) coordinates and the actually location on a map is not affected. I guess to decide it is us to bots whether they will take precision off the longitude or latitude in this case, I don't own it the image and its entry, but I might shepherd it for a while (my humor would be to say against the bot wolves simply because it sounds good and the bots actually are useful sheepdogs when you know them well and their capabilities and foibles and when to keep them at home with a dog deny — its stop at that point. Djm-leighpark (talk) 08:31, 11 July 2022 (UTC)
Having isolated the truncating of the trailing zeros I've raised it as its own topic at Commons:Upload Wizard feedback:Location precision information loss by Upload Wizard. I am somewhat of the view that I have multiple concerns with the handling of co-ordinate uncertainty and am reasonably certain there is likely no clear consistent agreed integrate solution between commons, templates, bots, rendering UI's, wikidata, DMS, etc. Per the approach ... if the information you uploaded is in the EXIF file then its entitled to be displayed I guess the solution if not happy with the uncertainty precision handling is not to load it. (I'd not while this has never been said to me but commons seem to love to advertise that I have an E7i dog(en-CRS)/mobile-phone(en-British & en-Hiberno)/cellphone(en-American&international) ... even to the extent that I have just purchased a new dog at least partially due to commons/bot mining of my Exif files .... but the missus has determined to purloin that dog so I'm sort of stuffed!). Anyway there's probably not a lot for me to add here for the moment. Thankyou for your help. Djm-leighpark (talk) 11:03, 14 July 2022 (UTC)

Wrong coordinates hotbed - circular area around the Null IslandEdit

for example File:Grebenhain Herchenhain Bonifatiuskanzel s.png. maybe it's a good idea to have a bot, which identifies files marked in a circular area around Category:Null Island. RZuo (talk) 07:44, 9 July 2022 (UTC)

I think the root cause of this is uhere the {{Location dec}}s call at Special:Diff/113410489 was incorrect and (0.48671802,.28259349) specified where (50.48671802|9.28259349) intended. It might be possible to do a bot to identified where the relationship between the (camera) location and object location are unreasonably different. Thankyou. Djm-leighpark (talk) 23:27, 10 July 2022 (UTC)

Table errorEdit

Hey folks, I am working on a larger table, but unfortunately the error

Warning: User:PantheraLeo1359531/Hofer Geschichtswege (edit) is calling Template:Table with more than one value for the "row10" parameter. Only the last value provided will be used.

appears. How can it be fixed? (Page: User:PantheraLeo1359531/Hofer Geschichtswege)

Thank you and greetings, --PantheraLeo1359531 😺 (talk) 13:22, 9 July 2022 (UTC)

@PantheraLeo1359531: You currently have two parameters called row10, one filled in ("Ein Mauerrest ist alles") and one not ("???"). Similarly, there are two parameters called row11, row12, row13, row14, and row15. I think you can only have one row with each number. --bjh21 (talk) 12:56, 10 July 2022 (UTC)
Okay thank you, I will figure this out :) --PantheraLeo1359531 😺 (talk) 13:50, 10 July 2022 (UTC)
I found it, thank you :D --PantheraLeo1359531 😺 (talk) 13:59, 10 July 2022 (UTC)

Tech News: 2022-28Edit

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

Recent changes

Changes later this week

  • There is no new MediaWiki version this week.
  •   Some wikis will be in read-only for a few minutes because of a switch of their main database. It will be performed on 12 July at 07:00 UTC (targeted wikis).

Future changes

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

19:22, 11 July 2022 (UTC)

FileImporter failed to import actual fileEdit

I was trying to use FileImport to import en:File:Ooblets.png to Commons, but got an error saying some data could not be committed. It did import the file description and its history, but the actual file was not imported. You can see that File:Ooblets.png only contains a description. Is this a known issue? Ixfd64 (talk) 17:47, 12 July 2022 (UTC)

Upload error for larger files (approx. >=100 MiB)Edit

 

Hey dear community,

unfortunately a new error occurs while uploading when the uploading files that are a bit larger. Those errors are "The server didn't respond within the expected time" or as in the screenshot. How could the problem be solved? :)

Thank you and greetings, --PantheraLeo1359531 😺 (talk) 15:03, 13 July 2022 (UTC)

Answered at Commons:Village pump#Problems with uploading files above 100 MiB.--Snævar (talk) 12:32, 15 July 2022 (UTC)

Wikidata Infobox underwent a major rewriteEdit

Since {{Wikidata Infobox}} is notorious for making category pages slow to load, Mike Peel and me are rewriting it in Lua. Please try out the new infobox using {{Wikidata Infobox/sandbox}} – You can find a changelog and submit feedback on the template talk page. --LennardHofmann (talk) 17:52, 14 July 2022 (UTC)

Is anyone else seeing a sudden increase in error reports at the MediaWiki Upload Wizard?Edit

I suddenly get a lot more error messages at the MediaWiki Upload Wizard, it's not just one error message, I get several different ones and only from today in the afternoon onwards. At first I thought that it was because of my new Mobile Data subscription and that uploading only works on Wi-Fi, but then I realised that I didn't have this before (and I've had a mobile data subscription for almost a week now), on Wi-Fi I still have lots of errors, it happens during uploads and during submissions. Sometimes it just says "Error", other times it claims that images aren't found in the stash, and I've seen a number of other (vague) errors. It happens to small files and normal size files. -- Donald Trung 『徵國單』 (No Fake News 💬) (WikiProject Numismatics 💴) (Articles 📚) 21:00, 14 July 2022 (UTC)

It seems you're not alone, as I assume the German discussion at Commons:Forum#Dauernd_Fehlermeldungen is about the same issues. Gestumblindi (talk) 21:23, 14 July 2022 (UTC)
Gestumblindi, Yes, exactly. They even listed the error messages I keep coming across. -- Donald Trung 『徵國單』 (No Fake News 💬) (WikiProject Numismatics 💴) (Articles 📚) 21:26, 14 July 2022 (UTC)
This is the same as #Upload error for larger files (approx. >=100 MiB) above.--Snævar (talk) 12:32, 15 July 2022 (UTC)

Tech News: 2022-29Edit

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

Problems

  • The feature on mobile web for Nearby Pages was missing last week. It will be fixed this week. [9]

Changes later this week

  •   The new version of MediaWiki will be on test wikis and MediaWiki.org from 19 July. It will be on non-Wikipedia wikis and some Wikipedias from 20 July. It will be on all wikis from 21 July (calendar).

Future changes

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

22:58, 18 July 2022 (UTC)

Question about Template:WEdit

Hello!

Why is a colon written with italics in {{W}}? See for example File:Wiki.png. It seems weird with the colon in italics. Jonteemil (talk) 09:56, 19 July 2022 (UTC)

I can see that it was added at the request of Sarang in 2016, though it's not obvious why. Maybe he can remember why? --bjh21 (talk) 13:01, 19 July 2022 (UTC)
AFAIK the edit of 2016-11-25 does not only result on a request by me.​​
Nevertheless, it makes an optical difference whether you link a file with {{W}} as above File:Wiki.png, or with {{F}} File:Wiki.png
(the link target is in both cases identical). IMHO {{W}} is more thought for articles, other namespaces as {{C}}, {{F}}, {{M}}, {{T}}, {{U}} have their own link templates.
But I see also no use or advantage to write the colon in bold & italic. -- sarang♥사랑 13:42, 19 July 2022 (UTC)
@Sarang: Sorry; I linked to the wrong edit. It should have been the next one, Special:Diff/219240806. You added the ''''' to the sandbox in Special:Diff/218747469. --bjh21 (talk) 14:45, 19 July 2022 (UTC)
@Bjh21: I can see now, yes, it is my guilt; but I cannot remind why I thought in 2016 that italic looks better 👀.
As I wrote above, {{W}} can be used and it is correct for all namespaces, but may not be the best choice for foreign files.
The template is protected also against template editors, so when a consensus for a change can be found it is not my turn. -- sarang♥사랑 15:01, 19 July 2022 (UTC)

Migrating licensesEdit

Hello, do you know where I could ask for someone to mass migrate the license of 5,000 files ? Luilui6666 uploaded her files under CCBYSA. Following a request by HK's computer linguists, she publicly announced her will to share her audio files under dual CCBYSA / CC0. But who could migrate all those files to dual license ? @VIGNERON and Kanashimi: Yug (talk) 11:32, 20 July 2022 (UTC)

Retrieved from "https://commons.wikimedia.org/w/index.php?title=Commons:Village_pump/Technical&oldid=676587923"