Policy | Technical | Proposals | Idea lab | WMF | Miscellaneous |
- Table of contents
- First discussion
- End of page
- New post
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.
Database error
I got this error while trying to save an edit:
[c42d457a-4fe1-4b6f-b69f-0cf0ad0ab0b9] 2022-08-16 04:08:56: Fatal exception of type "Wikimedia\Rdbms\DBTransactionError"
-- 64.229.88.43 (talk) 04:10, 16 August 2022 (UTC)
- And then
[11857e39-c6b5-4941-93c0-a4aed63ca40a]
and other new codes as I try to save the same edit or modify my edit and save -- 64.229.88.43 (talk) 04:12, 16 August 2022 (UTC)- There's an ongoing issue — try saving the edit again in a few minutes — TheresNoTime (talk • she/her) 04:15, 16 August 2022 (UTC)
- UPDATE: I'm able to save this edit now. It seems to have cleared up about the same time as the CAPTCHA error I reported below? -- 64.229.88.43 (talk) 04:48, 16 August 2022 (UTC)
- I wanted to share with you the wiki page including the detailed incident report: wikitech:Incidents/2022-08-16_x2_databases_replication_breakage. Apologies for the disruption- error messages appeared during 36 minutes for some users, preventing or making more difficult edits and certain actions, such as probably the ones mentioned on the section below. This was quickly detected by automated monitoring and a fix was implemented. Technology measures have been put in place and more are planned soon to avoid the same or similar issues from happening in the future. Again, sorry for the issues, and happy editing! --JCrespo (WMF) (talk) 18:24, 18 August 2022 (UTC)
- UPDATE: I'm able to save this edit now. It seems to have cleared up about the same time as the CAPTCHA error I reported below? -- 64.229.88.43 (talk) 04:48, 16 August 2022 (UTC)
- There's an ongoing issue — try saving the edit again in a few minutes — TheresNoTime (talk • she/her) 04:15, 16 August 2022 (UTC)
CAPTCHA missing
On a different edit that triggers the CAPTCHA mechanism, the CAPTCHA image is missing, so one is unable to respond to the CAPTCHA challenge as there is no image to interpret.
I assume this is related to the database problem I reported above? (this edit is unrelated to that one) -- 64.229.88.43 (talk) 04:21, 16 August 2022 (UTC)
- That I'm not sure about.. which page & is it consistently not appearing? (i.e. close the tab, re-open, refresh the page etc.) — TheresNoTime (talk • she/her) 04:39, 16 August 2022 (UTC)
- Yes, it's consistently not appearing. It happens when I try to use {{subst:submit}} on any draft article -- 64.229.88.43 (talk) 04:42, 16 August 2022 (UTC)
- UPDATE: It just cleared. After reloading a couple of minutes after my last set of tries, the CAPTCHA is now loading properly -- 64.229.88.43 (talk) 04:46, 16 August 2022 (UTC)
- I can also save the edit I was having problems with with the database error reported above... so it seems interlinked? -- 64.229.88.43 (talk) 04:47, 16 August 2022 (UTC)
- Please see my comment on the previous section. Apologies again. --JCrespo (WMF) (talk) 18:27, 18 August 2022 (UTC)
- wikitech:Incidents/2022-08-16_x2_databases_replication_breakage is interesting, though I don't see the connection between what the DBAs did to strip cached edits and in-process atmoicized writes, and the generation or display of CAPTCHAs. Perhaps I'm missing something since I'm not a DBA fluent with how MediaWiki uses MariaDB to generate squiggly images for verification challenges. Thanks for the info -- 64.229.88.43 (talk) 05:12, 19 August 2022 (UTC)
- Hi, thanks for your question. I am certainly not a MediaWiki expert, but there is a dependency between captcha functionality for enwiki and mainstash, which was what temporarily had a disruption:
root@db1152[mainstash]> select count(*) FROM objectstash where keyname like 'enwiki:captcha:%'\G *************************** 1. row *************************** count(*): 13604 1 row in set (0.012 sec)
- Mainstash used to live on Redis but now lives on MariaDB servers.
- This, added to the temporal coincidence of both the start and end of the issue, based on error logs, make me quite sure both issues were related. This is why I mentioned on the report edit-related activities, as things beyond pure wiki content edits were potentially affected, but not reads.
- Again, sorry for the disruption. --JCrespo (WMF) (talk) 09:00, 19 August 2022 (UTC)
Copy-paste article title also gets edit links
When I triple-click on the title of an article, it looks like the correct text is selected. But, when I copy-paste that, I find that I've also got the "edit" and "edit source" links. It's not just article titles; the same thing happens on any header.
Well, sometimes. See the second screenshot. The first line, with just "Columbia University" was pasted when I was in the source editor. The second line with the edit links was after I switched to the visual editor and pasted the same text. If I Command-Shift-V (Paste and Match Style), I just get the "Columbia University" part.
Any idea what's going on here? I'm sure this is at least partially platform-dependent (I'm on MacOS, Chrome), but perhaps there's some different markup which might give the browser/OS a better hint about how much text to include when doing copy-paste? -- RoySmith (talk) 14:28, 16 August 2022 (UTC)
- @RoySmith which skin are you using? — xaosflux Talk 14:42, 16 August 2022 (UTC)
- Vector. -- RoySmith (talk) 14:45, 16 August 2022 (UTC)
- @RoySmith one thing I notice is that you have that text there are all, that is not default. I'm assuming you are using a gadget (perhaps MediaWiki:Gadget-edittop.js) or a userscript that is inserting those extra links in to the title? That along with many of your other scripts (e.g. from User:RoySmith/common.js) may be causing portions of the page to load at different times. To troubleshoot, turn off all your scripts and see if you can narrow this down to a conflict between scripts first. — xaosflux Talk 14:53, 16 August 2022 (UTC)
- Hmmm, I seem to remember that was the same advice you gave me last time :-) Anyway, I tried it with an empty common.js, which didn't change anything. I disabled "Add an [edit] link for the lead section of a page" (which I assume is Gadget-edittop?), no effect there either. Well, it made the link on the lead section go away, but I still had the same issue on section heads. -- RoySmith (talk) 15:19, 16 August 2022 (UTC)
- @RoySmith thank you, that you are getting it on section headers too is useful - as having the links there are "standard". — xaosflux Talk 15:21, 16 August 2022 (UTC)
- BTW, not that this is any surprise, but if I paste into TextEdit or Stickies, I get the "edit" and "edit source" links (and they work when you click on them). Here's the RTF that's generated if I paste into TextEdit:
- -- RoySmith (talk) 15:27, 16 August 2022 (UTC)
{\rtf1\ansi\ansicpg1252\cocoartf2639 \cocoatextscaling0\cocoaplatform0{\fonttbl\f0\fswiss\fcharset0 Helvetica-Bold;\f1\fswiss\fcharset0 Helvetica;} {\colortbl;\red255\green255\blue255;\red255\green255\blue255;\red0\green0\blue0;\red66\green71\blue75; \red9\green47\blue157;} {\*\expandedcolortbl;;\cssrgb\c100000\c100000\c100000;\cssrgb\c0\c0\c0;\cssrgb\c32941\c34902\c36471; \cssrgb\c2353\c27059\c67843;} \margl1440\margr1440\vieww11520\viewh8400\viewkind0 \deftab720 \pard\pardeftab720\partightenfactor0 \f0\b\fs28\fsmilli14400 \cf0 \cb2 \expnd0\expndtw0\kerning0 \outl0\strokewidth0 \strokec3 22 June 2022 \f1\b0\fs20 \cf4 \strokec4 [{\field{\*\fldinst{HYPERLINK "https://en.wikipedia.org/w/index.php?title=User:RoySmith/sandbox&veaction=edit§ion=1"}}{\fldrslt \cf5 \ul \ulc5 \strokec5 edit}}\'a0|\'a0{\field{\*\fldinst{HYPERLINK "https://en.wikipedia.org/w/index.php?title=User:RoySmith/sandbox&action=edit§ion=1"}}{\fldrslt \cf5 \ul \ulc5 \strokec5 edit source}}] \f0\b\fs28\fsmilli14400 \cf0 \strokec3 \
- I haven't been able to duplicate this yet. There are a few new tickets open about having extra newline characters in some cases, but that's different. — xaosflux Talk 15:34, 16 August 2022 (UTC)
- Well, this has gotten even more interesting. I can reproduce this Safari, but not Firefox. That in itself isn't hugely surprising since Chrome and Safari share the same Webkit heritage (at least originally). What is astounding to me is that I can repro it in a Chrome incognito window, not logged in! It only happens if you triple-click to select. If you drag-select, or double-click on a single word heading, you don't get the "[edit]".
- At this point, I'm leaning towards this being a Webkit bug. On a Mac, triple-click means something like "select the entire paragraph". In a browser, I guess that means something like, "select the entire enclosing element which meets some criteria". I'm not quite sure what that criteria is, but it looks like what it's doing is grabbing everything in the enclosing h1 (h2, etc) tag, which includes the "[edit]" link. I can't fault Webkit for having a different definition of how much text to select than other browsers do, but it certainly seems wrong that the range of text copied should differ from the range of text highlighted.
- Now I need to figure out how much further I want to go down this particular rathole :-) -- RoySmith (talk) 17:54, 16 August 2022 (UTC)
- Correct. Triple click is a paragraph select. The H1 is interpreted to be the paragraph. Everything within that block is selectable text and that includes the edit links. It's just that the links are visually positioned 'out of band'. Because of the weird positioning it is difficult for the browser to show that the edit links were also selected. You can actually see it slightly on H2 headers, the selection color creates a line just above the underline in that case. As far as I know this has always been like this. —TheDJ (talk • contribs) 08:31, 17 August 2022 (UTC)
- I haven't been able to duplicate this yet. There are a few new tickets open about having extra newline characters in some cases, but that's different. — xaosflux Talk 15:34, 16 August 2022 (UTC)
- @RoySmith thank you, that you are getting it on section headers too is useful - as having the links there are "standard". — xaosflux Talk 15:21, 16 August 2022 (UTC)
- Hmmm, I seem to remember that was the same advice you gave me last time :-) Anyway, I tried it with an empty common.js, which didn't change anything. I disabled "Add an [edit] link for the lead section of a page" (which I assume is Gadget-edittop?), no effect there either. Well, it made the link on the lead section go away, but I still had the same issue on section heads. -- RoySmith (talk) 15:19, 16 August 2022 (UTC)
- @RoySmith one thing I notice is that you have that text there are all, that is not default. I'm assuming you are using a gadget (perhaps MediaWiki:Gadget-edittop.js) or a userscript that is inserting those extra links in to the title? That along with many of your other scripts (e.g. from User:RoySmith/common.js) may be causing portions of the page to load at different times. To troubleshoot, turn off all your scripts and see if you can narrow this down to a conflict between scripts first. — xaosflux Talk 14:53, 16 August 2022 (UTC)
- Vector. -- RoySmith (talk) 14:45, 16 August 2022 (UTC)
- This happens to me in Chrome+Monobook when using the reply tool. (And I also get the annoying "Convert formatting to wikitext? You pasted content with rich formatting. Would you like to convert this formatting to wikitext?" popup. I never ever want to paste content with rich formatting. Is there a way to disable this?) —Kusma (talk) 20:26, 16 August 2022 (UTC)
.mw-editsection
is set touser-select: none;
. I assume it's overridden by something on your end. Nardog (talk) 10:07, 17 August 2022 (UTC)- User-select has a whole let of edge cases however. So when you drag to select, you probably cannot copy the edit section indeed, because according to the spec those items are not selectable if the selection was "started" before those items. Select all, similarly has conditions determining if such user-select none items are copied or not. But with a triple click paragraph select, I suspect there is no 'start point' of the selection and no specific behaviour has been defined and/or implemented to enable the hiding of the content.
- The reason for these additional rules is that they wanted to protect consumers from websites that attempt to make the whole page non-copyable, as well as websites that try to manipulate the content of your pasteboard (consider someone using select none, to turn a inconspicuous command line example into a command that does something dangerous when pasted and execute..) —TheDJ (talk • contribs) 12:45, 17 August 2022 (UTC)
- Ah, this is all starting to make more sense now. If I examine the HTML (i.e. "Elements" pane in Chrome), the edit link is:
<a href="/w/index.php?title=Charles_Bathgate_Beck&veaction=edit§ion=1" class="mw-editsection-visualeditor" title="Edit section: References">edit</a>
- Chrome says the computed style for the anchor tag includes
user-select: none
, inherited frommw-editsection.
So, it doesn't look like anything is overriding it per-se as Nardog suggests. On the other hand, the MDN page on user-select says, "WebKit ... violates the behavior described in the spec", which does seem to be what's happening here. -- RoySmith (talk) 13:22, 17 August 2022 (UTC)- PS @TheDJ regarding your edge cases, if I go to Charles Bathgate Beck and drag-select over both the page title and the "An unassessed article..." line below it, the edit links don't show as selected. But when I copy-paste that, they're included in the pasted text. -- RoySmith (talk) 13:30, 17 August 2022 (UTC)
Preferences history?
This is prompted by the above #Copy-paste article title also gets edit links thread, but I'm breaking it out as a new section because it's a different question. Is there anyway to see your history of what preferences you've enabled/disabled and roll back to a previous state? Testing which user scripts might be doing something is fairly easy because each change to my common.js is logged and it's trivial to just roll back to the original state. When I'm playing the "which preference caused this?" game, not so much. I end up just keeping manual notes of what I'm turning off, but that's a pain and error-prone.
Also, is there any way to map from the user-visible strings ("Add an [edit] link for the lead section of a page") back to the associated gadget (MediaWiki:Gadget-edittop.js)?
And since I'm in whining and complaining mode, it would also be nice if scripts could be made to confess what they've done by adding a comment to the HTML they produce. That way, I could look at the HTML in a browser developer window and instantly see, "Oh, that link was added by Foo.js". As opposed to rummaging through different preferences pages (plus my common.js) trying to guess which it might be. -- RoySmith (talk) 15:47, 16 August 2022 (UTC)
- For the last part, depending on what is being added a script could add an additional class to it. — xaosflux Talk 15:52, 16 August 2022 (UTC)
Is there anyway to see your history of what preferences you've enabled/disabled and roll back to a previous state?
No.Also, is there any way to map from the user-visible strings ("Add an [edit] link for the lead section of a page") back to the associated gadget (MediaWiki:Gadget-edittop.js)?
I have previously suggested that every gadget description should have a link to its documentation or script page. Int admins (including me) are apparently lazy on the point. I will accept edit requests though if you'd like to work through the list of gadgets. :)
- Last per Xaos. That seems like a per-script thing you can request. Izno (talk) 16:01, 16 August 2022 (UTC)
is there any way to map from the user-visible strings ... back to the associated gadget
- perhaps the easiest way is to go to Special:Gadgets which shows the descriptive text for each gadget, together with links to the JavaScript and CSS pages that the gadget primarily uses. --Redrose64 🌹 (talk) 21:39, 16 August 2022 (UTC)
- While it's not history, you might appreciate that there's a link on Special:Preferences to download "My account data from this project", and it includes your current preferences. You could treat it as a backup copy. Now someone just needs to write a gadget to restore it ;) Matma Rex talk 02:09, 19 August 2022 (UTC)
Unhiding Hidden Errors in References via the CSS Question
The help for this error says that I can ask questions about Cascaded Style Sheets here, rather than at the Help Desk. If I should go to the Help Desk, then I will. I am trying to edit an article that is extensively referenced. On a Preview of my edit, I get the message that:
Script warning: One or more {{cite book}} templates have maintenance messages; messages may be hidden (help). I viewed Help:CS1 errors and tried to do what it said.
So I went to User:Robert McClenon/common.css, or rather, to the empty subpage that might have been there. I put in the content that the Help said, beginning with .mw-parser-output and tried to Preview the output. It says that there is a warning because Warning: Element (span.cs1-hidden-error) is overqualified, just use .cs1-hidden-error without element name.
What is overqualified? What should I do?
Robert McClenon (talk) 11:01, 17 August 2022 (UTC)
- @Robert McClenon: You can safely ignore the warning.
It is a linter warning meant to assist in writing stylistically good (in the opinion of the people who programmed the linter) CSS, but it will work just fine despite the warning, and is not something you need to concern yourself with.
"Overqualified" in this context means that (if your coding style is the same as the linter's author's) it should be specific enough to use.cs1-hidden-error
, which means "find any element that has the classcs1-hidden-error
", instead ofspan.cs1-hidden-error
, which means "find any element of typespan
that has the classcs1-hidden-error
. Rummskartoffel 12:38, 17 August 2022 (UTC) - The code at Help:CS1 errors#Error and maintenance messages is:
.mw-parser-output span.cs1-hidden-error {display: inline;} /* display hidden Citation Style 1 error messages */
- The higher specificity with
span
is actually necessary here to override this in Module:Citation/CS1/styles.css:
.cs1-hidden-error {
display: none;
color: #d33;
}
- For example, consider 3D pose estimation#cite note-7 (permanent link). The last reference has a hidden error message:
{{cite journal}}: Cite journal requires |journal= (help)
. It is only displayed ifspan
is included in the code. @Robert McClenon: In User:Robert McClenon/common.css you changedspan.
tospan-
and omitted what to do:{display: inline;}
. As Rummskartoffel said, you can safely ignore the warning you get with the correct code. PrimeHunter (talk) 01:40, 18 August 2022 (UTC)
mbox is now TemplateStyled only
Please report any issues you see at MediaWiki talk:Common.css#mbox is now TemplateStyled only. Thanks! Izno (talk) 17:50, 17 August 2022 (UTC)
FizzBuzz doesn't work
I've tried to write a FizzBuzz program in wikimarkup (no particular reason). Obviously, this isn't a serious project, but if anyone can see a.problem in my (incredibly messy) wikicode, it's at User:Qwerfjkl/sandbox/27. ― Qwerfjkltalk 20:12, 17 August 2022 (UTC)
- Here's a cleaner and working version using Template:For nowiki:
{{for nowiki|<br />|<nowiki>{{#ifeq:{{mod|{{{1}}}|3}}|0|Fizz|{{#ifeq:{{mod|{{{1}}}|5}}|0|Buzz|{{{1}}}}}}}</nowiki>|count=100}}
Your original {{for loop}} based code doesn't work because, first, you have too many levels of escaping of curly braces and pipes, and second, by the time {{replace}} gets called, the templates in its argument have already been evaluated so it's already done the calculation based on the literal string "%1" * Pppery * it has begun... 20:56, 17 August 2022 (UTC)- PpperyJust curious, how would you change this so that the fizz rule is "divisible by 3 or has a 3 in it" and the buzz rule is "divisible by 5 or has a five in it" (with fizz still being checked for first).Naraht (talk) 21:22, 17 August 2022 (UTC)
{{for nowiki|<br />|<nowiki>{{#if:{{#ifeq:{{mod|{{{1}}}|3}}|0|x}}{{#ifeq:{{#invoke:String|find|{{{1}}}|3}}|0||x}}|Fizz|{{#if:{{#ifeq:{{mod|{{{1}}}|5}}|0|x}}{{#ifeq:{{#invoke:String|find|{{{1}}}|5}}|0||x}}|Buzz|{{{1}}}}}}}</nowiki>|count=100}}
. This gets really ugly really fast. * Pppery * it has begun... 21:29, 17 August 2022 (UTC)
- PpperyJust curious, how would you change this so that the fizz rule is "divisible by 3 or has a 3 in it" and the buzz rule is "divisible by 5 or has a five in it" (with fizz still being checked for first).Naraht (talk) 21:22, 17 August 2022 (UTC)
- Using a Scribunto module seems like it should be considered a loss. (At that point what's stopping you from coding it entirely in Lua?) Nardog (talk) 22:07, 17 August 2022 (UTC)
- It's a reasonable programming challenge (which is what this is, presumably), to treat the existing set of modules as the baseline of an esoteric programming language and build up from that. That baseline is no less arbitrary than the no-Lua baseline of whatever functions the developers saw fit to install in PHP, unless you are saying we should regress all the way to {{qif}}. Note that all versions, even the original in Qwerfjkl's sandbox, use Lua somewhere, although Qwerfjkl's version and my first version hide it behind template wrappers, which I could have done in my second version if I saw fit to.
{{for nowiki|<br />|<nowiki>{{#if:{{#ifeq:{{mod|{{{1}}}|3}}|0|x}}{{#ifeq:{{strfind short|{{{1}}}|3}}|0||x}}|Fizz|{{#if:{{#ifeq:{{mod|{{{1}}}|5}}|0|x}}{{#ifeq:{{strfind short|{{{1}}}|5}}|0||x}}|Buzz|{{{1}}}}}}}</nowiki>|count=100}}
. * Pppery * it has begun... 23:04, 17 August 2022 (UTC)- @Pppery, thanks, I had no idea {{For nowiki}} existed. ― Qwerfjkltalk 06:28, 18 August 2022 (UTC)
- It's a reasonable programming challenge (which is what this is, presumably), to treat the existing set of modules as the baseline of an esoteric programming language and build up from that. That baseline is no less arbitrary than the no-Lua baseline of whatever functions the developers saw fit to install in PHP, unless you are saying we should regress all the way to {{qif}}. Note that all versions, even the original in Qwerfjkl's sandbox, use Lua somewhere, although Qwerfjkl's version and my first version hide it behind template wrappers, which I could have done in my second version if I saw fit to.
- Kindly, what is the point of this? If this were a real world case, you would be told to use Lua and to move on. This board is not for self-exploration unless it has the purpose of improving Wikipedia.
- Please move on. Izno (talk) 06:59, 18 August 2022 (UTC)
- I dunno how you template gurus do it. Whenever I see code that looks like this, I always get a very strong itch to rewrite it in lua. –Novem Linguae (talk) 21:56, 18 August 2022 (UTC)
Regarding upcoming talk page improvements
I realise that the upcoming talk page is live on some wikis (example: bn:আলাপ:ভারত). Currently, it is only in Article talk pages, but all other talk and pseudo-talk pages retain old design. I like everything about new talk page except that the new level 2 headings (default) appears like level 3 & below headings separated from each other using ---- (4 hyphens), which I don't appreciate. Where should I report this? Thanks! —CX Zoom[he/him] (let's talk • {C•X}) 07:06, 18 August 2022 (UTC)
- mediawikiwiki:Talk:Talk pages project/Usability is probably the right place, but it's less focused on appearance than it is on usability. Izno (talk) 07:25, 18 August 2022 (UTC)
- Thanks! —CX Zoom[he/him] (let's talk • {C•X}) 09:16, 18 August 2022 (UTC)
Deactivating certain global scripts per local project
Hello!
Is there a way to have some globally activated user scripts (Meta - global.js) not affect certain local projects (exclude them)? - Klein Muçi (talk) 09:04, 18 August 2022 (UTC)
- Change enwiki to the wiki you want to disable scripts. You can see a working example at my global.js (from line 55 until end) but it's a mess tbh. —CX Zoom[he/him] (let's talk • {C•X}) 09:15, 18 August 2022 (UTC)
if (mw.config.get('wgDBname') !== 'enwiki') { mw.loader.load('Script1'); mw.loader.load('Script2'); And any other usual js stuff // + Any message you wish to keep }
- @CX Zoom, thanks a lot! Exactly what I wanted. And thank you for the detailed example! :) - Klein Muçi (talk) 10:17, 18 August 2022 (UTC)
Template font size
{{Who's Who}} generates reduced size font. There are over 2,000 transclusions and the majority seem to be uses within the references section, where the font is already 90%, so the further reduction violates MOS:SMALL (e.g Maggie O'Farrell ref #8). What's the best way to resolve this? There could be a template parameter to specify font reduction when the template is used in normal-size text (if there are any, someone would have to find those and edit them). Is there a better way? MB 17:45, 18 August 2022 (UTC)
- MB, a similar issue is present in template {{Cite OED}}, used for example in ref #10 in Alchemy#References. The problem comes from Template:Link note, which has hardcoded CSS
font-size:0.95em; font-size:90%;
. I think the best solution is just to remove this bit of the CSS – output of {{Link note}} is already A) wrapped in parentheses and B) also has CSScolor:#555
(which some people don't like either). —andrybak (talk) 17:57, 18 August 2022 (UTC)- It looks like there are 34k more from {{subscription required}} that would also be fixed. MB 18:05, 18 August 2022 (UTC)
- 95% (Link note) times 90% (references) is sufficiently sized for MOS:SMALL (>85%). There is a way that this could depend on where the text appears (TemplateStyles).
- That said, our MOS:SMALL probably needs to be adjusted to point out the absolute minimum in pixels/pts, as text sizes on Wikipedia have generally increased with each new skin. There is also CSS
min()
which is newer but could be used later in the future (or double declared even today e.g.font-size: 95%; font-size: clamp(14px, 85%, 1em);
or some such). Izno (talk) 18:35, 18 August 2022 (UTC)- I think using a percentage as guidance is still preferable, under the assumption that readers will use their browser zoom capability to set the base font size to a comfortable size for them. (I know this is not universally true, but it's a reasonable default assumption, as teaching someone how to use their browser zoom feature will enable them to set their desired font size on Wikipedia and other sites.) isaacl (talk) 21:44, 18 August 2022 (UTC)
- Pixels being an example of "the minimum font size is actually X size, and we should not let anything go lower than that, percentages or otherwise". Our 85% rule is based on computing what the minimum font size was in Monobook, but Vector, new Vector, and Timeless all have larger font sizes, so it stands to reason that we can use smaller fonts and that really, it should be defined by the absolute minimum. Pixel-based sizes still respond to zoom anyway. Izno (talk) 22:06, 18 August 2022 (UTC)
- Yes, precisely because pixel-based sizes zoom, I think a percentage is still preferable. A user will use the zoom function to adjust the base font to a comfortable size, no matter what pixel size the skin has set. Thus specifying a reasonable minimum size as a percentage of the base font size will automatically scale to the user's preference. isaacl (talk) 22:14, 18 August 2022 (UTC)
- Pixels being an example of "the minimum font size is actually X size, and we should not let anything go lower than that, percentages or otherwise". Our 85% rule is based on computing what the minimum font size was in Monobook, but Vector, new Vector, and Timeless all have larger font sizes, so it stands to reason that we can use smaller fonts and that really, it should be defined by the absolute minimum. Pixel-based sizes still respond to zoom anyway. Izno (talk) 22:06, 18 August 2022 (UTC)
- I think using a percentage as guidance is still preferable, under the assumption that readers will use their browser zoom capability to set the base font size to a comfortable size for them. (I know this is not universally true, but it's a reasonable default assumption, as teaching someone how to use their browser zoom feature will enable them to set their desired font size on Wikipedia and other sites.) isaacl (talk) 21:44, 18 August 2022 (UTC)
Page previews displaying vandal images long after vandal edits were reverted
Some time ago today, the article Kharijites, today's featured article, was vandalised with vulgar images edited over the entire lead section. This resulted in this image (warning: graphic) becoming the page preview image for over an hour now. I'm fairly confident this is some server-side issue, as I've cleared my cache, and purged the article, the image, and the main page, and yet still the explicit image from the vandal attack is still showing up in the page preview on the main page of the site. I find it completely unacceptable that such a quick vandal edit could have such long-lasting effects. Is there anything that can be done about this on the technical side of things? Hecseur (talk) 19:22, 18 August 2022 (UTC)
- I don't see the graphic image. I hadn't attempted the preview until seeing this thread. Killiondude (talk) 19:25, 18 August 2022 (UTC)
- I carried out a dummy edit on the article, which seems to have sorted it out. Or maybe it was the recreation of a transcluded page without the images in question. *shrugs* Sdrqaz (talk) 19:31, 18 August 2022 (UTC)
- I am still seeing the image on mobile preview and header after accessing the article in the app yesterday, so more work may be needed to force clearing the cache on mobile. I'm unfamiliar with editing so not sure how to do it, but read this
- How can I purge a bad image?
- The pageimage only changes when a link in an article changes. For emergencies, please add/remove links from the page, reverting if necessary. Purging will not work. For larger emergencies please file a Phabricator ticket. MelitaJay (talk) 17:30, 19 August 2022 (UTC)
Page tab problems
Is anyone else having issues with their tool tabs - when I open my page tool tab, the bolded options no longer provide drill down options when I hover over them. It would be good to know if this is an issue that has just cropped up or a known long-term problem related to script incompatibilites or some other issue. Iskandar323 (talk) 19:46, 18 August 2022 (UTC)
- I've made a hotfix for MoreMenu, which I believe is what you're referring to. phab:T315418 is in fact what caused this. For those using Vector legacy + MoreMenu, you should soon see MoreMenu behaving normally, but the native "More" menu will still require a click to expand. — MusikAnimal talk 20:27, 18 August 2022 (UTC)
- @MusikAnimal: Great! Yep. That was the one, and it seems to be working again now. Thanks. Iskandar323 (talk) 06:03, 19 August 2022 (UTC)
WP:Contents issue
I am in the process of redesigning the WP:Contents page. At the bottom of the page, where it says content listings, there is a vertical line that I can't seem to get rid of. I tried editing the page a lot to see if I can get it, but to no avail. I'm hoping to get some help regarding how I can fix this. Interstellarity (talk) 21:41, 18 August 2022 (UTC)
- it looks like this line is a border added by the intro to single template. adding "|noborder=y" (after "|padbottom=20px", for example) should resolve your issue. dying (talk) 22:11, 18 August 2022 (UTC)
- @Dying: Thank you, that resolves the issue. I would also like to get rid of the whitespace between Category:Contemporary history by country and the Content listings. What can I do to fix that? Interstellarity (talk) 22:18, 18 August 2022 (UTC)
- i think that is just the space that the template inserts after what is defined as the lead, and before what is defined as the top. right now, the top is not defined, but most of the text is in the lead, so the space appears between the lead and the bottom. the space can be shifted up by adding "| top =" somewhere (on the line above "== Vital articles ==", for example). dying (talk) 22:40, 18 August 2022 (UTC)
- @Dying I would like to know on the contents page, how to fix the page width to variable which was raised at WP:VPI so that it looks better. Interstellarity (talk) 14:05, 20 August 2022 (UTC)
- it looks like xaosflux is correct, and the width is hardcoded into the template you were using. although it may be possible to override this, i would not worry about it too much, as the redesign has been reverted, citing the earlier reversion of a similar redesign of the about page. dying (talk) 20:28, 20 August 2022 (UTC)
- @Dying I would like to know on the contents page, how to fix the page width to variable which was raised at WP:VPI so that it looks better. Interstellarity (talk) 14:05, 20 August 2022 (UTC)
- i think that is just the space that the template inserts after what is defined as the lead, and before what is defined as the top. right now, the top is not defined, but most of the text is in the lead, so the space appears between the lead and the bottom. the space can be shifted up by adding "| top =" somewhere (on the line above "== Vital articles ==", for example). dying (talk) 22:40, 18 August 2022 (UTC)
- @Dying: Thank you, that resolves the issue. I would also like to get rid of the whitespace between Category:Contemporary history by country and the Content listings. What can I do to fix that? Interstellarity (talk) 22:18, 18 August 2022 (UTC)
#Anchors in links appear to be broken on all wikis, all skins
Looks like this could be a big bug that eventually gets questions here. Creating this section to help centralize discussion. Phab ticket created. –Novem Linguae (talk) 21:59, 18 August 2022 (UTC)
- Fixed. –Novem Linguae (talk) 23:21, 18 August 2022 (UTC)
- I saw your edit on my watchlist and ironically, the section link in the edit summary didn't work. Same in the page history and Special:Contributions/Novem Linguae. It apparently happens because the section name starts with
#
. The automatic edit summary link goes to Wikipedia:Village pump (technical)#Anchors in links appear to be broken on all wikis, all skins instead of Wikipedia:Village pump (technical)##Anchors in links appear to be broken on all wikis, all skins with double##
. I don't know whether it's an old bug or related to the current issue. PrimeHunter (talk) 00:45, 19 August 2022 (UTC)- Good catch. I created a ticket. phab:T315631. –Novem Linguae (talk) 01:47, 19 August 2022 (UTC)
- I saw your edit on my watchlist and ironically, the section link in the edit summary didn't work. Same in the page history and Special:Contributions/Novem Linguae. It apparently happens because the section name starts with
Running js via url
I remember seeing that a certain string when appended to a page url can run javascript on a one-time basis. I don't recall that. Can someone please help? Thanks! —CX Zoom[he/him] (let's talk • {C•X}) 07:35, 19 August 2022 (UTC)
- You are looking for
?withJS=MediaWiki:Pagename.js
or?widthgadget=gadgetname
—TheDJ (talk • contribs) 08:42, 19 August 2022 (UTC)- That second one, of course, should be
?withgadget
. The?withJS
only works for scripts in the MediaWiki namespace. For other scripts, see a similar question I answered about how to use the DYKcheck tool without installing it: Wikipedia talk:Did you know/Archive 186#Wikipedia:Did you know/DYKcheck. The same method could be used to run other scripts. It's not exactly what you asked for, but it may do what you need. MANdARAX XAЯAbИAM 17:14, 19 August 2022 (UTC) - (edit conflict) It's
withgadget
and it only allows gadgets withsupportsUrlLoad
at MediaWiki:Gadgets-definition, e.g. https://en.wikipedia.org/wiki/Example?withgadget=UTCLiveClock.withJS
can load any js page in the Mediawiki namespace, e.g. https://en.wikipedia.org/wiki/Example?withJS=MediaWiki:Gadget-UTCLiveClock.js. There is a similarwithCSS
.withgadget
is part of MediaWiki since December 2021.withJS
andwithCSS
rely on code in MediaWiki:Common.js. There is also a version in mw:Snippets/Load JS and CSS by URL. PrimeHunter (talk) 17:16, 19 August 2022 (UTC)- Thank you very much everyone! —CX Zoom[he/him] (let's talk • {C•X}) 14:58, 20 August 2022 (UTC)
- That second one, of course, should be
dashes script malfunction
Of late, the dashes script and various mirrors have stopped performing, and the –
button that calls the script in the dropdown menu (More
tab) has been replaced by auto ed
. At the same time, the script functionality has also disappeared. However, none of the core AutoEd modules seems to have changed. What could be causing this issue? Ohc revolution of our times 09:47, 19 August 2022 (UTC)
- The importScript call at line 150 is (I know not why) no longer returning a truthy value, so various things are not being set. I created a version of the script without that condition at User:William Avery/dashes.js, and it seems to work on my sandbox. William Avery (talk) 12:40, 19 August 2022 (UTC)
- It would seem importScript is no longer synchonous since this change. William Avery (talk) 11:57, 20 August 2022 (UTC)
- I completely removed it from my common.js a couple of days ago. I was concerned because of the what is mentioned above, but also the warning on GregU's dashes script, "Code that you insert on this page could contain malicious content capable of compromising your account." I really loved the convenience of using it, but not unless someone can come up with a safe and reliable code for us. — Maile (talk) 23:18, 22 August 2022 (UTC)
- It would seem importScript is no longer synchonous since this change. William Avery (talk) 11:57, 20 August 2022 (UTC)
Table not updating
Wikipedia:List of administrators/stat table - Wikipedia Wakelamp d[@-@]b (talk) 10:27, 19 August 2022 (UTC)
- @Wakelamp: Wikipedia:List of administrators/stat table is not automatic, or bot updated. You can updated it by editing. I've templated it as out of date. — xaosflux Talk 12:45, 19 August 2022 (UTC)
Is there an update to Vector-2022 today/yesterday?
Not sure if there is an update to Vector-2022 on 18 August 2022 and/or 19 August 2022, as Xtools and Shortdesc helper are suddenly no longer functional despite both already enabled in gadgets. Both gadgets were working fine on 17 August 2022 and before. — Paper9oll (🔔 • 📝) 12:40, 19 August 2022 (UTC)
- Paper9oll, I fixed XTools Article Info gadget on bnwiki in my own way. —Yahya (talk • contribs.) 14:50, 19 August 2022 (UTC)
- @Yahya Haven't tried your script, but this isn't really a permanent solution. But any idea, if it's due to an update to Vector-2022 that rolled out probably in past 2 days, that causes both tools to suddenly stopped functioning in Vector-2022? Not sure, if the update removed or renamed some css classes that causes both tools to no longer function/display. — Paper9oll (🔔 • 📝) 16:35, 19 August 2022 (UTC)
- The XTools gadget has now been fixed, both here on enwiki as well as the global script. Ironically, I was asked how the gadget worked so that the team would not break it, but it looks like that inquiry was for a different project (DiscussionTools), and unrelated to the change in Vector 2022. — MusikAnimal talk 19:41, 19 August 2022 (UTC)
- @MusikAnimal: Please could you give some detail of how you fixed your gadget – there are other scripts that currently hunt for the contentSub id. @Galobtter: Shortdesc-helper attaches to #contentSub and I have a user script that does the same thing. — GhostInTheMachine talk to me 17:20, 20 August 2022 (UTC)
- @GhostInTheMachine I did the same as Yahya did on bnwiki and am now inserting the content before
#bodyContent
, but only for Vector-2022. Hope this helps. — MusikAnimal talk 22:08, 22 August 2022 (UTC)
- @GhostInTheMachine I did the same as Yahya did on bnwiki and am now inserting the content before
- @MusikAnimal: Please could you give some detail of how you fixed your gadget – there are other scripts that currently hunt for the contentSub id. @Galobtter: Shortdesc-helper attaches to #contentSub and I have a user script that does the same thing. — GhostInTheMachine talk to me 17:20, 20 August 2022 (UTC)
- The XTools gadget has now been fixed, both here on enwiki as well as the global script. Ironically, I was asked how the gadget worked so that the team would not break it, but it looks like that inquiry was for a different project (DiscussionTools), and unrelated to the change in Vector 2022. — MusikAnimal talk 19:41, 19 August 2022 (UTC)
- @Yahya Haven't tried your script, but this isn't really a permanent solution. But any idea, if it's due to an update to Vector-2022 that rolled out probably in past 2 days, that causes both tools to suddenly stopped functioning in Vector-2022? Not sure, if the update removed or renamed some css classes that causes both tools to no longer function/display. — Paper9oll (🔔 • 📝) 16:35, 19 August 2022 (UTC)
- As well as Shortdesc Helper, d:User:Yair rand/WikidataInfo.js has stopped working for me on Vector 2022 around this time. Ham II (talk) 08:39, 21 August 2022 (UTC)
Multiple Table options when editing slowing down pages
Is anyone else getting the Tables options appearing just above the edit box multiple times when editing? I've got rows and rows of this, but only in the last 24 hours or so. It's really slowing down the page loading, practically making editing impossible, with the page crashing on some browsers. Iveagh Gardens (talk) 14:38, 19 August 2022 (UTC)
- @Iveagh Gardens: I suddenly had that problem today, and tracked it down to my common.js being imported into itself. Fixed by this edit: https://en.wikipedia.org/w/index.php?title=User:William_Avery/common.js&diff=prev&oldid=1105258013 I have no idea 1/ how that happened, 2/ why it didn't cause a problem before, or 3/ why the behaviour changed. You too seem to have that problem in https://en.wikipedia.org/wiki/User:Iveagh_Gardens/common.js William Avery (talk) 15:06, 19 August 2022 (UTC)
- @Iveagh Gardens You need to undo this edit: Special:Diff/1030376399. --Ahecht (TALK
PAGE) 18:51, 19 August 2022 (UTC)- @William Avery: and @Ahecht:, thank you both for that, it's been resolved. An odd sleeper bug! –Iveagh Gardens (talk) 07:25, 20 August 2022 (UTC)
- It would seem importScript no longer checks to see if a script has already been loaded, since this change William Avery (talk) 11:58, 20 August 2022 (UTC)
History split
Could an admin move/remove the oldest two revisions of https://en.wikipedia.org/w/index.php?title=Honor_walk&action=history? This was someone's sandbox, and two revisions for an unrelated article seem to have been moved along with the history for the current page. Thanks, WhatamIdoing (talk) 18:29, 19 August 2022 (UTC)
- Doing... — xaosflux Talk 18:38, 19 August 2022 (UTC)
- Done split to User:Drewmutt/sandbox/Baby cage. — xaosflux Talk 18:45, 19 August 2022 (UTC)
Blacklisting Ahmed Alhemrayi etc.
There have multiple attempts by sockpuppets to create articles on Ahmed Al-Hemrayi Ahmed Alhemrayi, and other forms of these names. There are also attempts to evade the record by the insertion of unnecessary disambiguators after the name. I am requesting that they be added to the Title Blacklist, which says that I may also ask for advice here, perhaps about how to make the request. Several forms of the name have already been salted in article space and draft space, so the spammers are tweaking the names. Is it necessary to discuss this anywhere else, or will the previous record of the deletion and salting be sufficient? Robert McClenon (talk) 00:44, 20 August 2022 (UTC)
- Some of the forms are only salted in draft space. See also Ahmed Alhemyari YouTuber and [[Ahmed Alhemyari ( You Tubers). Robert McClenon (talk) 00:52, 20 August 2022 (UTC)
- Just some advice on making the request. It took me ages to discover User talk:Mr intartok. The more examples showing the scale, variations and timescales, the better. -- zzuuzz (talk) 01:29, 20 August 2022 (UTC)
- Wouldn't it be better to leave an obvious title in Draftspace untouched to serve as a honeypot so that he isn't coming up with increasingly ludicrous names like Ahmed Alhemrayi' Hyper Deluxe YouTube Provocateur Hates Mirza Ahmad And Wants Wikipedia To Take Control Of Google To Get Those Fucking Search Results That I Look Up But Refuse To Admit It Changed? —Jéské Couriano v^_^v a little blue Bori 01:50, 20 August 2022 (UTC)
- Yes, I hate to see draftspace be salted because it non-salt allows recreation within draftspace at a location that is probably in someone's watchlist (if Twinkle is used for CSD nom). If someone is determined enough, salting would force them to create something like "Biography of Foo Bar" or "YouTube career of Foo Bar" instead of just "Foo Bar" which makes recreation detection difficult. —CX Zoom[he/him] (let's talk • {C•X}) 05:09, 20 August 2022 (UTC)
- Good points and I’ve done just that so I can tell when it has been recreated. Doug Weller talk 18:05, 20 August 2022 (UTC)
- Yes, I hate to see draftspace be salted because it non-salt allows recreation within draftspace at a location that is probably in someone's watchlist (if Twinkle is used for CSD nom). If someone is determined enough, salting would force them to create something like "Biography of Foo Bar" or "YouTube career of Foo Bar" instead of just "Foo Bar" which makes recreation detection difficult. —CX Zoom[he/him] (let's talk • {C•X}) 05:09, 20 August 2022 (UTC)
Graph module for Vega 3+
Hi, recently development of Graph Extension is more active. There's a slim shade of hope that Vega framework will be updated to a more recent version in the near future. Most of the graphs in Wikipedia articles are generated by template and associated Scribunto module – it's based on Vega 2 syntax. It's incompatible with Vega 3+.
Is anyone currently working on a new version (or complete rewriting) of this module Module:Graph prepared for Vega 3+?
Some part of code are workarounds of bugs in current version extension. Many bugs mentioned by editors can't be solved by module or template. For reference please see Template_talk:Graph:Chart and Module_talk:Graph
Current module is handling the most of the processing of user provided data. It seems that Vega 3+ can do the bulk of this work, presumably with better results and faster. It also can handle and transform external data (eg. Wiki data or tables) very well.
Maybe it would be a good idea to switch to Vega-Lite syntax. It's more human friendly and easier to understand. Syntax is simpler and requires less input for typical charts.
Any ideas? Volunteers? Unfounded critique? Pietrasagh (talk) 11:48, 21 August 2022 (UTC)
- @Pietrasagh: See phab:T223026 in mw:Phabricator. --AKlapper (WMF) (talk) 23:41, 21 August 2022 (UTC)
Vector 2022 now leaving a lot of blank space on the left and right of my screen.
A waste of space and I'm sure not what was intended. Doug Weller talk 16:19, 21 August 2022 (UTC)
- The blank space is intended, see mw:Reading/Web/Desktop Improvements/Features/Limiting content width § Goals and motivation and mw:Reading/Web/Desktop Improvements/Frequently asked questions § Why is the width of the content limited? Why is there so much white space?. Rummskartoffel 16:55, 21 August 2022 (UTC)
- @Rummskartoffel and this change was done in the last day? It doesn’t show on my iPad just my Wondows pc. Doug Weller talk 19:03, 21 August 2022 (UTC)
- None that I know about; there's (supposed to have) been a lot of blank space in Vector-2022 on larger screens for a while now. A difference between an iPad and a (presumably larger) PC screen would be expected. Rummskartoffel 19:52, 21 August 2022 (UTC)
- @Doug Weller, if you don't want to keep this extra whitespace, then I found a gadget today that I've enabled that reduces the whitespace that's added. It's called wide-vector-2022 and is near the bottom of the gadgets list. Dreamy Jazz talk to me | my contributions 22:50, 21 August 2022 (UTC)
- The gadget is only listed at Special:Preferences#mw-prefsection-gadgets if your skin is Vector 2022. Here is a comparison of Wikipedia in Vector 2022 without the gadget (assuming you haven't enabled the gadget) and with the gadget. PrimeHunter (talk) 23:56, 21 August 2022 (UTC)
- @Doug Weller, if you don't want to keep this extra whitespace, then I found a gadget today that I've enabled that reduces the whitespace that's added. It's called wide-vector-2022 and is near the bottom of the gadgets list. Dreamy Jazz talk to me | my contributions 22:50, 21 August 2022 (UTC)
- None that I know about; there's (supposed to have) been a lot of blank space in Vector-2022 on larger screens for a while now. A difference between an iPad and a (presumably larger) PC screen would be expected. Rummskartoffel 19:52, 21 August 2022 (UTC)
- @Rummskartoffel and this change was done in the last day? It doesn’t show on my iPad just my Wondows pc. Doug Weller talk 19:03, 21 August 2022 (UTC)
Section edit deletes rest of page
This is an issue that occasionally appears. With this section edit I accidentally replaced the rest of the page with just the edited section. This happens if when an edit section preview is saved in the browser cache. This happend when I started the edit one day and previewed it, closed the browser without saving the edit, then finished the edit the next day in a new browser session. Everything looks normal as you preview the section, but when you save it the rest of the page is gone. While the simple solution is not to use cached edits, it's not a behaviour that should be expected. — Jts1882 | talk 09:34, 22 August 2022 (UTC)
- When I start a section edit at Talk:Fish#Why are conodonts excluded?, the url is . After a preview it becomes https://en.wikipedia.org/w/index.php?title=Talk:Fish&action=submit, the same as if I edited the whole page. Is it the same url's for you? The information that you edited a section is no longer in the url. When you closed the browser, this information was apparently lost. After reopening the browser, it remembered the last url and what you had in the text area but did not communicate with MediaWiki that it was a section edit. MediaWiki apparently assumed it was a whole page edit. I don't know whether this is a known issue or has a fix other than not doing that. What is the browser? PrimeHunter (talk) 14:32, 22 August 2022 (UTC)
Sogdian language rendering support
In the Sogdian language article my Firefox browser displays gibberish instead of native characters and there's no in-article link to fix it. Where can I download relevant rendering support for Firefox? Brandmeistertalk 10:43, 22 August 2022 (UTC)
- @Brandmeister: Sogdian alphabet § Font has links to Noto Sans Old Sogdian and Noto Sans Sogdian. Rummskartoffel 11:01, 22 August 2022 (UTC)
- Thanks, works except the last line. Sogdian alphabet states it uses three scripts, but the infobox seemingly has four scripts, that fourth script doesn't render properly for me, despite installing both fonts. Brandmeistertalk 11:23, 22 August 2022 (UTC)
- @Brandmeister: Right, I missed that one. You'll need Noto Sans Manichaean as well. Rummskartoffel 11:31, 22 August 2022 (UTC)
- Thanks, works except the last line. Sogdian alphabet states it uses three scripts, but the infobox seemingly has four scripts, that fourth script doesn't render properly for me, despite installing both fonts. Brandmeistertalk 11:23, 22 August 2022 (UTC)
Automatically hide TOC in Vector 2022
Hello,
I would like to automatically hide the table of contents on every page load.
I am using the new Vector 2022 skin.
I tried to achieve this by manually triggering the "click" event of the "hide" button when the page loads. I added to following lines to my JS page:
$(document).ready(function() {
$(".vector-toc-collapse-button").click();
});
But, unfortunately nothing happens, and the TOC keeps appearing on the sidebar when the page loads. The code DOES work when I run it from my browser's console, but does nothing when added to my common.js page, even after clearing my browser's cache.
Does anyone have an idea how can I hide the TOC automatically on every page?
Thanks, Guycn2 (talk) 15:48, 22 August 2022 (UTC)
- It doesn't work because the javascript executes before the TOC has loaded. Something like this may work, though still very hacky (it checks for the button every 500 ms until it's found, then clicks it):– SD0001 (talk) 16:52, 22 August 2022 (UTC)
$(document).ready(function() { var interval = setInterval(function() { if ( $(".vector-toc-collapse-button").length ) { $(".vector-toc-collapse-button").click(); clearInterval(interval); } }, 500); });
Edit Notices on Mobile
Notice, WP:ENOM has launched wave 3 of the deployment, visibility to all autoconfirmed users. If there is a major breaking change discovered, this may be reverted at MediaWiki:Gadgets-definition. For other feedback, Wikipedia talk:EditNoticesOnMobile is available. — xaosflux Talk 18:11, 22 August 2022 (UTC)
Has WikiNav stopped working? It appears it tries to fetch data from wikinav.wmcloud.org, which is not returning the required CORS headers. Is there a way to circumvent this? I tried accessing wikinav.wmcloud.org directly but it's 502. Nardog (talk) 19:12, 22 August 2022 (UTC)
- Broken for me too. Certes (talk) 19:33, 22 August 2022 (UTC)
- An issue was opened in the WikiNav project on GitHub two days ago about this. The people listed as administrators here are the people with server access who should be able to log in and restart/fix it. Multiple people have also brought it up in the #wikimedia-research IRC channel, hopefully one of those mechanisms will get a response. Legoktm (talk) 22:50, 22 August 2022 (UTC)
Tech News: 2022-34
00:09, 23 August 2022 (UTC)