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 five days.
Template:Welcome-COI-acc already has logic (near the end) to suppress the category if the template was added to the page years ago. Perhaps it could also check that the page title doesn't end in ".js". Certes (talk) 19:00, 5 August 2023 (UTC)
The typical way to deal with this is simply to wrap the JS page in <nowiki>s. Since these are automatically changed, that could be fixed on the script side.
On the software side, while I have observed no actual consensus on the matter, my belief is that we want to continue to allow wikitext parsing in such content model pages. You could of course file a task to turn it off for JS content models (just as it is off for Scribunto). Izno (talk) 19:30, 5 August 2023 (UTC)
For the latter item, yes. For the former, that would be at WT:TW. I have observed some people say it is a good thing, not a bad thing, because that it is what allows such pages to be categorized, among other qualities. Izno (talk) 00:22, 6 August 2023 (UTC)
Before you request it be turned off, you might want to review T43155 where the parsing was explicitly re-added after it was accidentally removed back in 2012. It's one of those things that wouldn't be done if this were new code, but may need to be kept for hysterical raisins since it already exists. Anomie⚔ 01:42, 6 August 2023 (UTC)
Indeed, there are times when it is desirable, for instance if a user no longer requires their /chick.css user subpage (because that skin was removed ten years ago), they can tag it {{db-user}}, and it will show in Category:Candidates for speedy deletion by user. --Redrose64 🌹 (talk) 07:32, 6 August 2023 (UTC)
Another benefit of parsing is that many .js comments include wikilinks to imported scripts, enabling toolsmiths to notify their customers of changes. Certes (talk) 17:56, 6 August 2023 (UTC)
What would probably be most lost is categorization. en.wp doesn't tend to categorize their scripts but I think other wikis might. Izno (talk) 21:43, 6 August 2023 (UTC)
@Novem Linguae: Should Twinkle wrap twinkleoptions.js in <nowiki>...</nowiki>? Nardog (talk) 17:21, 6 August 2023 (UTC)
One thing to potentially experiment with is whether JSON content model pages do the same as JS pages in parsing stored wikitext. That could be a viable alternative for storing the config. Izno (talk) 17:24, 6 August 2023 (UTC)
Looks like twinkleoptions.js is already wrapped in nowiki. Example. The diff in the original post, User:AfroThundr3007730/twinkleoptions.js, is from 2018, so perhaps that is from before the nowiki patch was deployed to Twinkle. Looks like User:AfroThundr3007730/twinkleoptions.js is the only twinkleoptions page in that particular category. Search. I'll go ahead and use my interface administrator permissions to fix the original page. If there's a low number of other pages discovered, let me know and I can do some manual editing. –Novem Linguae (talk) 08:41, 8 August 2023 (UTC)
Vector 2022 table of contents: bolded heading differing from current scroll position
Tɛmplet:Tracked
Usually the bolded heading in the table of contents on the side with the Vector 2022 skin matches the current scroll position in the primary page content area. However at present, when viewing the incidents' noticeboard, this behaviour only persists when the current heading or sub-heading is near the top of the page. Once it scrolls away, the bolded heading reverts to a heading of a different section. This behaviour seems to have started with this edit to the section in question. The preceding version behaves as usual, while the following version does not. Can anyone figure out how the wikitext included (via transclusion) to collapse some headings has caused the change in behaviour, and how it may be fixed? (Pinging SGrabarczuk (WMF) and OVasileva (WMF).) isaacl (talk) 18:44, 5 August 2023 (UTC)
Hey @Isaacl. Thanks for raising this issue. We'll look into it. SGrabarczuk (WMF) (talk) 01:47, 9 August 2023 (UTC)
Identify political leader pages lacking the Infobox officeholder template, along with a user-friendly filter for sorting them by election or state. I have work on Tamil Nadu state & 2021 Assembly Election. Thanks in advance. - IJohnKennady (talk) 03:36, 6 August 2023 (UTC)
Maybe try Petscan, with a category selected, a high depth of subcategories (e.g. 10), and a "doesn't have template" {{Infobox officeholder}} selected. Example. Perhaps choose more specific categories and templates to reduce the # of results to a manageable level. Hope this helps. –Novem Linguae (talk) 04:39, 6 August 2023 (UTC)
Thank you very much i'll explore this. --IJohnKennady (talk) 13:55, 6 August 2023 (UTC)
And i have one more doubt, how to find, How many pages didnt have Electoral performance heading. _IJohnKennady (talk) 11:52, 9 August 2023 (UTC)
I have a question about the abuse filter: How can I write a filter to block users who continuously add spam content like the example in the image on the right-hand side?
Thank you. Plantaest (talk) 06:34, 6 August 2023 (UTC)
Would need to _target something. Got any ideas? Are the accounts all new editors? Do they put the same thing in each of their edits? Do they put the same thing in each of their edit summaries? Do they only _target certain pages? etc. –Novem Linguae (talk) 06:48, 6 August 2023 (UTC)
Both accounts that I mentioned above are new accounts. Shortly after their creation, they started engaging in disruptive behavior. As for other factors, I will investigate further. Thank you. Plantaest (talk) 06:52, 6 August 2023 (UTC)
For an simple filter you could do 'contains_any(added_lines, "_target line")' where '_target line' is whatever words he is adding. When you find one, I would use the search to see whether other people are using that same phrase. You can use vi:Special:AbuseFilter/test within 30 days of the edits to test what your filter is matching. Snævar (talk) 19:31, 8 August 2023 (UTC)
@Plantaest You're going to need to find "common patterns" on your own but something like below?
In any case it's neccesary to debug your code over and over to eliminate false positives before enabling the filter, especially when you choose block as the action to take. Dragoniez (talk) 03:26, 9 August 2023 (UTC)
A very inelegant solution is to write a SQL query to list your subpages, run it regularly using {{Database report}} and watchlist its output. Certes (talk) 18:04, 6 August 2023 (UTC)
Another inefficient option is to use a web monitor such as Distill on Special:Prefixindex/User:Whoever. Certes (talk) 18:08, 6 August 2023 (UTC)
If you have a page in your userspace that you regularly check, you could transcludeSpecial:PrefixIndex/User:DuncanHill/ to it. But you would still have to check manually because changes to the original page do not show up as changes to the _target page. -- Random person no 362478479 (talk) 20:47, 6 August 2023 (UTC)
Try putting {{user subpages}} (add your username as a parameter) somewhere you will see it frequently. -- Verbarson talkedits 14:18, 9 August 2023 (UTC)
Hello!
I wanted to translate page about Nastazja Staniszewska from polish to english, but wikipedia says that it could be done only by experienced users. What can i do about it? MadAurochs (talk) 15:12, 7 August 2023 (UTC)
If this is the Polish-language Wikipedia biography you are referring to, [1] I suspect a direct translation wouldn't be accepted, since by English-language Wikipedia rules, more coverage in independent sources would probably be needed to meet our notability criteria. You'd need to find such sources, and incorporate them into the article.
You cannot use WP:CX if you are not WP:Extended confirmed, meaning you need to have been on English Wikipedia for 500 edits and 30 days. If you still believe the biography is suitable, 1) you will need to do the translation by hand, and 2) I would recommend using WP:AFC for additional review. Izno (talk) 17:20, 7 August 2023 (UTC)
Latest tech news from the Wikimedia technical community. Please tell other users about these changes. Not all changes will affect you. Translations are available.
Recent changes
Mobile Web editors can now edit a whole page at once. To use this feature, turn on "⧼Mobile-frontend-mobile-option-amc⧽" in your settings and use the "Edit full page" button in the "More" menu. [2]
The drop-down templates in the Edit Window have always had a feature that if you click on one of the templates, input an URL, and clicked on the little autofill symbol next to it, it would automatically fill out the template. As of today, that's not working. I have three different browsers, and it's not working on any of them. It was working fine recently. Maybe it's because I'm trying to do that with a PDF? Feedback? — Maile (talk) 23:10, 7 August 2023 (UTC)
This is the Village Pump for technical issues on the English Wikipedia. It looks like sr:Википедија:Трг/Техника is the corresponding page on sr.WP. – Jonesey95 (talk) 22:36, 8 August 2023 (UTC)
Provide option to block font substitution on an SVG image
The SVG image creators create font family lists with a choice of fonts that meet the demands of Windows, Macs, Linux, and even Wikimedia.
So if Wikimedia just left it alone it would work fine. As long as there was a free font at the end of the font family list that was metric-compatible to the other fonts. See :
Wikimedia has the narrow free font Liberation Sans. But it is not being used. A wider font is being substituted for one of the other fonts in the list. Possibly DejaVu Sans:
I decided to make a test: Lahabali kɔligu:Font test for a Village Pump discussion.svg It appears that it either isn't processing fallback fonts anymore (just jumping right to the default Deja Vu Sans) or every unknown font is being "defined" as Deja Vu Sans so fallback never happens. Either way that sounds like a bug that should be reported in Phabricator. Anomie⚔ 22:06, 8 August 2023 (UTC)
Thanks, Anomie. Maybe you can post this at Phabricator. I am almost always baffled by aspects of it when I post there. You sound like you are more familiar with it.
From your image it looks like DejaVu Sans is being substituted for Lato and 'Helvetica Neue' and bogus font names. It looks like Liberation Sans is being substituted for Helvetica and Arial.
I think your image test would be better if "This is a test:" was in front of them all. Then comparisons would be longer and clearer. Right now I am just comparing "This is" for each one.
It looks like the narrower Liberation Sans should be the default fallback font instead of the wider DejaVu Sans characters and character spacing. --Timeshifter (talk) 22:52, 8 August 2023 (UTC)
Detect multiple transclusions of a template within a page
I'm looking for a way to detect multiple transclusions of a template within a page using a module, to add a maintenance category. Let's say we have {{A}} {{A}} in a single page, in which case I want to add e.g. Category:Multiple transclusions, but none when we only have {{A}} (single transclusion). Does anyone have any ideas? Dragoniez (talk) 02:57, 9 August 2023 (UTC)
This is not information that is tracked at a database level. Why do you want this ? Generally multiple transclusions shouldn't really be too much of a problem. —TheDJ (talk • contribs) 10:05, 9 August 2023 (UTC)
Many clever people have tried to answer similar questions here, and I don't think it is possible. Would the module which adds the category be called from template A or in some other way, or is either ok? If you tell us more about the problem, we may be able to think more laterally and find an indirect solution. Certes (talk) 11:08, 9 August 2023 (UTC)
Say, A is a template like {{Old XfD multi}}, which can have a bunch of "data rows". These rows don't need to be separated into multiple occurrences of the template and can be merged. I'm wondering if a bot can do this merging task. But if you develop such a bot, you'll need a way to get a list of the relevant pages, and I thought it'd be one option to have a tracking category so that we can collect page titles using list=categorymembers. I can think of other ways to do this, like using list=search, but the category solution seems to me to be most efficient, although I don't know if it's fundamentally possible to get a lua module to add such a category. This is why I thought I'd ask this. Dragoniez (talk) 12:04, 9 August 2023 (UTC)
If you're using a bot then a search like this should do the job. You may want to change the list of namespaces, perhaps to just Talk:; the only hit outside the one I listed is Template:Old XfD multi/doc. Certes (talk) 12:21, 9 August 2023 (UTC)
insource: doesn't discover redirects [3] with a non-matching name. PrimeHunter (talk) 14:58, 9 August 2023 (UTC)
In a module can't you just use string.gmatch for the template name (or {{[Tt]emplate name) on the page content and iterate the result to get the count? — Jts1882 | talk 16:53, 9 August 2023 (UTC)
Weno has a broken infobox displaying a giant redlink. I can't figure out how to fix it as it's somehow procedurally generated. Anyone know what to do? Ten Pound Hammer • (What did I screw up now?) 17:40, 9 August 2023 (UTC)
The template documentation is no help; it just says it "should not be used from article namespace pages". (Didn't we have a whole bunch of giant rfcs all saying not to do the sort of things that template does? Or did they suddenly start going the other way over the last year while I've been mostly inactive?) —Cryptic 17:49, 9 August 2023 (UTC)
I believe the most recent discussion on Wikidata in infoboxes is Wikipedia:Wikidata/2018 Infobox RfC, which came to no consensus. Unfortunately there's been a frozen conflict here, with regular "no consensus" results, for about as long as I've been editing. * Pppery *it has begun... 17:56, 9 August 2023 (UTC)
And I also removed the clearly wrong "This template is rated as pre-alpha" from the documentation, since it has 520 mainspace uses. * Pppery *it has begun... 18:01, 9 August 2023 (UTC)
It looks like the problem is that Template:Infobox settlement/Wikidata says {{#if: {{#property:P31}} | [[{{#property:P31}}]] }} which then strings the two P31 parameters of wikidata:Q1009384 together and turns them into a link. I am not sure that P31 can always be interpreted as "settlement type", certainly not as something that can be turned into a piped link. Jo-Jo Eumerus (talk) 18:16, 9 August 2023 (UTC)
Per the RFC, that Wikidata property call is invalid, since it does not check to see if the value is sourced. I have expanded the documentation for the template to explain that it should not be used in article space until it is modified to conform to the RFC's sourcing requirement. – Jonesey95 (talk) 18:25, 9 August 2023 (UTC)
I'm honestly inclined to just nominate it for deletion - the chance of the warning you added becoming anything other than dead letter otherwise is negligible and it seems like nobody wants to do the necessary work. * Pppery *it has begun... 18:52, 9 August 2023 (UTC)
No objections from me. The doc has had a note about the template needing to be fixed for three years, and the template has mostly gotten worse since then. It seems to be abandoned. – Jonesey95 (talk) 19:34, 9 August 2023 (UTC)
Does anyone know whether {{#invoke:WikidataIB|getValue|rank=best|qid={{{qid|}}}|Pxxx|fetchwikidata=ALL|onlysourced=yes}} is the right replacement for {{#if: {{#property:Pxxx}} | [[{{#property:Pxxx}}]] }} code? To solve the source thing. Jo-Jo Eumerus (talk) 20:01, 9 August 2023 (UTC)
So I did the only logical thing: Make a JavaScript program to get all the base domains from the table, and then (through a CORS proxy) see which ones are broken.
@QuickQuokka I'm not sure if you're looking for an answer to a question, or a pat on the back (LOL), but this sounds far too technical a point to raise at the Teahouse. I wonder if you might be better off making whatever point it is that you're making over at WP:VPT? I'm really not trying to be rude, but the folks over there understand much the same sort of stuff that you seem to. Me on the other hand: nah! Best wishes, Nick Moyes (talk) 20:30, 9 August 2023 (UTC)
Yeah I was basically just looking for answers as to why they're there. Are they supposed to be there? I don't know. QuickQuokka[talk • contribs] 20:33, 9 August 2023 (UTC)
At Gambling_age#Countries, a table, sorting Age column gives second Illegal then None then Illegal so sorting is not working. I do not know why. --109.175.38.25 (talk); 11:21, 10 August 2023 (UTC)
That column has data-sort-type="number", so the entries are sorted numerically. Entries with no numeric value remain sorted by country name, regardless of what non-numeric value (Illegal, None, etc.) they contain. Certes (talk) 11:47, 10 August 2023 (UTC)
I don't know where to lodge this information about Wikipedia:WhoWroteThat, since the page is a redirect to mediawiki; perhaps someone here is also active there or knows who to ask on en.wiki about this. Until Bocaranda, I've found WhoWroteThat to be reliable. Lately, it is glitching at Nelson Bocaranda, and I'm wondering if the interlanguage links are somehow throwing it off (since I started noticing it about the time I added them, but I can't be certain that was it). Today, it is attributing a ton of text that I wrote to WMrapids; as examples, look at the sentence using "knee pain", and the sentence starting with "Contrary to Article 143". And then halfway through the "Responses" section, it stops working entirely. SandyGeorgia (Talk) 15:18, 10 August 2023 (UTC)
@WhatamIdoing: who first told me about WWT, and may know where to put this; I don't do mediawiki. SandyGeorgia (Talk) 15:21, 10 August 2023 (UTC)
Community Tech handles that, so the best person to reach out to is probably MusikAnimal (WMF). WhatamIdoing (talk) 16:16, 10 August 2023 (UTC)
Hmm, I'm not sure what's going wrong here! I have filed phab:T344011 so we can investigate further. Thanks for the bug report, MusikAnimal (WMF) (talk) 18:26, 10 August 2023 (UTC)
In the future, for WhoWroteThat, bugs can be filed directly on Phabricator using this link. Just make sure to put "Who-Wrote-That" in the tags section. This will skip a couple of middlemen and pings. Creating a ticket with the correct tag emails the developers of that tool, such as MusikAnimal. Hope this helps. –Novem Linguae (talk) 12:30, 11 August 2023 (UTC)
The page for Rod Adkins is not appearing on the mobile web browser version.
It seems like the fire diamond in Chembox Template for all chemical compounds is misaligned on mobile devices. The background image is moved completely to the right and some of the numbers / letters overlap the diamond's boundaries. I've checked on multiple devices - all with latest version of Chrome Browser. The alignment is alright on PC. Check example : Benzene. I can't fix it (as I have no idea how it works). Can anyone having knowledge about it help? Thanks in advance!! Ray Frost (talk) 18:18, 10 August 2023 (UTC)
All the diamonds are misaligned to the down-left. Is there a way to edit it? As I said, I have no idea how that code works and I really don't want make it worse. Ray Frost (talk) 09:07, 11 August 2023 (UTC)
This is because the <figure> around the image has large margins on mobile, while it has no margins on desktop. This might be an oversight in the mobile styling for images, but I'm not 100% sure. It can be corrected by making use of TemplateStyles to style this element. —TheDJ (talk • contribs) 11:04, 11 August 2023 (UTC)
I have created {{NFPA 704 diamond/styles.css}} and tried to add it to the sandbox, but it hasn't fixed anything. I have almost no idea how to do TemplateStyles, though. Izno is usually good at them. – Jonesey95 (talk) 13:30, 11 August 2023 (UTC)
I'll reach out to him then and ask if he can help. Thanks Jonesey95!! Ray Frost (talk) 13:34, 11 August 2023 (UTC)
TheDJfixed the CSS for me, and now Benzene looks fine in mobile view. I was so close! Someday I may understand how CSS works. Good job, team! – Jonesey95 (talk) 16:01, 11 August 2023 (UTC)
Wow, it looks PERFECT now. Thanks a lot for helping!! (Besides I don't even know what CSS is XD) Thanks Again!! Ray Frost (talk) 16:04, 11 August 2023 (UTC)
@Jonesey95, .content is "outside the reach" of TemplateStyles. All TemplateStyles selectors are "hoisted" to .mw-parser-output. This means that when you wrote .content, what you really wrote was .mw-parser-output .content. Now, the .content element exists outside the .mw-parser-output element, so in reality you were _targeting nothing, as when you have multiple selectors they must be in the order of the HTML containers. This is something specific to TemplateStyles and that selector would have otherwise worked if it were in, say, Common.css, since that does not hoist CSS. The hoisting is one of the reasons that TemplateStyles is "safe". (There is one exception to how this hoisting works: you may _target classes on body and html if you write them as body.class or html.class so long as you pick another child element, say, body.class .infobox. The corresponding output will be body.class .mw-parser-output .infobox and similar.)
As for imagemap, the name of the HTML element is map. Izno (talk) 18:58, 11 August 2023 (UTC)
It's an easy fix, but I wanted to make sure it isn't intentional first. Actualcpscmscrutinize, talk 14:45, 11 August 2023 (UTC)
Strange one that. It's easy to make it display the list from 7 days ago instead of 8, but it looks like it's always been like that. Is it actually being used anywhere? Black Kite (talk) 15:05, 11 August 2023 (UTC)
Please go ahead. Thank you for the ping. Lourdes 05:24, 12 August 2023 (UTC)
I think the reason I made it 8 days was because the AfD should be deleted or kept after seven days of discussion (it would be the eighth day when the AfDs would be closed). Just double check and make the change if you think that is prudent. Thanks, Lourdes 05:29, 12 August 2023 (UTC)
I'm using a few MOS scripts for copy-editing, the list is at User:Lallint/common.js. However, the scripts, for example the EngvarB scripts, only seem to work on my common.js page, and not in article namespaces. Going into source editor with the scripts in article namespace does show some of the scripts, but some are missing, and the ones that show do nothing when clicked. When I go into source editor on my common.js page, all of the scripts show, and I can use the scripts as intended. I'm using the latest version of Firefox, and I've tried chrome but it does the same thing. I've had this problem for a year, but its still happened. Lallint 01:05, 12 August 2023 (UTC)
Those scripts are not compatible with the 2017 editor. Turn off "Use the wikitext mode inside the visual editor" in Preferences. Nardog (talk) 05:38, 12 August 2023 (UTC)
Hey, during a Quarry query today, I saw that there was a replag on the English Wikipedia. Then, coming here, I remember that when this happened last time, it was suggest that a link to the replag page be put in the VPT FAQs page but that doesn't seem to ever been done. Anyone want to take on that small task? LizRead!Talk! 02:06, 12 August 2023 (UTC)
Resolved