Wikipedia:Village pump (technical) - Wikipedia

I worked on a module that would serve as an enhanced editnotice loader for Wikipedia. See testwiki:Module:Editnotice_load and Module:Editnotice load (which is an exact copy). Features include category editnotices, better group notices, and editnotices by page ID (which would reduce the need to move pages around).

I want to get further feedback on this loader before it inevitably gets implemented. Please check out the testwiki. It should be backwards compatible with the way we do things, but I would like checks for this first.

If this is to be implemented, there will need to be a couple of changes made, including to:

• Template:Editnotice load (would need to be replaced with {{#invoke:editnotice load|main}})
• Template:Editnotice load/notext (would need to redirect to Template:Editnotice load, or should call {{editnotice load}} but with the parameter "notext=yes")
• Template:Editnotice/notice (would need to be updated to match that on testwiki)
• MediaWiki:Noarticletext-nopermission (should be updated with the following addendum: {{#invoke:editnotice load|protectionEditnotice}})
• MediaWiki:Protectedpagetext (would need to be updated to match that on testwiki)
• MediaWiki:Cascadeprotected (would need to be updated to match that on testwiki)
• Template:Editnotices/Group/Template:Editnotices (would need to be updated to match that on testwiki)
• MediaWiki:Titleblacklist-custom-editnotice (would need to be updated to match that on testwiki)

This would make the editnotice loader much more robust.

Immediately, in preparation for this, I would consider adding the following category editnotices templates:

{{BLP editintro}}

• Template:Editnotices/Category/Living people
• Template:Editnotices/Category/Possibly living people

{{Disambig editintro}}

• Template:Editnotices/Category/Disambiguation pages

Anything else? Awesome Aasim 19:06, 9 September 2024 (UTC)Reply

Some documentation on how it works from a user's perspective would be helpful, in order to understand the context and how it would be used in practice, including how security restrictions are enforced. On a side note, I'm not sure that its deployment is "inevitable". isaacl (talk) 22:03, 9 September 2024 (UTC)Reply

I have some testcases on testwiki. For best results, view when logged out and inspect the HTML when logged in.

testwiki:Taylor Swift should be a good example of me getting category editnotices working. testwiki:Protected title and testwiki:Protected title2 show the protection editnotice on both the create screen and on the "does not exist" screen when a title is protected from creation for other reasons.

testwiki:Special:EditPage/A should show the page notice from testwiki:Template:Editnotices/PageID/54370 (which is for A). You can also see I renamed previous "page notice"s to "title notice"s because the way page notices are bound to currently are actually to titles, not pages. The new "page notice" will remain bound to a specific page because it uses PageID. There will be no need to update the title notices for pages that exist. On the other hand, for pages that don't exist, the title notice will need to be kept up to date. Awesome Aasim 04:01, 10 September 2024 (UTC)Reply

I can't tell from the article page how to use the feature: where the edit notice lives, how will access be limited, and so forth. Thus it's hard to evaluate the feature without knowing the maintenance cost. isaacl (talk) 09:58, 10 September 2024 (UTC)Reply

The editnotices live in the same pseudo-space: Template:Editnotices/. See testwiki:Module:Editnotice load/config.

I also moved the editnotice links to a collapsible box because the number of creatable editnotices has gotten relatively high after adding category notices. Awesome Aasim 13:16, 10 September 2024 (UTC)Reply

OK, I see there's now a link above the edit notice point to its location, so category-based notices are grouped under a "Category" subpage. What are the enhancements for the group-based notices? isaacl (talk) 18:33, 10 September 2024 (UTC)Reply

There is less ambiguity in how they are handled. For example, on testwiki:Template:A/B/C/D/E, there are five different group editnotices that can be created. So if there is a page where it is desirable that the group Template:A/B needs one group notice, and Template:A/B/C needs another group notice, and Template:A/B/D needs another group notice, that can now be done; there will be one common group notice and two separate group notices for subpages. Awesome Aasim 19:21, 11 September 2024 (UTC)Reply

I would suggest to phase the rollout into stages, and creating a test plan to ensure nothing regressed. Editing this many interface pages and fully protected templates at once sounds like too much work for an admin to volunteer to. For instance, the specific category editnotices you mention can be left for later as we already have a decent system to handle those categories.
Immediately, in preparation for this, I would consider adding the following category editnotices templates this cannot be done immediately as they also need to be removed from Module:Mainspace editnotice, else they would show up twice when the rest of the changes are deployed. – SD0001 (talk) 08:01, 10 September 2024 (UTC)Reply

I actually think this might be something that is better done all in one go. Removing the two category editnotices from Module:Mainspace editnotice should be kind of a no-brainer after the rollout. The way that the module currently does these checks, checking the unparsed wikitext, currently sucks.

Do you have an idea for a Scribunto test runner for Module:Editnotice load to ensure that everything works with demo editnotices? Awesome Aasim 16:53, 13 September 2024 (UTC)Reply

I haven't noticed any bugs or regressions yet, if someone could take a second look at my code maybe then we will be able to identify potential problems. Awesome Aasim 12:52, 2 October 2024 (UTC)Reply

I submitted an edit request. I think this is something that could be botted by an admin opening up 8 edit windows and then saving all of the proposed changes at once. I have done this before, it gets annoying when you get rate limited but it is not impossible. Awesome Aasim 20:05, 8 October 2024 (UTC)Reply

On Wikivoyage, that article is just mediocre quality. There should be no start there. I am not sure how to remove it and what caused the error (could it happen for other articles?). _{Piotrus at Hanyang| reply here} 04:20, 26 September 2024 (UTC)Reply

It was added to Wikidata in this revision. Not sure why as looking through the history of wikivoyage:Kaesong it was never star quality.  novov talk edits 05:58, 26 September 2024 (UTC)Reply

@Hanyangprofessor2: The star is because of the "badge" (a little rosette) at d:Q109079#sitelinks-wikivoyage. As noted above, this was set by Dexbot (talk · contribs) almost ten years ago; you would need to ask its botop (Ladsgroup) what the mechanism is that triggered this amendment. If it really is wrong, these "badges" appear to be user-editable. --Redrose64 🌹 (talk) 15:15, 26 September 2024 (UTC)Reply

They aren’t; saving the changes to them is limited to certain user groups.  novov talk edits 22:59, 26 September 2024 (UTC)Reply

@Ikan Kekek FYI, and maybe you know who to ping. Or report this to WV Traveller's Pub, I am not sure how serious this issue is, but I think the star should not be there for 'usuable' articles. _{Piotrus at Hanyang| reply here} 07:21, 27 September 2024 (UTC)Reply

I don't understand the problem. It's starred on Wikidata? Best to discuss that there, I guess. I don't normally edit Wikidata. You could bring this up in the voy:Wikivoyage:Travellers' pub. Ikan Kekek (talk) 15:35, 27 September 2024 (UTC)Reply

@Hanyangprofessor2 The bot added the badge ten years ago because at least back then this revision to be exact had voy:Template:Usablecity. Note that the badge was added for "recommended article" [1] hence the silver (not gold). There are many badges. You should be able to see the list of page that have badges in voy:Special:PagesWithBadges Ladsgroup^overleg 10:26, 27 September 2024 (UTC)Reply

And the current version of voy:Kaesong#Go next still has {{usablecity}}. This is therefore a matter for Wikivoyage, and not our problem at all. --Redrose64 🌹 (talk) 18:06, 27 September 2024 (UTC)Reply

@Ikan Kekek @Redrose64 The issue is that usable article on Wikivoyage are just middle-level artices (see voy:Wikivoyage:Article status). A star should denote an equivalent of a Featured article - on Wikivoyage that would be a Star-class article. A Good Article equivalent there would be a Guide (which even uses the GA green cross). Having Featured Article-lookalike barnstars for Wikivoyage usable articles, which are equivalent to our B- or C- class articles, makes no sense and is arguably actively misleading. _{Piotrus at Hanyang| reply here} 03:16, 30 September 2024 (UTC)Reply

PS. And it is a problem for us (not for Wikivoyage), because it is us (English Wikipedia) that has misleading indicators suggesting that our sister project article is high quality, when it is not. Wikivoyage has correctly identified the article as a middle-level (usuable) article, but we are incorrectly starring them as high-level articles. _{Piotrus at Hanyang| reply here} 03:18, 30 September 2024 (UTC)Reply

PPS. Compare to Hiroshima, which is a star-level article on Wikivoyage, and is correctly tagged with that project's yellow star in our article. Why are we tagging Wikivoyage usable articles at all, and why are we using Featured Article symbol instead of the Wikivoyage blue circle (which is the symbol for their usable articles)? At minimum, the symbol for usable content should be fixed (from FA star to blue circle), and I'd strongly suggest removing any symbols for that class (which is below GA-level equivalent). I hope the issue is now clearer? _{Piotrus at Hanyang| reply here} 03:21, 30 September 2024 (UTC)Reply

@Hanyangprofessor2: The stars, discs etc. (of whatever colour) are added by mw:Extension:WikimediaBadges based on settings in Wikidata. If the extension is faulty, file a ticket at phab:. If Wikidata has the wrong settings, fix them, or find out at Wikidata why their bots are using imperfect algorithms. Whatever the problem is, it's still not our fault. --Redrose64 🌹 (talk) 20:14, 30 September 2024 (UTC)Reply

@Redrose64 But it is our problem, and I don't have time to learn the extension details to fix it. I am just reporting it here, so those more familiar with the issue can investigate it and fix it.

I will ping editors who have edited the mediawiki extension page you linked: @MarcoAurelio @Eisheeta _{Piotrus at Hanyang| reply here} 06:53, 2 October 2024 (UTC)Reply

@Hanyangprofessor2: How can it be out problem when (a) there is no fault at English Wikipedia and (b) there is nothing that can be done at English Wikipedia to alter the situation? As for MarcoAurelio and Eisheeta, they will probably tell you exactly what I have already said: that the extension displays a star according to whatever is set on Wikidata. Have you raised any discussions at either Wikidata itself, or at Wikivoyage? --Redrose64 🌹 (talk) 09:47, 2 October 2024 (UTC)Reply

@Redrose64 It is our problem because we are displaying misleading information to our readers. I am not saying it is our fault, I am not saying it is anyone's fault (we are all well meaning volunteers here), but it is not Wikivoyage of Wikidata problem, because the error (which may be related to some bad tool they use or used) affects us, not them. And as I said, I don't know where else to raise this problem, and it is us who should care the most about it, since we (our readers) are the ones most affected. _{Piotrus at Hanyang| reply here} 07:34, 3 October 2024 (UTC)Reply

(edit conflict) @Hanyangprofessor2: Two users above have suggested voy:Wikivoyage:Travellers' pub; you have posted there before regarding other matters, so you are aware of its existence. Then there is d:Wikidata:Project chat. Now please stop pretending that this is an English Wikipedia problem when all we are doing is reflecting data that is stored elsewhere. This is like reading in your newspaper about some unpleasant situation in a foreign country and expecting your local newsagent to do something about it. --Redrose64 🌹 (talk) 16:15, 3 October 2024 (UTC)Reply

As I explained to you, I don't believe it is Wikivoyage problem at all. Wikidata, to a small degree (because some data is hosted there). But this is primarily our problem; it doesn't matter where the data is stored - it is our project which displays misleading information. I do not understand why you are fine with our website displaying errors. _{Piotrus at Hanyang| reply here} 03:57, 4 October 2024 (UTC)Reply

Our website displays millions of errors. This is a tiny minor detail that in no way compromises the integrity of English Wikipedia. To quote Jonesey95: The problem is that a silver star is used for both "Good" (second-tier) and "Recommended" (i.e. third-tier, the level below Good quality) in the extension. Please note those words in the extension. Nothing that Jonesey95 has written demonstrates that it is our problem at all. Jonesey95 has restated - in different words - information that was already provided to you earlier in this thread. Sure, we display that little silver star. But the code to display that star is part of the MediaWiki software, which is shared by all WMF wikis. --Redrose64 🌹 (talk) 07:34, 4 October 2024 (UTC)Reply

Feel free to disagree, but I believe that removing even one error is a good thing. I don't feel that the fact that our website has millions of errors is ok. _{Piotrus at Hanyang| reply here} 03:06, 5 October 2024 (UTC)Reply

I did a bunch of digging to see what might be happening here. So far I have found a page explaining that on en.WikiVoyage, they have Star (=en.WP FA), Guide (=en.WP GA) and Usable (no en.WP equivalent?) articles. Then I found this October 2014 bot request on Wikidata listing those same three article statuses and asking for Dexbot to assign badges based on those statuses. The bot's edit adding the "recommended article" status for en.Wikivoyage to Kaesong on Wikidata happened in that same time frame. So far, it appears that everything is working as designed. Then I found this CSS page, part of the mw:Extension:WikimediaBadges extension, that assigns star images. It assigns a gold star to Featured articles, and a silver star to articles flagged with either "goodarticle" or "recommendedarticle" status.

As far as I know, en.WP does not have a "recommended article" status (I'm not seeing anything comparable in the table at {{Article history}}).

TL;DR: The "recommended" (i.e. third-tier) tag next to en.Wikivoyage on Kaesong on Wikidata appears to be correct, according to the statuses used on en.Wikivoyage. The problem is that a silver star is used for both "Good" (second-tier) and "Recommended" (i.e. third-tier, the level below Good quality) in the extension.

It seems to me that if a "recommended article" is a third tier, it should get a bronze star (to be in line with gold and silver). That might mess up the star color on other WMF wikis, though. Since the extension is not documented well (see T212020), and I haven't found a table or map that shows the different statuses on each monitored site, it is difficult to know whether changing "recommended article" to bronze in the CSS file would fix a problem here but break something on another site. – Jonesey95 (talk) 16:07, 3 October 2024 (UTC)Reply

It turns out that there is an existing Phabricator feature request at T189374 to make this change. If anyone here wants to make this change happen and knows how to actually upload a proposed change to gerrit/github or whatever site is used, be my guest. – Jonesey95 (talk) 16:24, 3 October 2024 (UTC)Reply

Pinging Krinkle and Ladsgroup, who have contributed code to this extension. – Jonesey95 (talk) 16:29, 3 October 2024 (UTC)Reply

Badges to my knowledge are owned by WMDE. Please contact wikidata team. Ladsgroup^overleg 18:01, 3 October 2024 (UTC)Reply

How? A link to the appropriate discussion page would be helpful. I find Wikidata impenetrable. – Jonesey95 (talk) 21:09, 3 October 2024 (UTC)Reply

@Jonesey95: d:Wikidata:Project chat, as I mentioned earlier. --Redrose64 🌹 (talk) 22:50, 3 October 2024 (UTC)Reply

Thanks. I have posted there. We'll see if anyone is able to help from there. – Jonesey95 (talk) 23:33, 3 October 2024 (UTC)Reply

@Jonesey95 Thank you for investigating it and trying to actually help, rather than brushing this off. I expect some readers of English Wikipedia are confused, but they likely don't even know (or care enough) to report this. _{Piotrus at Hanyang| reply here} 03:55, 4 October 2024 (UTC)Reply

• Do any of the regular (or irregular) watchers at VPT feel that this is an English Wikipedia problem? Or that it is not? Please state one way or the other. --Redrose64 🌹 (talk) 07:53, 4 October 2024 (UTC)Reply

  It's an en.WP problem in that we are affected by it. If my neighbor's car alarm is going off in the middle of the night, it's a problem for me in that I can't sleep, and it's a problem for my spouse in that my spouse has to listen to me complain about it. I would not be surprised if other WMF sites are affected by this doubling-up of second-tier and third-tier article quality indicators; if so, it is a problem on many sites. The origin of the problem appears to be in a Wikimedia (or WMDE, whatever the difference is) extension. Problems that manifest on en.WP are often caused by code that is outside of our immediate control. – Jonesey95 (talk) 12:45, 4 October 2024 (UTC)Reply

  I don't see a star at all, even if I log out and view with a majority desktop browser, or go into mobile mode. Does it need a gadget or preference enabled to see, or am I just missing it? But I agree with Jonesey95 that it's our problem if it's displaying on our site; and we should fix it locally if a global fix is impractical or undesirable. —Cryptic 13:22, 4 October 2024 (UTC)Reply

  so you can either get some earplugs (fix locally) but this just masks the problem, it doesn't make it go away. Or, you go round to your neighbour, tell them they have a problem with their car and ask them to fix their car (global fix). Here, we should be going to the neighbour. Nthep (talk) 14:10, 4 October 2024 (UTC)Reply

  Yes, getting your neighbour to fix it is best, but if the alarm keeps going off night after night, you wear earplugs in the meantime. —Cryptic 15:16, 4 October 2024 (UTC)Reply

  The trouble is, we forget to remove the earplugs after the neighbour fixes the car. Nthep (talk) 17:48, 4 October 2024 (UTC)Reply

  The stars are not visible in Vector 2022 due to a bug. Try forcing Vector Legacy: https://en.wikipedia.org/wiki/Kaesong?useskin=vector and note the silver star next to WikiVoyage in the left-side menus, under "In other projects". That silver star should be bronze, because Kaesong is a "Usable" (third-tier) article on WikiVoyage. This is admittedly a trivial matter, but we are at VPT .... – Jonesey95 (talk) 15:10, 4 October 2024 (UTC)Reply

  Thank you. .badge-recommendedarticle.badge-recommendedarticle { list-style-image: url(https://upload.wikimedia.org/wikipedia/commons/thumb/c/c7/Rekommenderad_gr%C3%B6n.svg/12px-Rekommenderad_gr%C3%B6n.svg.png); } in your CSS changes it to the green star from the phab ticket. Obviously that isn't usable sitewide as-is - the file needs to be protected, it should be uploaded at the proper size instead of relying on the scaled-down version which will eventually go away, and like you say above bronze is probably a better choice - but it's enough to show we don't have to wait on an upstream fix, which may or may not ever happen. —Cryptic 16:19, 4 October 2024 (UTC)Reply

  Sorry for being away from this thread for a while. None of this is a Wikivoyage problem, and there's nothing that we can do about it at Wikivoyage, as far as I can tell. It seems to be a Wikidata problem. Ikan Kekek (talk) 20:30, 6 October 2024 (UTC)Reply

  I'd rephrase it as "it's a Wikipedia problem caused by Wikidata". _{Piotr Konieczny aka Prokonsul Piotrus| reply here} 06:03, 7 October 2024 (UTC)Reply

What it says on the tin. The Earwig is aware of this. Whenever anyone tries to use the tool, they get this message most of the time: An error occurred while using the search engine (Google Error: HTTP Error 429: Too Many Requests). Note: there is a daily limit on the number of search queries the tool is allowed to make. You may repeat the check without using the search engine.

Obviously, there's a bit of tomfoolery around hitting the limit, which is apparently shared by all users of Wikipedia. There was some discussion in the WMF section of the pump a few weeks back about what the WMF can do about it. I'm mostly interested in what we can do in the meantime while it gets fixed. I dream of horses (Hoofprints) (Neigh at me) 00:56, 29 September 2024 (UTC)Reply

You could do your own search engine search for snippets of text from the article. One sentence from each paragraph should give an indication of problems. And you can tick the box on the tool to limit the check. Graeme Bartlett (talk) 05:49, 29 September 2024 (UTC)Reply

This is the message I get every time I try to use Earwig check tool since early 2024. It's always over the limit. I've asked Earwig about it multiple times and I think the problem is that bots can use it and they are causing it to hit its daily limit pretty early in the day. I wish bots could get booted of so that regular editors would have access to the tool but I have yet to see any change. I don't even try to use it any more. Liz ^{Read! Talk!} 22:43, 29 September 2024 (UTC)Reply

It does work for me quite often, probably as I am in a different time zone. You may have to await the end of the "day", and try again. Graeme Bartlett (talk) 22:47, 29 September 2024 (UTC)Reply

@Liz: There's a message from Chlod saying The Right People are aware and working on a way to authenticate. I'm sure that'll boot the bots off.

@Graeme Bartlett: I was thinking more of an alternative tool that we can use instead? Like, how does CopyPatrol work? I dream of horses (Hoofprints) (Neigh at me) 04:57, 2 October 2024 (UTC)Reply

Perhaps the bot behind this tool is what is exhausting Google? I don't know/ https://meta.wikimedia.org/wiki/CopyPatrol It also uses turnitin, and you can tick that box on earwig. But its findings show less than Google search. Graeme Bartlett (talk) 06:07, 2 October 2024 (UTC)Reply

There is some documentation that indicates that a bot is going through recent changes and marking the likely copyright cases to copypatrol. Looking at a single page, surfacing results for that page like that is less traffic than letting several users query that same page. I would say Copypatrol should be used for english wikipedia and other supported projects, but earwigs tool when copypatrol does not support the project. Snævar (talk) 01:15, 3 October 2024 (UTC)Reply

@Graeme Bartlett and @Snævar: CopyPatrol uses TurnItIn, not google (unlike Earwig, which uses both Google and TurnItIn). Probably why it shows less (which is a bit of a problem), but perhaps it is a stop gap measure. My main concern about CopyPatrol is that it's more useful for individual edits and not an entire article. I dream of horses (Hoofprints) (Neigh at me) 22:07, 3 October 2024 (UTC)Reply

Sigh... Where is this guesswork coming from? meta:CopyPatrol says it uss User:EranBot that uses both google trough Earwin and Turnitin. Read both links. Could you stop this guesswork nonesence and stick to facts? You are starting to annoy me. Also if you put an diff into earwigs tool it checks the whole article, not just the diff in question. Do not just repeat nonesence when proven otherwise. Snævar (talk) 09:37, 8 October 2024 (UTC)Reply

When trying to login to another Wikipedia for which I don't have a local account like https://mos.wikipedia.org I get the error:

Auto-creation of a local account failed: Cannot create account: The username is already in use. Please pick another name.

Any workaround? Killarnee (talk) 01:58, 3 October 2024 (UTC)Reply

@Killarnee: Have you both tried when you were already logged in at another wiki and when you logged out first? PrimeHunter (talk) 02:18, 3 October 2024 (UTC)Reply

@Dreamy Jazz maybe relevant to your existence given what you're working on. Izno (talk) 03:30, 3 October 2024 (UTC)Reply

I don't think so AFAIK. It appears to be related to merging wikitech accounts into SUL. Dreamy Jazz ^{talk to me | my contributions} 11:57, 6 October 2024 (UTC)Reply

It works for me. Special:CentralAuth/Killarnee says: "Global group: Two-factor authentication testers". Maybe that causes problems. The error message sounds like something that shouldn't happen but it's apparently a combination where MediaWiki:Authmanager-authn-autocreate-failed is called with MediaWiki:Centralauth-account-unattached-exists. The Killarnee account does not exist at https://mos.wikipedia.org but the bottom of Special:CentralAuth/Killarnee shows an unattached account at wikitech:User:Killarnee. This may be relevant. If it's your account then can you merge it at Special:MergeAccount or wikitech:Special:MergeAccount? PrimeHunter (talk) 04:13, 3 October 2024 (UTC)Reply

It was the Wikitech account and after the merge it works. Thanks a lot. Killarnee (talk) 12:05, 3 October 2024 (UTC)Reply

With the help of WMF staff we identified a critical issue with webauthn that is likely locking users out of their accounts. The issue prevents webauthn activated on a device from being used on another device, or between browser sessions. This means users can be activating webauthn , intending to secure their account, and end up losing access to wikipedia. Because relatively few users activate this feature in the short term, the issue may not be getting the attention it deserves. It will also discourage future users from activating webauthn, which is a critical security feature to protect the community.

Please help me find the appropriate contact with WMF technical staff to help get the fix merged. It's a one-line fix from upstream repository so it should be low risk. Tonymetz 💬 16:50, 3 October 2024 (UTC)Reply

I guess that would be us, the Platform Team. I'll raise it with the team and we'll have a look. Matma Rex talk 19:30, 3 October 2024 (UTC)Reply

Thanks for the note, webauthn has multiple known issues and is certainly in the "experimental" role. As far as our contributors and readers here at the English Wikipedia go: webauthn shouldn't be used by anyone for anything important. Technical reports in phabricator are of course welcome. — xaosflux ^Talk 00:09, 5 October 2024 (UTC)Reply

thanks for the context. On the ticket , Reddy mentioned it was completed by a contractor and hasn't been supported. To whom could I appeal to have it turned off? I believe it's locking people out, so it's a liability. Tonymetz 💬 18:00, 7 October 2024 (UTC)Reply

I think that would also be us. There's already a task: T376021 that lists some problems and suggests turning it off as one possible solution. I think that's currently waiting on some decisions about the new login system (code name "SUL3", see T348388 for some details), which may either let us fix it instead of disabling it, or force us to disable it, depending on which approach we end up going with. Matma Rex talk 01:10, 10 October 2024 (UTC)Reply

After reading [2] and the post and ensuing discussion here, I don't think this browser extension is ready for article talk pace on en.wiki. I'm not exactly sure where to voice a concern about this, so please move this feedback if appropriate. @Chemipanda, Ita140188, and Avatar317: VQuakr (talk) 20:04, 3 October 2024 (UTC)Reply

@VQuakr Feedback should probably go to meta:Talk:Future_Audiences/Experiment:Add_a_Fact. --Ahecht (TALK
PAGE) 21:05, 3 October 2024 (UTC)Reply

That would be fine for feedback to them; I guess here I'm more looking to see if there's agreement this shouldn't be used on en.wiki yet. VQuakr (talk) 21:20, 3 October 2024 (UTC)Reply

@VQuakr For reference, here is a list of all the edits made using this tool: https://hashtags.wmcloud.org/?query=addafact&project=en.wikipedia.org&startdate=&enddate=&search_type=or&user= 86.23.109.101 (talk) 21:59, 3 October 2024 (UTC)Reply

That is a helpful link, thanks!! I glanced at ~10 random ones, and they all looked fine; They were a sentence directly copied from the source with the text listed in the quote parameter for the cite. Maybe Chemipanda didn't use it properly (highlighted the title) or is running an outdated browser version? Editors should at least look at their generated posts to see whether they are normal/valid/coherent and revert them if not; this tool is still experimental.

If this were to work as promised, I see this as more helpful than people simply posting new sources in the Talk pages. (which is always helpful). ---Avatar317^(talk) 22:39, 3 October 2024 (UTC)Reply

@Avatar317 Yes, Looking through the edits my impression is that most of them are fine.

According to the page on meta the person using the tool has to select which part of the source to use, so the "adding the title of a paper rather than it's content" is user error, rather than an issue with the tool. There is still the issue of using the wikipedia page in the citation template that needs to be investigated though. 86.23.109.101 (talk) 11:54, 4 October 2024 (UTC)Reply

I asked a developer and they suggested that the original error was likely due to the user switching browser-tabs while the extension is scanning the page. Quiddity (WMF) (talk) 00:38, 8 October 2024 (UTC)Reply

Thanks everyone for the insight and especially @Quiddity (WMF): for the follow up! VQuakr (talk) 04:44, 8 October 2024 (UTC)Reply

Not sure if here or the Help desk is the right place... Anyway, I've two questions, please:

1. Is there a way (e.g., a tool) to extract diffs without going through the page history?
2. When I click on the timestamp of a signature, I get a comment-specific link (e.g., [3]). I couldn't find any help pages about this kind of link. Is there a reason why we provide diffs instead of these comment-specific links, which seem much easier to obtain?

Thanks, Gitz (talk) (contribs) 09:56, 4 October 2024 (UTC)Reply

For your question 2, they are described at mw:Help:DiscussionTools § Talk pages permalinking. jlwoodwa (talk) 16:31, 4 October 2024 (UTC)Reply

The comment links are a fairly new feature, only enabled on English Wikipedia in June (T365974). I suspect many editors haven't warmed up to them yet. Diffs may also be used in some cases if you want to avoid ambiguity as to who wrote what, since anyone can technically edit anything on any page. Comment links are much more convenient for reading or commenting in the linked discussion though. Matma Rex talk 17:19, 4 October 2024 (UTC)Reply

By extract diffs you mean? Izno (talk) 18:28, 4 October 2024 (UTC)Reply

Thank you all for your helpful responses - I wasn't aware of that Help page. By "extract diffs" I meant accessing or generating the diffs directly from the talk page, without manually navigating through the page history. When I hover over the timestamp, I see a series of options ("actions", "popups") but none for getting the diff, so I was wondering if there's a tool or shortcut to generate one. Gitz (talk) (contribs) 20:02, 4 October 2024 (UTC)Reply

No, I don't think there's a tool like that. Izno (talk) 20:46, 4 October 2024 (UTC)Reply

Diffs between what, from what talk page? Please provide an example. Nardog (talk) 22:56, 4 October 2024 (UTC)Reply

I assume Gitz6666 means the diff in which that comment was written. jlwoodwa (talk) 23:00, 4 October 2024 (UTC)Reply

Yes, that's what I meant - a direct way for obtaining this [4] from this [5] without going through the page history. Gitz (talk) (contribs) 23:16, 4 October 2024 (UTC)Reply

Gitz6666, I think User:Alexander Davronov/HistoryHelper fits that bill. — Qwerfjkltalk 16:33, 5 October 2024 (UTC)Reply

Thank you. That tool is not exactly what I was looking for (you still need to go on the page history) but is amazing: very helpful indeed!

There's a minor issue though. It works perfectly for creating "special:diff/ links". Using it, I created this:

• [4 ott 2024, 23:16]

But if I try to create a {{diff2}}, I get this:

• ott 2024, 23:16 - «‎Diffs and comment-specific links: Reply»

which is {{diff|prev|1249444013|4 ott 2024, 23:16}} and doesn't work. I have to turn it into a {{diff2}} by adding a "2" and removing "prev", to get this:

• 4 ott 2024, 23:16 - «‎Diffs and comment-specific links: Reply»
  

which is {{diff2|1249444013|4 ott 2024, 23:16}} and works.

I ping @Alexander Davronov: with many thanks for the tool. Gitz (talk) (contribs) 18:34, 5 October 2024 (UTC)Reply

If you use a browser that supports Chrome or Firefox extensions, you can try the mw:Who Wrote That? browser extension. isaacl (talk) 23:28, 4 October 2024 (UTC)Reply

"WWT only works on article pages (not talk, user, or other pages)." Nardog (talk) 23:30, 4 October 2024 (UTC)Reply

Sorry; for some reason, the mention of signatures didn't make me think about non-article pages. isaacl (talk) 23:34, 4 October 2024 (UTC)Reply

There is the "WikiBlame" tool (which is linked on history pages under "External tools: Find addition/removal"): https://wikipedia.ramselehof.de/wikiblame.php?lang=en. For example, we can find the diff of your original post in this topic this way: [6] → [7]. Matma Rex talk 19:56, 5 October 2024 (UTC)Reply

By the way, the database behind the comment links includes the diff numbers of the revision that added the comment (see docs here), although only for comments that were posted since the comment links were enabled – we weren't able to process all historical revisions, it would have taken forever [I worked on this feature with the Editing team about a year ago]. So you could run a SQL query like this to look it up:

select min(itr_revision_id)  
from discussiontools_item_revisions  
left join discussiontools_item_ids on itr_itemid_id=itid_id  
where itid_itemid='c-Gitz6666-20241004095600-Diffs_and_comment-specific_links' 
and itr_transcludedfrom is null;

+----------------------+
| min(itr_revision_id) |
+----------------------+
|           1249323141 |
+----------------------+

…but we never got around to building a user interface for that (Special:FindComment only shows the latest revisions of pages containing the comment, not the oldest), and we also apparently never got around to setting up replication of those tables to the public replicas (although they could be replicated, as noted in T303295#7850298), so you can't even build a Toolforge tool to do it right now. These things could be done with a bit of effort, though… Matma Rex talk 20:30, 5 October 2024 (UTC)Reply

I havent used the community pool before so Im sorry if this isnt in the right village. mobile wikipedia starting today as for some reason started auto directing me to en.m.wikipedia.org instead of the regular en.wikipedia.org. even if i directly remove the ".m" or "m.", it will just autodirect to it again. I really hate it, and find it unbearable to use and love the regular english language wikipedia much more. I dont know what is causing this problem. I havent seen anyone discussing this on either the wikipedia subreddit (where usually any updates are discussed) or on Wikipedia:News. I greatly appreciate any help with this, thank you! 92.236.211.53 (talk) 13:55, 4 October 2024 (UTC)Reply

Use the "Desktop" link at the bottom of mobile pages to request the desktop version. PrimeHunter (talk) 14:00, 4 October 2024 (UTC)Reply

Thank you for your quick response! I already tried this and it unfortunately results in it providing the literal desktop version of the website, resulting in large amounts of negative space and awkward text placement next to images due to website trying to work for the horizontal mobile. the site worked perfectly for mobile prior. is this happening on your phone too? 92.236.211.53 (talk) 14:07, 4 October 2024 (UTC)Reply

im typing from desktop as i also learned today that my phone's ip (this same ip) was caught up in a rangeblock to block a specific user(but is now resolved?). i thought just now that this might be whats causing this but i just made account on mobile and it still autodirects to en.m.wikipedia. i have no idea what to do 92.236.211.53 (talk) 14:28, 4 October 2024 (UTC)Reply

Device name:Pixel 6a

Model:Pixel 6a

Android version:12

I wish this information perhaps helps in finding out how to reverse this. I sent this from my mobile. 92.236.211.53 (talk) 16:48, 4 October 2024 (UTC)Reply

The behavior you're experiencing is how it has always worked. The "workaround" Primehunter provided is working how it has always worked. There isn't a way to "fix it". The closest thing you can do is have an account, change the account's skin preference, and then use the "use desktop" link when you are logged in and end up on the mobile website. Perhaps this is sufficient for you. Izno (talk) 18:31, 4 October 2024 (UTC)Reply

I went back through screenshots I took and saw that you and Primehunter were right, it has always been "en.m.wikipedia". I think there's been an update to mobile Wikipedia's base, light colour scheme that caused the add-on I was using, darkreader to render it differently.

I do notice that the text on tables is larger, and colours are in my opinion not working well together either in the official dark mode or using my add-on on light mode.

Current, disliked Wikipedia (lightmode+darkreader) from today: https://imgur.com/a/wnNflgF

Correct Wikipedia, just darkmode with no add-ons, also today:https://imgur.com/a/4xdBsow

Previous mobile Wikipedia colour scheme (lightmode+darkreader), from 28th of April: https://imgur.com/a/up24a8G

Is there anyway to go back to how it was previously because I really do prefer how it was literally just yesterday? I'm sincerely sorry for the misunderstandings 92.236.211.53 (talk) 19:33, 4 October 2024 (UTC)Reply

What specifically do you dislike about the "current" version? Izno (talk) 00:09, 5 October 2024 (UTC)Reply

There is a higher contrast between the letters and the dark background, the purple that lists clicked-on links is a lighter purple so you have to strain your eyes more to discern it, the text on tables is larger than it needs to be while the text on the rest of the articles is currently still at their previous very good and readable size (shown in the imgur comparison linked above), and I dont get how that happened.

I dont know how else to describe it, but it looks like there is a white or blue filter over the articles that makes my eyes hurt. I can make another imgur comparison if that would help explain what im reffering to (just two image links this time tho). 92.236.211.53 (talk) 15:35, 6 October 2024 (UTC)Reply

If you create an account or add ?useskin=timeless, then the desktop version is more mobile friendly a bit. Gryllida (talk, e-mail) 07:29, 7 October 2024 (UTC)Reply

Ive made an account and it hasn't reverted the UI to how it previously was sorry.

?useskin=timeless is working very well thank you. It's a hassle to paste it to the URL for each new article I click on since it resets to the awful default on every new link or page loaded or when the editl is opened. Is there anyway to make it the default, since it will also be bad for when I'm reading with mobile data, having to load the site twice. Thank you very much regardless! 92.236.211.53 (talk) 20:11, 9 October 2024 (UTC)Reply

Yes. You can make it the default by creating an account, logging in with it, then going to your Preferences, and under "Appearance" select the Timeless skin, then Save. But that's what Izno told you five days ago. — JohnFromPinckney (talk / edits) 21:03, 9 October 2024 (UTC)Reply

I installed the script and all of its modules, is it safe or not? Electrou (formerly Susbush) (talk) 19:00, 4 October 2024 (UTC)Reply

You're responsible equally for all the edits made with automated tools, if that's what you're asking. You still have to check to make sure your edits are correct and not disruptive. Remsense ‥ 论 19:04, 4 October 2024 (UTC)Reply

The original poster is probably referring to the message that begins "Code that you insert on this page could contain malicious content capable of compromising your account ..." at MediaWiki:Userjsdangerous. To answer the original question, yes, it is safe. Graham87 (talk) 02:05, 5 October 2024 (UTC)Reply

You can never be sure of that about user scripts (hence the warning). AutoEd and its modules are in the Wikipedia namespace and protected, which means they can be compromised if any admin's account is compromised. Nardog (talk) 02:12, 5 October 2024 (UTC)Reply

Yes, but the message @Graham87 linked to ends, If you are unsure whether code you are adding to this page is safe, you can ask at the appropriate village pump., which is what directed the OP here.

It's kind of pointless to do that if the answer is always going to be, "Weeeelll... you can never be completely certain..." — that's not helpful. The user was already warned, and while it's true that you never can be completely certain, the AutoEd code is currently safe. And since it's used by many Wikipedians, it will screw over a much larger portion of the community than just @Electrou in the unlikely event that it becomes unsafe, so it's probably not worth personally fretting over. FeRDNYC (talk) 17:35, 8 October 2024 (UTC)Reply

Most scripts are either in the MediaWiki namespace where js pages can only be edited by interface administrators, or in userspace where they can only be edited by the user and interface administrators. AutoEd is in the Wikipedia namespace for some reason. The pages are fully protected but all administrators can edit them so it's less protected than most scripts. There are currently 847 administrators but only 10 interface administrators and it's a more trusted position. Apart from the risk of malice, ordinary administrators may also know less about JavaScript and security (including securing their account), and accidentally do something unsafe. PrimeHunter (talk) 20:46, 8 October 2024 (UTC)Reply

Hi. Is there somewhere I can ask about using string replacement features in templates? I've been trying things like

strip numbers: {{#invoke:string|replace|source={{{exotic}}}|pattern=%-%d%,|replace=HHH}}

And I've only been able to make very simple substitutions. I'm familiar with regex etc. I must be missing something fundamental. Thanks. Johnjbarton (talk) 20:22, 5 October 2024 (UTC)Reply

@Johnjbarton: You need |plain=false if you use regex. See Module:String#replace (gsub). PrimeHunter (talk) 20:31, 5 October 2024 (UTC)Reply

@PrimeHunter Thanks!

However something else is very weird. Here I copied some numbers from the 'edit' view in a wiki page:

strip literals copied: {{#invoke:string|replace|source=−4, −2, −1, 0, +1|pattern=%-%d%,|replace=HHH|plain=false}}

gives

strip literals copied: −4, −2, −1, 0, +1

But if I type the characters in:

strip literals typed: {{#invoke:string|replace|source=-4, -2, -1, 0, +1|pattern=%-%d%,|replace=HHH|plain=false}}

I get

strip literals typed: HHH HHH HHH 0, +1

These look the same to me, but somehow no match? I think this is related to my failure when using a parameter for the source. Johnjbarton (talk) 21:58, 5 October 2024 (UTC)Reply

@Johnjbarton: The string you copied has minus signs in accordance with Wikipedia:Manual of Style/Mathematics#Minus sign. You typed hyphens which is a different character. Some browsers match on both with a browser page search like Ctrl+f but Lua does not. PrimeHunter (talk) 22:11, 5 October 2024 (UTC)Reply

Thank you. That explains where my morning went ;-) Johnjbarton (talk) 22:14, 5 October 2024 (UTC)Reply

And one other issue I accidently discovered: AFAICT you can't match on <ref>...</ref> because the ref tag is somehow rendered to a <span>...</span> before the match. Johnjbarton (talk) 22:27, 5 October 2024 (UTC)Reply

Refs get mw:Strip markers and interact oddly with some features. Consider for example {{#invoke:string|replace|source=<ref>U</ref>|pattern=U|replace=V}} which produces: '"`VNIQ--ref-00000032-QINV`"'. Huh? The replacement doesn't work inside <ref>...</ref> but it does work on the strip marker where it changes UNIQ...QINU to VNIQ...QINV. This exposes the now incorrect strip marker. The reference still works in spite of this but there is no link to it. PrimeHunter (talk) 23:47, 5 October 2024 (UTC)Reply

Yes, I stumbled into that one too ;-) I found Template:Strip tags for giving the text other than the refs so I was trying to find a way to get the inverse function, just the content not the refs. I succeeded in part but my solution is not robust, too many ways to fail. I think now I will regroup and plan to edit the input data into a form that is easier to format with templates. Johnjbarton (talk) 00:16, 6 October 2024 (UTC)Reply

@PrimeHunter Can #invoke:string|replace be cascaded, that is input as source= for another #invoke:string|replace? Seems like that would just work, but my out call does not match, just passes through. My attempt: User:Johnjbarton/sandbox/Infobox element/symbol-to-oxidation-state-entry Johnjbarton (talk) 21:53, 6 October 2024 (UTC)Reply

@Johnjbarton: It works but you were missing a pipe.[8] There is also {{MultiReplace}}. PrimeHunter (talk) 22:19, 6 October 2024 (UTC)Reply

Lua patterns are not regex, they are closer to C string format patterns. Notably, no logical OR ((A|BC)) and no lookaheads/behinds. Izno (talk) 21:31, 5 October 2024 (UTC)Reply

There is problem in this list (section "Minimum wages by country" and "Minimum wages by country (other countries)") to sort data by "Net (EUR)" and "Net (PPP)". What to do? Eurohunter (talk) 15:07, 6 October 2024 (UTC)Reply

What is the problem? It seems to work for me. – Ammarpad (talk) 17:07, 6 October 2024 (UTC)Reply

@Eurohunter you have described everything BUT the 'problem'. Never assume that others are seeing or experiencing the same thing as you, and make full and extensive descriptions of the problem that you are encountering. —TheDJ (talk • contribs) 19:04, 6 October 2024 (UTC)Reply

@@Ammarpad: @TheDJ: Sort it by lowest or highest value, a few times. Eurohunter (talk) 20:35, 6 October 2024 (UTC)Reply

@Eurohunter: I did and see no issue. WHAT IS THE PROBLEM? It's hard to help when you refuse to reveal what you think is wrong. PrimeHunter (talk) 21:26, 6 October 2024 (UTC)Reply

The third click on EUR sort buttons takes you back to the initial sorting, which is a sorting by country name. It is not a bug, it is a feature. Uwappa (talk) 09:35, 7 October 2024 (UTC)Reply

@TheDJ: @PrimeHunter: @Uwappa: Looks like I was wrong, but just noticed it's impossible to sort by "Gross (EUR)". Eurohunter (talk) 16:55, 7 October 2024 (UTC)Reply

@Eurohunter: The "Gross (EUR)" column has an image before the number. You can for example use data-sort-value at Help:Sortable tables#Specifying a sort key for a cell. PrimeHunter (talk) 17:08, 7 October 2024 (UTC)Reply

The column header has the attribute data-sort-type="number" but the data cells in that column all begin with either {{steady}}, {{increase}} or {{decrease}}, none of which are numeric. --Redrose64 🌹 (talk) 18:21, 7 October 2024 (UTC)Reply

When I share a youtube video with a timestamp I get a link like this:

https://youtu.be/Zl8BIUx8QW0?feature=shared&t=1

but when I try to post that on wikipedia it says the link is on a spam blacklist. I can't find it on meta:Spam blacklist or on MediaWiki:Spam-blacklist.

And it wouldn't even make sense to block it anyway because I can change the link to:

https://www.youtube.com/watch?v=Zl8BIUx8QW0#t=1

and suddenly it is allowed. Polygnotus (talk) 21:24, 6 October 2024 (UTC)Reply

Shorteners are categorically rejected. This one is rejected at meta:Spam blacklist \byoutu\.be\b. Izno (talk) 21:29, 6 October 2024 (UTC)Reply

Thank you. The spam blacklist is intended to blacklist spam, and shouldn't be hijacked by people with an irrational hatred for url shorteners. Polygnotus (talk) 21:36, 6 October 2024 (UTC)Reply

URL shorteners are used to introduce spam, and aren't always particularly stable addresses, and they can lead to hijacked sites, which are much more dangerous than spam. These reasons for banning them are categorically rational, contrary to your hyperbole. No, they will remain banned. Whether specifically youtu.be should have an exception is perhaps a worthy question, but as you said, the expansion is trivial, so just use the full URL instead. Izno (talk) 21:48, 6 October 2024 (UTC)Reply

Yes. Shirley there Izno reason not to use the full URL. EEng 23:07, 7 October 2024 (UTC)Reply

@Izno: I know what URL shorteners are. This particular URL shortener cannot be used for malicious purposes because it only redirects to youtube. So it is obviously irrational to block all url shorteners. It is rational to block attack vectors while leaving domain aliases unblocked. This kinda stuff should be decided on a case-by-case basis (e.g. block bit.ly and tinyurl but not youtu.be). I can use the full url, but others do not know how to do that. Polygnotus (talk) 22:00, 6 October 2024 (UTC)Reply

If someone doesn't know what a URL is or how to copy and paste it, they definitely shouldn't be adding external links to articles. Thebiguglyalien (talk) 06:27, 7 October 2024 (UTC)Reply

@Thebiguglyalien: If someone says something truly ridiculous, it is often wise to re-read it in its context. Polygnotus (talk) 06:30, 7 October 2024 (UTC)Reply

URL shorterners are blacklisted for good reasons. They can be used to circumvent blacklisting of their target. MediaWiki:Spam-blacklist blacklists several specific videos at youtube.com, e.g. the entry \byoutube\.com\/watch\?v=W0a6L7hbD7U\b. We don't want spammers to use a youtu.be redirect instead. And there are other problems with URL shorternes, e.g. that they can be shut down and break all links. If you don't think YouTube's owner Google would do such a thing then think again. They are shutting down their URL Shortener goo.gl.[9] PrimeHunter (talk) 21:55, 6 October 2024 (UTC)Reply

Gotta love https://killedbygoogle.com/ Polygnotus (talk) 22:00, 6 October 2024 (UTC)Reply

I actually agree that youtu.be shouldn't be blacklisted. The solution to PrimeHunter's concern would be to just blacklist the string W0a6L7hbD7U instead - the blacklist doesn't have to point to the full URL. But despite being a Meta admin and thus having the technical power to action this I don't have the social power to do it myself. * Pppery * _{it has begun...} 02:26, 7 October 2024 (UTC)Reply

@Pppery: Thanks! The discussion continues at meta:Talk:Spam_blacklist#youtu.be. Another advantage of blocking W0a6L7hbD7U is that it would work for both the youtu.be/%id% and /watch?v=%id% format. Polygnotus (talk) 02:33, 7 October 2024 (UTC)Reply

The key point here, which was (indirectly) mentioned by the OP, is that https://youtu.be/video_id links are provided by YouTube itself directly from their UI whenever a "Share" link is requested for a video. They are, in a certain sense, even more of a permalink than the actual https://www.youtube.com/watch?v=video_id page they redirect to.

And while it's true Google could terminate support for https://youtu.be/ tomorrow, they could also redesign YouTube tomorrow so that the https://www.youtube.com/watch page is no longer functional, replaced by https://www.youtube.com/view or some other nonsense, which the https://youtu.be/ redirects get updated to point to.

Do I think that will happen? Absolutely not; I just think it's of equal unlikelihood (...ow) that anything will happen to https://youtu.be/, as that would break like a quarter of the entire frickin' internet.

The simple fact is, when requesting links to YouTube videos from YouTube itself, users are provided with https://youtu.be/ links, which IMHO we shouldn't make it unreasonably difficult to make use of.

Especially considering, if a user is viewing a video in the YouTube mobile app (which accounts for a very significant percentage of YouTube traffic, at a level that shames our own mobile app's laughable 2%-3% of monthly pageviews), the short URL is the only URL they can retrieve. The app doesn't expose https://www.youtube.com/watch?v=video_id URLs anywhere. FeRDNYC (talk) 18:03, 8 October 2024 (UTC)Reply

Linking to invidious instance could be better, it loads faster and does not track the user as much. Gryllida (talk, e-mail) 07:26, 7 October 2024 (UTC)Reply

See Principle of least astonishment. Polygnotus (talk) 07:28, 7 October 2024 (UTC)Reply

The two issues appear to be the general issue with url shorteners, and spamming of the shortened url.

Although this is a url shortener it's doesn't have the issues inherent in most shorteners. The only end point is a youtube video, so the usual concerns that it could link to anything do not apply here. Whether you use .com or .be you can't link to anything but a youtube video (correct me if that's wrong).

The spam issue is separate, and blacklisting individual videos is a poor option unless it's in a very particular situation. But the .com version could be spammed as well. I don't know how long ago the spamming and blacklisting were, but maybe unblacklisting as a test would be useful. If the past issues reappear it could be reapplied. I can see reasons why the .be link would be easier to spam, but beans. -- LCU ActivelyDisinterested «@» °∆t° 18:59, 8 October 2024 (UTC)Reply

While it doesn't directly - it does procedurally. In many use cases using the youtube "share button" generates a shortener that also includes a tracker, which we don't want. And 'someone else can go back and remove trackers later' isn't a strong argument - bad edits that can easily be avoided (by just using the actual link) are much more desirable. — xaosflux ^Talk 10:29, 10 October 2024 (UTC)Reply

@Xaosflux: In GDPR countries that tracking parameter is omitted. Polygnotus (talk) 10:37, 10 October 2024 (UTC)Reply

Sometimes sure, and in the rest of the world it's not. — xaosflux ^Talk 10:49, 10 October 2024 (UTC)Reply

I would propose to develop a mechanism to expand the shortened URL to its full form. For example, either

• write a bot that automatically expands certain short URL patterns upon user publishing an edit, and if the expanded URL hits the spam blacklist, revert the edit. There are already external Spam blacklist search tools [10]. Or,
• integrate the short URL expansion mechanism into MediaWiki, automatically expand shortened URLs upon publishing. If the expanded URL hits blacklist then disallow the edit.

MilkyDefer 08:23, 10 October 2024 (UTC)Reply

Oh great, it is in idea lab. MilkyDefer 08:29, 10 October 2024 (UTC)Reply

Link for those curious: Wikipedia:Village_pump_(idea_lab)#URL_expansion_bots Polygnotus (talk) 08:31, 10 October 2024 (UTC)Reply

Hello, does lua template have the capability to get information like

• page contributors
• last date of edit to page

for a provided page name? If so, please send me an example? Thank you. Gryllida (talk, e-mail) 07:23, 7 October 2024 (UTC)Reply

@Gryllida: You don't need Lua for the second one, it is available as a variable. If you only need the last contributor, that also is available in the same way. --Redrose64 🌹 (talk) 09:40, 7 October 2024 (UTC)Reply

Need this info for page and for page talk so I think variable will not work. Need a list of contributors not only last one. I can get this information using js but would prefer to avoid it. if possible. Thanks. Gryllida (talk, e-mail) 14:16, 7 October 2024 (UTC)Reply

Why do you think that a variable wouldn't work? Consider the article London - we can do this:

• {{REVISIONTIMESTAMP:London}} → 20241006081446

  {{#time: H:i, j F Y (e)|{{REVISIONTIMESTAMP:London}}}} → 08:14, 6 October 2024 (UTC)

• {{REVISIONTIMESTAMP:Talk:London}} → 20240908185015

  {{#time: H:i, j F Y (e)|{{REVISIONTIMESTAMP:Talk:London}}}} → 18:50, 8 September 2024 (UTC)

If either London or Talk:London get edited, the above examples will change when this page is next edited or WP:PURGEd. --Redrose64 🌹 (talk) 16:04, 7 October 2024 (UTC)Reply

This is fabulous Thanks. I will go try to use it in my template now. Just need the nicks of contributors now if possible. Gryllida (talk, e-mail) 22:59, 7 October 2024 (UTC)Reply

No, Lua (Scribunto) does not have access to page history. One option would be to have a bot periodically build a list of contributors and update a page somewhere that a module could read. Or, have a JavaScript gadget which can use the API. All that is tricky. Johnuniq (talk) 00:41, 8 October 2024 (UTC)Reply

Js is ok,I can write. I was hoping for Lua. Why not? Can it be implemented for Lua to have such access? Thanks for your insight. 🙂 Gryllida (talk, e-mail) 10:28, 8 October 2024 (UTC)Reply

Part of the answer to that question is likely something vaguely along the lines of, "just as we expect of all wikipedians, Scribunto is here to create an encyclopedia, and no part of that goal ever requires access to edit history."

(Which... is actually kind of true. There are plenty of behind-the-scenes tasks/goals that could benefit from page history access, but none of them would ever directly affect article content.) While there are plenty of conceivable ways in which it would be useful to have history access (or other functionality) in Scribunto, the focus has primarily been on providing functional equivalents to what's achievable with template coding, but without the template-coding nightmares involved in building any sort of complex logic.

Templates similarly have no access to page history.

Another factor is that the results of Module {{#invoke:}} calls, like template transclusions, are meant to be cacheable. 'Dynamic' code that relies on making an external resource query, meaning it potentially changes each time the module is invoked, is a bad fit with the caching model. Lua results should ideally be fairly static unless a dependency is edited or the code is invoked with different parameters.

Not to say that these things couldn't, potentially, be implemented. They just haven't been, and adding them would be a significant development effort, it's not a matter of flipping a switch or inserting a line of code somewhere. In fact there's a Phabricator tracking bug (T50176) for bugs requesting new Lua functionality — it's a long list. Things like MediaWiki API query access, access to Category lists, Namespace indexes, etc. are already there. It doesn't look like edit history access has ever been directly requested. (But API queries would provide one potential path, since page history info is accessible via the API.)

It's important to note that none of those requests are actively being worked on, though. They're just that: Requests. Unfulfilled requests, with no predicted timeline for completion beyond "...probably never?" FeRDNYC (talk) 21:52, 8 October 2024 (UTC)Reply

i wanted list of article authors to inquire about edit to the article, e.g. send @ pings on talk. Gryllida (talk, e-mail) 03:35, 9 October 2024 (UTC)Reply

Your best bet will be to use xtools to generate a list of people who edited the article by using this link: [11] NightWolf1223 <Howl at me•My hunts> 03:41, 9 October 2024 (UTC)Reply

How do I delete a section (blank entire section) from my personal user talk page? I used to do it with a script from times before the software upgraded to include new stuff (e.g. subscribe button, 'Latest comment: 22 minutes ago | 1 comment | 1 person in discussion' and the like. Gryllida (talk, e-mail) 07:46, 7 October 2024 (UTC)Reply

@Gryllida: Edit the section, click anywhere in the edit box, then do: Ctrl+A   ← Backspace   Alt+⇧ Shift+S. You can use Delete instead of ← Backspace if that's easier for you. --Redrose64 🌹 (talk) 09:45, 7 October 2024 (UTC)Reply

My script used to do it in one click. Gryllida (talk, e-mail) 14:14, 7 October 2024 (UTC)Reply

Do you mean that you want another archiving script? I use (a fork of) https://en.wikipedia.org/wiki/User:Elli/OneClickArchiver.js Note that it possible to disable that new stuff. Polygnotus (talk) 09:49, 7 October 2024 (UTC)Reply

Yes I will check it out thanks. Gryllida (talk, e-mail) 14:16, 7 October 2024 (UTC)Reply

Your script stopped working likely due to mw:Heading HTML changes. Nardog (talk) 14:43, 7 October 2024 (UTC)Reply

The parameter "associated_acts" doesn't work, see Orelsan. --BigBullfrog (talk) 08:19, 7 October 2024 (UTC)Reply

@BigBullfrog: Well, no, because it's deprecated to the point of removal. See Template talk:Infobox musical artist/Archive 16#Associated acts confusion and Category:Pages using infobox musical artist with associated acts. --Redrose64 🌹 (talk) 09:51, 7 October 2024 (UTC)Reply

Oh I see, thanks. --BigBullfrog (talk) 01:09, 8 October 2024 (UTC)Reply

How to make this table look like this one? I don't see any parameters which could be used. Eurohunter (talk) 20:52, 7 October 2024 (UTC)Reply

What do you mean "look like"? They look roughly the same to me, except for some styling applied by |namestyle=, |headingstyle=, |class=, and similar. – Jonesey95 (talk) 21:24, 7 October 2024 (UTC)Reply

I'm gonna dissent from @Jonesey95's claim as those boxes look pretty significantly different to me, but I agree it's mostly a question of styling, all of which is done by parameters that most assuredly are there and being used — most of what's involved in making Template:Politics of Yemen look more like Template:Politics of Uzbekistan would involve removing the ugly style nightmare that's been imposed on the former. Places I'd start:

• Lose the border: 1px double #8C959A from all of the style parameters where it's used (titlestyle, headingstyle, and listtitlestyle), because that just looks like trash.
• Just remove |style=border 4px double var(--background-color-inverted, #101418); completely. (What is this obsession with double-lined borders?)
• Use {{Politics sidebar title}} to set the |title= parameter, rather than hardcoding separate |title=, |image=, |namestyle=, |titlestyle=, etc. Specifically, you'd probably want this:

  |title={{Politics sidebar title|country=Yemen|image=Emblem of Yemen (2).svg|size=125px|title=Yemen}}
  

  replacing not only |title= itself but also those other three parameters.
• Consider getting rid of the |headingstyle= and |listtitlestyle= entirely, as well. Beyond the border styling, all they do is set specific (and ugly) color parameters that ruin the look of the sidebar because content boxes of unequal dimensions are revealed. That makes for a very "ransom-note" kind of effect where different-sized yellow rectangles and red rectangles are slapped all over the place.
• Finally, if you don't want the contents of each expandable heading to be presented as just a wrapped horizontal line of text, remove hlist from the |bodyclass= parameter, as that's what makes them format that way.
  (If you do that, you might consider using the {{hlist}} template to create horizontal lists out of some of the links in specific lists, like Template:Politics of Uzbekistan does in the |list6= contents.)

FeRDNYC (talk) 22:34, 8 October 2024 (UTC)Reply

My global.css appears to not be working on mobile web (Firefox Nightly on Android) all of a sudden - the changes just aren't applied. It works fine on desktop. Is this a known issue? Suntooooth, it/he (talk/contribs) 21:57, 7 October 2024 (UTC)Reply

Suntooooth, could you please test in non-nightly version of Firefox for Android? —⁠andrybak (talk) 09:01, 8 October 2024 (UTC)Reply

Just tried it, still not working. Suntooooth, it/he (talk/contribs) 13:30, 8 October 2024 (UTC)Reply

Something that may be related - there are also some icons in the interface that aren't showing up on mobile (Firefox Nightly and Firefox). The two I've noticed are the "watch" icon on pages I'm watching, and the red alert circle that displays in the top bar if there's notifications. Suntooooth, it/he (talk/contribs) 13:43, 8 October 2024 (UTC)Reply

The icon issue is being discussed at Wikipedia:Village pump (technical)#Watchlist icon issue on Mobile. See also phab:T376359, phab:T376414. —⁠andrybak (talk) 13:59, 8 October 2024 (UTC)Reply

Got it, thanks! :] Suntooooth, it/he (talk/contribs) 14:07, 8 October 2024 (UTC)Reply

MediaWiki message delivery 23:38, 7 October 2024 (UTC)Reply

This is not a new issue (see previous discussions here and here for example), and I don't frequent the technical pump often, but the extremely valuable Refill tool has been non-functional for months (years?). Any updates? And, if it's broken/abandoned for good, is there a similar tool that can quickly convert bare URLs into formatted citations, and/or combine duplicate citations? Furthermore, is there a clear list of handy editing tools somewhere on Wikipedia? I've been a regular editor for well over a decade, so if there is one, I've overlooked or forgotten about it. There are a lot of problems on Wikipedia: prioritizing tools, and making them easily visible to editors who don't have a computer science degree, should be a top priority. Cheers, --Animalparty! (talk) 00:29, 8 October 2024 (UTC)Reply

https://refill.toolforge.org/ng for some reason. – Muboshgu (talk) 00:39, 8 October 2024 (UTC)Reply

I use reFill2 and something called RefRenamer but I don't know the link. Johnjbarton (talk) 00:42, 8 October 2024 (UTC)Reply

User:Nardog/RefRenamer? Polygnotus (talk) 01:58, 8 October 2024 (UTC)Reply

I'm trying to add https://commons.wikimedia.org/wiki/Data:Coconino_National_Forest.map to Coconino National Forest but it is unclear to me how to do so. I tried:

| image_map       = {{maplink-road|from=Coconino National Forest.map}}

But it's not showing up. I also tried to delete the old `map` entry and then adding this:

| map       = {{maplink-road|from=Coconino National Forest.map}}

But that got me this error:

Lua error in Module:Location_map at line 526: "?'\"`UNIQ--mapframe-0000000E-QINU`\"'?" is not a valid name for a location map definition.

Any ideas? TerraFrost (talk) 10:35, 8 October 2024 (UTC)Reply

I previously struggled with a maplink situation where the answer was to wait a few days for Kartographer to sort itself out. CMD (talk) 12:32, 8 October 2024 (UTC)Reply

The template's documentation suggests using embedded=. The map probably still needs a caption, but it's in the article. – Jonesey95 (talk) 14:31, 8 October 2024 (UTC)Reply

It looks like someone tweaked the CSS for the sticky table headers — which can be enabled with the fourth checkbox at Special:Preferences#mw-htmlform-gadget-section-test — so that (if your browser also satisfies a @media screen and (min-width: 1000px) media query) it applies a top: 3.125rem offset to table headers when one is stickied, to prevent the sticky header from either covering or sliding under the also-sticky TOC button.

Nice idea, in theory. Problem is, on pages containing nested and/or short tables that don't exceed the height of the screen, the stickiness can kick in at unexpected times, particularly when there are multiple tables. And when that happens, all of the tables' headers jump down a distance of 3.125rem, potentially covering their first data row.

I first noticed this at Module:Sports results, in the documentation. The "What it looks like" areas of those docs all contain short tables. If you have the sticky headers gadget enabled, then no matter where you scroll on that page, each table's header row will be shoved down to cover the first data row below it.

That's a problem, as it obscures content, and the only way to make it visible is to defeat the CSS rule applying top: 3.125rem. FeRDNYC (talk) 16:16, 8 October 2024 (UTC)Reply

Actually, it looks like this only affects nested tables, and it may be sufficient to augment the existing CSS rule:

@media screen and (min-width: 1000px) {
  .skin-vector-2022.vector-sticky-header-visible .jquery-tablesorter > thead,
  .skin-vector-2022.vector-sticky-header-visible .mw-sticky-header > thead {
    top: 3.125rem;
  }
}

with a second one overriding the offset in nested tables:

@media screen and (min-width: 1000px) {
  .skin-vector-2022.vector-sticky-header-visible .jquery-tablesorter .jquery-tablesorter > thead,
  .skin-vector-2022.vector-sticky-header-visible .jquery-tablesorter .mw-sticky-header > thead,
  .skin-vector-2022.vector-sticky-header-visible .mw-sticky-header .mw-sticky-header > thead,
  .skin-vector-2022.vector-sticky-header-visible .mw-sticky-header .jquery-tablesorter > thead {
    top: 0;
  }
}

FeRDNYC (talk) 16:57, 8 October 2024 (UTC)Reply

...Smaller issue, the nested table headings then end up passing on top of the sticky outer table headers when they cross, instead of underneath them. Looks like some z-index tweaking might also be needed. FeRDNYC (talk) 17:01, 8 October 2024 (UTC)Reply

Ohh, now I see. The offset isn't to avoid the floating TOC button, but rather the full-width version of the .vector-sticky-header. But the weird thing is, that CSS doesn't kick in until @media screen and (min-width: 1120px), so there's this weird 120px limbo range of browser widths where the table headings are ducking under nothing at all. FeRDNYC (talk) 22:53, 8 October 2024 (UTC)Reply

Those values change sometimes. I'll make an edit request. —TheDJ (talk • contribs) 08:16, 9 October 2024 (UTC)Reply

@TheDJ Nice, thanks!

The nested table issue is still a problem, though, whether the breakpoints are synced up or not. When a table's sticky-header activates and the top: 3.125rem; offset kicks in for its header rows, the header rows of all tables nested inside that table will also move down to obscure their own content, unless the offset is defeated for nested tables with something like my second CSS block above. FeRDNYC (talk) 09:18, 9 October 2024 (UTC)Reply

Yes, this is almost impossible to bypass. Sticky headers are relative to their scrolling context. So every time you introduce a new scrolling context (as done here at Module:Sports_results#L-277), you have to cancel out the offset of the main context. This is part of the reason why the sticky headers are not the default behavior. It is not really possible to make it work predictably in any and all contexts right now. If you want to override this specific situation, you need to make an override for this gadget's behavior in Module:Sports_results/styles.css. —TheDJ (talk • contribs) 11:11, 9 October 2024 (UTC)Reply

Just got the following error message dropping three See-alsos from a Draft, in this edit:

Database error
To avoid creating high replication lag, this transaction was aborted because the write duration (5.3958411216736) exceeded the 3 second limit. If you are changing many items at once, try doing multiple smaller operations instead.

[bf82d77e-9cdf-4b96-a5b2-5ac9cab8969a] 2024-10-03 15:00:40: Fatal exception of type "Wikimedia\Rdbms\DBTransactionSizeError"

The edit seems to have gone through fine, despite the message. Could this happen if I inadvertently hit Publish twice or something? I don't have any recollection of doing so, and I really don't know what happened. Everything is fine on my end, I don't need any action, just reporting this in case it's a first sign of something going on that needs to be watched. Mathglot (talk) 15:11, 3 October 2024 (UTC)Reply

*I unarchived this to reply*. @Mathglot: Sorry I didn't see this earlier, but your description reminded me of a recurring (possible) bug affecting the abusefilter - I checked and it does seem like your edit is related: your edit triggered the monitoring filter 9 times separately from the edit.

I'm unsure how active @Suffusion of Yellow is, the testing filter ("possible abusefilter bug") was added to help debug things from Wikipedia:Edit_filter_noticeboard/Archive_12#Filter_1253:_False_positive_ratio, where @ToBeFree created phab:T348237, about it.

I'm just noting this here, and pinging, in case either this Database error helps with the phab-reported abuse filter problem (or the other way around). – 2804:F14:80E1:2001:2DF4:42B2:8C4D:C416 (talk) 18:22, 8 October 2024 (UTC)Reply

Thanks for the ping and Mathglot for the report – I have now added this as a comment to the year-old task. ~ ToBeFree (talk) 19:44, 8 October 2024 (UTC)Reply

Over the past few weeks I've been occasionally getting logged out unexpectedly, despite ticking the "remember me" option every time. Most recently it's happened twice in the past ~24 hours. It always happens when I've been idle for a while, but only on the order of hours not days. I'm not aware that I've changed any of my settings recently. Thryduulf (talk) 20:15, 8 October 2024 (UTC)Reply

Me too. I believe there is a phab ticket covering this issue. Let me go find it real quick NightWolf1223 <Howl at me•My hunts> 20:55, 8 October 2024 (UTC)Reply

I've had the same issue for a week or so, I just rather lazily assumed it would get fixed at some point. -- LCU ActivelyDisinterested «@» °∆t° 21:08, 8 October 2024 (UTC)Reply

Probably the same problem as T372702. Matma Rex talk 16:16, 9 October 2024 (UTC)Reply

I don't know if this sequence of actions has a trigger in it.

1. explicitly log out on one machine (this invalidates all login cookies on all devices)
2. log in to en.wp on a different device, selecting "Keep me logged in (for up to one year)". I now have a fresh new login cookie
3. Microsoft informs me that updates require installation, so I finish what I am doing ...
4. ... close Firefox, go for "Start"→"Power"→"Update and restart", wait an age. Make coffee. Clear a pile of snailmail. Open Firefox ...
5. ... and back to my watchlist. One edit adds an image to an article, which I am suspicious about, so:
6. visit Commons. It says I am not logged in and should reload the page. In my experience, this never works, but following a different commons link does; so I go to the page history. I am now shown as logged in.
7. Still on Commons, I follow a link to en.wp - I am not logged in
8. Return to commons, visit another page, still logged in
9. go to Meta - I am logged in there
10. try en.wp again - not logged in

Why might en.wp stop recognising my login cookie when commons and meta are perfectly happy with it? --Redrose64 🌹 (talk) 20:17, 9 October 2024 (UTC)Reply

Not getting automatically logged in on some wikis sounds like some sort of anti-tracking protection in your browser. Commons and Meta share the same parent domain with login.wikimedia.org where the central session cookie is stored so browser restrictions on cross-wiki cookie access are more relaxed.

Does clicking on the login link at the top of the page on enwiki help? That should work in Firefox. Tgr (WMF) (talk) 18:26, 10 October 2024 (UTC)Reply

@Tgr (WMF): I think you missed something - my proper login (asking me to enter name and password) was on English Wikipedia. When I went to Commons and logged in there, I became logged out on Wikipedia, but remained logged in on Commons. --Redrose64 🌹 (talk) 20:16, 10 October 2024 (UTC)Reply

Yeah the logged out part is the bug Matma Rex linked. I'm just saying Commons and Meta login being more "sticky" on some browsers is expected - your enwiki session somehow went missing, your central session on login.wikimedia.org remained, and then other wikimedia.org wikis can recover the session from there but wikis on other domains can't. Tgr (WMF) (talk) 21:31, 10 October 2024 (UTC)Reply

OK it's not random but it is replicable:

1. On en.wp, log in (full login using Special:UserLogin, with Username/Password)
2. Click this link: commons: - observe that you are logged in
3. Use the browser's "back" button to return to en.wp
4. Press F5 to reload the page - observe that you are not logged in
5. Click this link: commons: - observe that you are still logged in at Commons

This also causes loss of session data and more than one lost edit. --Redrose64 🌹 (talk) 21:54, 10 October 2024 (UTC)Reply

The message "This is an old revision of this page" or "This is the current revision of this page" at the top of a permalink has the cdx-message--warning class but is not styled unless the skin is Vector 2022 (example). Is there a Phab task for this? Nardog (talk) 06:26, 9 October 2024 (UTC)Reply

There were several tasks about missing warning box styling in various places, but I don't think there was a task about this particular one. Please file it. :) Matma Rex talk 16:15, 9 October 2024 (UTC)Reply

@Matma Rex: Done. Please add appropriate tags; I didn't file it earlier mainly because I didn't know what tags to use. Nardog (talk) 23:06, 9 October 2024 (UTC)Reply

As I am climbing the bumpy learning curve for templates I hit another road block. This code (with extra double curlies on the outside) evaluates when I use Special:ExpandTemplates but just sits there in a page like this:

• {{
• common:−4, +4,
  
• notable:−3,^[1] −2,^[1] −1,^[1] +1,^[1] +2,^[1] +3,^[1]
  
• predicted:
  }}

My goal was to have a database layer accept the name of a formatter and a selector, then return a template with that formatter and the selected data. It works in ExpandTemplates, but where it counts. Any hints? (^[1])

Johnjbarton (talk) 21:43, 9 October 2024 (UTC)Reply

Oh, I unchecked Remove comments on the ExpandTemplates and the result is different. Still in the dark though. Johnjbarton (talk) 21:51, 9 October 2024 (UTC)Reply

This is a known, and annoying, but in ExpandTemplates, which half-parses the text and then parses it fully. How the ordinary parser works is that if a template outputs wikitext that wikitext doesn't get parsed again. If you really want to run through the parser multiple times you can use {{expand wikitext}}, so {{expand wikitext|{{ {{User:Johnjbarton/sandbox/Infobox element/symbol-to-oxidation-state-data|os-formatter=User:Johnjbarton/sandbox/Infobox element/symbol-to-oxidation-state-echo|symbol=C}} }} -> (example removed since template changes made it obsolete). While I've done that in the past it's kind of hacky. You also need to put a space between the two sets of curly brackets, or else the parser gets confused. {{{{1}}}} is parsed as { {{{1}}} } (take the value of a parameter and wrap it in curly brackets), not {{ {{1}} }} (evaluate Template:1 and then evaluate the result of it as the name of another template). * Pppery * _{it has begun...} 22:22, 9 October 2024 (UTC)Reply

Also if you were to put the opening curly braces in User:Johnjbarton/sandbox/Infobox element/symbol-to-oxidation-state-data itself, then that would work. (this is similar to how {{country data United States}}) et al. work. * Pppery * _{it has begun...} 22:36, 9 October 2024 (UTC)Reply

Ok great thanks! These are the kinds of things I need to learn:

• "How the ordinary parser works is that if a template outputs wikitext that wikitext doesn't get parsed again."

I was able to base my prototype on {{country data United States}} by changing the design of the "data". This kind of system is much easier to use with good examples. Johnjbarton (talk) 02:39, 10 October 2024 (UTC)Reply

You're welcome. Also, I misspoke - a better way of phrasing it is "How the ordinary parser works is that if a template outputs template calls those template calls don't get parsed again" - other wikitext like wikilinks, refs, etc. is of course parsed. There's a very long manual on how the parser works at mw:Help:Template and even more stuff at mw:Manual:Advanced templates if you want to really enter the weeds. * Pppery * _{it has begun...} 04:51, 10 October 2024 (UTC)Reply

Something I've been thinking about:

A lot of new people don't seem to see talkpage messages. The cause is not really important here; it may be a case of banner blindness, or our (mobile) interface is not clear enough, or whatever.

Would it be a good idea to implement a special message notification, perhaps one that:

• is hard to ignore
• can perhaps only be sent by an admin
• requires confirmation of receipt to dismiss (so it is on every page you visit until you click a button)
• takes up most if not all of the screen
• would still appear on the talkpage as a normal message so others can see them as well
• comes with a short explanation that someone is trying to reach them, translated in many languages

To prevent abuse in case of hijacked admin accounts we could restrict each message to only one recipient, and limit the amount you can send to 1 per minute. And perhaps it should only be possible to send such messages to people who are not extendedconfirmed. To prevent people receiving too many of these messages, perhaps limit them to, for example, 1 per hour per recipient.

Ideally those You may be blocked from editing without further warning the next time you... warnings would be sent via this alternative method of talkpage notification.

A potential downside is that its, in some cases, easier to give someone WP:ROPE and then not have to deal with them for the duration of their block.

I think that at least some people keep doing what they are doing, without ever noticing a growing list of messages on their talkpage of people trying to steer them in the right direction. Has such a feature been considered?

Polygnotus (talk) 02:51, 10 October 2024 (UTC)Reply

I was setting up the article at Gábor_Bálint and wanted to add the "category:Hungarian linguists" and it did not work because that category does not exist. I finally found "category:Linguists from Hungary" and I usually do not like this inconsistency (and especially do not see why American and English are special nationalities) so I added {{Category redirect|Linguists from Hungary}} at the wrong category. Now hot cat usually uses that and helpfully replaces the category if I typed "Hungarian linguists". Strangely hot cat does not seem to work at all today and the visual editor for categories does not have this automatic feature to suggest preferred category names. Perhaps someone knows a better way of explaining this or adding a suggestion for the right people. PS:hot cat now working!! Shyamal (talk) 12:48, 10 October 2024 (UTC)Reply

I added a new section using the "*" tab with this edit: https://en.wikipedia.org/w/index.php?title=Talk:Fishing_cat&curid=7607570&diff=1250477244&oldid=1250369650

The new section is included within the closed discussion. I might be able to fix it in this case, but it seems to be a bug.  —  Jts1882 | talk  19:03, 10 October 2024 (UTC)Reply

It's not really a bug; the person who closed the GA review section forgot to match their {{atop}} template with an {{abot}} template, which means the "close" box didn't end. I've fixed it. Writ Keeper ⚇♔ 19:10, 10 October 2024 (UTC)Reply

Thank-you. I knew there was a problem but couldn't identify it. It's too easy to cast blame on bugs.  —  Jts1882 | talk  19:18, 10 October 2024 (UTC)Reply

There appears to be a problem with {{cite web}} and related templates on some pages - see, for example, Beroidae, where all the references display "Lua error in Module:Citation/CS1/Configuration at line 2083: attempt to index a boolean value." rather than the reference. The references are displayed correctly in preview mode, with no template errors shown in the editor. I'm using Firefox with the Monobook skin. Tevildo (talk) 22:25, 10 October 2024 (UTC)Reply

I WP:NULLEDITed the page and the error went away. No idea of the cause. * Pppery * _{it has begun...} 22:35, 10 October 2024 (UTC)Reply

I need to create a series of ref tags from wikitext with refs. I'll settle for a very specific pattern of text removed. I tried things like: {{#invoke:string|replace|source=−4,<ref name="cn"/> −2,<ref name="cn"/>|pattern=[−+]%d,<.-><|replace=<|plain=false}} but the left angle bracket never matches. I think the match is being performed on a source or pattern after it has been converted to Help:strip markers. Thus the angle bracket is not in the source during the match. Is there a way around this? Johnjbarton (talk) 23:15, 10 October 2024 (UTC)Reply