If you want to report a JavaScript error, please follow this guideline. Questions about MediaWiki in general should be posted at the MediaWiki support desk. Discussions are automatically archived after remaining inactive for 5 days.
This tends to solve most issues, including improper display of images, user-preferences not loading, and old versions of pages being shown.
No, we will not use JavaScript to set focus on the search box.
This would interfere with usability, accessibility, keyboard navigation and standard forms. See task 3864. There is an accesskey property on it (default to accesskey="f" in English). Logged-in users can enable the "Focus the cursor in the search bar on loading the Main Page" gadget in their preferences.
No, we will not add a spell-checker, or spell-checking bot.
You can use a web browser such as Firefox, which has a spell checker. An offline spellcheck of all articles is run by Wikipedia:Typo Team/moss; human volunteers are needed to resolve potential typos.
If you changed to another skin and cannot change back, use this link.
Alternatively, you can press Tab until the "Save" button is highlighted, and press Enter. Using Mozilla Firefox also seems to solve the problem.
If an image thumbnail is not showing, try purging its image description page.
If the image is from Wikimedia Commons, you might have to purge there too. If it doesn't work, try again before doing anything else. Some ad blockers, proxies, or firewalls block URLs containing /ad/ or ending in common executable suffixes. This can cause some images or articles to not appear.
@Redrose64, The Bushranger: Looks like something was changed in the software to force the top margin to 2px, so the CSS-only tweak doesn't work. That being said, having it set to 2px instead of 12px likely makes the tweak unnecessary anyway. --Ahecht (TALK PAGE)16:46, 1 December 2025 (UTC)[reply]
Hello, I'm writing on behalf of the Wikimedia Foundation Product Safety and Integrity team. Over the past few months, we have been working on the User Info card. When you tap or click on the "user avatar" icon button next to a username, it displays data related to the user account. It helps access key information that can be helpful while patrolling. The feature is available for all users in preferences as well as global preferences ("User Info" under "Advanced options").
We released the feature on all wikis, saw good feedback and at this point, we believe that we can go further. Enabling it by default for some user groups will make their workflows simpler and more efficient, especially in the temporary accounts world. Specifically in relation to temporary accounts, the User Info card highlights if another user has turned on the ability to view temporary account IPs and provides an estimated number of temporary accounts from associated IP addresses.
We are planning to enable this feature by default for admins, checkusers, rollbackers and Temporary accounts IP viewers (TAIVs). The feature can be easily disabled in preferences.
What does by default mean? Will it be enabled for me too even though I enabled/disabled it in the past? (because popups felt superior, and it doesn't require an extra click!) — DVRTed (Talk) 22:40, 26 November 2025 (UTC)[reply]
Hey, I'm guessing that it'd appear for each user with any of these rights, regardless of whether they've enabled or disabled the preference before or not. But I will ask my colleagues to confirm this. SGrabarczuk (WMF) (talk) 22:52, 26 November 2025 (UTC)[reply]
Oh. I'm sorry, that is unexpected. When I tested that behavior a few months ago, I recall that conditional defaults would not override a locally or globally set preference. KHarlan (WMF) (talk) 11:59, 27 November 2025 (UTC)[reply]
So even greater display of info on registered users, and more secrecy for drive-by anons? Is that really a good direction to be pushing internet social projects? Andy Dingley (talk) 15:48, 27 November 2025 (UTC)[reply]
Hiding IP has made dealing with vandalism and especially political bias (Persistent PoV pushing that's not actionable single-edit vandalism) much harder. Who benefitted from that? Andy Dingley (talk) 16:12, 27 November 2025 (UTC)[reply]
You must have misunderstood the feature being enabled here. It's about providing more info about unregistered editors, and it is providing that info to the listed roles above.
If you are annoyed by temporary accounts, there is plenty of consternation at WP:VPWMF where you may provide feedback. You should move on if you have nothing to say about the specific feature in this announcement. Izno (talk) 16:23, 27 November 2025 (UTC)[reply]
I would like to publicly thank SGrabarczuk (WMF) and the other WMF developers who worked on this feature for listening to the feedback that early testers provided and making changes to the cards in order to make them more accurate. Good work. – Jonesey95 (talk) 17:48, 27 November 2025 (UTC)[reply]
Is there a way to get rid of the million tiny heads that are now cluttering almost every page that has usernames? It's visually utterly useless. --jpgordon𝄢𝄆𝄐𝄇20:05, 27 November 2025 (UTC)[reply]
@Quiddity (WMF): It's pretty bugged at the moment—likely due to the recent changes to .mw-userlink, I assume. Screenshot showing too many user account icons in my watchlist. This is with ?safemode=1. — DVRTed (Talk) 20:23, 27 November 2025 (UTC)[reply]
Perfect, thanks - but in future, can such changes be announced so people can opt in, rather than forcing us all to have it and then try and turn it off? GiantSnowman21:44, 27 November 2025 (UTC)[reply]
I found that the heads are clickable; clicking produces a pop-up box; near the top of that box is a three-dot icon, clicking that generates a menu which has "Turn off this feature", a direct link to the above setting. --Redrose64 🌹 (talk) 22:08, 27 November 2025 (UTC)[reply]
I turned mine off too, via this route. I do use most of the info provided by the box on a regular basis perhaps once or twice a day. If the head icon wasn't so overwhelmingly distracting I might have left them there, but the distraction far far overwhelms the utility of the function. - WalterEgo10:06, 28 November 2025 (UTC)[reply]
I added that to my common.css file, and it changed the heads from black to gray, which I find helpful. I agree with other editors that the heads are a bit intrusive, but I also like to access the information I get by clicking on them, and so, for me, making them gray is an improvement. --Tryptofish (talk) 01:24, 2 December 2025 (UTC)[reply]
The mw-userlink class is now applied to links to user in edit summaries and the like, making it impossible for gadgets and scripts to rely on the class being only in core interface parts. This potentially affects dozens of scripts. Nardog (talk) 14:41, 27 November 2025 (UTC)[reply]
They apparently wanted to be able to grey-background links to temporary accounts wherever those might appear, and usurped the "mw-userlink" class to do so. It may be worth filing a Phabricator task requesting they bring back a way to find the performing user in a watchlist or Special:RecentChanges row now that mw-userlink can also be applied to the page affected, the diff and history links, and links inside the edit summary. Anomie⚔15:09, 27 November 2025 (UTC)[reply]
Hello! I'm sorry to have caused this issue... Extending the set of cases where mw-userlinks is applied definitely wasn't planned nor needed for the task I was working on (which is adding gray backgrounds to selected temp. user links in content area). For that, we had to change the code that's responsible for adding the user-related classes to the links, and alas, we didn't catch the unwanted change to the scope of mw-userlinks.
The patch to fix the behavior has already been prepared and waits for CI and review. Given that this issue probably isn't a reason for emergency backport (which is the only kind of deployment allowed on Fridays), I expect the fix can be deployed to production on Monday morning.
Again, I'm sorry that this happened. As a person, who's part of the wiki communities, I feel how it is when gadgets break and require fixing. Unfortunately, this time, I'm at the more bitter side of things and I can't help immediately. I'll ensure, though, that the fix lands on production as soon as possible (which is unlikely to be today). MSzwarc-WMF (talk) 08:35, 28 November 2025 (UTC)[reply]
Well, don't be so hard on yourself. In fact I'm pleasantly surprised you're reverting it—most of the time devs are like "tough luck" when this kind of thing happens. Nardog (talk) 13:15, 28 November 2025 (UTC)[reply]
The fix is deployed now. It's possible that some pages still have these extra mw-userlink classes added, but forcing reload (or ?action=purge) should resolve that. MSzwarc-WMF (talk) 08:35, 1 December 2025 (UTC)[reply]
No, it wasn't that stressful (in fact, probably less that my original message implies). I primarily wanted to communicate what were the cause and expectations from the WMF side around the issue, so that the community didn't need to panick over the weekend :) MSzwarc-WMF (talk) 12:50, 1 December 2025 (UTC)[reply]
Why are my span.mw-usertoollinks modifier user scripts all messed up suddenly?
Basically, they modify the user tool links "(talk | contribs | block)" next to each user listed on the specific special page or area, and add more links to them to make performing actions much quicker.
Since the end of yesterday, suddenly, they're all completely messing up! They're now adding links to the wrong account or user from someone further up the list, and the scripts are now starting to set the "current_user" to "contribs" instead of the username of the current user to add user look links next to.
I'm stumped! I did make some code improvements to some of the scripts, but all four of them are having problems despite me only updating three of them. Rolling back all of my changes and clearing browser cache, the whole works, made no difference. What's going on? Can someone look at these scripts and maybe tell me if something has changed? They were all working perfectly fine up until when the user cards feature was deployed.
PLEASE HELP! I'd be forever in your debt and eternally grateful for any help, input, or guidance.... :-) (Please ping me in your responses, as I'm currently working on cleaning out my watchlist for being way too full...) ~Oshwah~(talk)(contribs)17:06, 27 November 2025 (UTC)[reply]
DVRTed - Oh, trust me... I'm absolutely not saying that the script I wrote is the best thing in the world code-wise. I happened to see the discussion made right above mine, and it looks like others have already beat me to it with their observations as well. Okay, cool! I'm just really happy to know that it wasn't me that overlooked something and caused these scripts scripts to mess up. My thanks to Izno for nesting my cry for help under the discussion located above this one, and my sincere thanks to you, DVRTed, for taking the time to look through my really shitty JS code... :-) ~Oshwah~(talk)(contribs)19:25, 27 November 2025 (UTC)[reply]
DVRTed - Thank you so much! Ugh... I was educated in C++ when I went to college, which is what I actually have my bachelor's degree in (whether you believe it or not, based off how awful my code is here...). What I need to do is find a resource that will help me to learn and get more familiar with JS and how it all works on the web vs my object-oriented programming mindset that's engraved into my brain. I wish there was something out there that could help me sharpen my skills with JS and with the MediaWiki libraries and built-in variables and functions... Thanks again; I owe you one... :-) ~Oshwah~(talk)(contribs)19:52, 27 November 2025 (UTC)[reply]
@Oshwah Re: I wish there was something out there that could help me sharpen my skills with JS and with the MediaWiki libraries and built-in variables and functions. I found it all very overwhelming when I first started working with MW components, APIs, etc. I learned a lot simply by looking at existing userscripts. I've rewritten your History-Log-Links from scratch with way too many comments, which might be useful for maintaining or debugging this script (and other related ones.) See User:DVRTed/sandbox/temp.js. PS: I hope this gesture doesn't come off as patronizing—this is me genuinely trying to be helpful because it seemed like you could use some pointers. PPS: Happy coding! — DVRTed (Talk) 01:58, 28 November 2025 (UTC)[reply]
DVRTed - Oh hell yes! Thank you for doing this! What you described and what you did for me is exactly what I needed! Looking at existing user scripts, forking some scripts and changing the code in order to customize them to my personal preference, and (at least attempting to) create some of my own scripts is exactly how I've managed to learn some of the MediaWiki libraries and (if anything) just how different JS is than the object-oriented programming mindset that I'm so used to. No, you're not coming off as patronizing or anything like that at all! This is really awesome and extremely helpful to me, and I seriously appreciate it a lot! Thank you. Now I just need to fix the other .mw-usertoollink scripts I wrote (such as this one) so that they work properly as well. If I had working examples of these scripts performing exactly what I intent, it would provide me a lot of good information and learning. I hope this response doesn't come off as me requesting you to spend more time and fix these other scripts as well. Either way, I'll eventually figure it out. Thanks again! :-) ~Oshwah~(talk)(contribs)02:10, 28 November 2025 (UTC)[reply]
DVRTed - Ohhh, SWEET JESUS... You have absolutely no idea how awesome this is and how happy you made me. I almost shook my computer monitor violently in excitement when I looked through that code. I obviously have a shit ton to learn with JS vs C++ (as I've been saying), such as how the value assignment works on line 20 with your constant var declaration, why you put publiclog_link into an array format [publiclog_link] on line 44, what ${variable} does vs just entering variable, how the different built-in tools and functions work, and many many more things. Ugh, I just need to find a resource that can just teach me JS from the very beginning... You made me very happy, and I thank you very much! :-) ~Oshwah~(talk)(contribs)02:29, 28 November 2025 (UTC)[reply]
C++ is generally harder to learn, but understanding certain basics about Javascript makes it much easier to follow, and also certain basics about Javascript running in a browser environment. So I agree with your assessment about finding a good introductory resource :-). (Some key differences off the top of my head: Javascript is garbage collected, and much like Java and other newer languages, its variables can only hold values of a specific set of types or the equivalent of a C++ reference to an object. Thus an object isn't copied when one variable is assigned to another; both variables point to the same object. Although ECMAscript version 5 does introduce the concept of classes, and thus ways to scope symbols within a class, the older versions do not have classes, and the only way to scope symbols is to declare them locally within a function. That's why you'll see Javascript code do things like declare an anonymous function and invoke it immediately, in order to avoid introducing symbols into the global namespace. Javascript does have an interesting inheritance mechanism where each object can hold an object reference to a prototype object that gets searched for a matching property if none exists in the current object. (The prototype object can have its own prototype property; the search will go up the chain until a match is found or there are no more prototypes to search.) I don't believe Wikipedia supports ECMAScript 5 in user scripts so only prototype-based inheritance can be used. In a browser environment, there is a pre-defined window object, and all global variables are properties of the window object.) isaacl (talk) 03:16, 28 November 2025 (UTC)[reply]
I don't believe Wikipedia supports ECMAScript 5 in user scripts so only prototype-based inheritance can be used.: User scripts run on your browser JS engine, and pretty much every modern browser has support for the class keyword. ChildrenWillListen (🐄 talk, 🫘 contribs) 03:27, 28 November 2025 (UTC)[reply]
As I recall, user scripts are validated before being served by the MediaWiki server, and the validator being used doesn't support ECMAscript 5. isaacl (talk) 03:31, 28 November 2025 (UTC)[reply]
Well, I should start using classes, too then :-). As I recall, there was a Phabricator ticket about updating the validator; perhaps it has been resolved. (Or maybe I've confused it with a ticket for ECMAscript 6 support.) isaacl (talk) 03:44, 28 November 2025 (UTC)[reply]
Thanks for the update. Last time I suggested to someone to use "let" they told me it was unsupported, which was the last time I looked into it. isaacl (talk) 04:01, 28 November 2025 (UTC)[reply]
Oh, and $(something) is functionality added by the jQuery library, so you can add reading a basic jQuery tutorial to the list. Nowadays, there is equivalent functionality in the Document Object Model API provided by the browser for a lot (most?) of the jQuery API, but some may still prefer the syntactic sugar of using something like $(".someParentClass .someChildClass") to fetch all matching elements. isaacl (talk) 03:27, 28 November 2025 (UTC)[reply]
It's checking if special_pagename is a truthy value (it would be false on a non-Special page) ANDif the current page name is included in the list of names; if both of these conditions are met, it is a "supported page." (MDN)
const new_links = [publiclog_link]; is so that the publiclog_link is added before anything else; this is to maintain the order from your original script: talk, contribs, publiclog, [ip related links], [other links, i.e, block]. With template literals, instead of something like "Hello " + name + "!", you can simply write `Hello ${name}!`. See https://developer.mozilla.org/en-US/docs/Web/JavaScript/Reference/Template_literals that explains it very well. Regards, — DVRTed (Talk) 03:52, 28 November 2025 (UTC)[reply]
I want to translate and create articles from Persian (Persian Wikipedia) to English. How do I activate the toen wiki tool? What are the article translation tools and how do I activate them? AndisheyAzad (talk) 23:12, 27 November 2025 (UTC)[reply]
How can I bypass Cloudflare to archive a site? I can’t archive it because of Cloudflare’s verification issue. (Sorry if this isn’t the right place for technical questions, I don’t know where else to discuss this.) Rafael Ronen08:07, 29 November 2025 (UTC)[reply]
In general, sure, but this question clearly involves someone unable to archive a page due to an obscure problem with their device (a crippled browser) which can't be resolved here. The solution is to get someone else to archive the page which has already been offered at the Teahouse. Johnuniq (talk) 01:55, 1 December 2025 (UTC)[reply]
due to an obscure problem with their device (a crippled browser) Do you think archive sites take raw HTML from the client to store on their server? — DVRTed (Talk) 10:09, 1 December 2025 (UTC)[reply]
Some actually operate that way! From Rhizome_(organization)#Web_archiving: "The "symmetrical web archiving" (browser-based) approach, meaning the same software is used to both record and play back the website.[24] While other web archiving tools run a web crawler to capture sites, Webrecorder.io took a different method, recording network traffic while a user browsed the site to capture its interactive features." This approach later developed into Conifer, which stores the capture at a central archive site. If Wikipedia ever created its own archive site, this is the software to use, it has the highest fidelity. With that said, John may have been thinking the user could not access web.archive.org, due to a block or something wrong with their browser. -- GreenC05:23, 2 December 2025 (UTC)[reply]
Rafael Ronen, unfortunately I tried 4 sites and none work (WaybackMachine, Archive.is, Conifer, Ghostarchive). CloudFlare makes it impossible to archive because the sites have a high level of security enabled (human check). Sometimes sites will reduce the level in the future, because CloudFlare interferes with normal users trying to access the site. Maybe they are having a bad time right now with AI scrapers or hackers, check back with them in the future to try again. -- GreenC03:08, 1 December 2025 (UTC)[reply]
When I'm viewing the preview of my edit(s) on my sandbox (when the User sandbox template is there, this message appears), it shows this message at the top:
“This sandbox is in the article namespace. Either move this page into your userspace, or remove the User sandbox template”.
However, when the NAMESPACE template is up there instead, the preview shows nothing — the dialog is gone — but after saving the page, it just displays User.
This started at Wikipedia:Help desk#Sandbox. I don't have an Android device for testing but apparently, if a userspace edit is previewed in the Android app then the magic word {{NAMESPACE}} returns blank which indicates mainspace and fools namespace-dependent templates. Other namespaces and magic words at mw:Help:Magic words#Namespaces may be affected but I cannot test it. It works in the iOS app and a browser. Can somebody with an Android device make some tests and report it at Phabricator if they confirm the bug? PrimeHunter (talk) 12:48, 30 November 2025 (UTC)[reply]
I think it's time then we allowed the option to opt out of Twinkle messages. To mute users should mean the ability to stop talk page messages from people. I have nothing against Joe and don't have an issue with him prodding articles which genuinely don't have adequate sourcing online, but I don't want to receive the prod notices. ♦ Dr. Blofeld20:41, 29 November 2025 (UTC)[reply]
Twinkle is used for many things, e.g. escalating warnings. Disruptive users shouldn't be able to opt out of that. Others might opt out of Twinkle to avoid one type of post and then miss other types. PrimeHunter (talk) 21:05, 29 November 2025 (UTC)[reply]
@Dr. Blofeld: I certainly didn't imply that. I just think there are too many problems with allowing users to opt out of Twinkle messages when Twinkle is used by so many users for so many different messages. We might allow a limited opt out like allowing users to opt out of prod messages but it sounds like significant work for a system very few would probably use. How bad is it to just remove or ignore the messages, and do you really never want to be notified about any article you have created? PrimeHunter (talk) 21:10, 2 December 2025 (UTC)[reply]
That's a fine system for bots. For gadget/user scripts, it's useful to have something that's easily detected client-side if the page is open ($('a.external[href*=optout\\.twinkle]')) or with an API call that has a small response (prop=extlinks with elquery param). Maybe the template could be made non-Twinkle specific, but if there's interest that can be done later as the advantage of not relying on the wikitext is that we can rename the template later, modify the external link it uses, etc. – SD0001 (talk) 11:28, 3 December 2025 (UTC)[reply]
It's not really the greatest system for bots either, but it's what we have. It works fairly well as a check when you're making an edit without using the "append a new section" feature, and it has both the advantage and disadvantage that it can't be (accidentally) transcluded from some other page. Anomie⚔12:48, 3 December 2025 (UTC)[reply]
I am working on getting 1st Maine Cavalry Regiment out of Category:Harv and Sfn no-target errors and have run into a problem with cite books. As I have been going editing the article I am getting new error messages of "Script warning: One or more {{cite book}} templates have errors; messages may be hidden (help).", one more every time I have fixed a harv cite issue. I apparently do not have a script installed to see what these issues are. Can someone look in on the article and tell me the error? And maybe also what I need to install so I can see the cite book errors as well? Thanks, Shearonink (talk) 18:28, 29 November 2025 (UTC)[reply]
You don't need a script. cs1|2 error messages are visible to everyone unless you have explicitly set your css to hide them (you haven't; at least not in your common.css). The easiest way to find those sorts of errors is to use your browser's find function (ctrl+f in windows) to look to the string (help.
You have hidden the two sidebars that can end up in that space. One of them is the goggles at the top right. One of them is the tools dropdown below the languages dropdown. Izno (talk) 21:46, 29 November 2025 (UTC)[reply]
No, it is by design. Reporting it will simply cause it to be closed immediately. You have been provided the two supported ways to deal with the layout of the page. Izno (talk) 22:02, 29 November 2025 (UTC)[reply]
Yes, and part of their objection was fixed by providing the goggle dropdown. (I don't know if it solved all of their objection.) Izno (talk) 22:33, 29 November 2025 (UTC)[reply]
Looks like you did create the page at one point: you created the redirect (in Special:PermaLink/852535838) by renaming the old version of the page to Glynis Jones (disambiguation). The history doesn't look like it because someone later did some history merging and splitting, which resulted in some of the disambiguation page edits you had moved to be merged with the redirect.Apparently xtools identifies a "creation" by looking for the rev_parent_id field to be 0. I don't know of any straightforward way to reset this (since T183375 fixed preservation across deletion and undeletion). Anomie⚔02:34, 30 November 2025 (UTC)[reply]
Unless someone is cleaning ones as they show up, I don't see any that were added after the end of October, and none before mid-September ish. Izno (talk) 18:41, 30 November 2025 (UTC)[reply]
This also hits a timeout but is probably marginally better since it dodges some obvious false positives. According to Help:Linksearch the externallinks table is available on Quarry. You can probably rustle up some SQL to find these (WP:RAQ can help if you don't know it).
The source isn't VE from what I can see. I suppose it's possible to use Citoid via the toolbar rather than via VE so that is a possible cause. Otherwise, I suspect this is or was some copy-paste bug introduced by some browser or browser extension. Izno (talk) 17:44, 1 December 2025 (UTC)[reply]
We had an issue from ~September 15th to ~October 5th related to the date URLs at the top adding an additional /web/timestamp
Izno posted some diffs above that post-date October 5, but the one's I checked appear be wikitext copied from other pages, or other parts of the article. -- GreenC04:17, 2 December 2025 (UTC)[reply]
I believe this is now repaired. The URLs were in over 100 articles, and probably over 400 links. If any new ones show up it will be from old diffs, such as a revert to an old version of the page. -- GreenC19:50, 2 December 2025 (UTC)[reply]
Hey, I wanted to let you experienced editors know about a common glitch I keep encountering. Some text inside collapsible lists in infoboxes becomes invisible when using dark mode. I'm not sure how to fix it, but I've seen it quite often. The last three examples I noticed were Territories of the United States, Ataturk, and George Washington.
Maybe someone else can reproduce. I can't on Firefox or in Chrome, even after actually checking on my mobile device. Are you using the Wikipedia official dark mode or some extension? Reader mode? Izno (talk) 17:49, 1 December 2025 (UTC)[reply]
Category does not appear in administrative backlog
A null edit usually fixes issues like this. Otherwise, you need to wait for the job queue to get to it, which can take days or weeks. – Jonesey95 (talk) 03:48, 1 December 2025 (UTC)[reply]
It has the code {{Admin backlog|5}} which adds Category:Administrative backlog if there are at least 5 category members, so it can go in and out of the parent category. I don't think a job is added to the job queue when the number of category members changes so it can take a long time to update. Some actions like a purge cause the category page itself to be updated but not the link tables which control the listings in the parent category so things can be out of sync. A null edit of Category:Requested RD1 redactions (not of the parent category) will update everything quickly. PrimeHunter (talk) 15:06, 1 December 2025 (UTC)[reply]
In short, if you want that Admin backlog template to categorize its category pages in a timely fashion, you'll need a bot to periodically null edit the pages that you care about. – Jonesey95 (talk) 15:37, 1 December 2025 (UTC)[reply]
Hello! I kindly request technical assistance to move the following draft out of my userspace and into the Draft namespace, per COI and AfC guidelines.
Current location:**
User:Associació Òpera Popular de Barcelona/sandbox
Requested destination:**
Draft:Opera Popular of Barcelona
Reason: As the subject of the draft is related to the organization associated with my username, I am following Wikipedia’s conflict of interest policies and the AfC process. Editors advised that the page should be placed in the Draft namespace for proper review by independent reviewers. I do not have the permissions to move the page myself.
Pel que fa al conflicte d’interès: sí, tinc relació amb l’entitat, i per això no estic editant l’article directament. Només he preparat un text neutre al meu espai de proves, tal com indiquen les polítiques de COI, i demano que un editor independent valori si pot ser traslladat a l’espai principal.
Si ho consideres inadequat igualment, ho respecto totalment. Però si creus que el text és neutral i referenciat, i que compleix els criteris mínims, t’agrairé moltíssim qualsevol orientació sobre el pas correcte a seguir.
Latest tech news from the Wikimedia technical community. Please tell other users about these changes. Not all changes will affect you. Translations are available.
Updates for editors
The Wikipedia Year in Review 2025 will be available on December 2 for users of iOS and Android Wikipedia apps, featuring new personalized insights, updated reading highlights, and refreshed designs. Learn more on the review's project page.
The Growth team is working on improving the text and presentation of the Verification Email sent to new users to make them more welcoming, useful and informative. Some new text have been drafted for A/B testing and you can help by translating them. See Phabricator.
Add a link will now be deployed at Japanese, Urdu and Chinese Wikipedias on December 2. Add a link is based on a prediction model that suggests links to be added to articles. While this feature has already been available on most Wikipedias, the prediction model could not support certain languages. A new model has now been developed to handle these languages, and it will be gradually rolled out to other Wikipedias over time. If you would like to know more, please contact Trizek (WMF).
View all 34 community-submitted tasks that were resolved last week. For example, the issue where search boxes on some Commons pages showed no results due to switch from SpecialSearch to MediaSearch, has now been fixed. [5]
The Wikimedia Foundation is in the early stages of exploring approaches to Article guidance. The initiative aims to identify interventions that could help new editors easily understand and apply existing Wikipedia practices and policies when creating an article. The project is in the exploration and early experimental design phase. All community members are encouraged to learn more about the project, and share their thoughts on the talk page.
I have a recurring problem where I nominate an article for deletion, and then don't get any notifications when comments are made or the discussion is closed. This would be a lot handier than bookmarking and coming back later, which is what I do now, as I often need to follow up with other cleanup, or sometimes there are questions that I could have answered. For example, on Wikipedia:Articles for deletion/강수연, there's no option to subscribe for new comments. If I go to Tools -> Subscribe, it seems that only subscribes me for new topics, but new topics are never created on AFD pages. Is there a good workaround for this, or is a feature request needed? -- Beland (talk) 03:14, 2 December 2025 (UTC)[reply]
Hmm, it looks like level 3 headers are being used on each AFD page. It would actually be useful to also be able to subscribe or unsubscribe from level 3 sections, maybe? Sometimes a long discussion will split into multiple subthreads. -- Beland (talk) 08:44, 2 December 2025 (UTC)[reply]
Aha, that's what I was thinking was out there somewhere. Added myself as a supporter!
Theoretically if we changed XFD level 2 headers to level 1 and then level 3 to level 2, we'd work around this, but that might create a compatibility and re-templating nightmare? -- Beland (talk) 10:03, 2 December 2025 (UTC)[reply]
@Beland: Since every AfD is on its own individual page, you can do what I did: at Preferences → Watchlist, enable "Add pages I create and files I upload to my watchlist". This also works for MfD, but not CfD, FfD, RfD or TfD, on all of which several separate nominations share one daily page. For these, you would need to enable "Add pages and files I edit to my watchlist". --Redrose64 🌹 (talk) 21:44, 2 December 2025 (UTC)[reply]
Unfortunately, my watchlist has over 1400 pages and I almost never check it. (When I do, it's to purge the list of followup items from years ago.) -- Beland (talk) 21:48, 2 December 2025 (UTC)[reply]
Ah, but if I restrict viewing my watchlist to the Wikipedia namespace, it does actually produce a useful list of AFD pages I recently created. Thanks for the suggestion. -- Beland (talk) 22:31, 2 December 2025 (UTC)[reply]
Caret color CSS change? (Affecting "Reply" textarea only)
I'm using the Vector 2010 skin in dark mode. Since returning from a few weeks away, I'm finding the caret in "reply" widgets is very dark grey (or maybe just very transparent) on black, making it nearly invisible. Which in turn makes it extremely difficult to make edits after typing. (Selection highlights in those textareas are also difficult to see, being navy or very transparent blue on black) In regular edit areas (such as my sandbox), it appears as its usual bright white, and selections the shade of green that I've configured. Has there been a CSS change recently? Though I can't find any caret-color rules using developer tools. I haven't edited my own user CSS lately, either. Using the latest Firefox on Mac (Sequoia), if that makes a difference. -- Avocado (talk) 16:43, 2 December 2025 (UTC)[reply]
Might be the syntax highligter. However, vector 2010 has no official dark mode support, so it is expected to vreak every once in a while and then you have to wait for a community memebrr to fix it (or not). —TheDJ (talk • contribs) 18:08, 2 December 2025 (UTC)[reply]
1. Not really sure how you fix but it’s desktop centric to use a first letter lowercase captcha when most phones default to capitalizing first letter. Proper English and all that. Anyway adds a level of friction on mobile
“Who’s the captcha stopping” the dumbest stuff, what is still a complete waterfall of bad faith contributions. But we might be switching to a invisble hcaptcha soon, so lets hope for that. —TheDJ (talk • contribs) 18:06, 2 December 2025 (UTC)[reply]
The landing page after a successful page deletion, e.g.: https://en.wikipedia.org/w/index.php?title=User:Beland/Comparison_of_circulating_currencies&action=delete (which unfortunately only works once unless you recreate the page) has dark mode problems. It's title "Action complete" and then there's a box titled "Maintenance links" which has text like "Depending on the reason for deletion, you may want to remove any links to this page (articles | redirects)." All the body text in this box (except for blue links) is nearly impossible to read grey-on-grey in dark mode. I'm not sure where this text is controlled from. -- Beland (talk) 22:18, 2 December 2025 (UTC)[reply]
Ah, it looks like I tried to fix those before. The problem only shows up when the content is displayed in context after deletion, not when viewing the content on a standalone page. I tested this time and I seem to have actually fixed the first two. Your changes to the third page make it much better standalone; not sure how to test that as a sequence. -- Beland (talk) 23:20, 2 December 2025 (UTC)[reply]
Greetings, The long-standing PetScan I've run like for months, is now showing error: Io(Io(Custom { kind: Uncategorized, error: "failed to lookup address information: Name or service not known" })). Against "Category - All articles lacking sources". If an expert here can investigate, that would be great. I know from in the past, sometimes, PetScan "magically" recovers, so I will try again tomorrow. (not urgent) Thanks. JoeNMLC (talk) 20:52, 3 December 2025 (UTC)[reply]
Producing a tag with an attribute is easy: {{#tag:foo|txt|bar=baz}} generates <foo bar="baz">txt</foo>. But I'm writing a template where the attribute should be optional: depending on a template parameter, there should either be the attribute with a value or no attribute at all. I thought code like this should work (using a dummy condition here): {{#tag:foo|txt|{{#if:true|bar=baz}}}}. But it doesn't, the attribute is ignored: <foo>txt</foo>. It looks like {{#tag}} only recognizes attributes if the = character occurs directly in the value, even {{#tag:foo|txt|bar{{=}}baz}} doesn't work. So far, I can only think of two ways to make this work:
Wrap the whole code in an {{#if}} clause that contains two separate invocations of {{#tag}}. Of course, that leads to a lot of code duplication, since the invocations are identical except for the attribute.
Always generate an attribute, but give it a dummy name (and value, maybe) in the case where I don't actually want it: {{#tag:foo|txt|{{#if:true|bar|dummy}}=baz}}. This works in my case (the next parser phase seems to simply ignore the unknown attribute), but it feels a bit dirty.
Unfortunately there isn't. I usually do #2 if I am calling a template, but I prefer #1 if I am calling parser function or anything that is a black box. P.S. The way I do #2 is usually by adding a hash: {{my template|txt|{{#if:true||#}}bar=baz}}. --Grufo (talk) 00:12, 4 December 2025 (UTC)[reply]
Can't remember if I posted this here, but exactly what the question says. Does wikitext support this for CSS? My userpage previously used a lot of custom CSS and had a bunch of contrast issues depending on which colour mode a user is on, which I need to fix by creating overprecise CSS. thetechie@enwiki (she/they | talk) 22:30, 3 December 2025 (UTC)[reply]
Not sure if this is the right place to post this, but I have an issue on my user page in which the userbox group does not work. If you expand it, it simply says {{{userboxes}}}. How do I fix this? thetechie@enwiki (she/they | talk) 22:31, 3 December 2025 (UTC)[reply]
@TheTechie:{{Userbox group}} recognises five named parameters: |collapse=|style=|title=|userboxes= and |footer= (it also recognises one positional parameter as an alias for |userboxes=). You're trying to use |title= (which is valid), |collapsed= and |content= (which are not). --Redrose64 🌹 (talk) 22:54, 3 December 2025 (UTC)[reply]
Why are there two templates with such similar names but different syntax that a typo of not hitting space could cause massive issues that aren't easily solvable? Should they be merged? ~212.70~ ~2025-31733-18 (talk) 04:58, 5 December 2025 (UTC)[reply]
I've started making a game log for the 1996–97 Golden State Warriors season unfortunately it's not formatting the way it should and has some inexplicable | in it and I want those gone, can someone assist me with the game log formatting?
Well, Trappist, I did basically post that I'm no expert... Thank you, I'm toddling off to fix it now. Always appreciate your expertise & advice. - Shearonink (talk) 15:16, 4 December 2025 (UTC)[reply]
The XTools gadget I think. it adds a link to the users contribs for the user who most recently edited that page Best wishes, Macaw*!20:00, 4 December 2025 (UTC)[reply]
Macaw*, I can't see any links like that in XTools, but there's a link at the bottom of xtools for reporting an issue. If you do so, make sure to include where the link is. — Qwerfjkltalk20:34, 4 December 2025 (UTC)[reply]
@Macaw*: Please say from the beginning where you see a reported problem. The contributions link works in all places I have tested but you load 68 scripts in User:Macaw*/common.js. I tracked it down to this script by Opencooper:
I have adjusted the code above to possibly do what you want. You can also use "transparent" instead of white, but it can cause problems in dark mode. – Jonesey95 (talk) 15:33, 5 December 2025 (UTC)[reply]
Works for me, I know because I tested it here. --Redrose64 🌹 (talk) 23:02, 1 December 2025 (UTC)
with this in your CSS: 
Moved from Wikipedia:Teahouse
View all 34 community-submitted tasks that were resolved last week. For example, the issue where search boxes on some Commons pages showed no results due to switch from SpecialSearch to MediaSearch, has now been fixed. [5]
