Jump to content

Wikipedia:Village pump (technical)

From Wikipedia, the free encyclopedia

This is an old revision of this page, as edited by 49.144.202.0 (talk) at 03:19, 26 December 2022 (→Search bar doesn't always lead directly to the searched page). The present address (URL) is a permanent link to this revision, which may differ significantly from the current revision.

 Policy Technical Proposals Idea lab WMF Miscellaneous 
Shortcuts
The technical section of the village pump is used to discuss technical issues about Wikipedia. Bug reports and feature requests should be made in Phabricator (see how to report a bug). Bugs with security implications should be reported differently (see how to report security bugs).

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.

Logged out upon switching languages

Recently I noticed when switching to another language on Wiki that I get automatically logged out, which is tedious when editing an article for an international subject and checking translations. This happens across browsers, and I believe my account should be unified. Wiki also seems to think my IP is hundreds of miles away when logged out (it shows an IP ban message), but I'm not using a VPN. Anyone else noticing this or know what is happening? Thanks. - Indefensible (talk) 19:06, 18 December 2022 (UTC)[reply]

This is follow-up to Help talk:Logging in#Logged out upon switching languages? I believe that the reply Logged out to my question When you return to the Wiki that you started out from - presumably English Wikipedia - are you logged in or not? is significant. In my experience I often appear to be logged out when I go to Commons:, Meta: etc. but upon retuen to English Wikipedia, I'm still logged in. --Redrose64 🌹 (talk) 22:47, 18 December 2022 (UTC)[reply]
Problem seems to have resolved itself somehow. - Indefensible (talk) 21:31, 20 December 2022 (UTC)[reply]
Mostly resolved but not 100%, happens again intermittently. - Indefensible (talk) 22:55, 24 December 2022 (UTC)[reply]

Search bar doesn't always lead directly to the searched page

For at least a year (if my memory serves me right), I've noticed that if I leave a page "untouched" in my browser for a few minutes or so, then type another article's title in the search box, it wouldn't go directly to that article, but instead to the search results page with a big banner reading "There is a page called xxx". It doesn't happen all the time, but when it does, backing to the previous page and re-searching would fix it, although sometimes I have to reload the previous page in order for it to work. It happens both on my Mac running High Sierra and my iPad running iOS 10. 2001:4453:5C6:CB00:FD89:3263:7361:56DF (talk) 10:29, 19 December 2022 (UTC)[reply]

What do you do to submit the search? Do you press Return while the focus is on the textbox, click on the search button, click on a suggestion entry, or something else? And you're using Vector legacy, correct? Nardog (talk) 05:15, 20 December 2022 (UTC)[reply]
Sorry just saw this now. I press Return on both devices. Both use Vector Legacy. 49.144.202.0 (talk) 03:18, 26 December 2022 (UTC)[reply]
I can confirm that this happens to me too on desktop site on Android. Sometimes it goes to the Special:Search page for that search term and sometimes directly to the relevant page in an unpredictable pattern. I did not really notice the "length of time page is untouched" but it could be a factor in play. —CX Zoom[he/him] (let's talk • {C•X}) 17:48, 20 December 2022 (UTC)[reply]
Same questions as above. Nardog (talk) 23:17, 20 December 2022 (UTC)[reply]
I almost exclusively, input something in the textbox and hit enter from keyboard to search. On Vector legacy skin. —CX Zoom[he/him] (let's talk • {C•X}) 08:53, 21 December 2022 (UTC)[reply]
Where is your mouse pointer located when you hit enter? I've noticed that the search suggestion under the pointer is selected when I press "enter" rather than the literal and exact search term I just typed in. If I move the pointer out of the danger zone so it's not pointing to any suggestions, then press enter, it works OK. Elizium23 (talk) 05:27, 24 December 2022 (UTC)[reply]
Hi, since its desktop site on Android, it doesn't have a pointer. Just that the search system doesn't have consistent result when used, due to whatever reasons. —CX Zoom[he/him] (let's talk • {C•X}) 07:05, 24 December 2022 (UTC)[reply]
the OP said it's on a Mac running High Sierra and iOS. Elizium23 (talk) 01:31, 25 December 2022 (UTC)[reply]

Tech News: 2022-51

Latest tech news from the Wikimedia technical community. Please tell other users about these changes. Not all changes will affect you. Translations are available.

Tech News

  • Because of the holidays the next issue of Tech News will be sent out on 9 January 2023.

Recent changes

  • On a user's contributions page, you can filter it for edits with a tag like 'reverted'. Now, you can also filter for all edits that are not tagged like that. This was part of a Community Wishlist 2022 request. [1]
  • A new function has been used for gadget developers to add content underneath the title on article pages. This is considered a stable API that should work across all skins. Documentation is available. [2]
  • One of our test wikis is now being served from a new infrastructure powered by Kubernetes (read more). More Wikis will switch to this new infrastructure in early 2023. Please test and let us know of any issues. [3]

Problems

  • Last week, all wikis had no edit access for 9 minutes. This was caused by a database problem. [4]

Changes later this week

  • There is no new MediaWiki version this week or next week.
  • The word "Reply" is very short in some languages, such as Arabic ("ردّ"). This makes the Discussion tools button on talk pages difficult to use. An arrow icon will be added to those languages. This will only be visible to editors who have the Beta Feature turned on. [5] [6]

Future changes

  • Edits can be automatically "tagged" by the system software or the Edit filter configuration system. Those tags link to a help page about the tags. Soon they will also link to Recent Changes to let you see other edits tagged this way. This was a Community Wishlist 2022 request. [7]
  • The Trust & Safety tools team have shared new plans for building the Private Incident Reporting System. The system will make it easier for editors to ask for help if they are harassed or abused.
  • Realtime Preview for Wikitext is coming out of beta as an enabled feature for every user of the 2010 Wikitext editor in the week of January 9, 2023. It will be available to use via the toolbar in the 2010 Wikitext editor. The feature was the 4th most popular wish of the Community Wishlist Survey 2021.

Events

Tech news prepared by Tech News writers and posted by bot • Contribute • Translate • Get help • Give feedback • Subscribe or unsubscribe.

MediaWiki message delivery 23:58, 19 December 2022 (UTC)[reply]

We should probably prep some changes for Help:Show preview before that time, to take this new preview into account. —TheDJ (talk • contribs) 14:59, 21 December 2022 (UTC)[reply]

Template-generated categories that don't exist, re-redux

Pursuant to Wikipedia:Village_pump_(technical)/Archive_201#Template-generated_categories_that_don't_exist,_redux, {{Infobox NRHP}} is now autogenerating the equally invalid Category:Historic district contributing properties in United States New Orleans East due to the recent addition of "nrhp_type=cp" to various infoboxes. As usual, however, nonexistent categories can't stay on pages, so it has to be either created or removed, but it can't be created as "X in United States [City]" is not an appropriate naming format for a category of this type -- and, as usual, WP:TEMPLATECAT explicitly deprecates using templates to autogenerate nonexistent categories. So, again, this category-generating function has to be stripped from the infobox. Bearcat (talk) 02:13, 21 December 2022 (UTC)[reply]

{{Infobox NRHP}} accepts |nocat=yes. There is an old discussion at Template talk:Infobox NRHP/Archive 4#Categorisation. PrimeHunter (talk) 03:15, 21 December 2022 (UTC)[reply]
That doesn't fix the core problem. Izno (talk) 03:40, 21 December 2022 (UTC)[reply]
I shouldn't have to go in and add code to the infobox to make redlinked categories go away — the infobox isn't supposed to be making any redlinked categories for anybody to have to fix in the first place. Bearcat (talk) 05:50, 21 December 2022 (UTC)[reply]
Jonesey95 didn't want to remove non-existing categories at the linked discussion. As a compromise, maybe the infobox could additionally add a maintenance category like Category:NRHP infobox adding non-existing category or use the existing Category:NRHP infobox needing cleanup. Then notify Wikipedia:WikiProject National Register of Historic Places that if nobody monitors it to fix the pages quickly then the infobox will be coded to stop adding non-existing categories. PrimeHunter (talk) 10:19, 21 December 2022 (UTC)[reply]

Gradient sigs

Hello! I'm attempting to create a signature for a user and I'm wanting to do a color gradient. Only issue is, I don't know how to create a color gradient without a crap ton of color tags which would quickly eat up the 255 character limit. Anyone know how? ― Blaze WolfTalkBlaze Wolf#6545 03:53, 21 December 2022 (UTC)[reply]

This was doubly difficult for me, as I wanted two gradients, but after some experimenting I came up with something, although I ultimately decided not to use it as my regular signature. Here's the code for the first half: [[User:Mandarax|<span style="color:white;background:linear-gradient(90deg,blue,red)">M<small>ANdARAX</small></span>]] MANdARAX • XAЯAbИAM 04:13, 21 December 2022 (UTC)[reply]
That works! Thanks! ― Blaze WolfTalkBlaze Wolf#6545 04:29, 21 December 2022 (UTC)[reply]
You're welcome. Also, since you probably only need one gradient, you could go with something more complex, such as [[User:Mandarax|<span style="color:white;background:linear-gradient(90deg,red,orange,yellow,green,blue,purple)">M<small>ANdARAX</small></span>]]. MANdARAX 04:36, 21 December 2022 (UTC)[reply]
Gradients are hard to get accessible. If you really feel you must use or provide one for others to use, MDN is a good start. Izno (talk) 04:36, 21 December 2022 (UTC)[reply]
Ew reading[Joke]Would using 2 colors that are on complete opposite sides of the color spectrum be enough to make it accessible? ― Blaze WolfTalkBlaze Wolf#6545 04:40, 21 December 2022 (UTC)[reply]
"Opposite" colors is what makes it hard. Try finding a text color that can be placed against a gradient from black to white along the whole spectrum of that color range (good luck). OTOH, you can maybe find something between, say, purple and red (it's likely just white), or yellow and green (probably just black, depending on how dark a green). Izno (talk) 04:51, 21 December 2022 (UTC)[reply]
Ah ok. The user requested either tech blue or red on a black background, so I figured why not make it a gradient. ― Blaze WolfTalkBlaze Wolf#6545 15:34, 21 December 2022 (UTC)[reply]
I am an editor and administrator who works on Wikipedia 99% of the time on Android smartphones using the desktop site on my phone. To be honest, I simply do not understand why editors choose to use signatures that other editors cannot read or have trouble reading. Garish signatures that draw attention to me-me-me. I dislike signatures where the lower half is visible but the upper half is invisible to me. Or any other bizarre signature flourishes that are hard to read across multiple platforms. It is as if John Hancock had thrown his quill pen to the floor and signed his name to the Declaration of Independence using a lump of charcoal that he pulled out of a fireplace, making zigeddy zaggedy marks, instead of creating a beautiful signature that everyone can read and remember 250 years later. What's up with that affectation? Cullen328 (talk) 05:07, 21 December 2022 (UTC)[reply]
Ppl feel awfully attached to standing out. As an admin and also afterwards, I've asked ppl to adapt their sigs and make them more accessible to others, but ppl don't give a flying f about it. This includes enough senior editors and fellow admins that I could not effectively enforce such polices back then. —TheDJ (talk • contribs) 09:52, 21 December 2022 (UTC)[reply]
My eyes are bleeding!! -Roxy the dog 17:11, 21 December 2022 (UTC)[reply]
Although I don't actually use the above signatures (except in this thread), I don't generally object to others using such sigs unless they're particularly obnoxious or difficult to read. MANdARAX • XAЯAbИAM 23:01, 21 December 2022 (UTC)[reply]
They are difficult to read, that's why people (including myself) object. Legoktm (talk) 23:22, 21 December 2022 (UTC)[reply]
I'm sure I read a while back that the (then) new and upcoming talk page software wouldn't be able to do text effect sigs due to a technical limitation, meaning everyone would have to have a normal plain text sig. What ever happened to that software update? - X201 (talk) 15:47, 22 December 2022 (UTC)[reply]
Most people hated it, and Wikipedia:Flow was uninstalled after a few trials. Some other WMF wikis (especially technical ones) still use it. —Kusma (talk) 16:21, 22 December 2022 (UTC)[reply]

I'm thinking of adopting this one as my new signature, tell me what you think:

 BD2412🌈🌠🚀  B.D.2412  BD2412 BD2412
B D 2 4 1 2 ! !
(talk)

15:21, 22 December 2022 (UTC)

First class. Well done. -Roxy the dog 15:56, 22 December 2022 (UTC)[reply]
Well, it certainly has a gradient. Certes (talk) 16:29, 22 December 2022 (UTC)[reply]
That slope is divine, isn't it. Izno (talk) 18:02, 22 December 2022 (UTC)[reply]
It's fine, except for the part with blue text on a golden background; I would definitely lose that part. ;-) MANdARAX • XAЯAbИAM 19:36, 22 December 2022 (UTC)[reply]
Strong oppose, but only because the reply tool doesn't work with it. Fix that and you're good. — MusikAnimal talk 20:25, 22 December 2022 (UTC)[reply]
@Mandarax and MusikAnimal: Thanks, I will take your comments into consideration. BD2412 T 16:07, 23 December 2022 (UTC)[reply]
No. It uses a table, and tables are block elements, and I'm pretty sure that block elements are forbidden in sigs. --Redrose64 🌹 (talk) 19:48, 23 December 2022 (UTC)[reply]
It was a joke. ― Blaze WolfTalkBlaze Wolf#6545 20:04, 23 December 2022 (UTC)[reply]
Woosh! Izno (talk) 20:16, 23 December 2022 (UTC)[reply]
Also, tables are flat, not gradients. SpinningSpark 18:05, 24 December 2022 (UTC)[reply]

WikiProject-wise edits

Would anyone be interested in creating a tool which displays user edits according to WikiProject (for example, "you've made 10 edits to WikiProject Plants, 5 edits to WikiProject Spiders, etc."). FacetsOfNonStickPans (talk) 09:40, 22 December 2022 (UTC)[reply]

This kind of already exists, see Wikipedia:WikiProject Directory. For example, Wikipedia:WikiProject Directory/Description/WikiProject Video games. Izno (talk) 17:24, 22 December 2022 (UTC)[reply]

Anyone else finding Chrome using huge amounts of memory when watchlists added?

This just started a week ago. Doug Weller talk 14:44, 22 December 2022 (UTC)[reply]

It continues. I've wiped out my old profile for Chrome and created a clean version, gotten rid of almost all extensions. 18 tabs including 3 watchlists and I'm at almost 7000 mb. Doug Weller talk 14:01, 23 December 2022 (UTC)[reply]

Plainlist now removed from Common.css

As a heads up, I've removed plainlist from Common.css to TemplateStyles. See MediaWiki talk:Common.css#Plainlist removed for more info. Izno (talk) 18:02, 22 December 2022 (UTC)[reply]

Wow, now I think I know why plainlist and other related templates when imported to other Wikimedia projects showed unexpected results even when all template dependencies were imported simultaneously. Probably because the sitewide css was never imported alongside? —CX Zoom[he/him] (let's talk • {C•X}) 07:11, 24 December 2022 (UTC)[reply]
Yes, "why don't my X look right" is a common support question. Izno (talk) 07:29, 24 December 2022 (UTC)[reply]

Unable to use VE

Moved from Wikipedia:Administrators' noticeboard/Incidents#Unable to use VE

Hello, I am unable to to use visual editor for creating or editing article, i have done the preference setting and all what i know to make it work but its not working out and the source editor is hard for me.

Kindly help me out please QDJ22 (talk) 02:39, 23 December 2022 (UTC)[reply]

@QDJ22: not really the best place for this question (I'd recommend somewhere like WP:VPT), but while you're here — does this link open the visual editor on WP:SANDBOX? — TheresNoTime (talk • they/them) 02:57, 23 December 2022 (UTC)[reply]
ohh i dont know, its still the same thing on the sandbox QDJ22 (talk) 03:08, 23 December 2022 (UTC)[reply]
@QDJ22: Odd.. do you see any errors? — TheresNoTime (talk • they/them) 03:12, 23 December 2022 (UTC)[reply]
no it will show edit beside edit source and after loading finish, it wont be there again QDJ22 (talk) 06:44, 23 December 2022 (UTC)[reply]
@QDJ22: What web browser and operating system are you using? Can you try loading it in a different web browser? Do you have javascript enabled? --Chris 05:37, 23 December 2022 (UTC)[reply]
i am using mozilla firefox and using dell pc, i dont know about the javascript that you mentioned and also its visual that i am using to respond now but not working for article QDJ22 (talk) 06:47, 23 December 2022 (UTC)[reply]
@QDJ22 what version of Firefox are you using? Go to this page, WP:MYIP, if you click the button do you see an IP address? (Don't tell us what it is.) — xaosflux Talk 20:13, 24 December 2022 (UTC)[reply]
I think the Firefox version is version 108.0.1 and its shows up to date, i can see my IP address too QDJ22 (talk) 20:49, 24 December 2022 (UTC)[reply]

Unable to delete a file after moving to Commons

Tracked in Phabricator
Task T244567

Attempting to delete File:KKNO logo.jpg (after having exported the file to Commons with Commons Helper) returns: Error deleting file: An unknown error occurred in storage backend "local-multiwrite".

Any thoughts on how to solve this? BD2412 T 20:47, 23 December 2022 (UTC)[reply]

Looks like this is being worked on in phab:T244567. — xaosflux Talk 22:59, 23 December 2022 (UTC)[reply]

"undo" seems to be restoring as well

These three edits by one user [8][9][10] were reverted by another user (in reverse order) [11][12][13]. This should have resulted in all three edits being reverted but it didn't. Each revert in addition restored the previous revert. So only the final revert had any lasting effect. SpinningSpark 20:56, 23 December 2022 (UTC)[reply]

Maybe Doug Weller clicked undo at all three edits before saving any of the three reverts. That would give a result like that when MediaWiki tries to undo the specific changes in an old edit without touching other parts of the page as it looked when the user clicked undo. PrimeHunter (talk) 21:59, 23 December 2022 (UTC)[reply]
Huh? Can you walk me through that. If you don't save the undo then nothing gets reverted and there would not be an entry in the page history at all. SpinningSpark 17:58, 24 December 2022 (UTC)[reply]
I meant that maybe he first clicked undo at all three edits and then he saved all three after the third undo click. PrimeHunter (talk) 23:28, 24 December 2022 (UTC)[reply]

Watchlist error

Why I see in my watchlist few entries like:

‎Removed [pl] alias: Główny teatr działań wojennych is related to theater of war (Q718893) so why is this messed with items above? Eurohunter (talk) 10:25, 24 December 2022 (UTC)[reply]

You will need to ask the Wikidata developers. We aren't responsible for or knowledgeable about why watchlist integration works with Wikidata the way it does. Izno (talk) 17:19, 24 December 2022 (UTC)[reply]
Those pages refer to Q718893 using {{label|Q718893}}, so changes to that item are listed in your watchlist if you're watching the pages. Matma Rex talk 19:51, 24 December 2022 (UTC)[reply]

Articles read - year long stats

Hello! Is there a way to see which articles were the most read during this year? Maybe a method to compile a list of the 10 most read articles or so? - Klein Muçi (talk) 10:27, 24 December 2022 (UTC)[reply]

on january 1st, this page should be able to https://pageviews.wmcloud.org/topviews/?project=en.wikipedia.org&platform=all-access&date=last-year —TheDJ (talk • contribs) 12:17, 24 December 2022 (UTC)[reply]
Usually needs a day or two more than the day after, but yes. Izno (talk) 17:19, 24 December 2022 (UTC)[reply]
Izno, @TheDJ, thank you! — Klein Muçi (talk) 12:15, 25 December 2022 (UTC)[reply]

How to print a parser function result after publishing the change?

Hi, is it possible to print (not render) a parser function result after publishing the change? For example, just an example, I want to insert {{#ifeq:{{Title year|page={{PAGENAME}}}}|2024|Yes|No}} into Brazil at the 2024 Summer Olympics and after publishing and revisiting the content page, I just see "Yes" as plain text, which is the result, instead of the whole code I provided above. If you still need more explanation, I will do it. Thanks! ⇒ AramTalk 21:33, 24 December 2022 (UTC)[reply]

Assuming that you want to hardcode whatever result the parser function is giving at the moment, just use {{subst:#ifeq:{{Title year|page={{PAGENAME}}}}|2024|Yes|No}}. Notice the addition of subst: before #ifeq:. This will hardcode yes into the page and the parser function will be gone. See Help:Substitution for details. —CX Zoom[he/him] (let's talk • {C•X}) 22:15, 24 December 2022 (UTC)[reply]
I think Aram wants the source text to have the full code now but automatically transform at a later date to replace the code with "Yes" in the source text without making a new edit. That is not possible. Source text can only change when a page is edited. As far as I know we don't have a bot which can be asked to make a certain edit like a substitution when a condition is met in the future. It would sometimes be handy to automatically make the source text cleaner when a condition is met and is expected or certain to hold permanently, e.g. automatically avoiding an ifexist test after a specific target page has been created. Pages can be deleted so this use case would be expected to hold and not certain. PrimeHunter (talk) 23:52, 24 December 2022 (UTC)[reply]
@Aram, for what purpose? — Qwerfjkltalk 09:13, 25 December 2022 (UTC)[reply]
@PrimeHunter: Actually, @CX Zoom: hit my target 95% with his arrow. But what I don't understand is why the result is always "No"! It should be "Yes" on Brazil at the 2024 Summer Olympics. @Qwerfjkl: We want to create too many articles around "Nation at the YEAR Summer Olympics" using Pywikibot script and for the purpose of past and present verbs (such as: "was" for those years before 2022 and "is" for those years after 2022) should be printed. And we can probably use it for many other purposes. ⇒ AramTalk 13:35, 25 December 2022 (UTC)[reply]
The substitution issue could be something that PrimeHunter could be able to help with. See Wikipedia:Village pump (technical)/Archive 200#Template substitution brings a visually different result from expected. —CX Zoom[he/him] (let's talk • {C•X}) 14:45, 25 December 2022 (UTC) per Certes below. —CX Zoom[he/him] (let's talk • {C•X}) 15:11, 25 December 2022 (UTC)[reply]
You may need a subst: within the inner braces too, e.g. {{subst:#ifeq:{{subst:Title year|page={{subst:PAGENAME}}}}|2024|Yes|No}}. Certes (talk) 14:55, 25 December 2022 (UTC)[reply]
For your specific use case, I believe, {{subst:#ifexpr:{{subst:Title year}} < 2022 |was|is}} would be an easier code. Works only if the title has some year, or else returns error. < will be for "less than" and <= will be for "less than or equal to" depending on your requirement. —CX Zoom[he/him] (let's talk • {C•X}) 15:20, 25 December 2022 (UTC)[reply]
@Certes: Thank you so much for your reply and that was very useful to hit the target 100%!
@CX Zoom: Thank you very much. Yes, your last code is a better idea and gave me the same result perfectly!
That is why English community is a good place for technical purposes. I will appreciate all your replies! ⇒ AramTalk 15:54, 25 December 2022 (UTC)[reply]
As others show, you have to subst all parser functions and template calls (and invoked modules if you use that). Any called templates must themselves have code to subst any parser functions, templates and modules they call. It's annoying. {{Title year}} has the required subst code but many templates don't. Recursive substitution was requested in phab:T4777 in 2005. Special:ExpandTemplates does it but cannot be used in wikitext. PrimeHunter (talk) 16:05, 25 December 2022 (UTC)[reply]
I'm so sorry for rementioning you again, @CX Zoom:, @Certes: and @PrimeHunter:. Because of the difference in number format, I modified the code slightly to {{subst:#ifexpr:{{subst:formatnum:{{subst:Title year}}|R}} < {{subst:formatnum:2022|R}} | true | false }}, but I don't know why it produces Expression error: Unknown character "{" on ckbwiki. I tried it on Persian Wikipedia and it produced what I expected. Is there a problem with the ckbwiki system? ⇒ AramTalk 18:13, 25 December 2022 (UTC)[reply]
As I said, any called templates must themselves have code to subst any parser functions, templates and modules they call. Template:Title year added it in 2021.[14] ckb:Template:Title year hasn't added it. PrimeHunter (talk) 18:35, 25 December 2022 (UTC)[reply]
There are complicated instructions at Help:Substitution#Recursive substitution. Simplified advice (something like this should probably be added near the beginning there): Try inserting {{{|safesubst:}}} right after every {{ which isn't part of a triple {{{, and see if it works. PrimeHunter (talk) 18:44, 25 December 2022 (UTC)[reply]
@PrimeHunter: Oh, I didn't think the problem might be with the Template:Title year on ckb. It worked! Thank you again! ⇒ AramTalk 19:06, 25 December 2022 (UTC)[reply]
@PrimeHunter, templates like {{expand wikitext}} can do this. — Qwerfjkltalk 20:09, 25 December 2022 (UTC)[reply]
@Qwerfjkl: How? Consider e.g. {{str number|1234abc}} which renders as 4. Special:ExpandTemplates shows the recursive expansion is simply the string "4". Can you do something in wikitext which saves the string "4"? {{subst:expand wikitext|{{str number|1234abc}}}} saves {{#invoke:Expand wikitext|main|{{str number|1234abc}}|unstrip=}}. PrimeHunter (talk) 02:46, 26 December 2022 (UTC)[reply]

TemplateStyles question

In css, . is for element class, # is for element id. What is @ for? —CX Zoom[he/him] (let's talk • {C•X}) 09:00, 25 December 2022 (UTC)[reply]

@CX Zoom, do you mean at-rules? — Qwerfjkltalk 09:17, 25 December 2022 (UTC)[reply]
@Qwerfjkl: Yep this is it, but I do not exactly understand what it is and what it does (even after reading that link) :( —CX Zoom[he/him] (let's talk • {C•X}) 11:23, 25 December 2022 (UTC)[reply]
@CX Zoom on-wiki you are most likely to run across such as @media. See here, these can apply different rules depending on what the client (the browser) says it is using or is capable of. We don't use a lot of these, but you can see ones such as @media screen in use at MediaWiki:Common.css. — xaosflux Talk 12:22, 25 December 2022 (UTC)[reply]
So, basically @media checks the size of viewport and adds some conditional css. Is it correct? —CX Zoom[he/him] (let's talk • {C•X}) 12:35, 25 December 2022 (UTC)[reply]
The @media ... { ... } construct does much more than check the size of a viewport. Basically, it is used to test the characteristics of the user agent (browser, etc.) and only apply the enclosed CSS rules when the test is satisfied. These tests are primarily the type of device - screen, print, etc. but may also be more complex tests, such as the available display width - see Media Queries Level 3 for a full description.
For example, at meta:User:Redrose64/monobook.css, I use @media print { ... } so that two rules (one to hide an infobox and certain other boxes, the other to set a font for the text) are only applied when I print a page, they are ignored when viewing the page on screen, and would also be ignored if I used screen-reader software to speak the page to me. MediaWiki:Common.css has two instances of @media screen { ,,, } and the enclosed rules primarily relate to the backgrounds of galleries, to be displayed on screen but ignored when printed.
Neither of these example stylesheets tests the screen width, however. If you can link an actual example, we can explain it more fully. --Redrose64 🦌 (talk) 16:19, 25 December 2022 (UTC)[reply]
The most common use in TemplateStyles is like in Module:Side box/styles.css, where minimum width is tested to account for mobile. Izno (talk) 16:53, 25 December 2022 (UTC)[reply]
Good. So, in this example, CX Zoom, there are two @media at-rules - the first one, @media (min-width: 500px) { ... } applies two rules only when the display width is 500px or more; the second one, @media (min-width: 720px) { ... } applies three rules only when the display width is 720px or more (in addition to the two rules applied by the first at-rule). See min-width. --Redrose64 🦌 (talk) 18:08, 25 December 2022 (UTC)[reply]
@CX Zoom not exactly. @media is a set of rules, and a client will choose to execute them or not, if it supports that extension, based on if it thinks it meets the condition. @media rules can be things like viewport size, device size, orientation, resolution. — xaosflux Talk 16:23, 25 December 2022 (UTC)[reply]
keyframes for animation is probably the other one, such as User:Chrs/bouncy.css (yes, I stumbled on that a couple weeks ago, kind of amazing). Izno (talk) 16:59, 25 December 2022 (UTC)[reply]

Make PrefixIndex list all pages

We can transclude Special:PrefixIndex on a page using the code {{Special:PrefixIndex/Wikipedia:Village pump}}, but it has a maximum limit of pages that are shown. We can remove redirects by |hideredirects=1 & strip prefixes by |stripprefix=1 but how do we transclude all the pages and not just the first few? Thanks! —CX Zoom[he/him] (let's talk • {C•X}) 09:18, 25 December 2022 (UTC)[reply]

You can't, because it would be problematic from a performance perspective if someone did like {{Special:PrefixIndex/S}} and it tried to list the 1.4 million matching titles. Anomie⚔ 12:00, 25 December 2022 (UTC)[reply]
Can it be done using multiple transclusions, each of which returns only 100 or so results. For example, transclusion 1 returns first 100 results, for transclusion 2 we put something like |startfrom=101 resulting in listing of pages 101-200 and so on? —CX Zoom[he/him] (let's talk • {C•X}) 12:26, 25 December 2022 (UTC)[reply]
Help:Transclusion#Special pages says "URL parameters can be given like template parameters". This means you can start from a given page name with |from=Village pump (policy)/Archive 117. I don't know whether you can start from a specified page number or specified number of times to click "Next page" at Special:PrefixIndex/Wikipedia:Village pump. The first "Next page" currently produces https://en.wikipedia.org/enwiki/w/index.php?title=Special:PrefixIndex&from=Village_pump_%28policy%29%2FArchive_117&prefix=Village+pump&namespace=4. In that url, from=pagename is the only indication of where to start so I doubt it's possible. PrimeHunter (talk) 15:48, 25 December 2022 (UTC)[reply]
It is a string match, so Archive 1, Archive 10, Archive 100, Archive 11, ... Archive 2, etc would come out. — xaosflux Talk 22:08, 25 December 2022 (UTC)[reply]

Font Readability

I am among the many millions of Babyboomers whose once excellent vision has declined with age. I have been using Wiki and making modest cash contributions since it began because I think Wiki is a fabulous idea.

I have accessed Wiki with many different devices and browsers over the years, but for many years now, I found it absolutely necessary to magnify the text.

If I just need a small amount of information, I can enlarge the entire screen's content and read the left side of a sentence, shift the screen to the right, then read the right side of the sentence, then shift the screen to the left and read the left side of the next sentence, then the right, etc..

If I want to do the deeper research that Wiki so skillfully enables then I have to remember where I left my reading glasses.

Wouldn't it be wonderful if I could simply select the font size as a preference and allow a word wrap function to automattically adjust text to my visual capacity when I log in? Boomerspop (talk) 12:52, 25 December 2022 (UTC)[reply]

@Boomerspop: In my browser (Chrome on MacOS), I can increase font size with cmd-+. I'm sure your browser has a similar option. Alternatively, you can use a custom CSS file (Special:MyPage/skin.css) to change font and font size. (I use a prettier font for Wikipedia, for example). See Help:User style for some information (possibly not enough if you are like me and don't speak CSS). —Kusma (talk) 13:04, 25 December 2022 (UTC)[reply]
Thanks for taking the time to reply to my ridiculous post. smh
I have routinely used that function for many years. It appears that in addition to the decline in my visual acuity, there has been a profound decline in my memory and cognitive acuity.
Wow. I expect that I will now spend a significant amount of time pondering that change.
Although it's quite sad, my personal problems are trivial in comparison to the much larger and very real problems of the world. Boomerspop (talk) 13:51, 25 December 2022 (UTC)[reply]
Or, for a solution affecting all applications (and available in multiple OSs), open your display/screen/monitor settings, and set your monitor to a lower resolution; this will automatically enlarge everything (probably) that is shown onscreen, while keeping the default windows and margins within the screen boundaries (so no side-scrolling). -- Verbarson  talkedits 23:01, 25 December 2022 (UTC)[reply]

Stop Nagging Me For Money

Stop nagging Me for Money! Wikkipedia is now a very annoying site begging for money several times on each page. I could see once per session but every f-ing page and several times on each page? Give me a f**king break! I bet my posts will be in violation of something or other on Wikkipedia but i don't care! At this point I don't care if I can never use Wikkipedia again as long as they know these nags are driving users away! Buggeroff22 (talk) 19:23, 25 December 2022 (UTC)[reply]

Now you've created an account you can switch fundraising banners off in Special:Preferences. Nthep (talk) 19:29, 25 December 2022 (UTC)[reply]
I don't believe logged-in users even need to switch fundraising banners off; as far as I know they aren't been shown to logged-in users. isaacl (talk) 21:46, 25 December 2022 (UTC)[reply]
^-- this. The most recent campaign should only be showing to non-logged in users. There are a bunch of reasons why when a page loads it could think someone isn't logged in though. — xaosflux Talk 22:05, 25 December 2022 (UTC)[reply]
@Buggeroff22: The banners are added by the Wikimedia Foundation, who receive any donations from them, rather than by Wikipedia's unpaid volunteers. Certes (talk) 21:11, 25 December 2022 (UTC)[reply]
How nice to learn I can block fund-raising banners in preferences! The fund-raising banners aren't showing today, but they were decidedly showing recently. And yes I was logged in, but I didn't know about the banner preferences. -- M.boli (talk) 21:58, 25 December 2022 (UTC)[reply]
Retrieved from "https://en.wikipedia.org/enwiki/w/index.php?title=Wikipedia:Village_pump_(technical)&oldid=1129568834"