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.
Dark mode Gadget and Vector 2022 skin
Hello, I'm using Vector 2022 Skin and Dark mode Gadget. In the recent Vector 2022 skin, the title has moved up the tab. However, there is a problem here. There is no problem in light mode, but in dark mode, another line appears above the title (shown in red squares above). I don't know if this is a bug in a Vector or a bug in a Dark mode Gadget. Bluehill (talk) 11:17, 7 July 2022 (UTC)
- It is because .mw-body has a 1px transparent border-top property which is causing the line to appear on the dark mode from what I understand. It is transparent with a white background, just not with dark mode, you could always disable this with custom css or change the color to the background color. Terasail[✉️] 11:25, 7 July 2022 (UTC)
- Pinging @SGrabarczuk (WMF), as I think he's familiar with both the gadget and Vector 2022. Whatamidoing (WMF) (talk) 00:20, 9 July 2022 (UTC)
- Thanks, @Whatamidoing (WMF). Hi @Bluehill, what dark mode gadget do you use? This isn't this one, isn't it? Do you still experience the bug? SGrabarczuk (WMF) (talk) 00:29, 12 July 2022 (UTC)
- @SGrabarczuk (WMF): see example page. — xaosflux Talk 00:47, 12 July 2022 (UTC)
- Thanks @Xaosflux. This is odd. I don't see the line when I'm logged in. Instead, the content is in a box, with all four borders. But in the private/incognito mode, I do see the line instead of the box. What's going on? I'm not sure what gadget/user script I'm using may change my experience! :D SGrabarczuk (WMF) (talk) 01:32, 12 July 2022 (UTC)
- Not sure, I don't think this is rally a software "bug" - there is a box there, maybe it isn't needed for something else - maybe it is, but the local CSS is styling it. Since darkmode here is just a local css, if someone wants to identify and change the element in it they can just make an edit request over at Wikipedia talk:Dark mode (gadget) to change the styling I suppose. — xaosflux Talk 09:51, 12 July 2022 (UTC)
- I agree, this isn't necessarily a software "bug". Our team should be aware of this, though, because we're working on the grid system, and there are just things that may make this change again. SGrabarczuk (WMF) (talk) 12:16, 12 July 2022 (UTC)
- ^^^ If you are interested in CSS or what Wikipedia pages look like, please do keep an eye out for messages talking about grids. mw:Vector 2022#Deployment plan and timeline says that this is coming up soon, and it sounds like a big change. Whatamidoing (WMF) (talk) 17:55, 13 July 2022 (UTC)
- I agree, this isn't necessarily a software "bug". Our team should be aware of this, though, because we're working on the grid system, and there are just things that may make this change again. SGrabarczuk (WMF) (talk) 12:16, 12 July 2022 (UTC)
- Not sure, I don't think this is rally a software "bug" - there is a box there, maybe it isn't needed for something else - maybe it is, but the local CSS is styling it. Since darkmode here is just a local css, if someone wants to identify and change the element in it they can just make an edit request over at Wikipedia talk:Dark mode (gadget) to change the styling I suppose. — xaosflux Talk 09:51, 12 July 2022 (UTC)
- Thanks @Xaosflux. This is odd. I don't see the line when I'm logged in. Instead, the content is in a box, with all four borders. But in the private/incognito mode, I do see the line instead of the box. What's going on? I'm not sure what gadget/user script I'm using may change my experience! :D SGrabarczuk (WMF) (talk) 01:32, 12 July 2022 (UTC)
- @SGrabarczuk (WMF): see example page. — xaosflux Talk 00:47, 12 July 2022 (UTC)
Restoring access to my user account.
Hello -- I am User:CharlesGillingham, and I was locked out of my account by the password system. I think it was sending the "password reset" message to an old email, or something along those lines. The help page advised that, if I didn't receive the "password reset" message I should open a new account, so I did. However, I have lost the editing privileges I enjoyed as a long-time editor. (2006 or so, hundreds of thousands of edits.) Can anyone advice me on how to reset password of my old account? ---- CharlesTGillingham (talk) 00:45, 12 July 2022 (UTC)
- @CharlesTGillingham: User:CharlesGillingham has not specified an email adress in the account. Special:CentralAuth/CharlesGillingham shows 21,415 edits here and a few to other projects but no advanced user rights. I don't know whether that is enough for somebody with the required access to verify your identity and set an email address for the account so you can get a password reset. It helps a lot that the user page states your identity (added by the user) so it can potentially be verified that the request is really from the account owner. Passwords never expire so you can keep trying. PrimeHunter (talk) 02:59, 12 July 2022 (UTC)
- The only privilege I need is "auto confirmed", so that's not really a concern. (I remember being notified, around 2011 or so, that I had passed 100K edits ... but of course that's not an issue worth worrying about.)
- The last password was Safari-generated, so there's no hope of my guessing the password -- literally intractable. It would still be nice to keep going in the same old account. Do you know how I might go about finding a person who might be able to set the email? ---- CharlesTGillingham (talk) 03:43, 12 July 2022 (UTC)
- Without an email or committed identity, the chances of you getting your account back are slim to none (see Help:Logging in#What if I forget my password?). Nardog (talk) 04:10, 12 July 2022 (UTC)
- And, as the fourth bullet point there says, the process is to email the Trust and Safety team at cawikimedia.org * Pppery * it has begun... 04:12, 12 July 2022 (UTC)
- I lost a lot of my passwords when troubleshooting Firefox recently. (I clicked a button that said "You won’t lose essential information like bookmarks and passwords." Well, it was half right.) However, I still have both my previous laptop and a full backup, and I was able to look up the passwords there. In Safari, there's also the possibility of passwords being stored in Apple's iCloud or Keychain. I hope that you are able to find your passwords. Whatamidoing (WMF) (talk) 18:06, 13 July 2022 (UTC)
Considerations for edit notices on mobile
On mobile platforms like the Android app and likely soon https://en.m.wikipedia.org, edit notices are delivered as a popup that needs to be dismissed (and can be revisited with a button), as opposed to a passive box above the editing window. I've implemented the same in the editor script I'm using right now which causes edit notices to appear as a popup on desktop platforms too. On mobile, there often just isn't enough screen real estate to display warnings in a passive box.
This is good for warnings like Template:Editnotices/Page/Talk:Goofy, it makes them harder to miss. But not all notices are used like this, Template:Editnotices/Namespace/File for example contains more generic information and pops up on every file description page the user hasn't edited before. Whether that's really needed is an open question, personally I lean towards no: I'd rather reserve edit notices for actual warnings specific to a particular page or subject.
- To stop a particular notice from showing on mobile platforms it can be wrapped in an element with the
nomobile
class. We should consider this for notices that are primarily informative and not really warnings. - A wall of text is unlikely to impress a mobile user, so consider wrapping everything outside the core message in an element with the
nomobile
class. - Many edit notices use markup to draw attention: background colors, images of exclamation marks, red and/or bold text, borders, etc. In a passive box these make sense due to banner blindness, but they are largely inappropriate when already shoving a popup in the user's face. They can also cause issues at limited screen width. Mobile platforms try to strip at least some (if not all) of this stuff, but please keep this in mind when designing a new notice.
- Shouldn't edit notices be popups on desktop too? It'll make them harder to miss, and do you really enjoy having that box sitting permanently above the edit window?
- How should we handle more generic information for mobile platforms that is best delivered passively? One solution I'm thinking of is the introduction of a new class for editnotices that, when detected, suppresses the popup but still enables the button to revisit the notice so the content is accessible. Maybe call it "nopopupnotice" or something. (edit: Detection of elements with the "nopopupnotice" class will be available once EditNoticesOnMobile gets synced from my userspace. The actual classname may be changed in the future.)
But I'd love to hear some more thoughts on this. — Alexis Jazz (talk or ping me) 18:18, 12 July 2022 (UTC)
- Wow... this topic just made me realize how blind to edit notices I really am. Also, since I'm now thinking about it, we should probably revisit the idea of edit notices such as the one on Talk:Goofy entirely. The new reply tool skips the edit notice entirely, so if someone is using that they will never see the warning about Goofy not being a cow. ~ ONUnicorn(Talk|Contribs)problem solving 18:30, 12 July 2022 (UTC)
- ONUnicorn, solid argument for saying "Farewell, DiscussionTools!" right there.
Edit: Whatamidoing (WMF) is right. They weren't shown on mobile until recently due to Template:Editnotice load (Diff 791185221) but otherwise it's correct. — Alexis Jazz (talk or ping me) 18:41, 12 July 2022 (UTC)- DiscussionTools' ==New Topic== tool displays edit notices. The [reply] button doesn't. I'm not sure that it makes much difference for replying to someone else's comments. Talk:Goofy has only two edits using the reply tool (and none with the ==New Topic== tool), and neither of them mention cows. Whatamidoing (WMF) (talk) 18:18, 13 July 2022 (UTC)
- ONUnicorn, solid argument for saying "Farewell, DiscussionTools!" right there.
- Whilst that's all great (and is a very good idea), it'd be even better if the developers could get around to iOS users and Mobile web users being able to see edit notices at all... Black Kite (talk) 18:44, 12 July 2022 (UTC)
- Alexis Jazz says that mobile web users will soon be receiving edit notices as a popup... that's the first sentence. ~ ONUnicorn(Talk|Contribs)problem solving 19:04, 12 July 2022 (UTC)
- It can now be tested. — Alexis Jazz (talk or ping me) 20:14, 12 July 2022 (UTC)
- Alexis Jazz says that mobile web users will soon be receiving edit notices as a popup... that's the first sentence. ~ ONUnicorn(Talk|Contribs)problem solving 19:04, 12 July 2022 (UTC)
Some some of pdf widget to select text in references and automatically create cites with page numbers (and other information)
Hope this is the right place for this post. Tell me if I should put it somewhere else. I've been thinking for a while about references in wikipedia. I think it might be nice if a reference could identify precisely which section of text supports a claim, and it might be nice if there were a GUI to do this.
This sort of GUI would:
- Make it easier for people to cite, creating fewer errors, and speeding up the editing process.
- Help ensure that all references had page numbers.
- Make it easier for people to check citations.
- Provide a more useful data set for machine learning tasks (can you see my real motivation?). Some machine learning tasks might be valuable for wikipedia, e.g. checking citations, suggesting to the reader which part of a page or document supports the claim, in a far flung universe automatically generating citaitons.
- I imagine such data could be use of to wikipedia's internal team.
There is some prior work for this sort of stuff in the open source hypothes.is library associated with Jeff Atwood of stackoverflow fame. And meta have been messing around with citations for fact checking recently and open sourced their work. I'm not sure we should particular try to help meta, but we could make it easier for the community as a whole to build on their work. Talpedia (talk) 23:26, 12 July 2022 (UTC)
- There are two aspects here, 1 creating an citation from pdf, 2 verifying pdf citation. For 1 there are a bunch of programs that help users to cite an pdf. There is no need for an wikipedia specific thing, because it is enough just to get an citation in an academic format. The requirement of an page number and section does filter these tools quite a bit. For 2, it is worth mentioning that IAarchiveBot started adding urls to pdfs to references with ISBNs. As for the problem itself, Wikipedia does require editors to reword things so they are not equal to the citation, so it would probably have to search for key words instead.
- As for why this is not a thing in the three editors (VisualEditor, 2017 Wikitext editor and 2010 wikitext editor) much of the information you want is in the pdf itself. Getting the information needed is not the issue, but as I understand it, the developers are hesitant to temporarily store an pdf just to get information out of it. As for the page and section, you kind of need to get that from an PDF viewer, as then you can ask for the page the editor is currently viewing. The three editors can however tick most of the boxes if you give it an identifier, like an ISBN, if it has one.--Snævar (talk) 06:56, 13 July 2022 (UTC)
- Thanks for the reply. I agree that all of this could be handled outside of wikipedia proper and through and external tool which provides citations. In fact, I imagine if this were to get into wikipedia proper it might have to be proven in such an external tool. I can see the "linuxy" argument for separate compatible tools. It's interesting to know that there is a tool that can give me page numbers from pdfs if I highlight a region, I'd like to give one of those a whirl if anyone new about them. The lazy version of me would love something to find the ISBN/doi from a pdf I'm viewing and include the page number.
- I guess the main addition within wikipedia associated with is the idea of selecting which span of text within a document contains the information, as well maybe as providing urls that select the page and piece of text. I don't quite know how you would deal with multiple references to different spans on different pages.
- I could also imagine people reviewing references selecting the bit of text that matches - assuming they are actually motivated to review what has been added. One thing I do sometimes when reviewing other people's claims is add page numbers.Talpedia (talk) 10:45, 13 July 2022 (UTC)
- Anyway, this is phab:T136722. This will be added to mediawiki sometime, but it seems blocked on the backend software, Zotero, or adding another backend software to get the necessary information. Snævar (talk) 12:17, 13 July 2022 (UTC)
Planet: small font on block quotes
When viewed from an iPhone, without being logged in to Wikipedia, two of the blockquotes (but not the others) in Planet show in a font much too small to read:
- the definition in this section, and
- the sub-stellar mass body quote in this section.
How can the font be fixed in the article so that all browsers will see a normal font? SandyGeorgia (Talk) 01:57, 13 July 2022 (UTC)
- @SandyGeorgia, when you say it is in font too small to read, which skin are you using? The default mobile skin ("Minerva") as is found at the mobile site? Or desktop ("Vector"), as are the links you provided? Just checking. Izno (talk) 04:51, 13 July 2022 (UTC)
- Both of those quotes look larger than the surrounding text (and, weirdly, are rendered in serif font instead of the sans serif used in the body) on my iPhone using Safari, not logged in. – Jonesey95 (talk) 05:54, 13 July 2022 (UTC)
- Izno does skin apply when not logged in? (How do I find which skin I'm using?) SandyGeorgia (Talk) 07:16, 13 July 2022 (UTC)
- When reading it from iPhone, I click on the desktop view ... is that what you mean? SandyGeorgia (Talk) 07:18, 13 July 2022 (UTC)
- You are likely running into automatic font size inflation that phones provide. With this, they increase the size of elements like headers and paragraphs etc compared to items the device thinks are less important like block quotes and images. It's expected behaviour on a phone when using the desktop version of a website (which was not designed to be used on mobile) and is an attempt to make desktop websites more readable on phones. So actually the block quote is at the 'proper' text size, its the paragraphs around it that are 'too big'. Our normal paragraph font size is around 14px, but on mobile with text inflation, that becomes a font-size around 24px. —TheDJ (talk • contribs) 08:03, 13 July 2022 (UTC)
- Thx, but ... Then why is it not happening on all blockquotes? Those two quotes are the only ones affected, and the reset of the text looks fine, as far as I can tell. I don't think the text around it is changed ?? Hard to tell ... SandyGeorgia (Talk) 16:22, 13 July 2022 (UTC)
- @SandyGeorgia, yes, that's exactly why I asked the question. As TheDJ explains, skins which are not 'optimized' for mobile (like Vector today) are going to run into browsers attempting to display content sensibly. I have seen similar behavior depending on other content as you do with the different quotes.
- I would highly advise against attempting to 'correct' this in the source page. The fundamental issue is Vector here, and not something worth changing because it may negatively impact other display, or as you seem to have discovered below, an awful lot of work that could compromise our guidelines on page layout. (I think some of your results are interesting, mind you.)
- At some point in the near-ish future, the new version of Vector may do a better job supporting mobile, so the problem will become more-or-less irrelevant except for a tiny quantity of logged in editors viewing the website (which accordingly should not be optimized for). Izno (talk) 17:35, 13 July 2022 (UTC)
- Izno OK, but I'm not sure if I've left this at the best place ... unclear what you are recommending, since I don't fully speak this language. Because this is a Featured article, it shouldn't compromise anything about images or quotes, and we should get it right (it could run WP:TFA once it passes FAR). Is User:SandyGeorgia/sandbox#2006 IAU definition of planet a good solution, compliant with everything ? SandyGeorgia (Talk) 19:36, 13 July 2022 (UTC)
- I'm suggesting that trying to work around this issue on mobile (iPhone) using the desktop website (specifically the Vector skin) is doomed to failure right now and which should not at all be cared about at TFA or any other process. Make it look decent on the mobile website (en.m.wikipedia.org) while using mobile and on the desktop website (en.wikipedia.org) when using a desktop. That's it. Izno (talk) 20:15, 13 July 2022 (UTC)
- Got it-- we'll work that out at Wikipedia:Featured article review/Planet/archive1 then. Thanks again! SandyGeorgia (Talk) 20:35, 13 July 2022 (UTC)
- I'm suggesting that trying to work around this issue on mobile (iPhone) using the desktop website (specifically the Vector skin) is doomed to failure right now and which should not at all be cared about at TFA or any other process. Make it look decent on the mobile website (en.m.wikipedia.org) while using mobile and on the desktop website (en.wikipedia.org) when using a desktop. That's it. Izno (talk) 20:15, 13 July 2022 (UTC)
- Izno OK, but I'm not sure if I've left this at the best place ... unclear what you are recommending, since I don't fully speak this language. Because this is a Featured article, it shouldn't compromise anything about images or quotes, and we should get it right (it could run WP:TFA once it passes FAR). Is User:SandyGeorgia/sandbox#2006 IAU definition of planet a good solution, compliant with everything ? SandyGeorgia (Talk) 19:36, 13 July 2022 (UTC)
- You are likely running into automatic font size inflation that phones provide. With this, they increase the size of elements like headers and paragraphs etc compared to items the device thinks are less important like block quotes and images. It's expected behaviour on a phone when using the desktop version of a website (which was not designed to be used on mobile) and is an attempt to make desktop websites more readable on phones. So actually the block quote is at the 'proper' text size, its the paragraphs around it that are 'too big'. Our normal paragraph font size is around 14px, but on mobile with text inflation, that becomes a font-size around 24px. —TheDJ (talk • contribs) 08:03, 13 July 2022 (UTC)
- No, you cannot select your skin while logged out besides using one of the two different websites (
en.m.
versusen.
). Which you are doing when you click that link. :) Izno (talk) 17:37, 13 July 2022 (UTC)
- When reading it from iPhone, I click on the desktop view ... is that what you mean? SandyGeorgia (Talk) 07:18, 13 July 2022 (UTC)
I fiddled again with the blockquote, and re-checked from my iPhone, not logged it. The first quote in this section is tiny; the next blockquote in the same section is fine. This is from the desktop view on iPhone. When I click on "mobile view", it's fine. I am posting this from my iPad, which shows no problem. SandyGeorgia (Talk) 16:44, 13 July 2022 (UTC)
- Ah, ha ... a clue ... doing this fixed the firt small blockquote (planet definition), but not the second one (sub-stellar mass). SandyGeorgia (Talk) 16:51, 13 July 2022 (UTC)
- What I did at User:SandyGeorgia/sandbox#2006 IAU definition of planet seems to work. SandyGeorgia (Talk) 19:12, 13 July 2022 (UTC)
- And, doing this solved the "sub-stellar mass" blockquote problem. So, it is related to not text, but image sizes around the quotes ?? So now, how do I get the first image up to a larger size if upright= is causing a problem? Have not tested switching the second to upright yet ... SandyGeorgia (Talk) 17:01, 13 July 2022 (UTC)
- And this; I will have to move to sandbox if more testing is needed. All for now, SandyGeorgia (Talk) 17:12, 13 July 2022 (UTC)
Special:ExpandTemplates can't expand refs
This special page can't expand templates in references. Thingofme (talk) 02:11, 13 July 2022 (UTC)
- Correct, nested expansion is a little weird. You can use {{#tag:ref|{{cite web|etc}}}} —TheDJ (talk • contribs) 07:55, 13 July 2022 (UTC)
- Actually refs are having a lot of problem nowadays as we can't use
<ref><ref></ref></ref>
(nested refs) as such we can expand {{refn}} but after expansion will get problem. Thingofme (talk) 09:11, 13 July 2022 (UTC)- This is one of the oldest issues regarding references. Where do you see "a lot of problems nowadays"? 172.254.222.178 (talk) 11:33, 13 July 2022 (UTC)
- Sorry this is one of the oldest (not nowadays) and I'm wrong about that. Does someone attempting to fix it? Thingofme (talk) 12:56, 13 July 2022 (UTC)
- I stopped following the various tickets on this years ago, so I don't know. IIRC, this was a pretty basic problem, involving the way the parser handled recursion. 50.75.226.250 (talk) 15:09, 13 July 2022 (UTC)
- Sorry this is one of the oldest (not nowadays) and I'm wrong about that. Does someone attempting to fix it? Thingofme (talk) 12:56, 13 July 2022 (UTC)
- This is one of the oldest issues regarding references. Where do you see "a lot of problems nowadays"? 172.254.222.178 (talk) 11:33, 13 July 2022 (UTC)
- Actually refs are having a lot of problem nowadays as we can't use
[Pointer] Defining a process for the discussion of making Vector 2022 the new default
Hey, if you don't watch the proposals section you may ignore a message you perhaps would prefer not to ignore, so this is like a redirect within the VP to increase the visibility.
In a nutshell, in one to two weeks, we would like to begin the conversation to update the default design of Wikipedia to the Vector 2022. We are interested in deciding on the process we want for the conversation before discussing the change itself. This is because we want to have a good decision-making process that allows for a way to identify the needs of the community from the new skin.
We'll be grateful for feedback on VPR. SGrabarczuk (WMF) (talk) 12:31, 13 July 2022 (UTC)
Was parsoid updated recently?
I know this is terribly vague, for which I apologize, but has anything changed in Parsoid in the past 24-48 hours? I'm working a heisenbug in a script I wrote which parses sock templates on user pages, calling $.get('/api/rest_v1/page/html/' + pageTitle);
to parse out the template data.
Starting yesterday, this started to fail on seemingly random user pages. I've seen pairs of user pages with byte-for-byte identical content where one parsed correctly and the other not. And now it's failing on more and more of them. I even saw one of my test cases transition from "this one works" to "this one fails" in the middle of a debugging session. A plausible explanation would be that parsoid started returning a different parse tree sometime yesterday and what I'm seeing is the user page parse trees slowly transition as some HTTP cache times out.
What's really confusing is that this didn't happen on Thursday. -- RoySmith (talk) 19:51, 13 July 2022 (UTC)
- @RoySmith, I would be willing to bet you're doing something similar to the issue in User talk:Jackmcbarn/editProtectedHelper#Gadget having issues with recent edits. Izno (talk) 20:12, 13 July 2022 (UTC)
Interesting. I'm still trying to get my head around that, but it certainly does smell similar, given that I've got:
const data = JSON.parse($(this).attr('data-mw')); return data["parts"][0]["template"]["target"]["wt"].match(/[sS]ock/);
-- RoySmith (talk) 20:23, 13 July 2022 (UTC)
- I downloaded your repo from github and took a look.
- So, the node you were trying to find has
typeof="mw:Extension/templatestyles mw:Transclusion"
. This change happened after @Izno updated the mbox template. - The fix is actually pretty simple in your case. Change
$html.find('[typeof="mw:Transclusion"]')
to$html.find('[typeof~="mw:Transclusion"]')
. Note that ~ addition there. The typeof attribute can embed multiple applicable types for the node. We should perhaps clarify our docs. - Let me know if that doesn't fix it. SSastry (WMF) (talk) 23:08, 13 July 2022 (UTC)
- I updated the docs and added a new section to clarify this. SSastry (WMF) (talk) 23:27, 13 July 2022 (UTC)
Unbirthday wish for a template
{{FAQ}} does not have the more common v • t • e buttons in the corner. Instead, it has a big "Edit" button. Could someone make it have (at least) a "View" button as well? I don't always want to edit the page. WhatamIdoing (talk) 03:21, 14 July 2022 (UTC)
- I have added a "view" link.[1] The template is used on talk pages so I haven't added "talk". PrimeHunter (talk) 04:18, 14 July 2022 (UTC)
- Could you have used
{{view|template=pagename|edit}}
? --Redrose64 🌹 (talk) 22:43, 14 July 2022 (UTC)- The edit link preloads Template:FAQ/Preload if the FAQ page doesn't exist. I don't know any navbar template which supports a preload. PrimeHunter (talk) 00:45, 15 July 2022 (UTC)
- Could you have used
CS1 maint.
Hi all, I've just fixed (I hope) some |url-status=bot: unknown
params at Royal Ulster Rifles, for example [1]. This is the first time I've come across this message. I wonder if someone could explain for a non-techie, please: Why does this happen? ie What is it that the bot can't recognise about what appears to be a standard 404 error? And why does this ref[2] generate the same CS1 maint. message although the original url is still live? Cheers, MinorProphet (talk) 12:37, 15 July 2022 (UTC)
- Have you asked the bot operator?
|deadurl=bot: unknown
was added at this edit (5×). In that edit it looks like IABot simply created|archiveurl=
and|archivedate=
from archive snapshot urls that were improperly assigned to|url=
. - The St Patrick's Barracks citation was added to the article by Editor Dormskirk at this edit. Perhaps that editor can answer your question about that citation.
- —Trappist the monk (talk) 13:19, 15 July 2022 (UTC)
References
- ^ "83rd (County of Dublin) Regiment of Foot". Regiments.org. Archived from the original on 13 January 2008. Retrieved 10 July 2016.
- ^ "Saint Patrick's Barracks, Ballymena". Archived from the original on 29 November 2014. Retrieved 17 November 2014.
- Sorry but I cannot shed any light on this either. Dormskirk (talk) 14:24, 15 July 2022 (UTC)
- Thanks, both. I probably don't need to worry my head too much about it, I'll just fix things whenever I come across them. Cheers, MinorProphet (talk) 18:47, 15 July 2022 (UTC)
- Sorry but I cannot shed any light on this either. Dormskirk (talk) 14:24, 15 July 2022 (UTC)
How to Add *Interactive Comparison Views* to Wikipedia?
Interactive Comparison Views between the "James Webb Space Telescope" (JWST) and the "Hubble Space Telescope" (HST) are being considered at "Talk:James Webb Space Telescope#Consensus on photo gallery" - the interactive comparison views of "JWST" and "HST" in the "NBC News" article at => https://www.nbcnews.com/data-graphics/compare-photos-nasas-james-webb-space-telescope-hubble-space-telescope-rcna37875[1] (also, at "ABC News")[2] are of most interest at the moment - QUESTION: Is there a way of adapting these interactive comparison views (in the NBC News article[1]) to Wikipedia - and particularly to the "James Webb Space Telescope" main article? - should note that the images are "NASA" and thus "Public Domain" - but the interactive code to compare the views in the way presented in the NBC News article[1] may be a challenge I would think - iac - Thanking you in advance for your reply - Stay Safe and Healthy !! - Drbogdan (talk) 12:51, 15 July 2022 (UTC)
References
- ^ a b c Chow, Denise; Wu, Jiachuan (12 July 2022). "Photos: How pictures from the Webb telescope compare to Hubble's - NASA's $10 billion telescope peers deeper into space than ever, revealing previously undetectable details in the cosmos". NBC News. Retrieved 15 July 2022.
- ^ Deliso, Meredith; Longo, Meredith; Rothenberg, Nicolas (14 July 2022). "Hubble vs. James Webb telescope images: See the difference". ABC News. Retrieved 15 July 2022.
Drbogdan (talk) 12:51, 15 July 2022 (UTC)
- I suppose you could write an extension for this type of media presentation, see mw:Manual:Developing extensions for how to get started. — xaosflux Talk 15:00, 15 July 2022 (UTC)
- Thanks for your comments - this may be well beyond my coding abilities at the moment - any specifics (ie, actual installation coding on an article page) welcome of course - iac - Stay Safe and Healthy !! - Drbogdan (talk) 15:10, 15 July 2022 (UTC)
- @Drbogdan short answer is: we can't today, because we don't have software that can do that available. Long answer is above, we don't like to just say "nope" for no good reason, but extension development is a long process for sure. Some options you could look in now: use a gallery to just show the images side-by-side in static form; make an animated GIF that does the slider back and forth automatically. The former is traditional and should have little resistance, animated gif's in articles are slightly contentious - but have some support. — xaosflux Talk 15:39, 15 July 2022 (UTC)
- Thanks for your comments - this may be well beyond my coding abilities at the moment - any specifics (ie, actual installation coding on an article page) welcome of course - iac - Stay Safe and Healthy !! - Drbogdan (talk) 15:10, 15 July 2022 (UTC)
@Xaosflux: (and others) - Thank You for your reply - and *Excellent* Comments and Suggestions - they're *Greatly* appreciated - the "GIF" option seems interesting - may try this at some opportunity - Thanks again for your reply - and - Stay Safe and Healthy !! - Drbogdan (talk) 18:35, 15 July 2022 (UTC)
Rollback all function not working
I'm attempting to use the "follback all" tab to revert these sock edits; although the edit summary box pops up, when I click "ok", nothing happens and the edits are not rolled back. Any other admins having this issue?-- Jezebel's Ponyobons mots 16:44, 15 July 2022 (UTC)
- Their particular way of being annoying is to revert their own edit right after they make it, so there is nothing to rollback. --Floquenbeam (talk) 16:49, 15 July 2022 (UTC)
- (edit conflict) I think this is because the IP self-reverted the edits? (e.g. attempting to "rollback selected" on the IPs edits to Mazda Capella fails due to this being the diff) — the background API call fails with the error
alreadyrolled
— TNT (talk • she/her) 16:49, 15 July 2022 (UTC)- Of course that's the reason! My brain is clearly still on holiday despite being back for two days. Thanks to you both.-- Jezebel's Ponyobons mots 16:59, 15 July 2022 (UTC)
- Finally ... FINALLY!! ... I type faster than someone else. --Floquenbeam (talk) 16:52, 15 July 2022 (UTC)
- Well, I also edit conflicted with you when replying, so you typed faster TWICE! -- Jezebel's Ponyobons mots 16:59, 15 July 2022 (UTC)
- insert {{we're number one! emoji}} here. --Floquenbeam (talk) 17:06, 15 July 2022 (UTC)
- Well, I also edit conflicted with you when replying, so you typed faster TWICE! -- Jezebel's Ponyobons mots 16:59, 15 July 2022 (UTC)
- *sees the section header sans context in my watchlist and panic* Writ Keeper ⚇♔ 17:29, 15 July 2022 (UTC)
Count of All articles in a Cat and sub-categories
Asked at Tea but no satisfactory response, so heading to where the techies hang out.
Is there a way to see how many articles are in a category inclusive of articles in subcategories (bonus points if dupes not counted but no biggie)
Specifically, I was trying to compare Category:People from Bangkok with Category:People from New York City. The former can be done by hand, but the later is not so easy. And if there is an on-wiki way, then I can expand my comparison to other cities/regions. Slywriter (talk) 18:53, 15 July 2022 (UTC)
- Petscan may work for you. Here's a category search that goes three levels deep; the category tree goes deeper than that, but you have to be careful about ending up in subcategories that are something else entirely. I get 31,195 results (no duplicates) from that search, limited to 10,000 shown on the default output table; you have to change the output in the Output tab to get full results. You may also want to traverse the category tree to understand what you are getting, including a lot of fictional people. – Jonesey95 (talk) 21:30, 15 July 2022 (UTC)
- It's not possible to set PetScan to go to unlimited subcategory depth: you need to specify depth as an integer (which effectively has no upper bound in either direction, it even permits negative values, even though those have no meaning). Don't set very high values - not only does it increase the processing time, it increases the possibility of hitting a category loop. --Redrose64 🌹 (talk) 08:39, 16 July 2022 (UTC)
WP 1.0 bot not working
— Preceding unsigned comment added by Pppery (talk • contribs) 20:25, 15 July 2022 (UTC)
Testers wanted for EditNoticesOnMobile
The showing Editnotices to mobile editors RfC passed today. This means Wikipedia:EditNoticesOnMobile will soon be enabled as a default gadget.
To ensure no unexpected issues arise testers are wanted. While the gadget has been tested, there are endless combinations of browsers, devices and editnotices out there and they can't all be tested by one person. Testing is simple! Enable "EditNoticesOnMobile" in your preferences and do what you normally do. If you run into any issues, report them on Wikipedia talk:EditNoticesOnMobile. If you don't run into any issues, also leave a note! This way we get some idea of how many people have tested the gadget. Thank you in advance! — Alexis Jazz (talk or ping me) 23:59, 15 July 2022 (UTC)
Problem with template
Hello!
On File:United Nations Office in Armenia logo2.png, why does {{NowCommons}} say ”don't delete, file doesn't exist on Commons” eventhough it does? Jonteemil (talk) 01:14, 16 July 2022 (UTC)
- It went away after I WP:PURGEd the page. Probably some timing-related problem. * Pppery * it has begun... 01:29, 16 July 2022 (UTC)
"Tag: Reverted" showing up on edits that clearly were never reverted
I don't know how long this has been going on, or what the extent of the problem is, but, for instance, this edit and the one following it have never been reverted, evn though they were tagged as reverted: [2].
(Obviously I'm a bit miffed because one of the edits was mine, and it was reverting vandalism -- so when I check my own edit history and see that my rvv has been tagged as reverted, I have to spend a considerable amount of time trying to figure out what's going on and whether anyone in fact reverted me without me getting a notification.)
So what is going on here? Softlavender (talk) 03:36, 16 July 2022 (UTC)
- The IP making to most recent edit to the page left it with wikitext exactly identical to the version as of 7 March 2022, so in some technical sense they reverted all edits after that one including both your vandalism revert and the vandalism you reverted. * Pppery * it has begun... 03:40, 16 July 2022 (UTC)
- Yes, the current revision is identical to a revision less than 15 edits ago (mw:Manual:$wgRevertedTagMaxDepth), so all those revisions are tagged "reverted". It's a tag which can come and go depending on the current version. It doesn't mean that an edit was individually reverted. PrimeHunter (talk) 03:51, 16 July 2022 (UTC)
- Global RFC started on this at meta:Requests for comment/Limit depth of marked reverts.--Snævar (talk) 08:44, 16 July 2022 (UTC)
- Yes, the current revision is identical to a revision less than 15 edits ago (mw:Manual:$wgRevertedTagMaxDepth), so all those revisions are tagged "reverted". It's a tag which can come and go depending on the current version. It doesn't mean that an edit was individually reverted. PrimeHunter (talk) 03:51, 16 July 2022 (UTC)
Searching article text dumps
I would like to search articles in a way that I think is too complex for CirrusSearch and would time out (or at least be antisocial) on Search++. It isn't a job for Quarry because it needs article text. I've looked at PAWS but the examples there seem to read article text via API, which is feasible but not ideal (and I'd run it locally rather than add the complexity of PAWS). I could download an 86 GB dump but it would surely be far more efficient to search on a WMF machine which has access to that dump then download a few MB of results. Ideally, each job would run on one section of the dump, using a simple program. (I have a perl version ready.) However, I could just about get by with grep or equivalent. Is there such a facility anywhere?
In case this is an XY problem, what I'm trying to do is find certain links containing typos, such as [[Madonna|Madona]], which can result from an editor typing in a target badly then linking to the correctly spelled article via a VE dropdown. grep could handle single insertion (Maddonna), deletion (Madona), substitution (Medonna) or transposition (Maodnna), but anything more complex (such as Damerau–Levenshtein distance ≤ 2) really needs a proper programming language. Certes (talk) 23:39, 16 July 2022 (UTC)
- @Certes dumps are already available on Toolforge. And you can run whatever freely licensed/open source programs there. Legoktm (talk) 03:08, 17 July 2022 (UTC)
On what basis are interlanguage links regionally categorised?
On what basis Russian (language), Marathi (language) & Malayalam are languages of the middle-east, and how is Spanish (language) African? It doesn't make much sense. Yes, these language show up in their respective continents (Europe, Asia) too but I still don't understand the basis. If languages of immigrants is included in deciding interlanguage link categorisation, we should have all Indian languages show up in America section but it doesn't. —CX Zoom[he/him] (let's talk • {C•X}) 14:18, 17 July 2022 (UTC)
- It's generally due to former colonies of those countries in those regions, where the language was or is an official language. For instance, there is Dutch in the americas due to their former Caribbean colonies. Spanish is in Africa because of for instance Equatorial Guinea. Malayalam is in the Middle East, probably because of Judeo-Malayalam ?? There are a lot of states which simply recognise a lot of languages for various reasons. The list with this mapping is jquery.uls.data.js, part of jquery.uls, part of the Universal Language Selector MediaWiki extension. —TheDJ (talk • contribs) 11:49, 18 July 2022 (UTC)
Where are the ArchiverLinks at Talk:Patrick Stewart...
When I view that page, the top post has the ArchiverLink but the other three posts on that page do not. I do not know why...and I wanna know. Thanks, Shearonink (talk) 18:49, 17 July 2022 (UTC)
- I don't know what this "ArchiverLink" might be but the page had formatting errors, which I've fixed. --Redrose64 🌹 (talk) 19:14, 17 July 2022 (UTC)
- Ah, that's what the issue was - D'oh...The headers! Oh, the "archiverlink" is one of these - Wikipedia:One click archiving. Thanks, Shearonink (talk) 19:27, 17 July 2022 (UTC)
Discussion at Wikipedia talk:New pages patrol/Reviewers § Does anybody use Special:Log -> Deletion Tag Log?
You are invited to join the discussion at Wikipedia talk:New pages patrol/Reviewers § Does anybody use Special:Log -> Deletion Tag Log?. –Novem Linguae (talk) 23:54, 17 July 2022 (UTC)
Upstream error
What does "upstream error" mean? It happened a few days ago, when I clicked on a Wikipedia page. I could pull up anything else on the internet, but not Wikipedia, Wikisource or Commons - not on any of my browsers. The error message just appeared again, and only lasted a minute or maybe less. But like last time, I could not pull up any wiki sites or Commons, but had no problem with any other sites. What is causing this? — Maile (talk) 01:55, 18 July 2022 (UTC)
- @Maile66 It means that the PHP part of Mediawiki cannot connect to the database part of Mediawiki. It can be caused by all kinds of issues, overloaded servers, malfunctioning extensions, bots making too many edits, database maintenance, misuse of extensions etc. The only people who really have the tools to diagnose this are the developers and sysadmins. 192.76.8.85 (talk) 02:48, 18 July 2022 (UTC)
- Thanks for the info. — Maile (talk) 02:54, 18 July 2022 (UTC)
- I guess the message actually said "upstream connect error" like in phab:T301505. PrimeHunter (talk) 03:04, 18 July 2022 (UTC)
- Thanks for the info. — Maile (talk) 02:54, 18 July 2022 (UTC)
Virtual keyboard behavior
When I am editing with the source editor, on an iPad (an old one, iOS 10.3.3) in desktop mode, the virtual pop-up keyboard "return" key maps to the normal carriage return as expected when typing in the edit window. But when I move to the edit summary input box, this key becomes "Go" and maps to "Publish changes". The problem for me is that I often hit this key by mistake when trying to hit the adjacent backspace key, leaving mangled and incomprehensible edit summaries that I can't fix. I would prefer only publishing my changes by closing the virtual keyboard and explicitly selecting the publish changes button. Can this be changed? MB 06:58, 18 July 2022 (UTC)
- Add the following to your common.js file:
// Prevent accidental submits
$(document).ready(function(){
$('input#wpSummary').keypress(function(e){
if(e.which==13) e.preventDefault();
});
});
- On any device, not just iPad, you'll no longer be able to accidentally submit with the enter/return/go key, and you'll just use the Publish changes button. I find it just as useful on desktop. MANdARAX XAЯAbИAM 09:24, 18 July 2022 (UTC)
- Thanks, I will try this when I get home to my desktop PC with a real keyboard, there is no way I am going to be able to edit my .js on this tablet. MB 20:26, 18 July 2022 (UTC)
Could a bot assist with table column manipulation?
Courtesy link: WT:WikiProject Countries#Assistance requested with SYNTH issue in country demographic articles
Is there a bot that could assist with table column operations in dozens or hundreds of articles? I reported a SYNTH problem at this discussion involving what appeared to be a dozen articles, where the fix involves primarily dropping one column from a table on each article having the issue, plus a couple of other concomitant column tweaks. I can do that and have been plodding through, but what I thought was a dozen articles has ballooned to 165 now, and I don't think that's the end of it. It's too many to handle individually. Is there a batch operation that could assist with this? Thanks, Mathglot (talk) 07:17, 18 July 2022 (UTC)
- @Mathglot, I'd suggest posting this at WP:AWBREQ or, if there are >500 pages, WP:BOTREQ. If you've written some regex to do this, it would be helpful it you could post that as well. ― Qwerfjkltalk 08:27, 19 July 2022 (UTC)
Problem showing UTC live clock gadget in Vector 2022 skin
The clock can't be seen complete in Vector 2022 skin in English Wikipedia. John123521 (Talk-Contib.) 13:46, 18 July 2022 (UTC)
- @John123521 please report problems with that gadget here: mw:MediaWiki talk:Gadget-UTCLiveClock.js so that its maintainers can look in to it. — xaosflux Talk 14:15, 18 July 2022 (UTC)
- Ah looks like you did. Are you only seeing this problem in vector-2022 on enwiki, or are you also seeing this problem on other projects with vector-2022? — xaosflux Talk 14:15, 18 July 2022 (UTC)
- I only seen this problem in enwiki; jawiki and zhwiki show the clock completely --John123521 (Talk-Contib.) 14:17, 18 July 2022 (UTC)
- I just saw it on testwiki as well. Think it has to do with per-project CSS settings - if one of the devs has fixes we can import them. — xaosflux Talk 14:24, 18 July 2022 (UTC)
- FYI, on eu.wikipedia.org and mediawiki.org it shows outside the menu altogether. When I tried to do this for en.wikipedia.org I got some complaints (I can't find the appropriate link right now), so it might benefit from some discussion about whether this should appear in the dropdown at all?
- FWIW the clock is in the user dropdown but is not clipped for me on English Wikipedia. Not sure why. Perhaps there's another gadget interfering here? Can you try disabling a few gadgets to narrow this down? Jdlrobson (talk) 17:33, 18 July 2022 (UTC)
- I just saw it on testwiki as well. Think it has to do with per-project CSS settings - if one of the devs has fixes we can import them. — xaosflux Talk 14:24, 18 July 2022 (UTC)
- I only seen this problem in enwiki; jawiki and zhwiki show the clock completely --John123521 (Talk-Contib.) 14:17, 18 July 2022 (UTC)
- Ah looks like you did. Are you only seeing this problem in vector-2022 on enwiki, or are you also seeing this problem on other projects with vector-2022? — xaosflux Talk 14:15, 18 July 2022 (UTC)
New section tab not working when JavaScript is disabled
The "New section" tab at the top of talk pages (such as this talk page!) is not working when JavaScript is disabled: when you click on the tab, nothing happens. The tab used to work fine without JavaScript, but the underlying code must have changed recently and broke it for no-JavaScript editors. It would be great to restore this functionality for no-JavaScript editors. See mw:No-JavaScript notes for more reasons why this is important. Biogeographist (talk) 16:43, 18 July 2022 (UTC)
- @Biogeographist which skin are you using? Do you have "Enable quick topic adding" enabled in Special:Preferences#mw-prefsection-editing? If so, does it work for you if you turn that off? — xaosflux Talk 17:02, 18 July 2022 (UTC)
- I turned off the "Enable quick topic adding" preference, and it works: the old behavior of the "New section" tab is restored. Thanks! I never would have figured that out by myself. Biogeographist (talk) 17:10, 18 July 2022 (UTC)
- And what is your browser? Does it work if you log out? It works for me in Firefox and Edge, both logged in and out. Try to bypass your cache. Use Ctrl+F5 in most Windows browsers, not F5 alone. If you disable JavaScript for testing then bypass after disabling it. PrimeHunter (talk) 17:08, 18 July 2022 (UTC)
- Firefox with NoScript. The preference change noted above fixed it. Biogeographist (talk) 17:10, 18 July 2022 (UTC)
- However, it doesn't work if I log out. Is there a way for IP editors to change the "Enable quick topic adding" preference? Biogeographist (talk) 17:14, 18 July 2022 (UTC)
- You should have said you use Noscript to "disable" JavaScript. I'm not suprised you get problems if JavaScript is enabled in the browser itself and you use a browser extension to control which JavaScript is allowed to run. I don't have Noscript. If I disable JavaScript in Firefox and "Enable quick topic adding" is enabled then it works for me. I don't get the quick topic feature which requires JavaScript but I do get the traditional new section window. Does it work if you really disable JavaScript? See e.g. https://www.lifewire.com/disable-javascript-in-firefox-446039. PrimeHunter (talk) 17:58, 18 July 2022 (UTC)
- Sorry that wasn't clear at first. NoScript is a pretty common way to disable JavaScript in Firefox, so I don't think the scare quotes are needed around "disabled", but you're right that it's necessary to differentiate methods of disabling JS due to technical implications. I just tested disabling JS via
about:config
, and the new section tab works as expected with that method even with "Enable quick topic adding" enabled, although that's not the method I use to disable JS. Biogeographist (talk) 18:50, 18 July 2022 (UTC) & 19:05, 18 July 2022 (UTC)- NoScript blocks JavaScript. I don't know the technical details but I guess your Firefox tells MediaWiki that it has JavaScript enabled and MediaWiki therefore chooses the JavaScript interface but NoScript blocks it. I don't know whether MediaWiki can make a workaround. PrimeHunter (talk) 19:44, 18 July 2022 (UTC)
- Sorry that wasn't clear at first. NoScript is a pretty common way to disable JavaScript in Firefox, so I don't think the scare quotes are needed around "disabled", but you're right that it's necessary to differentiate methods of disabling JS due to technical implications. I just tested disabling JS via
- You should have said you use Noscript to "disable" JavaScript. I'm not suprised you get problems if JavaScript is enabled in the browser itself and you use a browser extension to control which JavaScript is allowed to run. I don't have Noscript. If I disable JavaScript in Firefox and "Enable quick topic adding" is enabled then it works for me. I don't get the quick topic feature which requires JavaScript but I do get the traditional new section window. Does it work if you really disable JavaScript? See e.g. https://www.lifewire.com/disable-javascript-in-firefox-446039. PrimeHunter (talk) 17:58, 18 July 2022 (UTC)
- I'm going to open a bug on this. — xaosflux Talk 17:15, 18 July 2022 (UTC)
- phab:T313246 opened. — xaosflux Talk 17:22, 18 July 2022 (UTC)
- Also added a note on the preference label (MediaWiki:Discussiontools-preference-summary). — xaosflux Talk 17:25, 18 July 2022 (UTC)
- I noticed that DLynch asked at phab:T313246 whether I have "New wikitext mode" enabled, and I don't, nor any of the other beta features. Also, I have NoScript configured to allow
<noscript>
content, so blocking of that content is not the issue. I just tested it again while logged out, and the first time I clicked on the "New section" tab, it didn't work. But then I clicked on it a second time, and the second time it worked—it redirected to the basic editor. And now it always works when I'm logged out (always redirects to the basic editor), so I can no longer reproduce the issue when logged out. I don't know what changed; I swear it didn't work when I tested it before when logged out. So it appears that phab:T313246 could be closed. I'm sorry if I unnecessarily caused a bug report to be opened, although I'm glad I mentioned the issue since Xaosflux taught me the preference fix when I'm logged in. Biogeographist (talk) 21:04, 18 July 2022 (UTC)
- I noticed that DLynch asked at phab:T313246 whether I have "New wikitext mode" enabled, and I don't, nor any of the other beta features. Also, I have NoScript configured to allow
- Also added a note on the preference label (MediaWiki:Discussiontools-preference-summary). — xaosflux Talk 17:25, 18 July 2022 (UTC)
- phab:T313246 opened. — xaosflux Talk 17:22, 18 July 2022 (UTC)
academia.edu/download
Most users report this URL returns 404. However some say it works. The works and not-works are both in the USA. One works user reports success on Windows 10 (Edge) and macOS (Safari). One not-works user reports failure on Windows 7 (Chrome and Firefox) and Linux (Chrome and Firefox). There are about 1,000 URLs with academia.edu/download
that have the same problem. Does it work for you? -- GreenC 19:51, 18 July 2022 (UTC)
- Also discussed at User_talk:GreenC_bot#Flagging_non-dead_link_as_dead and Wikipedia:Link_rot/URL_change_requests#www.academia.edu/download/ -- GreenC 19:53, 18 July 2022 (UTC)
- If I go to the main page (academia.edu), it requires a login. Maybe the few "works" folks signed up for an account at some point and it kept them signed in? Schazjmd (talk) 19:58, 18 July 2022 (UTC)
- There's something very weird going on with that one. It redirects to https://d1wqtxts1xzle7.cloudfront.net/30869670/Turismo_y_Territorio_en_Salta-_Caceres_et_al-_CONICET-UBA_2012-with-cover-page-v2.pdf?[big-awful-hash]. Headbomb {t · c · p · b} 20:14, 18 July 2022 (UTC)
- Really? I didn't get a redirect, just a 404 (on both Edge and Chrome). Schazjmd (talk) 20:25, 18 July 2022 (UTC)
- Yes that's what it does when it works.. they host the content at AWS so it redirects there. When it doesn't work it looks like this. What browser did you use? -- GreenC 20:41, 18 July 2022 (UTC)
- The issue indeed seems to be of requiring an account. I'm on Firefox on Android, and have logged in account with Academia. the link works when I click in normally, but when I open it in incognito mode, it goes to a 404 page on Academia. TryKid [dubious – discuss] 20:52, 18 July 2022 (UTC)
- There's something very weird going on with that one. It redirects to https://d1wqtxts1xzle7.cloudfront.net/30869670/Turismo_y_Territorio_en_Salta-_Caceres_et_al-_CONICET-UBA_2012-with-cover-page-v2.pdf?[big-awful-hash]. Headbomb {t · c · p · b} 20:14, 18 July 2022 (UTC)
- Thank you, User:Schazjmd for figuring this out and TryKid for verifying. I emailed the site to let them know about it. The 404 status will cause bots to mark it dead. -- GreenC 21:32, 18 July 2022 (UTC)
Notification glitch
I recently Special:Notifications/isaacl received a notification on July 17, 2022 that I was mentioned in an edit. The edit in question, though, simply removed subsections with boilerplate text. Does anyone know why it would have triggered a notification? isaacl (talk) 20:25, 18 July 2022 (UTC)
CORS not allowing access to other projects
$.ajax( { url: 'https://de.wikipedia.org'+mw.config.get('wgArticlePath').replace('$1','Special:GadgetUsage?useskin=vector'), cache: false, type: 'GET' } );
I'm not asking for account data, this request can be made without cookies as far as I'm concerned.
It results in a CORS error. So I searched and found many solutions that don't work. In many questions about it it's unclear which options are for clients and which are for servers. I stumbled upon [3] which basically says "use this proxy". The stupid thing is: that actually works. It's obviously infinitely less secure and less reliable, but it works. *facepalm* There has got to be a better solution. — Alexis Jazz (talk or ping me) 21:11, 18 July 2022 (UTC)
- I found which makes the request without complaining, but no obvious way to get the page content. — Alexis Jazz (talk or ping me) 22:10, 18 July 2022 (UTC)
fetch('https://de.wikipedia.org'+mw.config.get('wgArticlePath').replace('$1','Special:GadgetUsage?useskin=vector'),{mode:'no-cors'}).then(response => {console.log(response);});
- Oh for fucks sake: https://stackoverflow.com/questions/43262121/trying-to-use-fetch-and-pass-in-mode-no-cors.
Long story short: in this case, evil people can easily get around CORS by using a proxy and good actors are forced to use a proxy as well because this is pretty dumb. What's the bloody point in blocking public resources? The actual request is still made, so if my goal was to send sensitive data toevil-incorporated.com
I still could. And if I need to retrieveevil-incorporated.com/mook.js
I still could. *facepalm* — Alexis Jazz (talk or ping me) 22:52, 18 July 2022 (UTC) - There is no better solution. This limitation of the web platform isn't to block you from retrieving whatever, it's to block you from retrieving it using someone else's device. As a simple example, if anyone on the internet could fetch https://de.wikipedia.org/wiki/Spezial:GadgetUsage from your browser, then they could extract your username from the result and associate it with your IP address. There are omre complicated scenarios, e.g. someone could access an intranet website that's only available from specific IP addresses. That's why using a proxy is the accepted workaround – then it's the proxy doing the retrieving from their own device and with their credentials, not with yours. Matma Rex talk 23:18, 18 July 2022 (UTC)
- (I'd recommend setting up your own proxy on Toolforge though, using someone else's proxy is indeed not exactly a good idea.) Matma Rex talk 23:20, 18 July 2022 (UTC)
- Matma Rex, thanks. Extraction of account details seems like it should be a non-issue: there should be a way to make the request without cookies. For the intranet, that would be a valid point, but an intranet site (which Wikipedia is not!) should specifically specify that its content should only be accessible by accepted domains. No, wait actually: if the data on the intranet site is sensitive in any way, it should be locked behind a login.
Also, using ToolForge as a proxy may not be allowed in this case. ToolForge rules are confusing with that. — Alexis Jazz (talk or ping me) 23:40, 18 July 2022 (UTC)- Even revealing the existence of an intranet site by allowing you to retrieve the login page is a privacy leak. Anyway, you're of course right that this could be done in a better way, but that is the platform we have to develop for and it has become this way for historical reasons; I thought you'd appreciate the explanation. There are sites on the internet (and definitely on intranets) that pre-date the introduction of CORS, and it has been specced this way to be compatible with sites that do not know of it.
- I don't see how that wouldn't be allowed on Toolforge, but what do I know.
- (Maybe the real solution to your problem would be to write a patch for the Gadgets extension that would make the gadget usage data available in the API somewhere. It seems like it could be added to action=query&list=gadgets easily enough. I'd be happy to review it if you cared to write it.) Matma Rex talk 02:00, 19 July 2022 (UTC)
- Matma Rex, I do appreciate the explanation, but it's still oddly designed and when "use a proxy" is the correct answer something has gone horribly wrong somewhere along the way. I could appreciate if intranet sites would specify that browsers should pretend they are unreachable when trying to access them from a foreign domain. I could also appreciate browsers doing that when they detect an internet site is trying to access something in a local range. But neither should be standard.
And say you know about some intranet site and you know how to hack it. Trick an employee into visiting your blog and you can make requests towards that intranet site! Never getting a response certainly complicates things, but the fact you can make requests at all should be worrying enough. Thinking about that, I'm starting to worry about routers.
Getting the usage data through the API would certainly be very nice. I'm pretty much completely unfamiliar with MediaWiki though and I haven't done any PHP in ages. I do wonder: if the API can be accessed from other domains, why can't other pages be accessed? If security is an issue, isn't there some render-as-anon option that could make CORS more lax? — Alexis Jazz (talk or ping me) 02:51, 19 July 2022 (UTC)- Consider if you were logged into your banking site and then visited a site with some malicious Javascript that made a request to access private information from your bank web site. To prevent it from going through, the cross-origin request has to be blocked by default. A proxy would be unable to access your info, as it would not be logged in as you. isaacl (talk) 03:46, 19 July 2022 (UTC)
- Isaacl, a request without cookies or other session data (compare opening a private window in your browser) would have the same effect for internet sites, wouldn't it? — Alexis Jazz (talk or ping me) 03:59, 19 July 2022 (UTC)
- Sure, making sure you're always logged out of your accounts would provide protection (and it's why this is a general security recommendation). In practice, users don't always log out, and don't browse every site with separate sessions restarted from scratch. Third-party Javascript code can be injected by third-party advertisers/trackers/discussion widget providers and so forth. Private browsing is, in a sense, overkill as not all cookies and other session data are problematic, but it's a reasonable default to wall off interactions between sites. In a similar manner, it's reasonable to block cross-site Javascript requests by default. isaacl (talk) 06:31, 19 July 2022 (UTC)
- I don't mean ask the user to log out, I mean more like
{mode:'no-cors'}
resulting in a request akin to how that request would be made if a private window was opened for it. That's what I initially expected from that option, but instead it just prevents you from getting any response at all. — Alexis Jazz (talk or ping me) 06:39, 19 July 2022 (UTC)
- I don't mean ask the user to log out, I mean more like
- Sure, making sure you're always logged out of your accounts would provide protection (and it's why this is a general security recommendation). In practice, users don't always log out, and don't browse every site with separate sessions restarted from scratch. Third-party Javascript code can be injected by third-party advertisers/trackers/discussion widget providers and so forth. Private browsing is, in a sense, overkill as not all cookies and other session data are problematic, but it's a reasonable default to wall off interactions between sites. In a similar manner, it's reasonable to block cross-site Javascript requests by default. isaacl (talk) 06:31, 19 July 2022 (UTC)
- Isaacl, a request without cookies or other session data (compare opening a private window in your browser) would have the same effect for internet sites, wouldn't it? — Alexis Jazz (talk or ping me) 03:59, 19 July 2022 (UTC)
- Yep, you definitely should worry about routers.
I do wonder: if the API can be accessed from other domains, why can't other pages be accessed? If security is an issue, isn't there some render-as-anon option that could make CORS more lax?
- I think in principle this would be possible, I don't know for sure why it's not allowed. I could guess that a) folks who worked on that wanted to encourage using the API instead of parsing the HTML output and b) it would require reviewing all of MediaWiki and extensions to make sure everything respects that parameter, and doesn't directly access global state like cookies. (There is a render-as-anon option in the API:
origin=*
, intended especially for anonymous CORS, for example: https://en.wikipedia.org/w/api.php?action=query&meta=userinfo&origin=*.) Matma Rex talk 10:47, 19 July 2022 (UTC)
- Consider if you were logged into your banking site and then visited a site with some malicious Javascript that made a request to access private information from your bank web site. To prevent it from going through, the cross-origin request has to be blocked by default. A proxy would be unable to access your info, as it would not be logged in as you. isaacl (talk) 03:46, 19 July 2022 (UTC)
- Matma Rex,
I don't see how that wouldn't be allowed on Toolforge, but what do I know.
wikitech:Wikitech:Cloud Services Terms of use: "Using Wikimedia Cloud Services as a network proxy: Do not use Wikimedia Cloud Services servers or projects to proxy or relay traffic for other servers. Examples of such activities include running Tor nodes, peer-to-peer network services, or VPNs to other networks. In other words, all network connections must originate from or terminate at Wikimedia Cloud Services."
Not so sure what I'd need would be allowed by that. Wikipedia isn't part of Wikimedia Cloud Services I think. And it certainly would be forbidden for any domain outside Wikimedia.
I thought about some script to create citations or similar things for stuff not supported by Citoid. Like importing ISBNs or something, processed by the client. CORS generally prevents that and ToolForge prohibits running a proxy to get the data from www.isbnsite.example to the user.
mw:Wikimedia Labs/Agreement to disclosure of personally identifiable information: "and agree your IP address will be made publicly available and not be treated as confidential". Okay, hard pass. — Alexis Jazz (talk or ping me) 05:09, 19 July 2022 (UTC)- A page that is labelled as a draft with talk page comments from 8 years ago? I don't think you have much to worry about there. Izno (talk) 05:32, 19 July 2022 (UTC)
- Izno, it's linked from wikitech:Portal:Toolforge/Quickstart though. — Alexis Jazz (talk or ping me) 06:25, 19 July 2022 (UTC)
- Huh, okay, I guess that does technically prohibit doing this, although I don't think that's the intended spirit of the rule. I'd ask for a clarification and I'd expect that doing what I suggested would be allowed. But I guess this is a moot point given SD0001's better solution below. Matma Rex talk 10:57, 19 July 2022 (UTC)
- A page that is labelled as a draft with talk page comments from 8 years ago? I don't think you have much to worry about there. Izno (talk) 05:32, 19 July 2022 (UTC)
- Matma Rex, I do appreciate the explanation, but it's still oddly designed and when "use a proxy" is the correct answer something has gone horribly wrong somewhere along the way. I could appreciate if intranet sites would specify that browsers should pretend they are unreachable when trying to access them from a foreign domain. I could also appreciate browsers doing that when they detect an internet site is trying to access something in a local range. But neither should be standard.
- @Alexis Jazz Have you tried using mw.ForeignApi? — MusikAnimal talk 00:17, 19 July 2022 (UTC)
- MusikAnimal, how would I get Special:GadgetUsage (an HTML page) through ForeignApi? The data from GadgetUsage isn't available through the API afaik. — Alexis Jazz (talk or ping me) 00:50, 19 July 2022 (UTC)
- It's available through the API, like all other query pages. https://en.wikipedia.org/w/api.php?action=query&list=querypage&qppage=GadgetUsage&qplimit=max – SD0001 (talk) 10:42, 19 July 2022 (UTC)
- Thanks, I didn't even know this is possible! Matma Rex talk 10:59, 19 July 2022 (UTC)
- This API is missing the information about whether the gadget is default or not though, so you have to guess whether "0" means no users or all users… But I realized you can cross-reference this with the data in https://en.wikipedia.org/w/api.php?action=query&list=gadgets, which marks
default
gadgets. Together with that I think this matches the Special:GadgetUsage functionality. Matma Rex talk 11:03, 19 July 2022 (UTC)
- It's available through the API, like all other query pages. https://en.wikipedia.org/w/api.php?action=query&list=querypage&qppage=GadgetUsage&qplimit=max – SD0001 (talk) 10:42, 19 July 2022 (UTC)
- MusikAnimal, how would I get Special:GadgetUsage (an HTML page) through ForeignApi? The data from GadgetUsage isn't available through the API afaik. — Alexis Jazz (talk or ping me) 00:50, 19 July 2022 (UTC)
- I suppose the simplest solution is to add the
origin
parameter to index.php the same way we have it on api.php. 0xDeadbeef 04:06, 19 July 2022 (UTC)
Tech News: 2022-29
22:58, 18 July 2022 (UTC)
Template transcluding categories and SD
{{Get short description}} transcludes the target page to find the short description, but it also seems to transclude the categories and short description. Trying wrapping it in <nowiki>...</nowiki>
, or using {{#invoke:Page|getContent|expand}} doesn't seem to work either. ― Qwerfjkltalk 08:18, 19 July 2022 (UTC)
Template:Infobox television Lua errors on uncreated pages
When adding {{Infobox television}} to a new page on desktop and clicking "Show preview", I see two Lua errors. Firstly, at the top of the prose part of the screen: "Lua error in Module:Infobox_television at line 106: bad argument #1 to 'find' (string expected, got nil)." Secondly, at the top of the infobox: "Lua error in Module:Infobox_television at line 284: bad argument #1 to 'match' (string expected, got nil)." I don't see this error once the page has been created, either in the article proper or the preview screen.
I believe the issue is that the Lua is failing to grab the name of the page that the infobox is on, as the title at the top of the infobox does not display in the preview. I'm using the editing preference "Show previews without reloading the page", in case that's relevant. I note that I'm not the only one with this issue. It's just the TV infobox that's causing the issue: the page title is shown correctly and there are no Lua errors with {{Infobox film}}, for instance. — Bilorv (talk) 11:02, 19 July 2022 (UTC)
- I couldn't replicate it when testing it on Etetetetete. I however added nil checks to the lines the error message pointed to. In general though, post issues at the most relevent location. This isn't it. Gonnym (talk) 11:23, 19 July 2022 (UTC)
How can I get the editor with the citation tool and the editor with strike through, etc
Also, although I have "always given the source editor", I now default to visual editor with the ability to switch. How I make these messes is beyond me. Sorry folks. I do a lot of sourcing, so really need to be able to cite easily. Doug Weller talk 11:53, 19 July 2022 (UTC)
- And I now have a 🖊 instead of the word edit. Doug Weller talk 12:39, 19 July 2022 (UTC)
- Using Vector 2022. I now have an arrow at the top to publish. Doug Weller talk 13:14, 19 July 2022 (UTC)
- @Doug Weller if you want avoid the visual editor most of the time, try selecting "Temporarily disable the visual editor while it is in beta" in Special:Preferences#mw-prefsection-editing. — xaosflux Talk 13:33, 19 July 2022 (UTC)
- @Xaosflux That worked! Although now I have to switch between Wiked and whatever it is that shows as this. Easy enough to do though. Doug Weller talk 13:59, 19 July 2022 (UTC)
- And solved my inability to preview problem. Thanks so much. I'm dying of the heat here and this was a real timewaster, glad I had help, as always, from User:Xaosflux. Doug Weller talk 14:38, 19 July 2022 (UTC)
- @Doug Weller if you want avoid the visual editor most of the time, try selecting "Temporarily disable the visual editor while it is in beta" in Special:Preferences#mw-prefsection-editing. — xaosflux Talk 13:33, 19 July 2022 (UTC)
- Using Vector 2022. I now have an arrow at the top to publish. Doug Weller talk 13:14, 19 July 2022 (UTC)
Search categories for both article and talk space conditions
Is there a way to search for articles matching an AND condition for categories amongst both the talk page and the main article page? eg. something like
All: incategory: "High-importance psychology articles" incategory: "All Wikipedia articles in need of updating"
The first category in this example is on article talk pages, the second category is on article pages. I know this search is not empty because of this table. If there is a way to do this, I think it would be worthwhile to add to Help:Searching/Features, Help:Searching, Wikipedia:FAQ/Categories and possibly also Wikipedia:FAQ/Categorization. Thanks Darcyisverycute (talk) 12:15, 19 July 2022 (UTC)
- Cirrus search can't do this, but PetScan may be able to. It can look for a category on the article and a template on the talk page. However, although All Wikipedia articles in need of updating is associated with the {{Update}} template, I can't find a suitable template for High-importance psychology articles. So my suggestion doesn't quite work, but someone may be able to fix it. If not then you might have to resort to a Quarry query. Certes (talk) 12:31, 19 July 2022 (UTC)