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.
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.
Hi all! We have good news to share regarding the ongoing problem with graphs and charts affecting all wikis that use them.
As you probably know, the old Graph extension was disabled in 2023 due to security reasons. We’ve worked in these two years to find a solution that could replace the old extension, and provide a safer and better solution to users who wanted to showcase graphs and charts in their articles. We therefore developed the Charts extension, which will be replacing the old Graph extension and potentially also the EasyTimeline extension.
After successfully deploying the extension on Italian, Swedish, and Hebrew Wikipedia, as well as on MediaWiki.org, as part of a pilot phase, we are now happy to announce that we are moving forward with the next phase of deployment, which will also include your wiki.
The deployment will happen in batches, and will start from May 6. Please, consult our page on MediaWiki.org to discover when the new Charts extension will be deployed on your wiki. You can also consult the documentation about the extension on MediaWiki.org.
If you have questions, need clarifications, or just want to express your opinion about it, please refer to the project’s talk page on Mediawiki.org, or ping me directly under this thread. If you encounter issues using Charts once it gets enabled on your wiki, please report it on the talk page or at Phabricator.
Sannita (WMF) Does it support horizontal bars? During the outage, I tinkered with a stopgap replacement that is template-based, and uses horizontal bars. For example, on Talk- or other non-mainspace pages, horizontal bars would permit the use of timeline-based charts that grows vertically downward as the timeline period is longer, unlike wit vertical bars which get thinner and thinner until they are squished into lines or become merged if too long a period is specified, unless averaging is introduced, which loses some detail and may hide sudden peaks. Meanwhile, the entire chart can be collapsed so it takes almost no vertical space on the Talk page except for the header. I am thinking in particular of the old, {{pageviews}} template often used among the headers of Talk pages, and disabled during the outage. Is there an option for a horizontal chart in the new extension? For some examples of horizontal pageviews from the temporary {{Xreadership}} template implemented as a stopgap during the outage, see Talk:Houthis, Talk:Same-sex marriage, or Talk:Pokémon. Thanks, Mathglot (talk) 21:26, 10 May 2025 (UTC)[reply]
@Mathglot Hi, thanks for your question. No, horizontal bars are not implemented yet, also because there would be a challenging time in showing them on mobile, given the reduced space. You can open a task on Phabricator, and then linking it back to me, so that I can put it on the developers' radar. If you have problems with Phabricator, then I can help you opening a ticket. Let me know. Sannita (WMF) (talk) 09:00, 13 May 2025 (UTC)[reply]
Sannita (WMF), thanks. Phab task added as requested. I can imagine various reasons why horizontal bars aren't implemented yet, but given that they already work on mobile in other contexts (see demo), I don't understand that reasoning. Thanks, Mathglot (talk) 16:17, 13 May 2025 (UTC)[reply]
Can the template list be closed by default in the editing window?
Note: Actually, it is just after the edit window, and is labeled "Templates used in this preview".
It is really annoying to have to scroll by a huge list of templates (especially in country list articles) before I can see changes, or see the full preview.
Mediawiki remembers whether the template list was collapsed or not from before. Most of the time though I don't pay attention because I am not on country list pages, and the template list is much shorter. And I may have looked for some template on that short list.
But then I happen to be working on a country list page, and have this problem. I would like some CSS to keep the template list closed by default regardless of my last use of it. --Timeshifter (talk) 17:58, 10 May 2025 (UTC)[reply]
Yeah, the keyboard shortcut isn't sticky. Fwiw, I don't think this is something you can do with CSS, but there might be a javascript solution. Afraid I'm not personally familiar enough with the editor to make any specific suggestions for that, tho. -- Avocado (talk) 18:59, 10 May 2025 (UTC)[reply]
The keyboard shortcut is not working for me at all on Firefox on Win 10 Pro.
It works for me in Firefox on Mac -- or at least, the "fold all"/"unfold all" ones do. You do have to click into the edit box first, which sometimes gets me. (And this is in the 2010 source editor, fwiw, with syntax highlighting enabled.) -- Avocado (talk) 23:19, 10 May 2025 (UTC)[reply]
I see the problem. We are talking about 2 different things. You are talking about within the edit window.
I am talking about the template dropdown list after the edit window labeled "Templates used in this preview". I added a note at the top of the thread. --Timeshifter (talk) 23:38, 10 May 2025 (UTC)[reply]
The "Templates used in this preview" list, and the other collapsible lists below the edit form, should remember their state. If you collapse it, then it should start off collapsed the next time you open the editor. Matma Rextalk00:07, 11 May 2025 (UTC)[reply]
Timeshifter knows that. They wrote I would like some CSS to keep the template list closed by default regardless of my last use of it., so what they want is for the collapse state to be forgotten, and re-initialised to collapsed. The related HTML is
which makes the triangles point to the right when the list is collapsed. Collapsing and uncollapsing are done by means of some JavaScript, which:
if the current state is collapsed: removes the mw-editfooter-toggler-collapsed and mw-collapsed classes, and also removes the display: none; declaration
if the current state is uncollapsed: restores the mw-editfooter-toggler-collapsed and mw-collapsed classes, and also restores the display: none; declaration
The presence or absence of the mw-editfooter-toggler-collapsed class determines whether the triangle points right or down.
The presence or absence of the display: none; declaration declaration determines whether the list is hidden or visible.
I can write a CSS rule (or two) which will make the list start off collapsed, but the collapsing would then be permanent; I think that JavaScript is required to then make it uncollapsed on click. --Redrose64 🌹 (talk) 10:42, 11 May 2025 (UTC)[reply]
If you can get it to always be collapsed when I load, reload, or save a page that would be great. But I want to be able to manually open the list. I'll use whatever works that I can add to my user CSS and user JS. --Timeshifter (talk) 18:18, 11 May 2025 (UTC)[reply]
Oh, sorry I misread that. You could do this in your user JS:
Some wikis support using different colors in light theme and dark theme. Is this feature currently supported in English Wikipedia, or not yet? Upset New Bird (talk) 12:00, 10 May 2025 (UTC)[reply]
@Isaacl, @Timeshifter: For example, I mean how to show the colors "white", "yellow", "purple", "red", "black" and "gray" in light mode as "black", "blue", "#80FF80", "cyan", "white", and "gray" in dark mode. Upset New Bird (talk) 00:07, 11 May 2025 (UTC)[reply]
There's no simple way to shift specific colours to different colours. The link I provided has a link to a page listing the standard set of colours, named by their role in the user interface design. You can redefine the corresponding custom CSS properties to different colour values, but you'll have to be comfortable with writing CSS to do that. isaacl (talk) 02:32, 11 May 2025 (UTC)[reply]
Thanks for making me aware of the light-dark() feature, first deployed by browsers in 2024. I'm not sure what your planned usage is, though. If you're using it in text you're writing, for example, then using light-dark() will ignore the user's light/dark mode Wikipedia setting in favour of the user's setting in the browser/OS. It also will only work with newer browsers. The page to which I linked explains how to write CSS rules that will follow the user's light/dark mode Wikipedia settings, including if they configure it to follow the browser/OS setting. isaacl (talk) 04:23, 11 May 2025 (UTC)[reply]
Clearly there's some subtleties in the dark mode implementation that I don't know about... The other issues I described remain. What is your intended usage? isaacl (talk) 08:41, 11 May 2025 (UTC)[reply]
The light-dark() function is quite new, it was added to CSS Color Module Level 5 with the 29 February 2024 revision. Since this doc is a W3C Working Draft, it should not be relied upon. To those sceptics who have told me in the past that W3C Working Drafts will eventually make it to W3C Recommendation, please note that the color-contrast() function, which was last described in the 28 April 2022 revision, has since been dropped. --Redrose64 🌹 (talk) 11:59, 11 May 2025 (UTC)[reply]
@Redrose64: It seems that English Wikipedia supports "light-dark()" function, but does not support "color-contrast()" function. This table shows different colors by the user's color mode (light or dark). [2]Upset New Bird (talk) 01:01, 12 May 2025 (UTC)[reply]
Support for light-dark() and color-contrast() is nothing to do with Wikipedia, it's entirely in your browser. If your browser doesn't support color-contrast(), that does not surprise me, as it was removed from the CSS Color Module Level 5 spec, which as I already mentioned, is a draft and subject to amendment. --Redrose64 🌹 (talk) 16:02, 12 May 2025 (UTC)[reply]
Are you referring to a specific table? For tables in general, I think it's better to just use colours from the standard set. The actual colours used in light and dark modes will be centrally maintained, and can be adjusted by skins. isaacl (talk) 14:30, 11 May 2025 (UTC)[reply]
I don't understand what is the current problem with tables in dark mode, or why any issues can't be handled by using the standard set of colours. isaacl (talk) 04:35, 12 May 2025 (UTC)[reply]
Note: The "light-dark()" feature is now available in all three major browser engines, and becomes Baseline Newly available as of 13th May 2024. See [3]. Upset New Bird (talk) 02:48, 12 May 2025 (UTC)[reply]
AIUI, light-dark is insufficient to support all display modes on Wikipedia. There is "light mode", "dark mode", and "OS mode" here. light-dark meaningfully supports only the last of the three. Izno (talk) 03:03, 12 May 2025 (UTC)[reply]
light-dark() reacts to the color-scheme property that is set by the dark mode toggle, so it should work also for "forced" light and dark mode. hgzh08:56, 12 May 2025 (UTC)[reply]
Trying to balance the party colours in this template I am creating
Hello, with the 2025 Australian Senate Election results currently being counted I am creating this template to create a new standard for Joint Tickets in the senates results. Currently they are raw modified tables in the results at the New South Wales and Victoria bits (look for the joint tickets involving HEART, People First and Libertarians), and on the pages there the 3 colours are balanced. I am trying to replicate this with the template to replace the need for modifying the table directly but it isn't working properly and I have no idea how to get the 3 colours to balance. The documentation provides an example from the NSW results of that election. Any tips or help on how I can get these colours to be balanced? Thanks in advance! Comfisofa (talk) 11:41, 11 May 2025 (UTC)[reply]
When I'm doing WP:DRAFTNOCAT/WP:USERNOCAT cleanup, because Category:Living people is massive (thus impossible to search manually) and collects new draft and user sandbox pages daily instead of once in a blue moon, I do an incategory search on it a few times a day instead of only dealing with it when the weekly reports run. I've noticed that for several weeks now that after getting a draft or user page out of the category there's been a lag before the page would actually drop out on refreshing the search — in the past a page would typically drop out close to instantly in some cases, and within 30 seconds to one minute in others, but for several weeks now it's taken more like 10 to 15 minutes before a page would drop.
Today, however, all of the draft/user pages that were in the category this morning still haven't dropped out more than two hours after being removed. So I wanted to ask, is there something wrong with incategory searching all of a sudden? Bearcat (talk) 15:39, 12 May 2025 (UTC)[reply]
Thanks for noticing, indeed the indexing pipeline got stuck today around 13:30 UTC and no updates were being processed. It failed very early in the bootup process which didn't trigger our typical alerts. New alerts have been added, and that system has been restarted and is now processing edits again. most of the pages in the example have cleared out, the rest of the backlog should finish soon.
As to the update latency, around 5 minutes is the expected minimum latency for edits to make it into search today. Somewhere between 5 and 8 is probably most typical. That was indeed on a 30s cycle previously, but the update pipeline had to change to include asynchronously generated information (such as article topic predictions) which pushed the minimum update time to around 5 minutes.
Thanks for figuring this out so quickly. No worries on the five to ten minute drop time — it is a minor hassle when I'm doing draft/user nocat cleanup, because I have no way to distinguish "page that just hasn't dropped yet" from "the creator added the categories back again one minute after I removed them" or "I actually missed a category the previous time" without checking the page a second or third time, but all things considered if that's the worst thing that happens to me all day it isn't that big a deal. So if there's a clear reason for it, it's a thing I can continue to live with — but obviously pages not dropping hours later was something weird, so thanks for resolving it. Bearcat (talk) 20:17, 12 May 2025 (UTC)[reply]
I'm familiar with the Raw Watchlist view, but that's alphabetical. Is there any way to get a listing of all articles on one's own watchlist, ordered by date added? -- Avocado (talk) 21:35, 12 May 2025 (UTC)[reply]
Ah, thank you. Yes, that would indeed make it impossible. And even if they started recording it in the future, that wouldn't help much with pruning my present watchlist based on prior waves of now-abandoned editing interests, nor with retrieving a list of pages I've edited in a particular period (though the latter could probably be achieved through some grouping of contribution log records, I suppose). -- Avocado (talk) 12:07, 14 May 2025 (UTC)[reply]
Thanks! That looks potentially useful. Personally, there's some select stuff from ancient history that I'd be sad to have removed. Hence the desire to manage it myself but with date as sorting criterion. -- Avocado (talk) 21:08, 15 May 2025 (UTC)[reply]
OTOH, sorting by the wl_id field may give you an equivalent to "ordered by date added" (just not the date itself). But I don't know of any way to do that without direct access to the production databases; existing UIs look like they generally sort by namespace and title, or don't sort at all. Anomie⚔13:01, 14 May 2025 (UTC)[reply]
Oh, sorting by ID is a good idea! Is that data accessible via API? If so, where might one look for docs about that? I could probably produce a quick-and-dirty script to pull that data in an afternoon. Even if the ID isn't in perfect chronological order, it'd be better than nothing for current purposes. -- Avocado (talk) 14:32, 14 May 2025 (UTC)[reply]
I appreciate your looking into it! I think I'm going to try to pull some of this off by reading the full contribution history from the API, since I have "watch page" on by default. Should be close enough. For read-only access, is one required to apply for bot operation permissions before creating a bot password for authenticated access to the API? -- Avocado (talk) 23:57, 14 May 2025 (UTC)[reply]
Latest tech news from the Wikimedia technical community. Please tell other users about these changes. Not all changes will affect you. Translations are available.
Weekly highlight
The "Get shortened URL" link on the sidebar now includes a QR code. Wikimedia site users can now use it by scanning or downloading it to quickly share and access shared content from Wikimedia sites, conveniently.
Updates for editors
The Wikimedia Foundation is working on a system called Edge Uniques, which will enable A/B testing, help protect against distributed denial-of-service attacks (DDoS attacks), and make it easier to understand how many visitors the Wikimedia sites have. This is to help more efficiently build tools which help readers, and make it easier for readers to find what they are looking for. Tech News has previously written about this. The deployment will be gradual. Some might see the Edge Uniques cookie the week of 19 May. You can discuss this on the talk page.
Starting May 19, 2025, Event organisers in wikis with the CampaignEvents extension enabled can use Event Registration in the project namespace (e.g., Wikipedia namespace, Wikidata namespace). With this change, communities don't need admins to use the feature. However, wikis that don't want this change can remove and add the permitted namespaces at Special:CommunityConfiguration/CampaignEvents.
The Wikipedia project now has a Wikipedia in Nupe (w:nup:). This is a language primarily spoken in the North Central region of Nigeria. Speakers of this language are invited to contribute to new Wikipedia.
Developers can now access pre-parsed Dutch Wikipedia, amongst others (English, German, French, Spanish, Italian, and Portuguese) through the Structured Contents snapshots (beta). The content includes parsed Wikipedia abstracts, descriptions, main images, infoboxes, article sections, and references.
The /page/data-parsoid REST API endpoint is no longer in use and will be deprecated. It is scheduled to be turned off on June 7, 2025.
The IPv6 support is a newly introduced Cloud virtual network that significantly boosts Wikimedia platforms' scalability, security, and readiness for the future. If you are a technical contributor eager to learn more, check out this blog post for an in-depth look at the journey to IPv6.
When you attempt to create a double redirect you are shown a warning that includes a suggested fix (i.e. if Foo is a redirect to Bar and you attempt to create a redirect to Foo, MediaWiki shows a warning recommending you change the target of your new redirect to be Bar).
Seven months ago (see Wikipedia:Village pump (technical)/Archive 216#Keep getting logged out), a problem was reported where the login cookie was failing to be recognised on English Wikipedia. This was resolved after about ten days. Something very similar has begun happening today. Steps to reproduce:
Assume that you are starting off as having explicitly logged out earlier in the day (Special:UserLogout)
At any page on English Wikipedia, log in
Follow some links to elsewhere within English Wikipedia, observe that you are still logged in on each page.
Go to any page on meta:. Observe that you are not logged in.
Follow any link to another page on meta:. Observe that you are logged in.
Return to English Wikipedia. Observe that you are no longer logged in.
Follow any link to another page on en.wp. Observe that you are logged in once again.
This has been happening to me for much longer than just yesterday, so it sounds like you were getting lucky.
I've seen suggestions that cookie blocking systems (and Firefox has this level of protection on by default particularly, IDK about the other browsers) can block the relevant cookies, so I went in and set exceptions for meta, auth, and en.wp, and it's still happening for me. I need to try fresh login here, but it's not encouraging.... Izno (talk) 22:25, 13 May 2025 (UTC)[reply]
While cumbersome, using the page history to select the earliest edit you want to see, than selecting "next edit" on each successive page would do that. Donald Albury13:19, 14 May 2025 (UTC)[reply]
For those using a desktop browser, the "Browse history interactively" dropdown that appears at the top of a diff page lets you hover over a bar graph to see the edit summaries of each edit. isaacl (talk) 15:45, 14 May 2025 (UTC)[reply]
Thanks both! Hitting "next edit" works indeed, but gets a bit tiresome.
The "Browse history interactively" dropdown only shows up on diff pages and requires you to scroll up, click a diff, scroll down, try to find what changed, et cetera.
With this new script you can just click and hold the slider and drag the mouse to the left and right.
I have a script on my PC that checks for new entries in various categories. For example, the Category:2022 deaths generally reports just a couple of additions on most days. However, starting on Monday, it exploded and reported bulk additions and still is. The articles themselves have not been updated, their histories show no recent changes and I could not find a specific template that has recently been changed. Hunting around implies that this is happening for other birth and death categories, but not for other person-related categories. (FYI, I call the API with a query like this: action=query&list=categorymembers&cmnamespace=0&cmtype=page&cmlimit=50&cmstart=2025-05-11T23:59:59.999&cmend=2025-05-11T00:00:00&cmsort=timestamp&cmdir=descending&formatversion=2&format=json&cmprop=title.) What happened around midday on Monday? Was there a database change? Did I miss a template change that has triggered bulk updates? Why does the API report changes that the articles do not? Answers on a postcard please — GhostInTheMachinetalk to me10:13, 14 May 2025 (UTC)[reply]
I can tell you that the cmstart and cmend parameters work off of the field that's reported with cmprop=timestamp. What may have caused mass updates to that, I have no idea. Anomie⚔13:09, 14 May 2025 (UTC)[reply]
See Talk:Coronation of Mindon Min. I added a new thread about a contradiction between the article and another. It appears to have been eaten by the "Overall assessment" section of the transcluded GA review above it. I can't work out why. Can anyone fix it? Thanks, DuncanHill (talk) 10:46, 14 May 2025 (UTC)[reply]
Hello guys! I did some changes on "Wi-Fi Protected Setup", and i want them to be verified by someone to make sure they are correct. If you want, and know something about Wi-Fi networks and cybersecurity, i would be grateful if you check them. Thanks in advance!
Discussion about an article's contents takes place on its corresponding talk page (in this case, Talk:Wi-Fi Protected Setup). There's a link to it below the article title. If no one responds, you can look at the list of associated WikiProjects at the top of the talk page, and use their talk pages to post a link to the discussion on the article talk page. isaacl (talk) 15:59, 15 May 2025 (UTC)[reply]
If there is a See also link in one article that read "[{See also|Radley_College#Rowing}]" and then the Rowing section had a name change to "Rowing Club", the See also link in the previous article breaks. This should be fixed. See also sections should look for name changes and adjust accordingly. NotQualified(talk)22:00, 14 May 2025 (UTC)[reply]
Broken anchors aren't fixed automatically and that can't be done because they can break for a variety of reasons. There's nothing magical about see also sections in the Wikipedia database. Graham87 (talk) 07:13, 15 May 2025 (UTC)[reply]
No. (not right now). They are also not unique, which is an additional challenge if you would ever want to do so (Think of repeating sub-sub-section names in an article for instance). —TheDJ (talk • contribs) 11:31, 15 May 2025 (UTC)[reply]
@NotQualified: By something that is anchor-able, do you mean content that could be given an anchor? Anchors are, in essence, the HTML id= attribute; and that attribute may be applied to all HTML elements (without exception). Since an HTML element of one type or another may be placed at any point in the content of a page, it follows that everything is anchorable. Such tagging would occur on every single edit, which would be impractical. --Redrose64 🌹 (talk) 21:00, 15 May 2025 (UTC)[reply]
Did the CSS just change on mobilein desktop view as seen on mobile? Page body text on my phone is a lot denser today. Chrome on a Galaxy phone. Largoplazo (talk) 14:59, 15 May 2025 (UTC)[reply]
Not on mobile, but on the usual Vector2022 view on a desktop I'm seeing text that appears a lot denser today as well. It's hard to tell because I don't have before and after screenshots, but my suspicion is that the leading (space between consecutive lines of text) has been reduced. I went into my custom css and increased the line-height (mine has a line ".vector-body {font-size: 115%; line-height: 150%;}" but you may not want such extreme values) and it looked a lot better again. —David Eppstein (talk) 18:28, 15 May 2025 (UTC)[reply]
Not sure if bigger... MonoBook here, and while I don't see that, I do see the pink box atop the editing window that - for instance - has the this-user-has-been-blocked-by-who-and-why looks to have larger text today. Or maybe it's always been this way and I'm losing my mind, that can't be ruled out? - The BushrangerOne ping only19:27, 15 May 2025 (UTC)[reply]
Aha. That would explain the larger text in the block notices. I also noticed the text in the box here looks odd (@Parsecboy: since I'm linking your page for an example!). And I'm going to guess that Wikimedia Commons got rolled out on Wednesday, which might explain the Metadata text looking bigger that I noticed there yesterday... - The BushrangerOne ping only22:48, 15 May 2025 (UTC)[reply]
I removed it from Chrome checking whether any extensions were causing problems (it was bad memory). Replaced it and it no longer shows up in Tools. Windows 11. Than ks. Doug Wellertalk16:03, 15 May 2025 (UTC)[reply]
I'm curious to know whether this module can be edited to format the team header to use Template:Diagonal_split_header or _2. When adding either template to an individual table using team_header={{diagonal split header 2|Home|Away}} the result only shows the class and style in plain text, presumably because the module creates the table using class="wikitable plainrowheaders"? StatmanIbrahimovic (talk) 18:24, 15 May 2025 (UTC)[reply]
I've already informed the tool creator but I don't think it is just a problem with this link. Any idea when this might be fixed? Thanks. LizRead!Talk!19:25, 15 May 2025 (UTC)[reply]
That's interesting. I also work with User:DreamRimmer bot II and that's been out of commission for the past three hours, I'm not sure there is any connection. It's a challenge when the tools you use every day don't function, you learn how much you rely on them. Thanks for the update on your end, Ahecht. LizRead!Talk!19:36, 15 May 2025 (UTC)[reply]
invoke:cite causing harv and sfn no-target errors false positives
Neither of those 'fixes' should be pursued. The 'fix' is to fix Module:Footnotes so that it recognizes {{#invoke:Cite|xxxx|....}} and can then extract the necessary info from the invoke.
Editor Hike395 rewrote most of Module:Footnotes/anchor_id_list to the point where I no longer recognize the code so I am not the best person to say if what you have added was a good addition. I do notice that the 'template' names created from #invokes are not listed in template_list. Edit this version of my sandbox (don't change anything) and click Show preview. Then, in the Parser profiling data dropdown, click show under Lua logs. You should see something like this:
template_list=table#1{["Cite SSRN/new"]=1,["Template:Harvard citation no brackets/sandbox"]=1,}
In my sandbox page there are two {{#invoke:Cite|news|...}}. Change one of them to {{Cite news|...}}. Show preview; Show Lua logs. You should see something like this:
template_list=table#1{["Cite SSRN/new"]=1,["Cite news"]=1,["Template:Harvard citation no brackets/sandbox"]=1,}
The answer to Trappist's question is because the template_list variable is populated by template_list_add() here, and that function accepts the raw template string Module:Footnotes/anchor_id_list/sandbox#L-762 at line 762, not the hacked version produced by template_get_name Module:Footnotes/anchor_id_list/sandbox#L-762 at line 761. Is that right? It seems to me that template_list_add() at line 762 can be replaced by list_add(template_name, template_list). But I'm not 100% sure.
By the way, 95% of the code in Module:Footnotes/anchor_id_list is still Trappist's code. You can see my diff here. I changed the way the global variables were updated (for caching and to handle errors correctly), rewrote a little code for efficiency, handled "fascicles", and added citeref_patterns_make(), but that was it.
To answer Ahect's question -- I'm a bit nervous about turning all invokes into fake-o templates, because I don't know if that will generate any false positives or negatives. You may want to only turn {{#invoke:cite|XYZ}} into {{cite XYZ}}, because that seems safer and more predictable. — hike395 (talk) 02:54, 16 May 2025 (UTC)[reply]
This version (permalink) of Gaza genocide directly precedes the edit that converted Module:Cite web and others to Module:Cite. Note that that §References section in that older version also has lots of harv errors. From that, I conclude that the change to Module:Citedid not cause any new problems. It appears that these errors began appearing 2025-05-03 at this edit (permalink). Since that time no one has bothered to notice or if they noticed, did not say anything. Of course, that harv error message is hidden so that might explain why the silence. No doubt, there are other articles where these sorts of error messages have not been noticed.
For those interested, Module:Cite web, Module:Cite news, and a few others are soon to be deleted so look now before their deletion prevents you from confirming what I have written.
The edit on the 3rd May marked the use of #invoke, so it seems to be #invoke that is causing the problem. As for not raising it earlier, I am sorry but I have a life. DuncanHill (talk) 21:45, 15 May 2025 (UTC)[reply]
Fixed and added a comment to help future editors understand why the template is written the way that I just did. —CX Zoom[he/him] (let's talk • {C•X}) 12:59, 12 May 2025 (UTC)
View all 27 community-submitted tasks that were resolved last week.
