That seems like a massive overreaction. The topic is now resolved and there's been no vandalism for several days, so hopefully it will just die down. * Pppery *it has begun22:27, 14 March 2024 (UTC)
This seems to have died now. For future reference it appears summary edits are prevented if you protect the entire board, even though they aren't if you protect only the topic. * Pppery *it has begun02:32, 26 March 2024 (UTC)
Semi protect Snippets/*
Latest comment: 2 years ago2 comments2 people in discussion
There were some IP edits for Snippets/*. Some bad users may inject these snippets with security vulnerability.--حبيشان (talk) 06:24, 15 April 2024 (UTC)
Latest comment: 1 year ago2 comments1 person in discussion
This page has been archived. Error resolved. There is an error loading the subpage (due to it being such a large board). The issue is being investigated. Sorry for the inconvenience, and thank you for your patience.Quiddity (WMF) (talk) 17:17, 6 December 2024 (UTC)
P.s. As a reminder, the DiscussionTools system that is now working on this talkpage, provides a menu link at "Tools → Subscribe" that enables us to be notified for the creation of new Topics (documentation at Help:DiscussionTools#Page subscriptions). Some folks watching this page, might like to use that system instead or in addition to the watchlist. Hope that helps! Quiddity (WMF) (talk) 14:56, 10 December 2024 (UTC)
Latest comment: 1 year ago4 comments2 people in discussion
User:BonziStudios (contribs) has newly created translations in the following 27 languages, but they appear to be machine-translated:
ang, ar, de-at, el, eo, es, fa, fr, he, it, ja, ka, ko, lt, nan, nl, pl, ps, pt, pt-br, ru, sco, tr, tw, uk, yue, zh - Shirayuki (talk) 08:05, 8 December 2024 (UTC)
It seems that edits need to be recent to be listed in Special:Nuke. However, since more than three months have passed since the edits by the user, they are not listed and cannot be deleted in bulk. I have reviewed and manually deleted the Japanese translations made by the user. As for translations into other languages, I am unable to determine whether they are machine translations. Shirayuki (talk) 11:31, 8 December 2024 (UTC)
I also cleaned up some Arabic translations (123). The Arabic translations were clearly unmodified machine translations from the unreliable MinT. I would support disabling automatic translation from MinT since it is making multiple issues both to reviewing translators, and readers. ToadetteEdit (talk) 12:01, 8 December 2024 (UTC)
Deleting empty /LQT Archive 1 pages
Latest comment: 1 year ago5 comments4 people in discussion
Done Deleted about 650 pages via Special:Log/Flow cleanup bot and about another 100 after manual review using my own account. Some of the remaining 340 pages could probably be deleted too but I was a bit paranoid, and keeping a history of the header will be useful if I decide to follow through with my idea of converting Flow pages to wikitext with history using XML import. * Pppery *it has begun19:24, 10 December 2024 (UTC)
Unprotect
Latest comment: 1 year ago2 comments2 people in discussion
Reduced to semi. It seems the reason was users were asking questions that went unanswered and are more suited for other places (this can still be the case given the page name). – Ammarpad (talk) 13:23, 11 December 2024 (UTC)
empty category
Latest comment: 1 year ago2 comments2 people in discussion
not the same text when I'm logged in and logged out
Latest comment: 1 year ago6 comments3 people in discussion
Sometimes I find a translation that is not "perfect" and I improve it. When I come back on this page a few days later, I still see the old text even if I refresh the page (with F5) or use another browser BUT ONLY WHEN I am logged in. When I am logged out, I can see the new translation text. It seems that this problem only occurs when I change the translated title of a page.
An example: when I am logged out, the title of this page is "Catégorie:Extensions liées à FileUpload" (it is the text that I wanted). When I am logged in (with this account), I see the old (and bad according to me) translation: "Catégorie:extensions de téléversement de fichiers".
No one can fix your account. It may be due to caching issues on your browser, you should now see "Catégorie:Extensions liées à FileUpload" as the title of the category. ToadetteEdit (talk) 19:28, 11 December 2024 (UTC)
Like I said, the problem was on several browsers so it was not a cache issue. But this page works now, thanks for the fix.
I had the same problem with this page but I just solved it by myself: I changed a translation not in the title then restored it and the title has been updated. Which means probably a bug somewhere. Mahabarata73 (talk) 13:57, 12 December 2024 (UTC)
Like I said, the problem was on several browsers so it was not a cache issue.
Latest comment: 1 year ago9 comments4 people in discussion
Next up on the list of tasks to do before the Flow maintenance script runs: make sure pages that on pages that have an existing archive structure the Flow board becomes part of that archive structure rather than becoming its own alien thing and orphaning the existing archive structure behind a pointer to a Flow board. I've manually processed pages with odd archiving setups (of which there are annoyingly large number), leaving around 200 pages where there's a pre-existing /Archive or /Archive 1 page. It seems to me that these can be processed automatically by:
If the old archive is named "/Archive", move it to "/Archive 1" since it's not the only archive. (does a redirect need to be left behind here)
Move the Flow board to "/Archive 2".
If there's an old "/LQT Archive 1" page like Extension_talk:Include, then move it back for the history (and then needs manual review on how to update any pointers). Otherwise, create the page with {{Archives}}.
Re: "(does a redirect need to be left behind here)" - I think it would be fine to leave/create redirects, in order to avoid having to manually check for incoming links on each of them. Plus I believe the ancient essay w:WP:Redirects are cheap is still generally accurate.
Done. I ended up deleting most of the /LQT pages rather than moving them. And I got sidetracked by more pages with odd archival setups. I think that at this point for every Flow page the maintenance script will move there aren't any other archives left so the maintenance script's action is a reasonable one. And hopefully I'm done now. * Pppery *it has begun01:24, 13 December 2024 (UTC)
I was wrong. I found a lot more bits of old spam/junk during the post-cleanup-script review. Going to semi-automatically delete another few hundred to thousand pages of junk in user talk namespace. * Pppery *it has begun22:24, 17 December 2024 (UTC)
Running a bot to delete 1887 user talk pages of users with <100 global edits that have never been touched by anyone with >500 global edits. I manually reviewed the content of each page beforehand, and excluded 666 pages (most of which are requests for support that should have gone to the support desk years ago). * Pppery *it has begun03:31, 18 December 2024 (UTC)
And now done. I spot-checked some of the remaining Flow pages and was not inclined to delete any of them. So I think that route is satisfied and the remaining pages will be converted to wikitext sometime. * Pppery *it has begun23:23, 18 December 2024 (UTC)
Can I use mediawiki.org to host templates?
Latest comment: 1 year ago2 comments2 people in discussion
The en wiki citation templates made a change a few years ago that make it a lot harder to set up citation templates locally and for developers. The citation templates now require a file that's on commons, which local installations and third party wikis aren't usually set-up for.
I've fixed my local installations but I was wondering if I could put my "fixed" templates online somewhere to make it easier for third parties and developers to download... is "Module:" namespace only for stuff actually being used by mediawiki.org? Could/should I instead host the modules and templates as a subpage of Citoid, i.e. Citoid/Module:Citation (and is that an okay use of mediawiki.org? Since T121470 does not exist yet. Mvolz (WMF) (talk) 13:12, 12 December 2024 (UTC)
It's fine with me, but make sure to link to the originals in the edisummaries and add some documentation, for when someone finds it in 3 years and wonders why we have this duplicate :D —TheDJ (Not WMF) (talk • contribs) 13:36, 17 December 2024 (UTC)
templates with 2 categories but only one is visible
Latest comment: 1 year ago4 comments2 people in discussion
If you look at the source code of this template, you will see that there are 2 categories inside "includeonly" tags:
Category:MediaWiki hooks
Category:Undocumented MediaWiki hooks
But on pages using this template, for example this page, only the first category is visible.
Why? The template says "if you know about it then add a doc" (I summarize). But if no one can see this category, don't you think that limits the interventions on these pages? Mahabarata73 (talk) 21:59, 14 December 2024 (UTC)
Latest comment: 1 year ago1 comment1 person in discussion
Hello Mediawiki contributors,
I hope that you are in good spirits. My name is Chinmayee Mishra and I am a part of the Let’s Connect working group - a team of movement contributors/organizers and liaisons for 7 regions: MENA | South Asia | East, South East Asia, Pacific | Sub-Saharan Africa | Central & Eastern Europe | Northern & Western | Latina America.
Why are we outreaching to you?
Wikimedia has 18 projects, and 17 that are solely run by the community, other than the Wikimedia Foundation. We want to hear from sister projects that some of us in the movement are not too familiar with and would like to know more about. We always want to hear from Wikipedia, but we also want to meet and hear from the community members in other sister projects too. We would like to hear your story and learn about the work you and your community do. You can review our past learning clinics here.
We want to invite community members who are:
Part of an organized group, official or not
A formally recognized affiliate or not
An individual who will bring their knowledge back to their community
An individual who wants to train others in their community on the learnings they received from the learning clinics.
To participate as a sharer and become a member of the Let’s Connect community you can sign up through this registration form.
Once you have registered, if you are interested, you can get to know the team via google meets or zoom to brainstorm an idea for a potential learning clinic about Mediawiki or just say hello and meet the team. Please email us at letsconnectteam@wikimedia.org . We look forward to hearing from you:)
I think it make sense to use the script to convert pages to wikitext, buy I need to make sure if only sysops can use the script because your archived page history sees that it has been imported, and importing is restricted to sysops and users in the import user group, and I am not in any of them. ToadetteEdit (talk) 17:11, 25 December 2024 (UTC)
Anyone can use the script to generate XML. Only users in the Special:ListUsers/import group (which can be granted and removed by crats, and currently includes no non-crat users) can actually import XML on-wiki. I'll handle actually running it when the time comes - what I was hoping for here was more people confirming the idea makes sense, checking the output to make sure I didn't screw anything up, etc. * Pppery *it has begun17:34, 25 December 2024 (UTC)
I don't think we should allow translations to Akan because 1) the language is missing in the translate interface, and 2) it can get outdated for a long time. I suggest importing existing translation to Twi language subpages as it the the most appropriate language. ToadetteEdit (talk) 19:00, 1 January 2025 (UTC)
Latest comment: 1 year ago2 comments2 people in discussion
I think I just got caught in Special:AbuseFilter/95 -- please could someone create user:a smart kitten for me as a blank page, so that I can add to it myself? (In response to MediaWiki:Abusefilter-globaluserpages, what I want to put in my mediawikiwiki userpage is specific to this wiki, and e.g. a link to my Phabricator profile would have less relevance on a global userpage than on a MediaWiki-specific userpage.)
@Pppery, I suggest a new abuse filter be set up to prevent "this is racism" posts from being sent onto talk pages. Protection is evidently not enough, as the users will simply "wait outside" and immediately vandalism once protection is over, and the fact that Support Desk questions are from new users and protection will prevent them from asking questions. Yesterday I saw that sort of post that was reverted and revdelled on a user talk page. ToadetteEdit (talk) 07:26, 11 January 2025 (UTC)
Latest comment: 1 year ago3 comments2 people in discussion
Hi! Special:Contributions/103.115.243.181 has just made a series of 15 non-translation related disruptive edits to Help:Reset password/bn but I can't undo them all myself because I don't have local rollback, and manual reverts and TwinkleGlobal don't seem to work on translation pages? They also created a bunch of nonsense subpages. [[Project:Administrator's noticeboard]] redirected to here so I'd thought I'd just post this. Thanks! :) MolecularPilot (talk) 03:51, 21 January 2025 (UTC)
Undone. Translate extension works in an odd way which means that what the IP did was technically a page creation and hence undoing it was a deletion which needed admin rights. * Pppery *it has begun04:28, 21 January 2025 (UTC)
Latest comment: 1 year ago7 comments3 people in discussion
Given that the Village Pump (and other discussion pages) transitioned from Flow to standard discussion pages, a bot that archives threads should be considered. ToadetteEdit (talk) 10:10, 7 December 2024 (UTC)
I wonder if we try 14 days first just to give people a bit more of a chance to respond, we can always review and change later one.
I would archive to a number subpage, Year wouldn't be too bad for VP but I suspect that Support Desk might get too large. P858snake (talk) 11:52, 22 January 2025 (UTC)
Latest comment: 1 year ago2 comments2 people in discussion
Please move Help:Extension:UniversalLanguageSelector/Input_methods/zh-pinyin-transliteration to Help:Extension:UniversalLanguageSelector/Input_methods/zh-latn-pinyin-transliteration for the link change in the ULS input method menu. -- Winston Sung (talk) 15:48, 23 January 2025 (UTC)
Universal Code of Conduct annual review: provide your comments on the UCoC and Enforcement Guidelines
Latest comment: 1 year ago1 comment1 person in discussion
Please help translate to your language.
I am writing to you to let you know the annual review period for the Universal Code of Conduct and Enforcement Guidelines is open now. You can make suggestions for changes through 3 February 2025. This is the first step of several to be taken for the annual review.
Read more information and find a conversation to join on the UCoC page on Meta.
do you have any idea which is the word for all images except svg? that word is not listed in the link you gave. if you dont know what i'm talking about, then you dont know. RoyZuo (talk) 17:01, 27 January 2025 (UTC)
Latest comment: 1 year ago2 comments2 people in discussion
Hello everyone! If someone performs mass translations on a large scale (e.g. hundreds of changes a day), is it appropriate to grant a flood flag (temporary; ofc not to clutter the RC feed)? I haven't found anything on this subject, so I'm asking. Best regards, BZPN (talk) 16:05, 27 January 2025 (UTC)
There is no flood flag on this wiki. It would also be inconvenient to temporarily promote users to the bot user group, which is the only user group that has the bot userright which makes edits not appear on recentchanges. ToadetteEdit (talk) 18:16, 27 January 2025 (UTC)
Latest comment: 1 year ago4 comments2 people in discussion
User is disruptively editing - including blanking, test edits, messing with other people's userspace etc. Already warned several times by another user, and continued (I just cleaned up after them messing with someone's userspace, and then they did it again!). Can they please be blocked to prevent this disruption? Thanks :) MolecularPilot (talk) 02:25, 27 January 2025 (UTC)
Reminder: first part of the annual UCoC review closes soon
Latest comment: 1 year ago1 comment1 person in discussion
Please help translate to your language.
This is a reminder that the first phase of the annual review period for the Universal Code of Conduct and Enforcement Guidelines will be closing soon. You can make suggestions for changes through the end of day, 3 February 2025. This is the first step of several to be taken for the annual review.
Read more information and find a conversation to join on the UCoC page on Meta. After review of the feedback, proposals for updated text will be published on Meta in March for another round of community review.
Please share this information with other members in your community wherever else might be appropriate.
Latest comment: 1 year ago1 comment1 person in discussion
I have a good idea. But now I am not sure what I am very much looking for the needs. If you are unable to find the right solution to this problem. Please let me know if you have not already received the package yet. I will be notified of this order soon as I have it. 41.123.107.22901:43, 11 February 2025 (UTC)
Report concerning User:151.255.36.98
Latest comment: 1 year ago2 comments2 people in discussion
Latest comment: 1 year ago3 comments2 people in discussion
I’m not entirely sure if this is the right place to ask, as I mainly contribute to Wikipedia and rarely visit MediaWiki, but I’d appreciate any help or clarification on this.
I recently tried to build a template in Ukrainian Wikipedia based on a module imported from English Wikipedia and noticed that the module (which has its own page here on MediaWiki) relies on several predefined separator messages from MediaWiki, namely:
These messages are used by the module to format link toolbars properly. The module also includes a dot separator parameter, which links to MediaWiki:Dot-separator. While this message exists in English Wikipedia, it does not exist at the MediaWiki level, meaning that for the module to work properly, each wiki has to manually create this page. Moreover, this namespace is often restricted, making it difficult for local communities to create new pages when needed.
The module has already been imported into multiple wikis, but MediaWiki:Dot-separator is mostly missing at the local level (I haven’t checked all wikis, but I haven’t seen it outside of English Wikipedia). Would it be possible to add MediaWiki:Dot-separator on the MediaWiki level with the same content as in English Wikipedia? Gzhegozh (talk) 15:34, 14 February 2025 (UTC)
These bots, and their operators, have been inactive on mediawiki.org for 5+ years, or have explicitly retired. Therefore, the bot flags might be candidates for removal. Three Sixty (talk) 21:52, 20 February 2025 (UTC)
Upcoming Language Community Meeting (Feb 28th, 14:00 UTC) and Newsletter
Latest comment: 1 year ago1 comment1 person in discussion
Hello everyone!
We’re excited to announce that the next Language Community Meeting is happening soon, February 28th at 14:00 UTC! If you’d like to join, simply sign up on the wiki page.
This is a participant-driven meeting where we share updates on language-related projects, discuss technical challenges in language wikis, and collaborate on solutions. In our last meeting, we covered topics like developing language keyboards, creating the Moore Wikipedia, and updates from the language support track at Wiki Indaba.
Got a topic to share? Whether it’s a technical update from your project, a challenge you need help with, or a request for interpretation support, we’d love to hear from you! Feel free to reply to this message or add agenda items to the document here.
Also, we wanted to highlight that the sixth edition of the Language & Internationalization newsletter (January 2025) is available here: Wikimedia Language and Product Localization/Newsletter/2025/January. This newsletter provides updates from the October–December 2024 quarter on new feature development, improvements in various language-related technical projects and support efforts, details about community meetings, and ideas for contributing to projects. To stay updated, you can subscribe to the newsletter on its wiki page: Wikimedia Language and Product Localization/Newsletter.
We look forward to your ideas and participation at the language community meeting, see you there!
Latest comment: 1 year ago5 comments4 people in discussion
There is no page to discuss controversial deletion on this wiki, so i thought i'd open a thread here. Basically this page shows up when you google "mediawiki consulting prices" which i think is confusing. I'm not sure the joke is funny enough to bother keeping, and would suggest deleting. Or maybe blanking the way we do for archived extensions, with a link to see old version. I don't know, if __NOINDEX__ works in that namespace maybe that. Perhaps just a really big banner on top indicated that the page is sarcastic would be sufficient. Anyways, I was wondering what other people thought about this. Bawolff (talk) 19:27, 30 January 2025 (UTC)
I think it's OK to keep, but a clear notice should be provided saying that it is a joke and retained only for humourous purposes (the category at the bottom won't work). Leaderboard (talk) 13:29, 11 February 2025 (UTC)
Latest comment: 1 year ago16 comments5 people in discussion
When the new documentation for CodeMirror was introduced at the end of last year, it looks like the documentation for CodeMirror 5 was deleted after a copy-and-paste move to Extension:CodeMirror/5. However, while the history of the page was undeleted and merged to the new title, it looks like the previous page's translations are still deleted.
Is it possible (and/or desirable) for these translations to be restored & moved to the new title for the CodeMirror 5 documentation? IMO it would be best if this could happen, due to the work that will have been put into translating the previous page, & to preserve the internationalization of the previous documentation. I admit that I don't know exactly how this would be done, though -- would all the old Translations:Extension:CodeMirror-pages have to be undeleted & moved to match the new title? Or could the old translated pages (e.g. Extension:CodeMirror/fr) be restored & moved to (e.g.) Extension:CodeMirror/5/fr, the translation units on Extension:CodeMirror/5 restored, and the page re-marked for translation?
It is possible technically but they needs to share the same divisions. The more different, the more work to do this. The page itself must be marked for translation. wargo (talk) 22:08, 22 February 2025 (UTC)
Based on what I can see, it seems like Special:Permalink/6856129 (in the history of Extension:CodeMirror/5) might be the version of the page immediately before the translations were deleted. If this is the case, would restoring this version of the page (until the translations are restored) resolve the issue around needing to have the same divisions? Best, —a smart kitten[meow]14:43, 23 February 2025 (UTC)
My thoughts are there's not much value in continuing to translate outdated docs. Yes, CodeMirror 5 is still being used in WMF production, but no one should be building any integrations against it at this point. I should have preserved the revision history, though… I know better than that. Sorry. If there's enough demand (it sounds like there is) I can write a script to get the translations back, but ideally we'd prevent new translations from being added. — MusikAnimaltalk22:36, 22 February 2025 (UTC)
Yes, I thought there was a feature for this. Thank you. Okay, I will get the translations restored ;) I have a similar script from some time ago that hopefully still works. If not, please bear with me as I'm quite busy with other matters.
I don't recall exactly, but could it be that I was unable to move the page due to the volume of translations and/or combined revision count? I know I must have tried moving the page, first… Anyway, I'll get this cleaned up. Belated thank you to Pppery for restoring the history, and to all here for bringing this to my attention. — MusikAnimaltalk00:32, 23 February 2025 (UTC)
IIRC you would have needed sysadmin rights to move the page since it had more than 500 parts - but you appear to be a sysadmin which makes you omnipotent. * Pppery *it has begun01:58, 23 February 2025 (UTC)
This is a stupid argument to have, but puppet says you're in restricted, which I had thought was sufficient (although it would have put you in the T378429 situation). Anyway, not knowing what you were doing well enough to carry out the move the proper way is a satisfactory historical answer, so I'll not continue this line further. * Pppery *it has begun05:17, 23 February 2025 (UTC)
I don't think we need to even "discourage" translations - there's value in ensuring that people not proficient in English can read "outdated" information. Leaderboard (talk) 03:31, 23 February 2025 (UTC)
I've also restored the history of the translated pages, and fixed a few units whose fuzzy status was lost. It looks like some of the translate units weren't copied over properly though, compare this diff, for example. * Pppery *it has begun14:11, 12 March 2025 (UTC)
It also looks like the Page display title translations may have not made it over from the previous title. (Thank you for running the script, MusikAnimal, & for restoring the histories, Pppery:)) Best, —a smart kitten[meow]15:06, 12 March 2025 (UTC)
Latest comment: 1 year ago2 comments2 people in discussion
Hello, I’ve created a page at The Creative Processes Workshop to demonstrate how MediaWiki could be used by a psychotherapy center to document creative therapy techniques. The content is intended as a hypothetical example of MediaWiki’s application, not as promotion. Is this acceptable, or does it need adjustments? Thanks! Allocht 12.03.25 Allocht (talk) 01:38, 12 March 2025 (UTC)
The page you attempted to create at הסדנה לתהליכים יצירתיים, before being blocked by the abuse filter, is not in my opinion within this website's scope. We already have plenty of testimonials about how other websites view MediaWiki's features in places like MediaWiki testimonials/Sites using MediaWiki, and what you wrote seems very run-of-the-mill and doesn't stand up enough above those to warrant a separate page. * Pppery *it has begun04:57, 24 March 2025 (UTC)
Request for Edit Permission on GrowthExperiments/Help
Latest comment: 1 year ago2 comments2 people in discussion
Hello, I’m AyushKhati, an Outreachy applicant working on task T389124 to add debug logging instructions to GrowthExperiments/Help. My edit was disallowed due to new user restrictions and possibly an external link (Phabricator task). I’ve set up a local MediaWiki instance and aim to improve documentation. Could an admin please grant me edit rights or advise on how to proceed? Thank you! — Preceding unsigned comment added by Ayush Khati (talk • contribs) 21:06, 17 March 2025 (UTC)
Apologies for the delayed response. GrowthExperiments/Help does not exist, and it seems like per phab:T389124#10645245 creating a separate page is not the desired solution, so I'm not inclined to exempt you from the mainspace filter. The link spamming filter is very lenient - just making your edit without adding links and then adding them later would avoid it. * Pppery *it has begun05:00, 24 March 2025 (UTC)
Merge request
Latest comment: 1 year ago4 comments4 people in discussion
I do not see much use anymore for having both around either. So, FWIW, I'm all for merging them! With the phab:NNN#CCC interwiki link, I'm not sure any of them is actually still needed? Anyway, I think it would be good to merge them. --QChrisNonWMF (talk) 06:11, 22 March 2025 (UTC)
I guess there is some bug here. The page appears to be fully protected but I couldn't find the relevant logs, and I can see IP edits from almost two decades ago. Sounds illogical, but how this page is protected and when was it protected. It doesn't make sense to me... ToadetteEdit (talk) 09:15, 25 March 2025 (UTC)
I've reduced the protection to semi. Since it's translatable nobody can really do anything that bad there as stuff won't show up in the actual sandbox until it's marked. * Pppery *it has begun18:05, 25 March 2025 (UTC)
Report concerning User:128.75.116.72
Latest comment: 1 year ago2 comments2 people in discussion
Latest comment: 1 year ago8 comments5 people in discussion
Hello. A policy regarding the removal of "advanced rights" (administrator, bureaucrat, interface administrator, etc.) was adopted by global community consensus in 2013. According to this policy, the stewards are reviewing administrators' activity on all Wikimedia Foundation wikis with no inactivity policy. To the best of our knowledge, your wiki does not have a formal process for removing "advanced rights" from inactive accounts. This means that the stewards will take care of this according to the admin activity review.
We have determined that the following users meet the inactivity criteria (no edits and no logged actions for more than 2 years):
These users will receive a notification soon, asking them to start a community discussion if they want to retain some or all of their rights. If the users do not respond, then their advanced rights will be removed by the stewards.
However, if you as a community would like to create your own activity review process superseding the global one, want to make another decision about these inactive rights holders, or already have a policy that we missed, then please notify the stewards on Meta-Wiki so that we know not to proceed with the rights review on your wiki. Thanks, EPIC (talk) 16:49, 22 February 2025 (UTC)
@Pppery: so should we take this as Catrope's flags should be kept? If that should be your only exception here I assume the rest could be removed though (including Matanya who has agreed to removal). EPIC (talk) 20:07, 14 March 2025 (UTC)
I guess so ... I'm not happy with the lack of community input from anyone other than myself here, but, unless anyone else comments, keep Catrope and remove everyone else. * Pppery *it has begun20:08, 14 March 2025 (UTC)
I'd actually recommend the removal of the sysop flag of Catrope as well. The last time it was used was 7 years ago. Also considering that sysop rights isn't that difficult to get here and the lack of input from Catrope, there really isn't any strong reason to exclude his flag removal. Minorax (talk) 07:01, 23 March 2025 (UTC)
I agree with Minorax. Obviously it is not needed for Catrope. If the user needs the rights for their WMF account, they could request it via the WMF process. --Ameisenigel (talk) 08:42, 23 March 2025 (UTC)
Flow cleanup bot supervised run nearing completion
Latest comment: 1 year ago19 comments4 people in discussion
Just a heads up to the community - I've basically finished my manual testing of User:Flow cleanup bot. A bunch of quirks are documented on the user page, but I'm at this point satisfied that it does everything that is practical to do, even though it isn't a perfect representation.
I intend to run the bot in unsupervised mode to convert all ~8500 Flow boards to wikitext some time in late February or early March. This is your last chance to comment on the matter. * Pppery *it has begun03:34, 12 February 2025 (UTC)
I don't right now. It's on my queue to wrangle those later, but not something I've coded yet, or will code in the immediate future. While for the supervised bits I've often been deleting the Flow board my plan for the main bot run is to let Flow talk page manager move to page to "Pagename/Flow" and then overwrite the stub it leaves behind with the export so the links will continue to work until Flow is fully uninstalled. * Pppery *it has begun18:20, 15 February 2025 (UTC)
Things are happening slower than I expected. It's now looking like this will happen mid to late March (and I'm going to extend the temporary rights on Flow cleanup bot, which will expire before then). * Pppery *it has begun03:07, 1 March 2025 (UTC)
@Pppery: the bot is importing some pages to <talk page title>/Flow export (e.g. [1], [2]). Just to double-check, is this something that anyone needs to worry about/do anything about, or will things end up fixing themselves? Best, —a smart kitten[meow]21:34, 11 March 2025 (UTC)
It's intended for now. If there's an empty stub with no content (or a redlink) at the base page it puts the export there, otherwise it puts it at /Flow export since I don't want to clobber the Flow board for reasons explained earlier in this thread. I'm honestly not sure what to do in those cases. My thinking for now is to leave them at /Flow export until Flow is fully undeployed, and then move them to the title without /Flow export. Other suggestions welcome. * Pppery *it has begun21:37, 11 March 2025 (UTC)
The main bot run has now finished, importing ~8000 exported Flow boards. I'm going to process the special cases it punted on or skipped tomorrow, since it's after midnight in my timezone now. * Pppery *it has begun04:29, 12 March 2025 (UTC)
I've finished cleaning up almost all of the edge cases now. At this point the only Flow board that still needs importing is the support desk, which is being a pain due to its huge size (even just one month's worth of posts is several times more content than the import interface will tolerate). I'll deal with that somehow tomorrow. * Pppery *it has begun03:30, 15 March 2025 (UTC)
Perhaps it could have been, but I've decided to modify the script to just do the import in batches of 50 revisions, which is slightly ugly but works. * Pppery *it has begun14:08, 15 March 2025 (UTC)
Even that was a pain at times, and took hours with several false starts. Anyway, I've now finally imported the support desk, so I hereby declare this phase of Flow deprecation is complete. I do still plan to do a bot run to fix links to "Topic:" pages as I suggested above later, but first I'm going to take a long break from editing MediaWiki.org because I've been working on this pretty much nonstop for days and it's probably proved to be one of the hardest coding projects I've ever done in my life. * Pppery *it has begun01:50, 16 March 2025 (UTC)
I've started writing and testing the code to fix links to the topic namespace, replacing them with the DiscussionTools header or comment ID. Examples at Special:Contributions/Pppery (alt). This is going to be like before, where there's a main bot run and then a lot of edge-case fixes where something about the Flow structure means I can't find the header or comment they intended to link to ...
Finally this only fixes local links on MediaWiki.org, of course. Links on other websites are going to have to die, or be dealt with via another process like phab:T389680. It isn't really practical to maintain a database of topic -> wikitext export links for every single topic as there are 100,000 of them and the current code is best-effort not 100% accurate.
I have now gone a head and fixed links to both Flow topics and LiquidThreads threads. Which I had expected to be a fairly simple project, but instead ended up taking a full day of work and stumbling across so many edge cases, including a former admin clobbering some talk page comments from 2014 by invoking Cthulhu (okay, that's slightly embellished). * Pppery *it has begun19:29, 27 March 2025 (UTC)
Report concerning User:5.125.5.205
Latest comment: 1 year ago2 comments2 people in discussion
I'm reporting this so that someone with higher level can update the link, and a suggestion that some pages (like this one) should have external links allowed. Kazink (talk) 09:19, 27 March 2025 (UTC)
Final proposed modifications to the Universal Code of Conduct Enforcement Guidelines and U4C Charter now posted
Latest comment: 1 year ago1 comment1 person in discussion
The proposed modifications to the Universal Code of Conduct Enforcement Guidelines and the U4C Charter are now on Meta-wiki for community notice in advance of the voting period. This final draft was developed from the previous two rounds of community review. Community members will be able to vote on these modifications starting on 17 April 2025. The vote will close on 1 May 2025, and results will be announced no later than 12 May 2025. The U4C election period, starting with a call for candidates, will open immediately following the announcement of the review results. More information will be posted on the wiki page for the election soon.
Please be advised that this process will require more messages to be sent here over the next two months.
The Universal Code of Conduct Coordinating Committee (U4C) is a global group dedicated to providing an equitable and consistent implementation of the UCoC. This annual review was planned and implemented by the U4C. For more information and the responsibilities of the U4C, you may review the U4C Charter.
Please share this message with members of your community so they can participate as well.
page_namespace == 4 is placed as the first check. Also, action == 'edit' is not necessary.
I switched the current user_groups check to user_rights to also exclude global user groups that have the autoconfirmed user right, in addition to local user groups
Instead of some separate page_id conditions, I used an equals_to_any(page_id condition and added three coments of what project pages are excluded, and it saves at least one condition.
page_namespace == 4 &
!("autoconfirmed" in user_rights) &
!equals_to_any(
page_id,
1428, /* Sandbox */
2084484, /* Support desk */
1926565 /* Village Pump */
)
That's an utterly colossal amount of work that greatly exceeds the value. It seems better to abandon this whole system and just use the default from upstream, which I just did. * Pppery *it has begun16:00, 15 April 2025 (UTC)
If you ever re-introduce it, please make sure to protect the translation pages. In this case Template:Userlogin-remembermypassword was not protected, and it seems that anyone could edit it and thus change the message displayed on the login page. I was about to file a security bug about it when I noticed it has been deleted. Matma Rex (talk) 17:11, 15 April 2025 (UTC)
Vote now on the revised UCoC Enforcement Guidelines and U4C Charter
Latest comment: 1 year ago1 comment1 person in discussion
The Universal Code of Conduct Coordinating Committee (U4C) is a global group dedicated to providing an equitable and consistent implementation of the UCoC. This annual review of the EG and Charter was planned and implemented by the U4C. Further information will be provided in the coming months about the review of the UCoC itself. For more information and the responsibilities of the U4C, you may review the U4C Charter.
Please share this message with members of your community so they can participate as well.
Latest comment: 1 year ago7 comments4 people in discussion
This administrator keeps doing nonsensical changes at times. The last one affecting me was undoing an edit of mine to fix a broken URL. He claims to use a neutral URL to allow automatic redirection to the user's preferred language version of the page but his change simply creates a dead link because in this case there's no other page than the en-US page!
Well, here I get an error page claiming the URL doesn't exist for my preferred language (Spanish) but it does for English, pointing to the US page which is the only one I can find. Tactica (talk) 06:44, 17 April 2025 (UTC)
@Tactica: I tested this using the following steps. Based on this, the claim that the link is dead appears to be due to a temporary issue or a user-specific configuration, not because the link itself is invalid.
I set the preferred language to Spanish and enabled "Remember language". (This can only be done on a different page that has a Spanish version.)
I then tested the link used in my revision. It correctly redirected to the en-US version, which is the default.
Ah, I see now. If I set my browser's language to Spanish, disable the "Remember language" setting, and then click the link in my revision, it does indeed redirect to a "Page not found" page...
Latest comment: 1 year ago1 comment1 person in discussion
An empty "Priority languages" field had mistakenly been set on Template:Wikibase main page, and "Prevent translations to languages other than the priority languages" had also been enabled, which made it impossible for anyone to translate the page. I have just corrected this. Please check if there are any other pages with the same issue. Shirayuki (talk) 00:39, 19 April 2025 (UTC)
Report concerning User:2401:4900:3000::/36
Latest comment: 1 year ago2 comments2 people in discussion
Latest comment: 1 year ago3 comments3 people in discussion
It's not spam and this IP address have been blocked by abuse filter because, technetial blocking is wrong. Please fix for edit filter. JustAces (talk) 00:52, 27 April 2025 (UTC)
Yeah, indeed. We get so many IPs spamming their email address where they don't belong that a fairly harsh filter is necessary, and has occasional false positives. * Pppery *it has begun20:56, 27 April 2025 (UTC)
Vote on proposed modifications to the UCoC Enforcement Guidelines and U4C Charter
Latest comment: 1 year ago1 comment1 person in discussion
The Universal Code of Conduct Coordinating Committee (U4C) is a global group dedicated to providing an equitable and consistent implementation of the UCoC. This annual review was planned and implemented by the U4C. For more information and the responsibilities of the U4C, you may review the U4C Charter.
Please share this message with members of your community in your language, as appropriate, so they can participate as well.
Latest comment: 1 year ago2 comments2 people in discussion
I got here because there is a sort of block that for sure I don't understand it. I am trying to register my personal open discussion or rehearsal or essay page here, that is all. Thank You. MarySol6192. MarySol6192 (talk) 18:32, 2 May 2025 (UTC)
Latest comment: 1 year ago3 comments2 people in discussion
I’ve asked this first at the Support Desk, but because I request in effect for editing of one or two gadgets this seems to belong at the Village Pump.
First a copy of my Support Desk question:
Hello, the auto numeration activated with MediaWiki:Gadget-autonum.css and MediaWiki:Gadget-autonum.js (I load them in my global.js) does not work well together with Vector-2022 skin, because the counter reset does not work, and so all lower sections are just counted up. Note, that in vector-2022 only the else tree of the script is active and the code of the CSS is used. If you think, why I do not just ask the author Krinkle – well he wrote almost a year ago “I do not use the autonum gadget myself. For now, I have exceed the time I'm willing to spend on this gadget. I suggest gathering support and awareness of other people in the community, to hopefully find someone who is able and willing to maintain this JS/CSS snippet for further modifications.” (Krinkle’s user talk page on meta, cf. meta:Special:Diff/26715423 or the full conversation at m:Special:PermaLink/26721127#Section autonumeration with Parsoid). As an example: Manual:FAQ (itself not ready for vector-2022, at least the toc part I looked for) has 12 sections, and the latest one has 6 subsections which is fine displayed in (legacy) Vector from 2010, but with Vector 2022 I see the count 12.107.
End of copy
I was meanwhile able to fix this locally. This works only for the new DOM structure for the sections active in Wikimedia universe since last year (I’ve added a regarding note also to Krinkle, but did not remember that this is, of course, also active in Vector-2022). Since the gadgets are only for internal use this should be OK; the question is, though, how to alter Snippets/Auto-number headings, then. The CSS does not even need the selector added by the script, so it could be considered to delete this. But then all users who imported it need to get an information.
So, long story short, could one of the interface admins, please, replace the active MediaWiki:Gadget-autonum.css with the following style code:
If you want to keep the script in use then prepend .mw-parser-output with .tpl-autonum (with a space in between, of course) like it is seen in the active version, and keep the existent last part for JS mode.
As a side note: Somewhere a notice could be added that the style is best loaded by user script (global/common.js) because then exceptions for pages could be added where the style should not be loaded. —Speravir (talk) – 00:10, 29 April 2025 (UTC)
Thank you! I just now wanted to update the Snippets, but noticed that Krinkle has added the code there as transclusion of the gadgets, so the update has been done automatically. —Speravir (talk) – 23:32, 10 May 2025 (UTC)
Can't thank
Latest comment: 1 year ago1 comment1 person in discussion
In the hirstory for a page, I only see "undo" and no "thank". I would like to be able to thank people, it's a nice and uncluttered way of expressing appreciation/understanding. Is there something I need to enable, or is it a priviliege that gets unlocked? Douginamug (talk) 17:30, 10 May 2025 (UTC)
Report concerning User:223.225.169.119
Latest comment: 1 year ago2 comments2 people in discussion
Call for Candidates for the Universal Code of Conduct Coordinating Committee (U4C)
Latest comment: 1 year ago1 comment1 person in discussion
The results of voting on the Universal Code of Conduct Enforcement Guidelines and Universal Code of Conduct Coordinating Committee (U4C) Charter is available on Meta-wiki.
Latest comment: 1 year ago7 comments4 people in discussion
I made some bold changes to Download recently. @Shirayuki and @Pppery suggested, based on the importance of that page, that it would be better to revert those changes and first draft in my userspace. Here is that draft: User:Douginamug/Draft:Download It makes some fairly dramatic changes to title, content and structure: I tried to group related changes into the same revision and give meaningful revision comments.
I trust people will have resistance to a lot of the changes! My hope would be to work forward gradually and step-wise, from strongest consensus backwards. Curious to hear your opinions. Cheers, Douginamug (talk) 21:21, 10 May 2025 (UTC)
@Douginamug: Since there have been no comments from other users regarding your edits, I do not believe a consensus has been reached, so I do not intend to mark the relevant revision for translation.-- Shirayuki (talk) 11:44, 16 May 2025 (UTC)
@Shirayuki Thank you for explaining your reasoning and for your patience. I took the absence of comments to mean the absence of resistance, but I see I was too eager: ~1 week is not that long in the scope of this project. I would mention that there is one positive comment from @Pppery on your talk page.
Marking changes for translation isn't exactly easily reversible as it will fuzzy stuff and waste translator effort (although any translations not edited at all between the fuzzy and the revert do get unfuzzied) I'm happy to mark changes for translation if someone needs to commit to taking that step. But that shouldn't be done until things settle down first. And I agree Douginamug's changes look like an improvement, except I would keep the "system requirements" section -- there are a lot of pages, including the Main Page itself, that start off with a bold link to "Download" as the first thing someone might click. * Pppery *it has begun19:05, 16 May 2025 (UTC)
Latest comment: 1 year ago5 comments2 people in discussion
In the template {{Deprecated}}, parameter 2 (optional message) is used, but it is not normally displayed. It appears that parameter 2 is only output when both parameter 2 and parameter newvarlink are specified. However, there is a missing space between the output of parameter 2 and the following See {{{newvarname}}} for... message.
For example, in AuthPlugin, the optional message Superseded by AuthManager... should be displayed, but it is not.
The example didn't actually work. (The current one with the version number doesn't either, actually.) Should have been fixed rather than removed - I started doing that yesterday, but it's taking a while; working with translated templates is such a pain. I'll get it working eventually. Tgr (WMF) (talk) 10:13, 16 May 2025 (UTC)
@Tgr (WMF): Until this revision, the template was simple and the role of parameter 2 was clear. It seems that later feature additions (based on a sandbox version by User:Waddie96) caused it to stop working correctly. I'm not sure what the intended behavior of the template is supposed to be.-- Shirayuki (talk) 11:32, 16 May 2025 (UTC)
This year, the term of 2 (two) Community- and Affiliate-selected Trustees on the Wikimedia Foundation Board of Trustees will come to an end [1]. The Board invites the whole movement to participate in this year’s selection process and vote to fill those seats.
The Elections Committee will oversee this process with support from Foundation staff [2]. The Governance Committee, composed of trustees who are not candidates in the 2025 community-and-affiliate-selected trustee selection process (Raju Narisetti, Shani Evenstein Sigalov, Lorenzo Losa, Kathy Collins, Victoria Doronina and Esra’a Al Shafei) [3], is tasked with providing Board oversight for the 2025 trustee selection process and for keeping the Board informed. More details on the roles of the Elections Committee, Board, and staff are here [4].
Here are the key planned dates:
May 22 – June 5: Announcement (this communication) and call for questions period [6]
June 17 – July 1, 2025: Call for candidates
July 2025: If needed, affiliates vote to shortlist candidates if more than 10 apply [5]
August 2025: Campaign period
August – September 2025: Two-week community voting period
October – November 2025: Background check of selected candidates
Board’s Meeting in December 2025: New trustees seated
Learn more about the 2025 selection process - including the detailed timeline, the candidacy process, the campaign rules, and the voter eligibility criteria - on this Meta-wiki page [link].
Call for Questions
In each selection process, the community has the opportunity to submit questions for the Board of Trustees candidates to answer. The Election Committee selects questions from the list developed by the community for the candidates to answer. Candidates must answer all the required questions in the application in order to be eligible; otherwise their application will be disqualified. This year, the Election Committee will select 5 questions for the candidates to answer. The selected questions may be a combination of what’s been submitted from the community, if they’re alike or related. [link]
Election Volunteers
Another way to be involved with the 2025 selection process is to be an Election Volunteer. Election Volunteers are a bridge between the Elections Committee and their respective community. They help ensure their community is represented and mobilize them to vote. Learn more about the program and how to join on this Meta-wiki page [link].
Please let me know how to solve the problem related to SUL3
Latest comment: 1 year ago2 comments2 people in discussion
Hello !!!
Yesterday, when I tried to log in to the Jawiki I was shown the message, "You need to verify your login. A verification code has been sent to your email address, please enter that code here," and the message, "Contact X if you no longer have access to your account's email address." Since I did not register my e-mail address, I sent the following message to X, but I have not yet received a reply from X, even though about nine hours have passed.
I am user:天帝淵瀑布 of jawiki.
When I tried to login to jawiki recentely, the message "You need to
verify your login. A verification code has been sent to your email
address, please enter that code here." was displayed.
But I had not registered my e-mail address, so I cannot recieve the
verification code.
The message "Contact X if you no longer have access to
your account's email address" was also displayed, so I send this
messafe.
Please let me know what happened, and let me know how I can resolve
this probrem.
Thank you
Also, I asked a question in Japanese Wikipedia with the IP address 2001:268:C28A:24C7:F467:9E4F:37D8:6E57 but I have received no reply.
It is not displayed now, but when I was denied login yesterday, a message was displayed saying that SUL3 was involved, so I am writing this message.[1]
Please let me know by email or on this page what to do.
Thank you
The text above is almost translate from the original text in Japanese with machine translation. I attached the original text in Japanese, but I got a warning that it was spam, so I removed it.
The messaages below are sent from you.
Your account or IP address has been blocked by Abuse filter.
The reason given is Automatically blocked by abuse filter. Description of matched rule: IP adding email address or with email address in summary.
Start of block: 04:23, 28 May 2025
Expiry of block: 04:23, 11 June 2025
Intended blockee: 2001:268:C288:74D5:E5C0:DC06:88FD:4554
You can contact Abuse filter or another administrator to discuss the block. You cannot use the 'e-mail this user' feature (Special:EmailUser) unless a valid e-mail address is specified in your account preferences and you have not been blocked from using it. Your current IP address is 2001:268:c288:74d5:e5c0:dc06:88fd:4554, and the block ID is #158869.
Please include all above details in any queries you make.
--~~~~
This edit has been identified as spam. If it is not spam, contact an administrator. However, if you attempt this edit again, your account or IP address will be automatically blocked by the abuse filter.
You did the right thing, but it might take some time for the team to get back to you (several days). "Since I did not register my e-mail address" You most likely did register, but forgot about which email address you used. There is also the option that there is a bug in this new functionality, but that team you emailed should be able to figure that out. —TheDJ (Not WMF) (talk • contribs) 10:07, 28 May 2025 (UTC)
References
↑At first I tried to send this message to Talk:MediaWiki_Platform_Team/SUL3.
Latest comment: 1 year ago3 comments3 people in discussion
I've been translating site content to Spanish for some time. Which is the best procedure to follow when encountering a fairly long and complex page (say, more than a few dozen translation units and a size of several KB) that clearly was automatically translated? Mark it for deletion ({{Delete}}, {{Speedy}})? Just fix the translation? Sabbut (talk) 16:48, 22 May 2025 (UTC)
Bumping this question to prevent automatic archival, as I'm also interested in what folks' thoughts are about (what to do with) automated translations on MW.org. Best, —a smart kitten[meow]14:23, 6 June 2025 (UTC)
Personally I think it would depend on the translation and the content that is there, There is nothing wrong machine translation per say (The user should be QAing the translation like anything else). If its horribly bad and you don't have time to retranslate I would would probably delete it, If it just needs simple corrections and time is available you could probably just correct it. P858snake (talk) 22:18, 6 June 2025 (UTC)
Display Bug on Translated Page
Latest comment: 1 year ago2 comments2 people in discussion
In the English original, as well as any languages lacking a translation for that translation unit, the spurious markup does not appear.
I tried structuring the translate and span tags in the source to make sure they’re balanced and correct, to no avail. Perhaps someone more knowledgeable than I can look into it? --tooki (talk) 18:38, 25 May 2025 (UTC)
I think their rights should be removed as there is no point or benefit in keeping them, and it helps with clear stats. Thanks! -- CptViraj (talk) 14:49, 6 June 2025 (UTC)
This year, the Wikimedia community will vote in late August through September 2025 to fill two (2) seats on the Foundation Board. Could you – or someone you know – be a good fit to join the Wikimedia Foundation's Board of Trustees? [3]
Learn more about what it takes to stand for these leadership positions and how to submit your candidacy on this Meta-wiki page or encourage someone else to run in this year's election.
Best regards,
Abhishek Suryawanshi
Chair of the Elections Committee
On behalf of the Elections Committee and Governance Committee
Latest comment: 1 year ago1 comment1 person in discussion
Hello, we are the Wikimedia Foundation Trust and Safety Product team. Temporary accounts are successfully live on pilot wikis, and now we are rolling them out on more wikis. Because the community here is particularly technical, we plan to enable temporary accounts for this wiki next week. This project is especially relevant to logged-out editors, who this feature is designed to protect. But it is also relevant to community members like mentors, patrollers and admins – anyone who reverts edits, blocks users, or otherwise interacts with logged-out editors as part of keeping the wikis safe and accurate.
Why are we building temporary accounts
Our wikis should be safer to edit by default for logged-out editors. Temporary accounts allow people to continue editing the wikis without creating an account, while avoiding publicly tying their edits to their IP address. We believe this is in the best interest of our logged-out editors, who make valuable contributions to the wikis and who may later create accounts and grow our community of editors, admins, and other roles. Even though the wikis do warn logged-out editors that their IP address will be associated with their edit, many people may not understand what an IP address is, or that it could be used to connect them to other information about them in ways they might not expect.
Additionally, our moderation software and tools rely too heavily on network origin (IP addresses) to identify users and patterns of activity, especially as IP addresses themselves are becoming less stable as identifiers. Temporary accounts allow for more precise interactions with logged-out editors, including more precise blocks, and can help limit how often we unintentionally end up blocking good-faith users who use the same IP addresses as bad-faith users.
If you want to test the temporary account experience, for example just to check what it feels like, go to testwiki or test2wiki and edit without logging in.
Tell us if you know of any difficulties that need to be addressed. We will try to help, and if we are not able, we will consider the available options.
Look at our previous message about requirements for users without extended rights who may need access to IP addresses.
To learn more about the project, check out our FAQ – you will find many useful answers there. You may also look at the updates and subscribe to our new newsletter. If you'd like to talk to me (Szymon) off-wiki, you will find me on Discord (both the general English one and the one about MediaWiki), and Telegram. Thank you!
Declined. They're not spamming, they're appealing a no-warning no-talk block on Wikidata and there's no real other venue to do. If people are silenced everywhere for no clear reason they are prone to lash out. * Pppery *it has begun22:22, 1 July 2025 (UTC)
Report concerning User:~2025-110841
Latest comment: 1 year ago2 comments2 people in discussion
Latest comment: 1 year ago2 comments2 people in discussion
It would be desirable that the template (or a simpler, condensed version) was part of a suitable system message so that it was automatically interted in every page in this namespace. Right now a significant number of help pages lack the template and editing them one by one to add the template is not only boring but in the case of translatable pages it gives extra work to language administrators for no real benefit. Tactica (talk) 16:31, 9 July 2025 (UTC)
If it was in a system message, presumably there'd need to be some way (from an individual page) to achieve what the |imported=1 template parameter currently does (in order to signal that some of a given page's content may not be PD). Best, —a smart kitten[meow]16:56, 9 July 2025 (UTC)
Add option to turn off Link Previews.
Latest comment: 1 year ago2 comments2 people in discussion
Latest comment: 1 year ago2 comments2 people in discussion
JorgeElias2302 is creating translations in the languages (de, es, pt-br, ca, it, sv, af) they probably don't know. They are doing the same thing on translatewiki.net. Nemoralis (talk) 10:43, 10 July 2025 (UTC)
Nothing new since the temp block on the 6th, But since they have performed cross wiki vandalism, Have requested a global lock on meta. P858snake (talk) 08:50, 14 July 2025 (UTC)
I wasn't able to change the content model (as i'm not a Interface Admin), But did delete both so it should reset on recreate I hope, If you need any content from the sandbox archives, Please let me know and I should be able to dig it out. P858snake (talk) 09:40, 14 July 2025 (UTC)
Latest comment: 1 year ago2 comments2 people in discussion
Hello, could you please semi-protect Help:Temporary accounts permanently, as this page is linked to the notice where the unregistered user try to edit (i.e. Warning: You are not logged in. Once you make an edit, a temporary account will be created for you. Learn more.). Thanks. SCP-2000 (talk) 06:14, 21 July 2025 (UTC)
Latest comment: 1 year ago7 comments2 people in discussion
This template was incorrectly protected, Despite the template being "This page is protected so it can only be edited by administrators", so can you use a special page to unprotect this? ~2025-145089 (talk) 17:09, 21 July 2025 (UTC)
Latest comment: 1 year ago2 comments2 people in discussion
There are a number of Page display title translations that contain just the page's name plus the translation's language code (e.g., Extension:UploadWizard/fr). (This search should hopefully be an okay heuristic for finding some of them, though it does contain a number of false positives.)
As far as I can see (please correct me if I'm wrong!), page-display-title translations shouldn't contain the language code (e.g. /fr) at the end like this; as it isn't part of a translation of a page's title, and as it causes {{Localized link}} to include that language code when linking from other pages in the same language.
Because of this, should these translation pages be deleted/be edited to have the language code removed (or, where a previous revision exists without the language code included in the text, reverted back to that)?
Sounds like a question for a translation admin like @Shirayuki but I think faulty pages should be renamed. It doesn't look like a trivial task though, unless the number of badly named pages is very small. Tactica (talk) 13:07, 27 July 2025 (UTC)
Report concerning User:~2025-26937-0
Latest comment: 1 year ago2 comments2 people in discussion
If a translation is wrong you can fix it yourself. In the case of a Special: page, translations are usually done on translatewiki so you should raise the matter there. If the issue is a translation from a template expanded here by the special page, just fix the template (translation). Tactica (talk) 12:47, 27 July 2025 (UTC)
Change content model to JSON
Latest comment: 1 year ago3 comments2 people in discussion
Latest comment: 1 year ago2 comments2 people in discussion
Hello! Could I kindly ask if one of the translation admins could help me with marking Skin:Lakeus for translation? I think that maybe Shirayuki isn't around at the moment (they previously help me with this matter). Thanks in advance! -- Lakejason0 (talk) 12:58, 29 July 2025 (UTC)
Latest comment: 1 year ago4 comments2 people in discussion
Please replace the broken link http mathjax.readthedocs org en/latest/tex.html#mhchem with https docs.mathjax org en/latest/input/tex/extensions/mhchem.html . ~2025-31902-6 (talk) 02:27, 3 August 2025 (UTC)
Is there a better replacement link? The new link you propose describes mhchem but doesn't expand/clarify the relation between math chem and mhchem (as it is used in the sentence). --Clump (talk) 13:57, 3 August 2025 (UTC)
So it never was actually relevant as a reference for the relation between math chem and mhchem. Link removed. --Clump (talk) 13:40, 4 August 2025 (UTC)
Report concerning User:QuyQuang2048 is better
Latest comment: 1 year ago2 comments2 people in discussion
Latest comment: 1 year ago8 comments4 people in discussion
I'm wondering, is there something flat out wrong with my changes to Module:Navbox/styles.css or is miser mode or the job handling for this site really this slow that nav boxes in dark mode still look the same 60 hours later? A few days ago, as I copied a template from enwiki I read there that something was updated once a month, but I found hard to believe that things were this slow. Now, however, I'm not so sure. :/ Tactica (talk) 10:57, 4 August 2025 (UTC)
It seems to be displaying as intended now? phab:F65712002. Perhaps it was a server-side thing, or a browser-cache thing? Doing either a purge, or a "hard-refresh", can sometimes help with delays. [I.e. You don't mention trying either of these options specifically, so it might be worth my mentioning both w:WP:PURGE and the separate w:WP:REFRESH). HTH. Quiddity (WMF) (talk) 17:29, 4 August 2025 (UTC)
I tried all kind of purging methods, nothing works. In the end I went and cleared the cache from Firefox itself for this site and wikipedia just in case, and I'm still seeing the old CSS at work. Even switching to Chromium shows me the same and not the intended look I was expecting. I just added a screenshot to that task.
So I suspect the CSS didn't work as expected, or maybe it's the template (and the documentation) here not being in sync with Wikipedia, as that's the version I'm using locally. Tactica (talk) 19:34, 4 August 2025 (UTC)
I wonder if the CSS in Module:Message_box/ombox.css is overriding what you expect to see? (EDIT: Caveat: I'm not deeply experienced with tracking down how `inherit` works, and don't have time to poke around now, so this is just a hypothesis) Quiddity (WMF) (talk) 20:19, 4 August 2025 (UTC)
As I see it that should only affect omboxes but I'm not sure, really. My local version of that file is also from Wikipedia.
It's no big deal anyway, it's just a pity that this was for nothing and navboxes here still look wrong in dark mode :/ Tactica (talk) 20:39, 4 August 2025 (UTC)
Well yes, the navbar links being invisible is the main issue. I'd replace the module with Wikipedia's version, but doing that here isn't as simple as experimenting locally on my own MW instance where I'm currently the only user and navboxes aren't yet used anywhere :-) A secondary question is the "boring" colour palette in dark mode, but that's a matter of taste and besides my take of it doesn't necessarily follow the recommendations for dark mode, in fact trouble appears as soon as you use custom background colours as per the examples in the template documentation.
I think your styles are overridden by the dark-mode style fixes that use the !important keyword. These styles can be disabled in MediaWiki:Wikimedia-styles-exclude by adding the theme-night value to the source. Values should be separated by |. But before disabling it, all other cases that are covered by this CSS file must be tested.
Although there is no description page for that component, is it necessary to create a page for the component in the Extension namespace in order to create a description page for the hook? -- Shirayuki (talk) 03:03, 11 August 2025 (UTC)
Report concerning User:~2025-26937-0
Latest comment: 1 year ago2 comments2 people in discussion
Restricting creation of empty categories with Translate
Latest comment: 1 year ago5 comments4 people in discussion
A patch for phab:T390348 was merged a week ago, which allows us to restrict who can use the Translate extension to create translations of categories that are currently empty. This has been a longstanding problem on this site (see the task itself for links to complaints), and I propose we restrict it to sysops and translation administrators. What do people think? * Pppery *it has begun20:43, 11 August 2025 (UTC)
Just FYI, User:APaskulin_(WMF) is away on leave through January 2026. If the Draft is in a publishable state, I would say let's give @Douginamug a few days to reply to these messages and if there's no action, then one of us who are here talking about this can go ahead and make the changes / publish the draft. Does that sound acceptable? TBurmeister (WMF) (talk) 14:18, 12 August 2025 (UTC)
@Pppery @TBurmeister (WMF) thanks for bringing this up. Sorry I dropped out, a combination of being unsure if I was overstepping on such and important page + rest of life. I'm totally fine for people to implement/adapt things I drafted: I'm much more interested in the result than recognition. I will continue discussion on the bottom of the draft talk page. Douginamug (talk) 14:18, 15 August 2025 (UTC)
Report concerning User:"Bagaimana cara menghubungi CS AirAsia
Latest comment: 1 year ago2 comments2 people in discussion
@GZWDer: That seems reasonable, though we of course have api.wikimedia.org as the main user-facing pages nowadays. I think this is something the MediaWiki Interfaces team owns, however, so I would want their opinion first. Jdforrester (WMF) (talk) 09:46, 4 May 2025 (UTC)
I would not call the API Portal (api.wikimedia.org) our main user-facing pages. Technically, the portal was never "officially" launched, it lags behind MediaWiki in terms of adoption/readership, and many of the docs pages presented on it are not updated very regularly. The "Core REST API" endpoints are also tightly coupled with a specific implementation that we're likely going to retire. There are other reasons that I won't get into here, but I would avoid putting too much weight on it being a preferred source of truth.
That being said, we are investing in improving our API experiences this year, which includes focusing on docs quality and consolidation. We will revisit the future of the API Portal and how it fits with other docs solutions later this year. I will share more specific plans and timelines once we have them! HCoplin-WMF (talk) 19:33, 18 August 2025 (UTC)
I have re-flagged this discussion for PM User:HCoplin-WMF and other WMF colleagues, but just FYI Halley is currently out of the office so there may still be some delay in reply; maybe someone else from MWI team can reply. TBurmeister (WMF) (talk) 16:33, 14 August 2025 (UTC)
Should this discussion be moved to Phabricator; both so that it can be specifically tagged for the MW Interfaces team's attention, and also given that - in any event - a maintenance script run would be needed to move this page (per Pppery)? Best, —a smart kitten[meow]17:01, 9 July 2025 (UTC)
I think I would support moving it. One alternate option would be to instead redirect it to API, which currently serves as a landing page that attempts to direct people to the various MediaWiki-related APIs including API:Action API. api.wikimedia.org has a similar, though somewhat broader scope and I don't think should be considered as relevant for the decision about API:Main_page specifically. Just FYI, the Wikimedia Technical Documentation Team is currently in the research/discovery phase of work to improve the discoverability of all these different collections of API docs; this will likely involve some future changes to API and related pages that seek to help people navigate to the landing pages for a specific API. TBurmeister (WMF) (talk) 16:24, 14 August 2025 (UTC)
Sorry, I realize my comment was a bit unclear. I think the Action API main page should clearly reflect that API's identity and not pretend to be the only API for MediaWiki. I think API:Action_API achieves that best as a page title (and I note it is already redirecting to API:Main_page). My comment was about what we could do with API:Main_page if we agree that it should not serve as the landing page for only the Action API.
One other note: there are some external dependencies that my team maintains and would need to update if the URL for the Action API landing page changes from API:Main_page to API:Action_API; the most important one I can identify right now is the URL we use in https://developer.wikimedia.org/use-content/content/ would need to change (this is not a big deal, just noting it here so we don't lose track of it). TBurmeister (WMF) (talk) 16:44, 14 August 2025 (UTC)
This suggestion resonates with me too, @TBurmeister (WMF). It makes sense that API:Main_page would reference the generic API overview (although that page could also use some clean up love), with API:Action_API reflecting appropriate name space and scoping for the Action API specifically. Rerouting the main page would likely help people discover other flavors of APIs (eg: REST APIs) instead of thinking that the Action API is the only option. HCoplin-WMF (talk) 19:41, 18 August 2025 (UTC)
I am very much in support of this transition and really appreciate you flagging it :) This proposal is aligned with where we are heading with Wikimedia APIs, including making the APIs more approachable by investing in improving REST coverage. Based on the API listening tour and developer satisfaction survey conducted last fiscal year, we have a lot of work ahead of us to improve the discoverability and understanding of the different APIs that we already offer. Putting them onto a more even playing field for the MediaWiki docs hierarchy would be a great starting point. It also frankly just matches the established pattern for the API namespace better. HCoplin-WMF (talk) 19:48, 18 August 2025 (UTC)
Yes. I'm saying our articles that mention it need to link to a simple explanation here on this wiki. You're not suggesting that every instance of that term be linked to an external webpage, are you? - dcljr (talk) 07:42, 25 August 2025 (UTC)
@Dcljr: It's a pretty fundamental Web tech concept, akin to "Web server" or "browser". It's not really our place to try to define it. I think trying to document the bits of the world for which we're not responsible is a bad idea. Jdforrester (WMF) (talk) 18:01, 26 August 2025 (UTC)
If a Wikipedia article existed about it everyone would link to it without a second thought and that's an "external" page too, so I don't see what's the big deal. If anything we'd only have to remain consistent with the page we link to, *if* it is necessary to link to a given page at all. Tactica (talk) 18:26, 26 August 2025 (UTC)
The "big deal" is just that I couldn't tell what TheDJ's position on this actually was (link off-wiki or don't link at all). As you have seemed to imply that not linking to an explanation at all is a viable option, I will just point out that not everyone coming to a page like Manual:$wgLogos, for example, will know what DOCUMENT_ROOT is, or where it might be found. (It may be a general term, not a MediaWiki specific one, but it is a pretty arcane one compared to, say, "web server".) Closest thing we seem to have to the kind of thing I'm looking for is at Manual:Installing MediaWiki#Upload files to your web server, but that explanation is kind of "buried" in the text, plus it's way more information than most of the uses of the term elsewhere in our documentation actually require. (Somewhat ironically, that section actually links the more common term "web server", in exactly the way I'm suggesting we should be doing with "document root" and "DOCUMENT_ROOT".) I posted here merely to see if there was some better target that I was overlooking. - dcljr (talk) 20:48, 26 August 2025 (UTC)
My opinion comes down to that it is not our job to document how webservers work. Linking to external pages seems fine to me, but honestly, people should have already learned this before ever trying to install MediaWiki. —TheDJ (Not WMF) (talk • contribs) 22:03, 26 August 2025 (UTC)
We don't need to "document how webservers work" [eye roll], just not leave regular folks in the dark when technical jargon is used on this wiki. You do realize, do you not, that some people install MediaWiki through things like cPanel on shared servers, which tends to hide a lot of the installation details from them — until they find one day that they actually need to know certain details to do things they want to do (like change the way a site logo is configured). In such cases, our documentation should not throw up unnecessary barriers to understanding. Anyway, thank you for clarifying your position (even if I do end up disregarding it). I think we're done here. - dcljr (talk) 00:30, 27 August 2025 (UTC)
I don't think we need to define or link it, but I think it should be more consistently referred to as "document root" and not "DOCUMENT_ROOT" or "docroot" or any of the other variations. It's not a variable (although most web servers do have a variable for it) it's the name of a configuration concept. (Of course, I don't mean when a particular web server config is being talked about.) SamWilson23:50, 26 August 2025 (UTC)
Report concerning User:~2025-47132-5
Latest comment: 11 months ago2 comments2 people in discussion
Category:Template should be deleted or soft-redirected to the plural
Latest comment: 11 months ago3 comments3 people in discussion
Given the existence of Category:Templates, the less logically named Category:Template should either be deleted (and the title watched by interested parties — note that it has many translations) or soft-redirected to the plural title. I have already recategorized the handful of pages (4) and subcats (2) that were listed there. - dcljr (talk) 01:44, 25 August 2025 (UTC)
Below is some behavior that I am concerned with. Was going to let this go, but they keep popping up on my watchlist, and have not admitted to or apologized for any of the rudeness or LLM use. In their defense they are willing to discuss content / disruptive editing, although not necessarily stop or fix it.
If I may, I'd humbly suggest some action about it rather than a discussion. Quoting myself, most of Waddie96's edits lately have been reckless if not outright vandalism as he clearly doesn't test his changes neither before or after hitting the Publish button. Last time I checked wikis were meant to be a collaborative space to share and improve knowledge about a given matter, not some people undoing sabotage from others. I still remember an edit from a developer wondering "why nobody updates these pages" (changelog quote), while some people appear to be using this wiki as their personal test area just to increase their edit count or some other weird purpose, with zero consideration for actually improving the content. And yet, nothing is done about it. Tactica (talk) 16:33, 4 September 2025 (UTC)
I am less concerned with who needs to apologize to whom and more with what is being changed and why, and why these changes are not being done with more caution. All the examples in Extension:InputBox currently have overlap/spacing and colour issues---basically, it is now a hot mess. Prior to the bulk of Waddie96's edits (say the August 30 version, which at least has only a few minor changes from Waddie96) it is readable and clean. @Shirayuki: made some edits among Waddie96's changes too, so it's not clear cut whether there's any point in keeping the changes or not (and perhaps there's another specific revision that is better) but otherwise I am tempted to just revert it to that old version. More generally, I am not sure what Waddie96 is trying to do overall. I see lots of editing churn, most of which seems to focus on trivial changes to colours or icons, or delegating things into templates. Some of Waddie96's changes have involved (non-negative) interaction with others here, and I also haven't been following any related phab discussions, so perhaps it represents progress of some form, but it would be nice to have the actual vision expressed (and agreed upon) here too, as at the moment I have an impression of it being mainly less-than-competent and arbitrary revision over useful change. --Clump (talk) 17:21, 4 September 2025 (UTC)
I'm not expecting a direct answer to this but what would you have done already if an IP account was responsible for the current state of Extension:InputBox? I mean this is one of the problems with this site, some admins and rollbackers only see and act on vandalism from IP accounts. I could also mention the latest simplification effort by Shirayuki to Extension:DiscussionTools removing part of the documentation but he seems to be above every policy here or even common sense, so if the developers don't care, who am I to complain. Tactica (talk) 18:57, 4 September 2025 (UTC)
@Clump: My edits on the page in question were limited to fixing translation markup and simplifying translation units to reduce the burden on translators, so feel free to revert them as needed. Shirayuki (talk) 22:32, 4 September 2025 (UTC)
Good evening, it's late in Europe hence my reply. Without delving into much until it is for me to respond, the 'mess' on the inputbox article was a CSS from a template transclusion changing all the other inputbox's CSS too. I commented that template out, and problem fixed. 👌 Waddie96 (talk) 23:38, 4 September 2025 (UTC)
Note: (personal opinion) it's probably best to contain the discussion to issues on this wiki, if there are cross technical community issues it should probably be raised with the tech conduct committee. — Preceding unsigned comment added by P858snake (talk • contribs)
Latest comment: 11 months ago3 comments2 people in discussion
I have written what I believe to be a useful extension to the popular HotCat gadget, which I’ve successfully implemented on ICANNWiki. It allows customization of the sometimes excessive icons HotCat produces, which — depending on the number of categories — can hinder readability. I’ve uploaded the customizer to User:VersedFenrir/HotCatCustomizer.js and published the source on GitHub under GPL-3.0: https://github.com/mark-wd/HotCatCustomizer. I’m not fully familiar with the internal MediaWiki workflow; from what I understand, an interface-admin needs to review it before it can be made available to the wider public. Let me know if I can help in any other way. VersedFenrir (talk) 18:32, 9 September 2025 (UTC)
Hi. The primary source for that gadget is at c:MediaWiki:Gadget-HotCat.js, and from there it is often directly imported to other wikis (e.g. English Wikipedia's w:en:MediaWiki:Gadget-HotCat.js). I'd suggest copying/adapting your comment over to the talkpage for that (c:MediaWiki talk:Gadget-HotCat.js) to see if the main developers/maintainers of the gadget are interested in examining your code and potentially merging it into the default gadget. [disclaimer: I am not a dev.].
I'd also hesitantly advise: We don't usually make something into a gadget unless many folks are already using it via a user-script method. I would also speculate that it might be preferable to have this feature as part of the default code, to reduce worrying about future-breakages if/when the underlying codebase structure is changed. But perhaps other editors here have deeper insights.
That is very helpful, @Quiddity. Even as someone who manages a mid-sized wiki, I am experiencing a bit of a learning curve in learning how to contribute "upstream" the different types of novel code that I develop, offering it back to the broader MediaWiki environment. VersedFenrir (talk) 23:45, 10 September 2025 (UTC)
Report concerning User:~2025-57087-3
Latest comment: 11 months ago2 comments2 people in discussion
Upcoming Dark Mode user interface rollout for anonymous Wikimedia sites users
Latest comment: 10 months ago1 comment1 person in discussion
Hello Wikimedians,
Apologies if this message is not in your language. Please help translate to your language.
The Reader Experience team will launch the Dark mode feature for anonymous users on all Wikimedia sites, including yours, on October 29, 2025.
Dark mode is an option that allows users to view pages in light-coloured text, and icons on a dark background. Once it is available for anonymous users, they can enable it when using various devices. More information on ways to enable it can be found on this page.
Given many pages are still not compatible with dark mode this will be an opt-in feature and not automatically apply to pages.
Dark mode requires modifications to content pages and templates, and since our initial launch in July 2024, we have been working with communities and helping them prepare for dark mode. Before the rollout, it is essential that template authors and technical contributors test dark mode and read this page to learn how to make pages Dark mode-ready and address any compatibility issues found in templates.
We will fix most color compatibility issues only on the most-viewed pages on projects with over 5 million monthly page views. Technical contributors with an account should opt into dark mode currently using preferences or settings and test pages and seek help before the release to ensure everything complies before the enablement.
It does seem like a temporary problem, but not all of them are still working:
Gadgets YouTube MultimediaViewer Scribunto PdfHandler Math Interwiki WikiEditor Poem Echo Timeless MinervaNeue MonoBook are still down Telesphoreo1 (talk) 19:42, 28 September 2025 (UTC)
Latest comment: 10 months ago4 comments2 people in discussion
The behavior of the pages tag has changed, so that any page with more than one use of the pages tag implements only the first one and none of the others. Thais can be seen, for example at:
Note that this affects the majority of content pages across all Wikisource projects, effectively hiding all content except the first page section from all readers. This change seems to have happened with the last 12 hours.
Thanks for the bug-report. I've forwarded it on to some of the engineers. They think it might be a result of the code-updates for phab:T278481 and they are now in the process of rolling-back that latest patch. Quiddity (WMF) (talk) 20:29, 1 October 2025 (UTC)
This should now be fixed (the reverting-patch was merged). I've checked the example page-links you provided (thank you for supplying those! Examples always make things clearer) and most were automatically working again, but a few needed to be purged. Thanks again. Quiddity (WMF) (talk) 21:16, 1 October 2025 (UTC)
There's not much point in reporting accounts with zero edits to the local admins here absent some reason to think they will specifically target MediaWiki.org. Just report to the stewards and move on. * Pppery *it has begun15:57, 14 October 2025 (UTC)
Protect
Latest comment: 10 months ago2 comments2 people in discussion
I've deleted the translation units they created. There are some modifications in existing units that, looking more closely, seem to be better (but mind you I don't know Galician language, only because it's close to Spanish). You may want to take a look at those. Ciencia Al Poder (talk) 18:03, 19 October 2025 (UTC)
Report concerning User:((Uw-uhblock)) --Username violation, hard block--
Latest comment: 9 months ago2 comments2 people in discussion
Help us decide the name of the new Abstract Wikipedia project
Latest comment: 9 months ago1 comment1 person in discussion
Hello. Please help pick a name for the new Abstract Wikipedia wiki project. This project will be a wiki that will enable users to combine functions from Wikifunctions and data from Wikidata in order to generate natural language sentences in any supported languages. These sentences can then be used by any Wikipedia (or elsewhere).
There will be two rounds of voting, each followed by legal review of candidates, with votes beginning on 20 October and 17 November 2025. Our goal is to have a final project name selected on mid-December 2025. If you would like to participate, then please learn more and vote now at meta-wiki.
Thank you!
Latest comment: 9 months ago1 comment1 person in discussion
What I can say here is that I'm seeing Special:LintErrors/duplicate-ids having so many lists. Mostly from other languages that use Translate extension. I'm not sure if somebody has already filed out this track on Phabricator.
The id attributes in other language pages are just making them same while English one doesn't (it starts with "sectionname_number"). I hope this issue gets fixed. —Baris6161TURK (talk) 21:29, 20 October 2025 (UTC)
Report concerning User:Beerftwweb
Latest comment: 9 months ago4 comments3 people in discussion
Applications for the committees open on October 30, 2025. Applications for the Affiliations Committee, Ombuds commission and the Case Review Committee close on December 11, 2025. Learn how to apply by visiting the appointment page on Meta-wiki. Post to the talk page or email cstwikimedia.org with any questions you may have.
There's a more elegant solution: Add overflow: hidden; to the style element of the div. It makes the div grow to contain all floating elements. Ciencia Al Poder (talk) 21:02, 30 October 2025 (UTC)
TBH I'm not even sure having issues from Wikipedia and other WMF sites reported here makes sense. IMO they should wash their dirty laundry locally, so to speak. Tactica (talk) 19:52, 11 November 2025 (UTC)
Agreed, but that should be a seperate proposal, which could be more complicated considering we would have to edit quite a few interface messages. It certainly makes more sense to have on meta wiki, at least. Matrix (talk) 22:00, 11 November 2025 (UTC)
Latest comment: 9 months ago9 comments5 people in discussion
There are ~3000 pages in Category:MediaWiki code. For example Manual:AbstractContributionHandler.php. The vast majority of these are empty skeletons with essentially no content, and the links in the infobox are broken a non-trivial portion of the time because the file was moved or the class was namespaced. And MediaWiki just (in what I think was a bad decision) renamed every single folder to be uppercase, and despite my efforts with {{Capitalize folder}} this ends up breaking even more links.
Unless there's some special magic about the way this site works wrt the average MediaWiki instance, there's nothing to win by deleting all those pages, other than decreasing the amount of pages the spambots can vandalize. They would be no longer accessible to non-admins and the documentation would become poorer, because a skeleton is still better than nothing.
As for the capitalization changes, it's up to the adminship to have a ReplaceText extension or similar installed for cases like this one. Why this facility isn't available in a site that is fundamentally about documentation and bound to need this every now and then is beyond me. Tactica (talk) 16:27, 12 November 2025 (UTC)
It's better to have nothing and direct people to search for what they are looking for on doc.wikimedia.org instead than it is to have pages that are broken nobody is putting in the effort to fix. * Pppery *it has begun17:31, 12 November 2025 (UTC)
Or, maybe a good chunk of the content currently in doc.wikimedia.org should be moved (or at least mirrored) here. Also, I'd say not having an easy means to replace text site wide is what makes a lot of pages to remain stale. Tactica (talk) 17:38, 12 November 2025 (UTC)
I've never understood the point of these pages; I'd vote for deleting them. I'd be interested in hearing what people think should be added to those pages to make them worth keeping. Is the idea that we have a page here for every single file in the core repo? I get the feeling that they date from a time when MediaWiki code was much less structure and had things like multiple classes per file (at least, judging by the examples for {{MW file}}). What's the point of a page like Manual:ApiQueryRevisions.php? We could write something like "A query action to enumerate revisions of a given page…" but we've already written that in the file itself and it's available at https://doc.wikimedia.org/mediawiki-core/master/php/classMediaWiki_1_1Api_1_1ApiQueryRevisions.html in a way that's guaranteed not to become out of sync with the code. Any more general documentation that's useful about that class should probably be in API:Revisions, and documentation about the architecture or class hierarchy should be done with topics and @defgroup. SamWilson01:49, 13 November 2025 (UTC)
This convention started before we had a site hosting the php doc. And once you have something, hard to get rid of it. It is also searchable from this site, which the autogenerated docs are not. Im in favor of getting rid of it in principle, but i dont have a good picture about what it is they now contain that other docs dont, so a careful strategy to me makes sense. —TheDJ (Not WMF) (talk • contribs) 08:09, 13 November 2025 (UTC)
Reminder: Help us decide the name of the new Abstract Wikipedia project
Latest comment: 8 months ago1 comment1 person in discussion
Hello. Reminder: Please help to choose name for the new Abstract Wikipedia wiki project. The finalist vote starts today. The finalists for the name are: Abstract Wikipedia, Multilingual Wikipedia, Wikiabstracts, Wikigenerator, Proto-Wiki. If you would like to participate, then please learn more and vote now at meta-wiki.
Thank you!
Latest comment: 8 months ago6 comments4 people in discussion
During development of Wikispeech, I was testing directly to our page: Extension:Wikispeech/Pronunciation errors/sv and unfortunately, my IP-address became blocked due to "vandalism". I am fairly new in this eco system, but I was wondering if it perhaps could be possible to cancel the blocking of my IP-adress? Ofcourse I understand now, that I should have used the /sandbox for testing against wikis, but now I know better, but it would be great if the blocking could be cancelled.
It is best to ask @Clump, as he added the block. However. if you are making anonymous edits without edit summaries (like "I'm testing this new vandalism"), then it is likely you will get blocked indeed, so try to improve on that. You can also use test.wikipedia.org —TheDJ (Not WMF) (talk • contribs) 09:21, 25 November 2025 (UTC)
Unblocked; sorry about that---testing and nonsense edits tend to look similar, :) and yes, edit comments would help and be appreciated. --Clump (talk) 12:07, 25 November 2025 (UTC)
Latest comment: 8 months ago7 comments3 people in discussion
Following the MediaWiki update to the parsed heading structure, the main page CSS should be updated accordingly - MediaWiki:Common.css#L-37. Thanks.
Replace:
I can't figure out what this styling is supposed to do. Could you please explain why this should be done, and provide a test case that is currently broken and would be fixed were this change made? @Serhio Magpie: * Pppery *it has begun03:25, 28 November 2025 (UTC)
These styles hide the first heading in the content that duplicates the page title on the main page. My proposed fix: instead of hiding the h2 element itself (which worked previously), it targets the h2's container element. Example without styles (see identical headers):
FWIW, I can't see the duplicate heading either but I do see the extra separator that shouldn't be there, using Firefox if that's of any relevance. Tactica (talk) 04:42, 28 November 2025 (UTC)
Latest comment: 8 months ago2 comments2 people in discussion
The two pages I link in this section's heading have been repeatedly vandalized by anons. We block one, only for it to return under a new temporary account. The likelihood of constructive edits to those pages by anons is vanishingly small IMO, so I suggest we protect them against anon editing. Mr. Starfleet Command (talk) 14:35, 4 December 2025 (UTC)
Latest comment: 8 months ago4 comments2 people in discussion
Howdy. Today I boldly created the article Manual:JavaScript hooks. I think it should have equal weight to the current article Manual:Hooks, which is about the PHP hooks. They're both pretty developed hook systems.
Actually it requires a sysadmin since the page consists of more than 500 translations. But I think this is premature - Manual:Hooks, as a page dating back to 2006 with hundreds of subpages and lots of template infrastructure linking to those subpages, is clearly not on an equal footing with a singular page you created today. * Pppery *it has begun04:39, 15 December 2025 (UTC)
Also my worry is may the wiki is full of broken links like this, so I said may need do a global text replacement to fix all bugs like it. LBLaiSiNanHai (talk) 10:14, 22 December 2025 (UTC)
Latest comment: 7 months ago8 comments4 people in discussion
I noticed many many page is a stub or substub, and I want to expand them, also I already expanded some (e.g. Manual:EditPage.php), also, I want make articles that I expanded can be translated, noticed current TA may make a mark after long time, for better contributing effective, I want request TA, but I already acknownledged my translation policy knowledge need to improve, so, I will request this permission after I learned more about it, this is a RfC, please give me suggestions by reply this topic, also you can Support or Oppose me, but please leave reason, thanks! LBLaiSiNanHai (talk) 04:48, 24 December 2025 (UTC)
I came here to talk about blocking or warning you and found this. indeffed at home wiki as a sock, a handful of local translation edits here already reverted (translating into the wrong language?) and disabled at phabricator. learn to use the tools you already have properly before requesting new access. Jeremyb (talk) 07:00, 27 December 2025 (UTC)
About the wrong translating, I am using my tool LetWiki to rollback wrong translating by another vandaler, I make some mistakes (rollbacking more than 1 time), for diffs, it looks like I added wrong translating into page, just a mistake, if you means another, please give diff link, I will check it, thanks for reporting LBLaiSiNanHai (talk) 07:10, 27 December 2025 (UTC)
However, this actually created several problems including the broken page transclutions with malfunctioned language converter tags exposed and using the workaround of Template:Conversion-zh, Template:LC zh. More breakages could be found on phab:T328838.
More briefly for the zh part: The old configuration can only translate into zh while the new configuration can translate into zh-hans (for zh-Hans-CN, zh-Hans-MY, zh-Hans-SG), zh-hant (for zh-Hant-TW) and zh-hk (for zh-Hant-HK, zh-Hant-MO).
Note: "translatewiki.net page translation model"/"Miraheze Meta page translation model" refer to the same translation model.
I've added my comments on the associated Phabricator task you linked, which is basically about doing the same thing on every multilingual wiki. TL;DR: I'm opposed because as it currently stands, this proposal would quadruple the work of translators. Aaron Liu (talk) 16:18, 2 August 2025 (UTC)
I'd say rather than doing this, we sort of finding a way to actually implement the NoteTA (manual conversion RULES, so not quadrupling the work but actively using the LC model) for content page. -- Lakejason0 (talk) 17:03, 2 August 2025 (UTC)(edited at 17:05, 2 August 2025 (UTC))
Without using /zh-hans, /zh-hant, /zh-hk, we have to pass the language tag every time using message bundle messages.
-- Wrapping all of them under /zh using {{LC zh|, without using /zh-hans, /zh-hant, /zh-hktmb.new(mb_page_title,lang_tag):t(message_key):params(lang_tag):plain()
-- Using separated /zh-hans, /zh-hant, /zh-hk, we no longer need to pass the language tag :params( lang_tag ) every timetmb.new(mb_page_title,lang_tag):t(message_key):plain()
With this change, every Lua module using translation bundles can be simplified:
Even if T196501 is solved, you still have no way to either get the requested language tag or pass the lang_tag parameter because we are currently using $1 instead of {{{lang|}}}, which make the message bundle messages to be something different like {{{lang|$1}}}. -- Winston Sung (talk) 08:41, 8 August 2025 (UTC)
I don't think I understand. As long as lang is set to the needed value somewhere, it should work if we can get all the parent frames, even if it is input by the parser. Aaron Liu (talk) 21:42, 9 August 2025 (UTC)
There might be some misunderstandings.
You can only get "template arguments" like {{{1|}}} after T196501 being solved so we no longer need to write {{LC zh|lang ={{{lang|}}}|
However, "system message arguments"/"interface message arguments" like $1 are never something can be get from frame:getParent().args without either creating new methods to the frame object or still writing {{LC zh|lang = $1| in Wikitext.
:t(message_key):params(lang_tag) use the "system message argument API" instead of "template argument API".
The current problem is there are no way to pass template parameter (and only can pass system messsage parameter) when calling system messages. We currently have the way to get the current user interface language but there is no way to properly pass it without extra work on every template calls. -- Winston Sung (talk) 16:08, 15 December 2025 (UTC)
If any page can get the page variant through a Lua call, the page variant no longer needs to be passed through template parameters. Is there something else that needs to be passed? Aaron Liu (talk) 22:31, 2 January 2026 (UTC)