MediaWiki talk:Gadgets-definition

From Wikimedia Commons, the free media repository
Jump to navigation Jump to search
MediaWiki:Gadgets-definition forms part of the MediaWiki interface and can only be edited by administrators, stewards and interface editors.
To request a change to MediaWiki:Gadgets-definition, add {{Edit request}} to this talk page, followed by a description of your request.
This interface message or skin may be documented on mediawiki.org or translatewiki.net.
 SpBot archives all sections tagged with {{Section resolved|1=~~~~}} after 14 days.

Turn on MediaWiki:Gadget-CategoryAboveBelowImage.js

[edit]

{{Editprotected}}

See discussion: Can someone please turn this on per default? --El Grafo (talk) 07:49, 17 June 2015 (UTC)[reply]

@El Grafo: Please file a request on phabricator:. This needs a integration in MediaWiki to avoid Jumping Content. --Steinsplitter (talk) 10:48, 17 June 2015 (UTC)[reply]
@Steinsplitter: thx → phab:T102776 --El Grafo (talk) 11:45, 17 June 2015 (UTC)[reply]

Yes Piyaphart (talk) 11:41, 2 January 2022 (UTC)[reply]

tabularImportExport

[edit]

Would someone please:

Thank you —TheDJ (talk • contribs) 13:50, 23 January 2017 (UTC)[reply]

@TheDJ: I see you are importing stuff from tools-static.wmflabs.org which is a third party service, thus i have privacy concerns regarding that. The script is also importing stuff from your own userspace. If those two issues are resolved i am happy to crate the gadget. --Steinsplitter (talk) 13:53, 23 January 2017 (UTC)[reply]
if you have concerns about tracking that is happening at wmflabs.org, you should report that with the foundation, since that kind of tracking would be illegal per the terms of usage of the labs infrastructure. If someone wants to copy those scripts into MediaWiki namespace to avoid having to import them from toollabs or from my user space, they are welcome to do so, but since that requires administrative powers, there is little assistance that I can provide in that area. Either is fine with me. —TheDJ (talk • contribs) 14:11, 23 January 2017 (UTC)[reply]

MoreMenu

[edit]

{{Edit request}}

Hello! I'd like to propose adding the MoreMenu gadget to Commons. For Vector users, it adds up to two dropdown menus ("Page" and "User") containing links to relevant logs, uploads, external tools, and admin/checkuser/oversight functions. There is an older script designed for Monobook but I'm not sure how well it would work here on Commons.

I feel this would be a nifty tool for many users, especially admins. If you'd like to test it out, you can add the following your vector.js: 

mw.loader.load('https://en.wikipedia.org/w/index.php?action=raw&ctype=text/javascript&title=MediaWiki:Gadget-dropdown-menus-vector.js');

The source of the gadget itself would the same, loading it from the English Wikipedia, that way you get all the updates.

Assuming the script will live at MediaWiki:Gadget-MoreMenu.js, the gadget definition would be along the lines of: 

* MoreMenu[ResourceLoader|skins=vector|dependencies=mediawiki.api,mediawiki.util,user.options]|MoreMenu.js

And the description could be something like: 

[[meta:MoreMenu|MoreMenu]]: add Page and User dropdown menus to the toolbar with links to common tasks, analytic tools and logs (Vector skin only)

linking to the documentation at meta:MoreMenu.

Thanks for your consideration — MusikAnimal talk 02:11, 18 April 2017 (UTC)[reply]

I don't find the script useful for my admin-work. Anyway, @Steinsplitter: for more info. --Hedwig in Washington (mail?) 02:49, 9 May 2017 (UTC)[reply]
 Not done Not much interest from anybody else. --Hedwig in Washington (mail?) 03:39, 20 July 2017 (UTC)[reply]
I find this tool extremely helpful for my admin-work. I would support it as a Gadget if others were interested. For now, it lives in my vector.js ~riley (talk) 00:30, 15 November 2019 (UTC)[reply]

Dark-Vector skin

[edit]

Hello, what do you think about to install the Dark-Vector skin⁉ PS: You can try out it on Commons Beta, seems not fully perfect but usable as opt-in. PPS: I mean it looks much better as the black skin installed on the EnWP. -- User: Perhelion 19:37, 19 October 2017 (UTC)[reply]

@Perhelion: Dark mode looks awesome! Would it be possible to make it a gadget? Masum Reza📞 00:59, 20 October 2019 (UTC)[reply]
Thanks, yes of course, but I think now it would be good to make a proposal first. -- User: Perhelion 09:04, 21 October 2019 (UTC)[reply]

I checked Wikipedia and found it has a black background gadget that can be enabled here:

See CSS and discussion:

Some vector wikis on Shoutwiki have a black skin. See discussion:

--Timeshifter (talk) 01:36, 23 October 2019 (UTC)[reply]

Adding a gadget to make all tables sortable?

[edit]

Don't know if simply adding the "sortable" class to a table post-load is enough, or if scripts apply the sorting event handler once on page load, but I'd like to see an official interface gadget that allows users to make tables sortable that weren't explicitly declared unsortable or sortable. Apollolux (talk) 03:42, 27 November 2017 (UTC)[reply]

WikiMiniAtlas is down

[edit]

{{Sudo}} Hi commons admins. meta:WikiMiniAtlas is down due to phab:T185797; I suggest disabling the default load of

WikiMiniAtlas [ResourceLoader|default]|WikiMiniAtlas.js
To prevent readers from ending in an error screen when clicking on the icons until this can be repaired. — xaosflux Talk 16:27, 27 January 2018 (UTC)[reply]
[edit]

I'm sure the gadget has some advanced features that are missing in MultimediaViewer, but it seems very confusing that every page has two slideshow experiences by default. We should keep this gadget as an option for users that prefer it, but by default the MultimediaViewer slideshow seems more than sufficient. ed g2s • talk 13:35, 28 March 2019 (UTC)[reply]

Revision Counter

[edit]

Is it possible to integrate this helpful tool here? It's a gadget on deWP and shows if resp. how often you edited the page. --Stepro (talk) 23:10, 26 July 2020 (UTC)[reply]

New gadget suggestion: BatchRename

[edit]

I've been working a lot in categories like Category:Images with meaningless prefixes and Category:Files of Japan with bad file names. These (and other categories like them) often have large batches of images and other files that are all named similarly, and need the same similar change made to the file name. If there was a way to select a bunch of them, then batch rename them using a pattern of some sort, that would be incredibly useful and save all sort of time. It would probably need some sort of limiter to prevent it from doing too much at the same time.

As an example, in Category:Images with meaningless prefixes, I've been working through a bunch where I'm simply moving the date from the start of the file name to the end. There are hundreds of this particular pattern, and I've run into others like these.

Thoughts? ···日本穣 Talk to Nihonjoe 20:00, 17 May 2022 (UTC)[reply]

moving File:(2019) ปราสาทหินวัดสระกำแพงน้อย 23 DSCN0254.jpg to File:ปราสาทหินวัดสระกำแพงน้อย 23 DSCN0254 (2019).jpg is not good. files should not be moved for cosmetic changes. RZuo (talk) 12:47, 21 May 2022 (UTC)[reply]
i see these files were added into Category:Images with meaningless prefixes by User:Watchduck. a year is not a meaningless prefix. RZuo (talk) 12:50, 21 May 2022 (UTC)[reply]
Yes, renaming files for cosmetic reasons is generally bad. And a year is not technically a meaningless prefix. But some users have the extremely annoying habit to use prefixes to get the "best places" in categories. If this kind of nonsense were tolerated, we would sooner or later get names like File:(Paris) Eiffel tower.jpg. This is not essentially about the cosmetics of file names. It is about discouraging a SEO approach to file names. Watchduck (quack) 19:46, 21 May 2022 (UTC)[reply]
I beg to differ. If all uploaders would start the filename with the date, all photos in every category would be proper sorted by date. --Stepro (talk) 21:45, 21 May 2022 (UTC)[reply]
I doubt that will ever happen, so we'll have to work with what we have. Regardless of that (which is a clarification discussion for somewhere else), this kind of gadget would be extremely useful when moving multiple similarly named files like I've been doing for several hundred photos of a flood in Japan. Whoever originally uploaded them gave them sequentially numbered names, but the names were not helpful in identifying the contents of the photos. Instead of spending days slowly plodding through all of them, a gadget like I describe would have allowed them to be moved within an hour or two. ···日本穣 Talk to Nihonjoe 01:06, 24 May 2022 (UTC)[reply]
@Nihonjoe: Have you tried User:Jeff G./massrename.js as copied from User:Perhelion/massrename.js with doc at User:Jeff G./massrename?   — Jeff G. ツ please ping or talk to me 01:21, 24 May 2022 (UTC)[reply]
I have not. I'll take a look at it. ···日本穣 Talk to Nihonjoe 17:46, 24 May 2022 (UTC)[reply]
@Jeff G.: Okay, I tried it out and it worked well for a batch of about 50 images. Would there be a way to have it also have the option of removing or adding a category (I mostly need the removing part) as part of the moving? All the images were moved fine, but I'll have to manually remove the Category:Files of Japan with bad file names from each one. Being able to do it while moving the file would be much more convenient. Perhaps code could be taken from the regular move request template to do that? ···日本穣 Talk to Nihonjoe 17:40, 25 May 2022 (UTC)[reply]
@Nihonjoe: Maybe, but sadly I can barely read js, let alone write it. Feel free to snag a copy for your own userspace and work on it there. Links to free online tutorials gladly accepted. Note, the cat removal can be done by Cat-a-lot, COM:AWB, COM:JWB, or COM:VFC.   — Jeff G. ツ please ping or talk to me 17:46, 25 May 2022 (UTC)[reply]
I'll try out Cat-a-lot. It looks like the simplest tool to use for what I'm doing. ···日本穣 Talk to Nihonjoe 18:31, 25 May 2022 (UTC)[reply]

Support for Proveit

[edit]

It seems that Help:Gadget-ProveIt is "hidden":

  • ProveIt [ResourceLoader|dependencies=mediawiki.api,jquery.cookie,jquery.textSelection,jquery.ui|hidden]|ProveIt.js|ProveIt.css

Would it be possible to enable it on Commons?

(see also this ongoing discussion) A455bcd9 (talk) 08:24, 11 December 2022 (UTC)[reply]

Promote Userscript 3D-Models User Script as a gadget on Commons

[edit]

{{technical}}

During the Wikimania Hackathon, a significant amount of 3D content was identified on Wikimedia Commons. However, many users remain unaware of this resource. As a solution, there was a discussion about developing a gadget that would introduce a dedicated "3D Models" section alongside the existing "Images" and "Videos" sections. This enhancement aims to facilitate user access to the extensive collection of 3D models available on Wikimedia Commons.

A user script has been created to implement this feature. It strategically places a "3D Models" button next to the "Videos" section on Wikimedia Commons. This button would serve as a direct link for users to explore the repository of 3D models hosted on the platform. Therefore, we would like to request support for promoting this user script to a fully-fledged gadget, making it more visible and accessible to users interested in 3D content on Wikimedia Commons.

Link to the script: https://www.mediawiki.org/wiki/User:Gopavasanth/UserScripts#1._3DModels.js

cc: @Fuzheado

Regards, Gopavasanth (talk) 07:03, 16 August 2023 (UTC)[reply]

Why not just submit this as a patch to the Special:MediaSearch code? It sounds like a great addition which would be translatable and supported there? Jdforrester (WMF) (talk) 07:15, 16 August 2023 (UTC)[reply]
I’m inclined to agree; @Gopavasanth how do you feel about that suggestion? (For one thing, the button should be easier to translate in the extension.) Lucas Werkmeister (talk) 22:49, 3 November 2023 (UTC)[reply]
@Gopavasanth reminder :) Lucas Werkmeister (talk) 18:05, 2 March 2024 (UTC)[reply]
I added {{Edit request}} above because this seems like one. If not, please feel free to remove the template. whym (talk) 14:31, 16 August 2023 (UTC)[reply]
@Gopavasanth, Lucas Werkmeister, Jdforrester (WMF), and Fuzheado: I am a late arrival into this discussion. Can we file it into the archives, or there is some action needed by Commons admins? --Jarekt (talk) 04:21, 24 June 2024 (UTC)[reply]
@Jarekt: I don't believe the edit has been made, or the code push has happened either. Archival might cause this stalled work to turn into entirely-forgotten work instead? Jdforrester (WMF) (talk) 10:59, 24 June 2024 (UTC)[reply]
Actually, I think we misunderstood this edit request. It doesn’t look like it adds a new tab to Special:MediaSearch, like James and I assumed; rather, it adds another button to the Main Page, between “Videos” and “Upload”. So upstreaming it to the MediaSearch extension doesn’t really make sense.
But I’m also not sure how much sense it makes as a gadget. If the goal is to raise awareness of 3D models, I don’t think a gadget that users have to enable first would help much. Could we add the link to the main page directly, at Template:Main Page Template? (We’d probably have to discuss that somewhere else first though, or someone will get angry, I assume.) Lucas Werkmeister (talk) 19:54, 26 June 2024 (UTC)[reply]
Yes, the right long term solution is to showcase 3D models a first class (or at least second class) data type on Commons. Right now it gets lost entirely. - Fuzheado (talk) 19:38, 22 July 2024 (UTC)[reply]
@Gopavasanth, Fuzheado, Jdforrester (WMF), and Lucas Werkmeister: I added "3D Models" link directly to Template:Main Page Template. I also added it to en and pl versions of the Main Page. If any of you speaks other languages please translate "3D Models" to that language and add it as well. And Lucas thank you for figuring out what is the purpose of the gadget. --Jarekt (talk) 02:36, 9 September 2024 (UTC)[reply]
@Jarekt: Good that this has been (semi?-)resolved. Jdforrester (WMF) (talk) 12:33, 9 September 2024 (UTC)[reply]
German translated. Thanks for updating the template! Lucas Werkmeister (talk) 18:06, 9 September 2024 (UTC)[reply]

Remove mentions of "writeapi"

[edit]

{{Edit request}} The writeapi user right was removed in MediaWiki 1.43.0-wmf.17, deployed yesterday. See phab:T294397 for the background. This means that gadgets that require the writeapi right now don't appear for anyone. The writeapi right was granted to everyone anyway (including IP users), so I think the correct thing to do is simply to remove all mentions of writeapi from the gadget definitions. For concreteness, that means:

  • Remove |rights=writeapi from the definition of "Favorites"
  • Remove ,writeapi from the definition of "RotateLink"
  • Remove ,writeapi from the definition of "RenameLink"
  • Remove |rights=writeapi from the definition of "AjaxQuickDelete"

Please could someone with appropriate permissions make those changes? --bjh21 (talk) 11:27, 7 August 2024 (UTC)[reply]

✓ Done, thanks. -- CptViraj (talk) 18:39, 7 August 2024 (UTC)[reply]

Remove MediaWiki:Gadget-VIAFDataImporter.js

[edit]
It is requested that an edit or modification be made to this protected page.
Administrators: Please apply <nowiki> or {{Tl}} to the tag after the request is fulfilled.

Marsupium

As pointed out by Aschroet on Help talk:Gadget-VIAFDataImporter#No longer needed... the data that can be imported with this tool should rather be added to Wikidata. I see a lot of cases for which this tool adds redundant data. There is no need and rather possible harm from its existence as a gadget. --Marsupium (talk) 16:37, 6 November 2024 (UTC)[reply]

How about putting a notice saying that this is superseded by Wikidata, and encouraging users to disable it by themselves? Can a notice like that be inserted into the gadget? Silently removing it will surprise its users. It will probably need to go at the end, but I think we can take some time. (Note: I'm not volunteering to modify the gadget for now, though. I hope someone else can.) whym (talk) 13:22, 11 November 2024 (UTC)[reply]
I count 3 edits made using this tool this year. Special:GadgetUsage says there are 2325 users with the gadget enabled, out of which only 229 have been active in the last 30 days. For deprecation notices we have 3 options: Displaying a note every time someone loads a page with the gadget enabled (until they disable it), displaying a note once, and displaying a note if they try to use the tool. Displaying a note every time is overkill for this, and nobody uses this often enough to see a note when they use the tool. If someone writes up what a once-per-device deprecation notice would look like, I could do it, but I don't really think it's necessary. AntiCompositeNumber (talk) 22:14, 11 November 2024 (UTC)[reply]
A message on click would be my choice, but if the usage is that low, I agree it won't be effective. I expected a bit more than the 3 instances of the tool usage. That said, the mechanism of a once-per-device deprecation notice could be benefical, if it's generalized for all gadgets, not just this one. whym (talk) 23:51, 11 November 2024 (UTC)[reply]
This sounds like a very clean solution if someone can actually provide the needed code. If that turns out to be difficult, it doesn't sound to harmful just to deactivate it given the low usage. Also, tools that disappear is something that happens. So even if not the cleanest solution I guess the surprise would be limited. --Marsupium (talk) 09:17, 12 November 2024 (UTC)[reply]
Retrieved from "https://commons.wikimedia.org/w/index.php?title=MediaWiki_talk:Gadgets-definition&oldid=956003371"