MediaWiki talk:Gadgets-definition

From Wikimedia Commons, the free media repository
Jump to: navigation, search
Namespace-mediawiki.svg MediaWiki:Gadgets-definition forms part of the MediaWiki interface and can only be edited by administrators.
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 or TranslateWiki.
Translations: English
Filing cabinet icon.svg
SpBot archives all sections tagged with {{Section resolved|1=~~~~}} after 14 days.

migration to other RTL and multilanguage projects[edit]

en: MediaWiki talk:Gadgets-definition special:Preferences
w: ar:, arc:, dv:, fa:, ha:, he:, ks:, ku:, lad:, pa:, ps:, sd:, tk:, ug:, ur:, yi:
others: test, m:, commons:, wm2008:, incubator:, beta.wikiversity:

local links[edit]

  1. MediaWiki:Common.js
  2. special:Gadgets MediaWiki:Gadgets-definition talk
  3. MediaWiki:Gadget-section-General
    1. MediaWiki:Gadget-BiDiEditing MediaWiki:Gadget-BiDiEditing.js
  4. MediaWiki:Gadget-section-LanguageSupport and MediaWiki:Gadget-section-AdditionalRTLLanguageSupport
    1. MediaWiki:Gadget-UseLangArc MediaWiki:Gadget-UseLangArc.js
    2. MediaWiki:Gadget-UseLangAr MediaWiki:Gadget-UseLangAr.js
    3. MediaWiki:Gadget-UseLangDe MediaWiki:Gadget-UseLangDe.js
    4. MediaWiki:Gadget-UseLangDv MediaWiki:Gadget-UseLangDv.js
    5. MediaWiki:Gadget-UseLangEn MediaWiki:Gadget-UseLangEn.js
    6. MediaWiki:Gadget-UseLangEo MediaWiki:Gadget-UseLangEo.js
    7. MediaWiki:Gadget-UseLangEs MediaWiki:Gadget-UseLangEs.js
    8. MediaWiki:Gadget-UseLangFa MediaWiki:Gadget-UseLangFa.js
    9. MediaWiki:Gadget-UseLangFr MediaWiki:Gadget-UseLangFr.js
    10. MediaWiki:Gadget-UseLangHa MediaWiki:Gadget-UseLangHa.js
    11. MediaWiki:Gadget-UseLangHe MediaWiki:Gadget-UseLangHe.js
    12. MediaWiki:Gadget-UseLangKs MediaWiki:Gadget-UseLangKs.js
    13. MediaWiki:Gadget-UseLangKu MediaWiki:Gadget-UseLangKu.js
    14. MediaWiki:Gadget-UseLangLad MediaWiki:Gadget-UseLangLad.js
    15. MediaWiki:Gadget-UseLangPa MediaWiki:Gadget-UseLangPa.js
    16. MediaWiki:Gadget-UseLangPl MediaWiki:Gadget-UseLangPl.js
    17. MediaWiki:Gadget-UseLangPs MediaWiki:Gadget-UseLangPs.js
    18. MediaWiki:Gadget-UseLangRo MediaWiki:Gadget-UseLangRo.js
    19. MediaWiki:Gadget-UseLangRu MediaWiki:Gadget-UseLangRu.js
    20. MediaWiki:Gadget-UseLangSd MediaWiki:Gadget-UseLangSd.js
    21. MediaWiki:Gadget-UseLangTg MediaWiki:Gadget-UseLangTg.js
    22. MediaWiki:Gadget-UseLangTk MediaWiki:Gadget-UseLangTk.js
    23. MediaWiki:Gadget-UseLangYi MediaWiki:Gadget-UseLangYi.js
    24. MediaWiki:Gadget-UseLangUg MediaWiki:Gadget-UseLangUg.js
    25. MediaWiki:Gadget-UseLangUr MediaWiki:Gadget-UseLangUr.js

under test[edit]

  1. MediaWiki:Gadget-section-TestMode
  2. MediaWiki:Gadget-QuickEdit MediaWiki:Gadget-QuickEdit.js
  3. MediaWiki:Gadget-EoMagicalConversion MediaWiki:Gadget-EoMagicalConversion.js
  1. MediaWiki:Gadget-ShortDiff MediaWiki:Gadget-ShortDiff.js
  2. MediaWiki:Gadget-ShortLink MediaWiki:Gadget-ShortLink.js
  3. MediaWiki:Gadget-Purge-tab MediaWiki:Gadget-Purge-tab.js
  4. MediaWiki:Gadget-CSS-tab MediaWiki:Gadget-CSS-tab.js‎
  5. MediaWiki:Gadget-XHTML-tab MediaWiki:Gadget-XHTML-tab.js


  1. MediaWiki:Gadget-UseLang MediaWiki:Gadget-UseLang.js

Force summary[edit]

This is a "softer" version o the default force edit summary script. It doesn't require a reload, but jumps to the empty summary, makes it blink in red & puts the focus on the field. Afterwords cu yan still save, if you decide that the summary is not needed. I'd propose adding it to the gadget list--DieBuche (talk) 09:45, 3 June 2010 (UTC)

Funny, de.wp recently discussed about that. 2 years later. Wouldn't mind if such a gadget would be default. -- Rillke(q?) 14:44, 21 September 2012 (UTC)


Is it possible to add so that we have inbrowser SVG editing integrated into MediaWiki with file save revision support? That would be great! Matt (talk) 16:38, 2 January 2011 (UTC)

I've already done some work on doing this as an extension (mw:Extension:SVGEdit) and have some ideas for tweaking it to work as a gadget too -- I'll see what I can whip together. I'll poke some notes at and here. --brion (talk) 23:28, 2 January 2011 (UTC)
Symbol support vote.svg Support
But where are the notes? -- Rillke(q?) 14:44, 21 September 2012 (UTC)


Commons:Database_reports/User_preferences#Gadgets shows the number of active and inactive users who have them enabled. --  Docu  at 07:04, 25 June 2011 (UTC)

Remove obsolete gadget[edit]


See MediaWiki talk:Gadget-EnhancedUndelete.js#Obsolete. Helder 15:47, 5 October 2011 (UTC)

✓ Done though left the gadget parts in place, at least for the moment.  — billinghurst sDrewth 03:13, 6 October 2011 (UTC)

Location of category interface gadgets[edit]

Saibo moved [1] a new category interface gadget, but there are several ones in the "category" section already "cat above all" and "cat below image". What distinguishes an interface modification from a tool anyway? Confused... Rd232 (talk) 19:28, 2 December 2011 (UTC)

Umm, well, at first I went to the prefs page to switch on the gadget and was looking in the interface section where I didn't find it. Then I improved the code and desc. a bit, and then I saw the still strange position beneath the categorizing(!) tools cat-a-lot and so on. Since I was chatting anyway with Rillke I asked and did not hear a oppose rather a agreeing position. Anyway, it was my decision and I didn't thought that someone opposes.
Yes I would move
  • Kategorien über jeglichem Seiteninhalt
  • Kategorien über jeglichem Seiteninhalt, jedoch unter dem Bild auf Dateibeschreibungsseiten
too (I may note that I did not know about those two gadgets in this section).
What else should be interface if not such visual changes? If you do not agree that it fits better in "interface" move it back - you were first. ;-) Cheers --Saibo (Δ) 22:18, 2 December 2011 (UTC)
I don't know... I tried moving some things about, as a fair amount of illogic has accumulated. Let's see what the reaction is. Rd232 (talk) 23:09, 2 December 2011 (UTC)
I hope you didn't loose some gadgets in the Toowaaboo. ;-) That looks good on first sight, thanks! Probably things will stay suboptimal until we put gadgets in several categories. Cheers --Saibo (Δ) 23:29, 2 December 2011 (UTC)
Yes, there are plans to eventually (a year or two?) revamp the whole gadget interface anyway. In the mean time, I wish we could get the mechanism working again where gadgets can go onto other pages of Preferences; it seems to be broken. Rd232 (talk) 23:32, 2 December 2011 (UTC)


Please restore the original layout and seek consensus first.
  • CategoryAboveAll|CategoryAboveAll.js
  • CategoryAboveBelowImage|CategoryAboveBelowImage.js
are not limited to file namespace. Let's leave this to more experienced administrators. --  Docu  at 06:52, 3 December 2011 (UTC)
Thanks for the error report; I've amended the section name. I'm not reverting; I used to take your insistence on prior consensus more seriously when I didn't know how little you care about consensus for things you want to happen. Rd232 (talk) 09:30, 3 December 2011 (UTC)
PS Those shouldn't even be on the "gadgets" page - they're not tools. But {{gadget-desc}}'s |page parameter doesn't seem to be working :( Rd232 (talk) 09:47, 3 December 2011 (UTC)
We just want to make sure things are checked before being implemented as it's important that experienced editors review these change before.
Understandably, you don't want to revert yourself, but the edit request isn't addressed to you. --  Docu  at 09:53, 3 December 2011 (UTC)
page parameter: I know you mentioned it before, but I forgot about. Sorry. Should be Pictogram voting keep.svg Fixed now. Please do not use numbers, instead use the reference now. If it does not work, let me know, please. -- RE rillke questions? 10:36, 3 December 2011 (UTC)
Have you seen this working? MediaWiki:Gadget-DropdownToTabbar could serve as a test case; it's not working for me. If/when it works, I'd make a helper template to translate the numbers to id names, for backward compatibility and easier use. Rd232 (talk) 12:24, 3 December 2011 (UTC)
No. Unfortunately, no js seems not to be loaded on the perferences page except the default ones by the software (mw and jquery, geoiplookup, bannercontroller, and the user's settings). Pretty useless. -- RE rillke questions? 12:46, 3 December 2011 (UTC)
That's disappointing. I can't find a related bug, if you want to file one to ask for JS to be loaded on it. Rd232 (talk) 13:15, 3 December 2011 (UTC)

I fear this is intended behavior. Gadgets are community developed and may contain unsave code. Of course we could make a hack to enable scripts here by replacing the target of the Preferences - link and instead run a JavaScript that either replaces the page with an iframe and listens for it's ready event or by sending a XHR and replace the page's contents with the altered result from the server for the preferences-page. -- RE rillke questions? 16:03, 3 December 2011 (UTC)

I wondered about it being the intended behaviour for security reasons... but I'm not sure if those security reasons are really more compelling on the Preferences page? If the concern is that a malicious gadget script could prevent a user deactivating it, it can always be disabled clientside (Javascript off) until someone with access deals with the script itself. Rd232 (talk) 16:09, 3 December 2011 (UTC)
I think the best is, if you ask a mediawiki developer directly or file a bug on bugzilla. If this whole software is documented that poorly, that you have to guess each "why", they have to deal with those questions. -- RE rillke questions? 16:29, 3 December 2011 (UTC)
There is an open bug related to this: Bug 18186. Helder 16:49, 4 December 2011 (UTC)

What should be "FilesCategories"? I like it more before this change. --Saibo (Δ) 02:01, 4 December 2011 (UTC)

MediaWiki:Gadget-section-FilesCategories: "Interface: Files and categories". It was originally "file pages", and I added "categories" to accommodate the category interface gadgets. I don't think any particular arrangement is ideal; I'm open to suggestions. Rd232 (talk) 17:11, 4 December 2011 (UTC)
Leave it ===Filepages=== and make a new section "Categorypages" if you do not want to have LongNames in the "others" section. "FilesCategories" is not really a word and unclear what it means (apparently it should mean File and category pages). Cheers --Saibo (Δ) 00:42, 5 December 2011 (UTC)
Your suggestion was my first instinct; but splitting would make each section rather short. And a new section could not be "CategoryPages" as some of the interface category gadgets also affect galleries and file pages. Rd232 (talk) 00:55, 5 December 2011 (UTC)

Docu, can you live with the current situation since the new heading reads "Interface: Files and categories"? And this is actually what they do: Changing the interface concerning categories. And BTW, you are responsible for the confusing gadget-name. If it is not related to files only, it should not have this name and this description. But now it is too late. Changing the gadget-name will make all users loose their setting concerning this gadget. But a better description what it actually does would be highly appreciated. -- RE rillke questions? 21:39, 26 January 2012 (UTC)

I think the confusion stems from newbies moving things around, out of their original context.
I'm not sure if the "interface" section is that great. It works well with things like "display of UTC time", but for other items?
As the gadgets are category related, I think it's perfectly fine in the category section where it was. --  Docu  at 19:45, 27 January 2012 (UTC)
Yes, interface is ambiguous. HotCat is also an interface. But until someone has a bright invention, I won't change anything again. -- RE rillke questions? 20:30, 27 January 2012 (UTC)
Somehow I think you contradict yourself: one side your saying the newbie change confuses you and the other side you don't want any change.
"Interface: Files" seems just as silly: the entire Commons is about files. I know some just get lost in "Commons:" namespace, but still .. --  Docu  at 22:06, 27 January 2012 (UTC)
"newbie change" -- never said this. Such a disrespectful wording, I would never use, Docu. And I did not say it confuses. If you want to do something constructive, you can think about how to reduce the count of the gadgets or how to improve their descriptions like you started with cc. The amount and cryptic words in the description or documentation, this was actually something confusing me when I started with Commons. -- RE rillke questions? 22:22, 27 January 2012 (UTC)
If the current description isn't understood in its context, they links should be placed back to where it was. It appears to be a newbie change as clearly the user making the change didn't understand what he was changing. As it's part of the learning process, there isn't really anything problematic about being a newbie. Obviously changing things and then saying it's confusing, that isn't really constructive. --  Docu  at 22:28, 27 January 2012 (UTC)
It is also not constructive to discuss here anymore since it seems to be impossible to for me to tell you that - when I say "when I started with Commons" - I found it confusing before that change. -- RE rillke questions? 22:47, 27 January 2012 (UTC)
In this case, I don't think you actually changed it. You are just saying the current situation is confusing. --  Docu  at 23:11, 27 January 2012 (UTC)

Arbitrary break[edit]

I've reviewed what the structure was before I changed it (here), and I see no reason to prefer the old one. Looking at the current structure, I see a possible slight improvement (it's a pity we can't have subheadings on the actual Preferences tab): if we move "search-in-category" to "FilesCategories", then everything that's left in "Categories" is a maintenance-related gadget. Make that a subheading of Maintenance (in the best form we can manage, which is Maintenance: Categories and the structure is then slightly clearer, I think. Still not great, but better. Rd232 (talk) 00:09, 28 January 2012 (UTC)

New groups[edit]

Is there a limitation how many times a gadget appears on the page?

Given that the topical sort is a bit problematic, maybe we could add additionals sections:

  • To make it easier to get an overview, maybe we could start with a short for frequently used gadgets that are not activated by default. (Might help new users. Selection can be done based on usage stats)
  • Further, to find new gadgets, we could add a section for gadgets created or substantially updated in the last three months. (Makes it easier for regular Commons users to find them)
  • Separately, it might help to list all gadgets that are de-activating features.
  • To conclude, we could list all gadgets that are activated by default.

Cheers. --  Docu  at 09:30, 11 February 2012 (UTC)

I don't know if that would be a good way to organise the Preferences page, but it sounds an excellent idea for a supplementary page (like Commons:Gadgets/Gadget-list say) which can be prominently linked from the top of the Preferences page. The advantage of a supplementary page is that users can watch it and see changes pop up on their watchlist. Finally, as a supplementary page it avoids radically changing the existing page, which will be less work and less likely to annoy an unknown number of people. The downside of a supplementary page would be that it couldn't (I think) use the existing Preferences il8n system, since you can't transclude MediaWiki namespace pages. Well whether it's ultimately a supplement or a replacement, it would help to do a draft to see what it might look like. Rd232 (talk) 12:12, 11 February 2012 (UTC)
Better focused sections should improve the readability of the current page.
If watchlisting is your concern, you can already watchlist this page.
Commons:Gadgets/Gadget-list wont be working properly as it wont show which tools one has activated. --  Docu  at 12:38, 11 February 2012 (UTC)
True. Maybe it would be helpful to provide a "watch this page" link from the top of the Preferences tab? Rd232 (talk) 13:48, 11 February 2012 (UTC)
I like the idea. Problem: We cannot access this page directly with JavaScript. Without JS duplicate gadget-entries seem to be impossible (not tested but it is a HTML-form that is posted and therefore duplicate names (lead to duplicate parameters) are impossible). Docu aren't you an admin in ? Just try it there.
I believe MediaWiki itself should offer a way to display by added-date, usage by active users, type of gadget/category. -- RE rillke questions? 13:16, 11 February 2012 (UTC)
User:Krinkle knows about plans in this area for the future. Sometime this year or next, I think, gadgets will be more like a directory and less like the current list. Rd232 (talk) 13:48, 11 February 2012 (UTC)
The front-end for users will not change on the short term. There's quite a few nice things coming in the near future in Gadgets 2.0. However those are mostly infrastructural changes. We've basically rebuild the Gadgets framework from the ground up in a way that is much more effeciënt and scalable. Among the new features are Gadget repositories (gadgets made on the repo wiki can be shared to all other wikis, much like "Commons" is for embedded files). However there are no significant changes for the end-users of gadgets in the next major version. But this code refactoring does enable a wide range features to be created in the future. Something I personally hope to get in Gadgets 3.0 would be removal of the static preferences tab, and instead introduce a more visual way of ordering, sorting, documenting and searching for gadgets. But for now we need to get Gadgets 2.0 in a stable state so that all existing features still work as expected, which is going to be a tough job considering that with a large wiki farm as the one of Wikimedia, there are practically no unused edge cases –Krinkletalk 14:15, 11 February 2012 (UTC)
Thanks for the explanation. Rd232 (talk) 15:32, 15 February 2012 (UTC)
I tried it at test: currently on gadget can only appear once on the page. I suppose that also avoid issues if the settings are not in identical. --  Docu  at 06:02, 15 February 2012 (UTC)
Right. So where does that leave us? Rd232 (talk) 15:32, 15 February 2012 (UTC)
To a sortable table. Ever bought at amazon? BTW, it is possible to use js, but I won't do (too busy): Bind and event listener to the preferences-link, e.preventDefault(), retrieve the preferences-page with an XHR, insert the body of that page into the DOM, add the functionality that is wanted. -- RE rillke questions? 23:42, 15 February 2012 (UTC)
A sortable table?? Lovely idea, but I don't see how that can be done without a lot of script magic (if script is really reliable as a method; sounds like a security loophole that might get fixed). Rd232 (talk) 00:28, 16 February 2012 (UTC)
They won't get "the loophole fixed". This would require using a different serverdomain for the prefs. And yes, it would require a lot of coding to create such a table. -- RE rillke questions? 00:47, 16 February 2012 (UTC)
A sortable table seems a good idea. --  Docu  at 06:00, 16 February 2012 (UTC)

Browser requirement[edit]

Is it OK to have as a gadget a script that doesn't work in IE8 or older (but works in Chrome, Firefox etc)? I'd like User:Magog the Ogre/cleanup.js to be a gadget... Rd232 (talk) 00:02, 8 August 2012 (UTC)

Can you elaborate on "doesn't work"? –Krinkletalk 01:12, 8 August 2012 (UTC)
User_talk:Magog the Ogre/cleanup.js/Archive#IE8. It was over a year ago so my memory is somewhat vague, but my tests in IE8 had the script literally freeze the browser. Magog the Ogre (talk) (contribs) 14:00, 8 August 2012 (UTC)
It is ok to have such a script, I think. The fact however must be noted at the gadget's definition and the script must disable itself automatically in incompatible browsers. addOnloadHook is deprecated. There is still invalid JS at /\|(\s*[Dd]ate\s*\=[^\{]*\s*)(\d{4})\s*([\\\\\\/\.\s])\s*(\d{1,2})\s*\3\s*(\d{2})(?!\d)/mg -- Rillke(q?) 15:08, 8 August 2012 (UTC)
How in the world did you manage to find that? Magog the Ogre (talk) (contribs) 16:48, 8 August 2012 (UTC)
There is a lot more work: (use /*jshint maxerr:1000*/). Especially undeclared variables should be fixed. -- Rillke(q?) 17:18, 8 August 2012 (UTC)
Oh I know the script is an utter mess. I only recently found out about JSLint and... not programming it so it looks to an outsider like a three year old was just mashing on the keys. Magog the Ogre (talk) (contribs) 18:27, 8 August 2012 (UTC)

Descriptions at Special:Gadgets are unclear[edit]

Special:Gadgets is the description page for Special:Preferences#mw-prefsection-gadgets.

I believe many of these gadgets would be used a lot more if people could figure out what they do without having to turn them on first. Even when they do turn them on they may not be able to figure them out, or use all their capabilities.

So longer descriptions, even a few more words, or an additional sentence for some of the items, would help a lot. Some of the descriptions need to be rewritten altogether.

Almost no one has the time to turn them all on to figure them all out. --Timeshifter (talk) 22:11, 9 August 2012 (UTC)

Well, better than descriptions are real documentation − we start to have quite a lot in Special:Gadgets(and even translated), but we sure need more help with that… Jean-Fred (talk) 19:40, 10 August 2012 (UTC)
I think we are talking about 2 separate things. People can go to to translate all of the short gadget descriptions at once on the Special:Gadgets page, or Special:Preferences#mw-prefsection-gadgets. We could even put a translate box there ourselves. So I think we should start there first. Other people can and should work on more detailed documentation and translation at the individual doc pages listed at Category:Gadget script documentation. --Timeshifter (talk) 01:57, 11 August 2012 (UTC)
Special:Gadgets is the description page for Special:Preferences#mw-prefsection-gadgets. - well actually it isn't (descriptions are stored in individual MediaWiki pages, eg MediaWiki:Gadget-HotCat), but that's not important. I totally take your point about gadget functionality needing to be clearer on the Preferences page; I did actually improve a lot of the English descriptions a bit a while ago. Some are fairly self-explanatory; some others have documentation links. We could provide more detail in individual descriptions - even mini-screenshots - but it would make the whole preferences page much bigger. A click or hover to expand solution might work, but that would need MediaWiki changes, since normal javascript is blocked on that page. Also, there is supposed to be a whole new approach to gadgets coming to MediaWiki maybe later this year, and I've no idea what that will look like. Rd232 (talk) 00:21, 11 August 2012 (UTC)
OK, I see now that Special:Gadgets has more info. I think Special:Preferences#mw-prefsection-gadgets should be completely redone. I hope Gadget 2.0 does so. I suggest a table of contents, and an additional gadget tab page or two in My Preferences. I also believe that all the descriptions on Special:Preferences#mw-prefsection-gadgets should be typed there, and not transcluded. That would help tremendously. I could rewrite and make better, short, clear descriptions for many of the gadgets. Others could too. But it needs crowd sourcing the same as any other text page on Wikipedia. Or at least simpler access. Edit-protected page that any admin can edit directly. I am talking about the descriptions only. There should be a space for descriptions after each gadget. On the Special:Preferences#mw-prefsection-gadgets tab page itself. --Timeshifter (talk) 01:55, 11 August 2012 (UTC)

Autocomplete gadget[edit]

adds autocompletion for templates and links (including categoeries) to editbox

{{editprotected}} I would like to import here he:MediaWiki:Gadget-autocomplete.js, a gadget that adds autocompletion for templates and links (including categoeries) to editbox. To import it please create the following pages, and then add the gadget to the list of available gadgets (Probably under Interface=>Editing):

Thanks, ערן (talk) 11:14, 14 July 2013 (UTC)

  • Can this be enhanced so the dropdown is shown below or directly above the position that deserves autocompletion?
  • For templates, can a tooltip be shown containing the description entered in TemplateData?

-- Rillke(q?) 13:24, 14 July 2013 (UTC)

  • It is too complicated to position the autocomplete in the caret position (and to make it work in any browser).
  • I would like to keep the gadget simple and fast. It is mainly for linking (categories and links), while templates syntax ({{templatename}}) is just a bonus. Hints and wizards for templates are different feature , and there are good tools for that (VE, TemplateParamWizard - the last one "recognize" this gadget and use it).
ערן (talk) 14:18, 14 July 2013 (UTC)
Ok. This will stay one week open and I announce it at COM:VPP. -- Rillke(q?) 15:01, 14 July 2013 (UTC)
Just a reminder. Neukoln (talk) 19:12, 21 July 2013 (UTC)
There was no reaction; how should I interpret this? Implied consent? -- Rillke(q?) 20:45, 21 July 2013 (UTC)
Symbol support vote.svg Support Oh, Commons need definitely something like this, because Commons works mostly with templates and they are a huge amount of this. -- Perhelion 08:21, 4 June 2014 (UTC)
Whoa, slow down there. Let's not make any hasty decisions. This topic hasn't even been open for one whole year! --Dschwen (talk) 17:46, 4 June 2014 (UTC)

Commons Commander[edit]


Commons Commander ran on Toolserver, but Magnus Manske won't port it to Labs. Please remove it from the list. --Tacsipacsi (talk) 11:13, 29 July 2014 (UTC)

✓ Done --Steinsplitter (talk) 11:17, 29 July 2014 (UTC)

Turn on MediaWiki:Gadget-CategoryAboveBelowImage.js[edit]


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

@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)
@Steinsplitter: thx → phab:T102776 --El Grafo (talk) 11:45, 17 June 2015 (UTC)

Gallery Details Gadget[edit]

Per Commons:Village_pump#Gallery_Details_Gadget, please replace

* GalleryDetails|GalleryDetails.js


* GalleryDetails[ResourceLoader]|GalleryDetails.js

-- Tuválkin 11:53, 10 September 2015 (UTC)