Commons:Village pump/Technical

From Wikimedia Commons, the free media repository
Jump to navigation Jump to search

Shortcuts: COM:VP/T • COM:VPT

Welcome to the Village pump technical section
Technical discussion
Village pump/Technical
 Bug reports
 Code review
Tools
 Tools/Directory
 Idea Lab



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

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

Request to add Tai Ahom Unicode to Commons[edit]

Moved to MediaWiki_talk:Titleblacklist#Whitelist Tai Ahom alphabet

F2C[edit]

It seems that Flickr2Commons has been shut down as I can't upload even a single file. When I try to enter Flickr file ID to the upload tool it only turns to blue but doesn't upload a file! Юрий Д.К 09:57, 11 July 2023 (UTC)Reply[reply]

i confirm the problem. it's stuck at the blue phase.
the tool was last working at 13:45, 10 July 2023. RZuo (talk) 13:13, 11 July 2023 (UTC)Reply[reply]
use Special:UploadWizard instead. RZuo (talk) 13:14, 11 July 2023 (UTC)Reply[reply]
Already notified @Magnus Manske: as the creator of F2C. --A1Cafel (talk) 15:11, 12 July 2023 (UTC)Reply[reply]
@Magnus Manske: @RZuo: @A1Cafel: Working now, thanks Юрий Д.К 20:12, 12 July 2023 (UTC)Reply[reply]

Hi, please help with the problem presented in PHAB:T341636.
Apparently, it affects all editors whose languages are RTL.
מקףHyphen 14:44, 12 July 2023 (UTC)Reply[reply]

Motd/2023-07[edit]

Could someone fix the width issue in {{Motd/2023-07}}? Thanks, — Racconish💬 12:56, 15 July 2023 (UTC)Reply[reply]

Search / Skip PDFs / Filemime[edit]

While doing searches on Commons, I noticed a 'recent' addition in the form of a link labelled "Skip PDFs", which is slightly easier than adding -pdf to my search string. It has unintended consequences, and I can't find a way to report a bug to the relevant originator. For example, if I enter "deer valley" (with double quotes) in the search box, I get all variations of that. If I then click on the Skip PDFs link, in the search string I then get each double quote mark replaced by ampersand hash 34 semicolon which doesn't produce the intended result. PeterWD (talk) 08:57, 15 July 2023 (UTC)Reply[reply]

Indeed. You might get more help to fix this problem at Commons:Village pump/Technical. -- Asclepias (talk) 15:47, 15 July 2023 (UTC)Reply[reply]
Thanks, but how do I move a discussion without losing formatting, signatures, etc.PeterWD (talk) 08:16, 16 July 2023 (UTC)Reply[reply]
You copy-paste the whole think as wikitext and add a note (usually using <small> for the note, and signing it) to indicate you have done so. - Jmabel ! talk 15:00, 16 July 2023 (UTC)Reply[reply]
Thanks, now moved from Commons:Help desk. PeterWD (talk) 15:28, 16 July 2023 (UTC)Reply[reply]
yall need to help pressure some interface sysop to take action for MediaWiki_talk:Searchmenu-new#Skip_pdfs. RZuo (talk) 16:47, 16 July 2023 (UTC)Reply[reply]

GalleryDetails doesn't work[edit]

MediaWiki talk:Gadget-GalleryDetails.jsמקףHyphen 13:57, 17 July 2023 (UTC)Reply[reply]

Yes, sadly. For a few days now. -- Tuválkin 15:24, 17 July 2023 (UTC)Reply[reply]
Is it known what causes this? ‎מקףHyphen 15:56, 17 July 2023 (UTC)Reply[reply]

Tech News: 2023-29[edit]

MediaWiki message delivery 23:06, 17 July 2023 (UTC)Reply[reply]

Commons:File types needs update[edit]

Commons:File types says mpeg is a "Nonfree file format", but some uploads are in this format? e.g. File:4U 1820-30.mpeg, File:Pantun berlirik a-a-a-a.mpg. i have no knowledge about this issue so i dont know how to rewrite the help page. RZuo (talk) 12:13, 18 July 2023 (UTC)Reply[reply]

MPEG uploads have been enabled three years ago, after last MPEG patents expired in February 2018. So Commons:File types used to be correct, but isn’t anymore. —Tacsipacsi (talk) 00:58, 19 July 2023 (UTC)Reply[reply]
I've updated it in English, German, French, and Spanish. The Squirrel Conspiracy (talk) 03:10, 19 July 2023 (UTC)Reply[reply]

Thumbnail displays in special search results shown as squares again ?[edit]

Hello the thumbnails in special search results are back to squares for me. I thought we had agreed that this is hindering the oversight and that this new layout was rolled back or disabled generally for commons. lengthy discussion here the big code block with css hack shown there was added to my common.css but stopped working for me since ca. 14 days. What's up with this? In a way the square previews look smooth as a page ... but it hinders mass-reviewing subtle things like sloppy crops around the edges as the discussion shows in examples. And why 'castrate the integrity of each and every image' and discard the basic notion of landscape vs portrait format? So again : how to opt out, please. Thanks. Peli (talk) 19:15, 20 July 2023 (UTC)Reply[reply]

I confirm this is happening, to me too, even with the hack added to User:Tuvalkin/common.css. (The one to suppress thumbnails for cats is working, though. -- Tuválkin 01:02, 22 July 2023 (UTC)Reply[reply]
Like just about anything that broke on Commons two weeks ago: phab:T314318, specifically mw:Parsoid/Parser Unification/Media structure/FAQ#The "image" class is no longer present on file description links. Replacing .image with .mw-file-description should help. —Tacsipacsi (talk) 22:49, 22 July 2023 (UTC)Reply[reply]
Perfect, it works! -- Tuválkin 04:56, 23 July 2023 (UTC)Reply[reply]
Yes, confirmed. This hack works. Maybe it should be the default thumbnail layout for everyone on commons or at least be added as an option in user preferences. Thanks Peli (talk) 08:52, 28 July 2023 (UTC)Reply[reply]
Moving it to an (opt-in) gadget should be feasible, both technically and organizationally (I fear WMF would object to changing the default), good idea! Unfortunately I can’t do it myself. Hopefully an interface administrator will notice this; if not, you could ping one of them. —Tacsipacsi (talk) 16:13, 28 July 2023 (UTC)Reply[reply]
Maybe @Raymond: can help getting this proposal to be installed as an opt-in preference for logged-in users by the tech-team. Eventhough I would not know why other users would only need to see 1/4 of the thumbs in their special-search results. Peli (talk) 16:50, 8 August 2023 (UTC)Reply[reply]
@Pelikana Technically I could do. But I am not sure about the process to enable new gadgets. I would propose to ask on Commons:Administrators' noticeboard Raymond (talk) 17:47, 8 August 2023 (UTC)Reply[reply]
Ok thank you for the response. Maybe I will wait until the yearly tech wishlist is open again. It's not clear to me why these square thumbs are preferred by the layout team, and set as a default, over just showing complete thumbs. Peli (talk) 18:05, 8 August 2023 (UTC)Reply[reply]

Annoying confirmation step[edit]

When I'm on a Commons file description page, and click on a link, I often (but not always) get a popup as follows:

commons.wikimedia.org

This page is asking you to confirm that you want to leave — information you’ve entered may not be saved.
Leave page Stay on page

I could understand this happening if I was editing the page at the time, but it can happen even when I click the first link on Commons having just arrived from Wikipedia, before I click an edit link. It happens most often when I click the "Original file" link to view the full-size image, but also happens for e.g. links to other files, or category links. It even happens when I click the "Edit" tab. It only happens on Commons but not on other WMF wikis.

Is this a commons feature, or a browser feature? I use Firefox, presently version 115. Is there any way of circumventing it so thT I don't have to keep on clicking that "Leave page" button? --Redrose64 (talk; at English Wikipedia) 13:13, 22 July 2023 (UTC)Reply[reply]

This topic was brought up in the discussions earlier with no real outcome for a solution as far as i can remember. Someone checked ... and found ... was still open. Nowadays I (go back &) stay a moment longer on the page and than leave it without the popup, in the hope this fixes this issue for that page for others too. Peli (talk) 19:06, 22 July 2023 (UTC)Reply[reply]
I found a persistant one here. Shows the alert upon leaving page Peli (talk) 23:27, 25 July 2023 (UTC)Reply[reply]
I have the same problem in Firedox 102.13.0 on Mac when I select a piece of text and then want to leave the page. No problem with Safari 16.5.2. Wouter (talk) 20:33, 28 July 2023 (UTC)Reply[reply]

Motion Picture Copyright Descriptions Collection, 1912-1977[edit]

  • search: site:tile.loc.gov/storage-services/service/mbrs/cdmmi/ filetype:pdf
  • I do not know to find the meta data URLs
  • Many Public domain scripts, press sheets, other
  • can acquisition be automated?
  • .... 0mtwb9gd5wx (talk) 16:26, 22 July 2023 (UTC)Reply[reply]

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

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

Anyone? Jonteemil (talk) 14:48, 28 July 2023 (UTC)Reply[reply]
@Glrx: Can you confirm or disconfirm this? Jonteemil (talk) 19:11, 2 August 2023 (UTC)Reply[reply]
@Jonteemil and Rillke:
I've been using User:Rillke/SVGedit.js for a time, but I have not paid much attention to the RSVG rendering. I usually do not hit the preview button. When I do, I'm happy to see a local SVG rendering. RSVG departs from the SVG specification in a few places.
The RSVG preview has not worked in a long time. For example, using SVGedit on File:IPv6 header-en.svg (which specifies a width and height) does not produce an RSVG preview.
If I look at the SVGedit code, line 396 does a fetchPreview(val). I presume that obtains the RSVG rendering. That method probably fails, so line 413 substitutes a PNG rendering of File:Bug blank.svg. (An alternative explanation is the preview method succeeds but line 399 image/jpeg is incorrect and causes a failure. I expect RSVG to return an image/png rather than an image/jpeg. Data URL claims JPEG but is PNG. Another possibility is the line 411 timeout is too short.)
Looking further, fetchPreview sends its request to //convert.toolforge.org/svg2png.php. If I go to that website and issue a request for a large (2199×1477) SVG file, I get a 500 Internal Server Error. If I give it a small file, my computer receives a appropriate PNG. I will guess the endpoint functions for at least some files.
That leads me back to guessing something goes wrong inside of line 397 .done.
Glrx (talk) 20:51, 2 August 2023 (UTC)Reply[reply]
@Glrx: Okay, I don't probably use the tool as often as you do but I do it from time to time and I always preview so I don't happen to save anything erroneous. This problem is something that I haven't experienced before so it must be some new change to the code, or the code of another program that the SVGedit tool uses. Do you know of anyone who'd be willing to take a look at fixing this? Jonteemil (talk) 04:46, 3 August 2023 (UTC)Reply[reply]
@Jonteemil and Cmglee:
You load SVGedit from Meta:User:Jonteemil/global.js, but you use Cmglee's version at User:Cmglee/SVGedit.js. That's fortunate because Cmglee is still active; Rillke has not edited in some time. You can ask Cmglee to try changing line 401 to use image/png to see if that fixes preview.
Glrx (talk) 05:32, 3 August 2023 (UTC)Reply[reply]
Thanks for your clear instructions and analysis, @Glrx: I've changed "jpeg" to "png" but the problem persists. I think rsvg previews are broken as with commons:commons_SVG_Checker. Would you be able to debug why commons:commons_SVG_Checker also gives the bug image? Thanks, cmɢʟee ⋅τaʟκ 15:34, 3 August 2023 (UTC)Reply[reply]
@Cmglee:
Thanks for running the test. I'll try looking at the HTTP transfer and see if there are cross origin issues.
The code backing the SVG Checker also uses line 451 image/jpeg:
Thanks again.
Glrx (talk) 17:58, 3 August 2023 (UTC)Reply[reply]
image/jpeg likely isn't the issue as it worked before around 2019. Don't know if Commons_talk:Commons_SVG_Checker#is_it_down? is a useful lead. Thanks too for trying, cmɢʟee ⋅τaʟκ 19:23, 3 August 2023 (UTC)Reply[reply]
@Cmglee and Jonteemil:
I go to Commons SVG Checker, select an SVG file, and then execute the SVG check.
The request to convert.toolforge.org/svg2png.php fails.
Console reports
Referrer Policy: Ignoring the less restricted referrer policy “origin-when-cross-origin” for the cross-site request: https://convert.toolforge.org/svg2png.php index.php:322:8
Cross-Origin Request Blocked: The Same Origin Policy disallows reading the remote resource at https://convert.toolforge.org/svg2png.php. (Reason: CORS header ‘Access-Control-Allow-Origin’ missing). Status code: 200.
The request fails in the browser because the svg2png does not supply an appropriate Access-Control-Allow-Origin header.
Cannot find tool on toolforge.org.
Guess this is the source
This URL should return the version:
svg2png.php line 35 calls matchOrigin($origin) and emits appropriate CORS access headers if there is a match. I'm confused. The access headers were not emitted, but if no match then no PNG should be emitted (exit is called before calling RSVG). A PNG was emitted. Is there another source? Is PHP or something else suppressing the CORS headers?
I cannot find matchOrigin; I expect it to be in shared/commons.php, but that links to Rillke (which is not 2 dirs up).
Interesting GitHub issue re toolforge and wmflabs (apparently fixed by renaming wmflabs URLs to toolforge URLs around 2020).
line 8 uses old URL:
  • $url = $prot . "://tools.wmflabs.org/$tool_user_name/";
but does not seem to be used for matching the origin.
Glrx (talk) 20:36, 3 August 2023 (UTC)Reply[reply]
@Jonteemil and Cmglee:
I suspect that is not the current source. I can convert SVG to PNG from a non-WMF origin, so I suspect the current source has deleted not only the origin matching test but also the CORS headers.
Glrx (talk) 21:19, 3 August 2023 (UTC)Reply[reply]
@Glrx: Thanks again for investigating. I must admit that your findings are far beyond what I'm familiar with. Pinging @Redrose64: and @JoKalliauer: (may not be active recently) for their opinions, cmɢʟee ⋅τaʟκ 02:22, 4 August 2023 (UTC)Reply[reply]
@Cmglee and JoKalliauer:
Turns out that Johannes cloned convert to make his SVG workaround bot. His clone has the matchOrigin code:
I still cannot explain the failure to supply the CORS headers.
Glrx (talk) 04:12, 4 August 2023 (UTC)Reply[reply]
webservice restart might work
@Glrx and Jonteemil: I do not know why Rillke's rendering does not work, maybe consider reopening phab:T217362.
I assume that Commons:Commons_SVG_Checker might use the same code, which recommends since 2019 to use @Jarry1250: tool: https://svgcheck.toolforge.org/ which works imho flawlessly. (But you have to manually upload the image.)
I assume that
webservice stop
webservice --backend=gridengine start
would fix it, see wikitech:Help:Toolforge/Web. I also sometimes have to restart webservice for https://svgworkaroundbot.toolforge.org/ to work again.
github.com/JoKalliauer/convert doesn't help in this case, it only converts svg to (less buggy) svg, it does not render svg to png, and the issue with User:Rillke/MwJSBot.js is imho independent on the SVG, therefore it won't help. I use Rillke's code basically as black-box without understanding JavaScript, so I won't be helpful in bug fixing the code, or finding the issue.
I'm basically inactive, and stopped following treads, however I'm happy to get pinged to help. :-)
 — Johannes Kalliauer - Talk | Contributions 07:50, 4 August 2023 (UTC)Reply[reply]

Quickfix needed for wrongly rotated file (exif error)[edit]

Hi this file shows up right in crop/rotation tool but wrong in description page. Original rotation was wacky in exif and this showed in the loading of the image from right to left. How to fix this and similar halfway incorrect rotations? Thanks. Similar issues from those days in crop tool vs. descr. page. Peli (talk) 22:10, 24 July 2023 (UTC)Reply[reply]

Fixed visual part of this case. Peli (talk) 10:57, 25 July 2023 (UTC)Reply[reply]

Tech News: 2023-30[edit]

MediaWiki message delivery 02:18, 25 July 2023 (UTC)Reply[reply]

Nie mogę podmienić zdjęcia.[edit]

Dobry wieczór. Chciałem podmienić fotografię własnego autorstwa: [3] na inną w lepszej jakości, ale wyskakuje mi komunikat: "If you do not provide suitable license and source information, your upload will be deleted without further notice. Thank you for your understanding". Wbrew temu co mówi komunikat nigdzie nie widzę rubryki na wstawienie jakiejkolwiek informacji licencji fotografii. Prosiłbym o pomoc w tej sprawie. KujKuń (talk) 22:16, 25 July 2023 (UTC)Reply[reply]

How to deal with seemingly unused gadgets needing an update[edit]

There are still some gadgets that have now outdated code after changes according to phab:T314318, see also corresponding FAQ: mw:Parsoid/Parser Unification/Media structure/FAQ #The "image" class is no longer present on file description links.

Some used gadgets already have been updated, but these haven’t yet:

The first one is mentioned in a comment in User:DrTrigon/common.js, but this user is inactive since 2016.

What I cannot estimate, though, are potential external uses. — Speravir – 23:22, 29 July 2023 (UTC)Reply[reply]

Old appearance for editor[edit]

How do I get back the classic old box for editing with "Publish changes" "Show preview" "Show changes" buttons below "Summary"? Commons help sends to Meta and then MediaWiki and there I choose the "[[]]" option under the eye of Visual Editing in the pencil menu, to no avail. I go to my Preferences and I have legacy Vector 2010 and disabled Visual Editor, but nothing. Any idea? Anything to install? ※Sobreira ◣◥ 〒 @「parlez」 04:02, 30 July 2023 (UTC)Reply[reply]

Perhaps a screenshot (on temporary external source) would better help for understanding. Do you speak of the text being coloured? This would be the syntax highlighting with CodeMirror. This image does show it with Chinese text on zhwiki. — Speravir – 23:36, 1 August 2023 (UTC)Reply[reply]
@Speravir: Oh, thanks, I was off for a while. I mean the box where you write the text, not the text itself. I uploaded the difference:
What I find, it changed a few months ago; to the left of the first blue button there's a pencil and
a "[[]] Source editing" below when you click, but pressing that nothing changes for me. I have a cookie blocker (Ninja cookie) but I disabled it and it's the same.
The beloved system that I'd like,
and the only one we used to have.
Sobreira ◣◥ 〒 @「parlez」 00:13, 11 August 2023 (UTC)Reply[reply]

Tech News: 2023-31[edit]

MediaWiki message delivery 23:52, 31 July 2023 (UTC)Reply[reply]

Converting very big JPEG2000 files to JPEG[edit]

Hi, While uploading some maps, I convert them from JPEG2000 (the source) to JPEG, to get a format more usable by everyone. Some very big files (10404864.jp2, 954 MB; 15328045.jp2, 1.1 GB; 15328046.jp2, 296 MB; 15328047.jp2, 182 MB; 15328049.jp2, 958 MB; 15328050.jp2, 626 MB) fail to convert (with ImageMagick) even with 32 GB of RAM. Has anyone access to a bigger system could do that? On Toolforge, one gets usually a few GB at most, so it won't work. Any other idea? Yann (talk) 18:54, 2 August 2023 (UTC)Reply[reply]

I have tried, too, with my 64 GiB RAM system, but I failed, too :( --PantheraLeo1359531 😺 (talk) 14:51, 4 August 2023 (UTC)Reply[reply]
Thanks for your message. It seems possible to tweak ImageMagick to use less RAM, but I failed to find the proper parameters. With the default parameters, the process requires 65 GB for commit. I also tried with Gimp: same result. Yann (talk) 21:44, 4 August 2023 (UTC)Reply[reply]
It is really weird. I wonder how a 1 Gigabyte image takes up so much RAM. I worked with several Gigabyte-scale images, and they only needed 10 or 15 GiB RAM. I added 500 GB of virtual RAM, and the conversion with ImageMagick still failed :( --PantheraLeo1359531 😺 (talk) 13:27, 7 August 2023 (UTC)Reply[reply]

Renaming creator templates?[edit]

Any suggestions on how to fix the issues caused by this renaming? If I just rename the template back to how it was before, will it cause further problems with the categorization? DS (talk) 19:50, 4 August 2023 (UTC)Reply[reply]

I've renamed the per-image calls to this template to use the disambig'ed version. Took moments. We might not need the disambiguation, but as usual when there's a notable other version of the same name, it's not a bad idea to do it prematurely. Andy Dingley (talk) 22:15, 4 August 2023 (UTC)Reply[reply]

Site loading errors[edit]

Hi everyone, for quite a while I have now experienced regular connection failures, where Commons returns me server-responses like the following:

Error
Our servers are currently under maintenance or experiencing a technical problem. Please try again in a few minutes.
See the error message at the bottom of this page for more information.
-
If you report this error to the Wikimedia System Administrators, please include the details below.
Request from 2a02:908:eb41:7ce0:ddbc:cd3:f0f5:41ec via cp3052 cp3052, Varnish XID 1055918443
Error: 503, Backend fetch failed at Sat, 05 Aug 2023 10:53:46 GMT

I am to 95% certain that this error persists on MY end and that the backend side is not to blame at all, because I get error messages from other websites, too, for example:

The requested page could not be loaded.
* Check your internet connection and try again.
* Certain browser extensions, such as ad blockers, may block pages unexpectedly. Disable these and try again.
* (our site) may be temporarily unavailable. Please check back later.

Can someone please change the error messages, so that the connection error is no longer blamed on Wikimedia's servers alone? --Enyavar (talk) 11:52, 5 August 2023 (UTC)Reply[reply]

The error message says Error: 503, Backend fetch failed. That’s quite unlikely to come from your end, even if it happens to coincide with other issues. —Tacsipacsi (talk) 22:24, 5 August 2023 (UTC)Reply[reply]
I regularly have that problem whenever categorizing multiple files in a row, in the recent days. For example in the time indicated in the error message above, but also for example yesterday between the timestamps (17:47, 5 August 2023) and (18:00, 5 August 2023): 10-20 minutes enforced downtime per hour. Unless there have been actual Wikimedia server problems in those timeframes, I still think it has been my own lousy connection. But if this a server-side problem you should really look into that. Enyavar (talk) 12:57, 6 August 2023 (UTC)Reply[reply]

Template:Cfdh includes the TOC[edit]

In for example Commons:Categories for discussion/2023/03, the {{Delh}} template includes the TOC, which it shouldn't. Commons:Categories for discussion/Archive/2023/03, Commons:Deletion requests/2023/08/01 solves this by placing a template at the top which then makes the {{Cfdh}}/{{Delh}} being placed below the TOC. Another solution, if possible, is to do some code hack, like {{Clr}}(?), to make the TOC be placed above {{Cfdh}}. Jonteemil (talk) 00:48, 7 August 2023 (UTC)Reply[reply]

Edit several description pages of files in a category at once[edit]

Dear community,

I wrote a wrong date in the description page of several files in a category. How can I find and replace all the dates of the files in a category at once?

Thank you! --PantheraLeo1359531 😺 (talk) 15:05, 7 August 2023 (UTC)Reply[reply]

See Help:VisualFileChange.js. Yann (talk) 21:28, 7 August 2023 (UTC)Reply[reply]
Thank you :) --PantheraLeo1359531 😺 (talk) 17:24, 8 August 2023 (UTC)Reply[reply]

Tech News: 2023-32[edit]

MediaWiki message delivery 21:18, 7 August 2023 (UTC)Reply[reply]

ZoomViewer produces a 503 error[edit]

Hi, Please see phab:T343796. This happens to all files I checked. Yann (talk) 12:24, 8 August 2023 (UTC)Reply[reply]

Commons:Upload&uploadformstyle=basic[edit]

Hi. Have not heard this error reported from other users, but whenever I use the Commons:Upload and then press "Basic upload form" the Basic upload page is activated and then reactivated. So if you start to type after the first activation, you will get the new page and then you will be asked if you want to ditch your first input. This is rather annoying and has been going on for some weeks. Someone must have changed the behaviour of the page. Is there any hope of getting the old setup back? It worked. Cheers Rsteen (talk) 14:44, 8 August 2023 (UTC)Reply[reply]

Hi, I suppose you mean here. I don't see this behaviour. Yann (talk) 16:02, 8 August 2023 (UTC)Reply[reply]
That is strange. As soon as I opened the link, I got the repeated opening of the page, just as I wrote above. Has anybody else tried it? Cheers Rsteen (talk) 04:03, 9 August 2023 (UTC)Reply[reply]

MediaWiki:Gadget-QICvote.js[edit]

The gadget isn't working now. Regards!! --Ezarateesteban 16:59, 8 August 2023 (UTC)Reply[reply]

What happened to this file?[edit]

At File:Brexpiprazole.svg, I recently reverted a older version. But the current image and several of the older versions seem to have gone blank. Previously, they weren't. Any idea what happened and how to fix it? I brought this up at the help desk (see Commons:Help_desk#What_happened_to_this_file? for details) and a resolution hasn't been found and it was suggested that I ask here. Marbletan (talk) 19:04, 9 August 2023 (UTC)Reply[reply]

There is now a new version by Glrx, which looks fine. Yann (talk) 19:10, 9 August 2023 (UTC)Reply[reply]
e/c
@Marbletan: I removed the SVG 1.0 DTD and some attributes on the svg element. Now it displays. Glrx (talk) 19:13, 9 August 2023 (UTC)Reply[reply]
Thanks for the quick fix! Marbletan (talk) 19:15, 9 August 2023 (UTC)Reply[reply]

VFC error[edit]

If I open VisualFileChange and enter the username RickyDean76 there is an error and no files are being rendered. Why is this? Jonteemil (talk) 21:41, 9 August 2023 (UTC)Reply[reply]

corrupted file history[edit]

Hello, please at first read the related section at Commons:History merging and splitting then check the page's history, now I have 2 solutions:

solution #1
a) restore the main page to the revision as of 04:45, 5 August 2023‎
b) undelete File:Germann with Sircar and McGinley 2022 (edited) (2).png
c) merge File:Germann with Sircar and McGinley 2022 (edited) (2).png into the main page
solution #2
a) restore the main page to the revision as of 19:20, 21 July 2023

I prefer the solution #2 because it makes the page's history clean and uncluttered, although I don't know if restoring a page to an old revision does restore its *file history* or not.

THANKS VERY MUCH -- FARHAAD 1992 (talk) 02:54, 11 August 2023 (UTC)Reply[reply]