Wikipedia:Village pump (technical)

Jump to navigation Jump to search
 Policy Technical Proposals Idea lab WMF Miscellaneous 
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).

Newcomers to the technical village pump are encouraged to read these guidelines prior to posting here. 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.

Frequently asked questions (FAQ) (see also: Wikipedia:FAQ/Technical)
Click "[show]" next to each point to see more details.
If something looks wrong, purge the server's cache, then bypass your browser's cache.
This tends to solve most issues, including improper display of images, user-preferences not loading, and old versions of pages being shown.
No, we will not use JavaScript to set focus on the search box.
This would interfere with usability, accessibility, keyboard navigation and standard forms. See task 3864. There is an accesskey property on it (default to accesskey="f" in English). Logged-in users can set a gadget in their preferences.
No, we will not add a spell-checker, or spell-checking bot.
You can use a web browser such as Firefox, which has a spell checker.
If you have problems making your fancy signature work, check Wikipedia:How to fix your signature.
If you changed to another skin and cannot change back, use this link.
Alternatively, you can press Tab until the "Save" button is highlighted, and press Enter. Using Mozilla Firefox also seems to solve the problem.
If an image thumbnail is not showing, try purging its image description page.
If the image is from Wikimedia Commons, you might have to purge there too. If it doesn't work, try again before doing anything else. Some ad blockers, proxies, or firewalls block URLs containing /ad/ or ending in common executable suffixes. This can cause some images or articles to not appear.
For server or network status, please see Wikimedia Metrics. If you cannot reach Wikipedia services see Reporting a connectivity issue
« Archives, 169, 170, 171, 172, 173, 174, 175, 176, 177, 178, 179, 180, 181, 182, 183, 184, 185, 186, 187, 188, 189


Accessing Wikidata references as plain text[edit]

I would like to access the properties stated in and/or reference URL as a string. The intent is to use this type of references as a switch in Template:Chembox CASNo/format to decide whether the CAS number is linked to the CAS Common Chemistry database. Not all CAS numbers have an entry in that database. --Leyo 11:12, 22 April 2021 (UTC)

@RexxS, Pppery, and Thayts: Could you possibly help in this matter? --Leyo 19:15, 25 April 2021 (UTC)
@Leyo: I can say that Module:Wd does not support this, but the best I can come up with is to check whether the property has a reference or not like this:
{{#if: {{wd|property|sourced|Q42750891|P231}} | {{wd|property|sourced|linked|Q42750891|P231}} | {{wd|property|Q42750891|P231}} }}5471-63-6
I hope this helps nevertheless. Thayts ••• 22:30, 30 April 2021 (UTC)
@Thayts: Thank you for your reply. Unfortunately, it needs to be checked if there is a reference to the CAS Common Chemistry database. If not, there would be a dead link (see e.g. ALC-03152036272-55-4) that needs to be suppressed.
Would it be very difficult to expand a module or to create a new one that is able to access each element in the corresponding item? --Leyo 23:25, 2 May 2021 (UTC)
I looked for different test cases to play around a little:
  1. CAS RN: WP = WD; WD ref: Common Chemisty → 1,3-diphenylisobenzofuran (Q42750891)
  2. CAS RN: WP = WD; WD ref: other → 4,5-dichloro-1,2,3-dithiazol-1-ium chloride (Q27251702)
  3. CAS RN: WP = WD; WD ref: Common Chemisty + other → alectinib (Q21099132)
  4. CAS RN: WP = WD; WD ref: none → tozinameran (Q97154240), lugdunin (Q26156270) (has imported from)
  5. CAS RN: WP ≠ WD; WD ref: Common Chemisty → zeatin (Q2276562)
  6. CAS RN: WP ≠ WD; WD ref: other →
  7. CAS RN: WP ≠ WD; WD ref: Common Chemisty + other → Brigatinib (Q4653190)
  8. CAS RN: WP ≠ WD; WD ref: none → 1-propionyl-lysergic acid diethylamide (Q21096201) (no CAS RN in WD at all)
Based on the results, I used adapted versions of the code provided by Thayts above to omit the dead links to the CAS Common Chemistry database, at least for the chemicals that do not have a referenced CAS number in their WD item (cases 4 and 8). However, also for the case 2 on one hand, as well as for cases 5, 6 and 7 on the other hand, there shouldn't be such a link. Any help on how to achieve this is still greatly welcomed. --Leyo 21:39, 5 May 2021 (UTC)

Bot to update archive configurations?[edit]

I recently moved State v. Chauvin to Trial of Derek Chauvin after closing a requested move. Several days after the move, I noticed that a thread was incorrectly archived to Talk:State v. Chauvin/Archive 3 rather than Talk:Trial of Derek Chauvin/Archive 3 because the |archive= parameter of {{User:MiszaBot/config}} was still set to Talk:State v. Chauvin/Archive %(counter)d. I needed to manually update the archive configuration to prevent that from happening again. Has there ever been any discussion about a bot to update archive configurations after page moves in order to prevent this from happening? Another workaround would be to specify Talk:{{BASEPAGENAME}}/Archive %(counter)d}} rather than specific page names like Talk:State v. Chauvin/Archive %(counter)d, but I'm not sure all editors would do that consistently. – Lord Bolingbroke (talk) 18:49, 1 May 2021 (UTC)

Then that's a bug in OneClickArchiver. The script creator is no longer with Wikipedia, so I advise not using that script at all. {{User:MiszaBot/config}} is for the configuration of lowercase sigmabot III (talk · contribs), which is the designated successor of the MiszaBot family. --Redrose64 🌹 (talk) 19:33, 1 May 2021 (UTC)
@Redrose64: OneClickArchiver's documentation says that "this script uses a page's MiszaBot configuration (see User:MiszaBot/config) to determine the archive page", so I don't think it's a bug with the script. Regardless, the same issue would arise when a bot archives a page if the |archive= parameter isn't updated like I described above. I was trying to get an idea of whether a bot could update that parameter after page moves, or whether we would need to rely on editors manually updating the parameter. – Lord Bolingbroke (talk) 19:52, 1 May 2021 (UTC)
No, the same issue will not arise: if the portion of the |archive= parameter before the final slash isn't an exact case-sensitive match for the page where {{User:MiszaBot/config}} is used, lowercase sigmabot III simply refuses to archive the page. See User:Lowercase sigmabot III/Archive HowTo#Parameters explained. This is an anti-vandalism measure, since if someone alters |archive= to a value that is not sensible, you don't want archives ending up in unexpected places.
It is the responsibility of the person who moves a page to move any subpages as well as performing any post-move cleanup. --Redrose64 🌹 (talk) 20:39, 1 May 2021 (UTC)
Thanks, I missed that part of the documentation. I will certainly make sure to update the archive configurations going forward. Still not sure what was going on with OneClickArchiver though; it would probably be worthwhile for someone more technically proficient than me to look into it since it is such a widely used script. – Lord Bolingbroke (talk) 20:53, 1 May 2021 (UTC)
Category:Pages where archive parameter is not a subpage was created in January but hasn't been fully cleared of old errors yet. A page move sometimes fails to move existing archives so a bot or script shouldn't update the parameter automatically, or ignore it. It was discussed at Wikipedia:Bot requests/Archive 81#Make archive bots assume standard naming. PrimeHunter (talk) 10:32, 2 May 2021 (UTC)
Thanks PrimeHunter, this answers my question. – Lord Bolingbroke (talk) 04:07, 3 May 2021 (UTC)

Left-justified elements in mobile infoboxes[edit]

I have noticed that certain multimedia elements are left-justified on mobile versions of infoboxes. For example, check out the mobile versions of our articles for London ([1]; see the imagemap in the infobox) and La Marsillaise ([2]; see the embedded ogg). I am not sure how related these problems are, but I think they should be patched so there is centering, like on the desktop versions. — Goszei (talk) 19:40, 1 May 2021 (UTC)

I have ameliorated the London example with <div style="display:inline-block;">. Not sure if that's a good idea, but it works. — Goszei (talk) 00:00, 5 May 2021 (UTC)

Wikipedia:WikiProject Tropical cyclones/Tracks[edit]

So, I've been attempting to run the script mentioned in Wikipedia:WikiProject Tropical cyclones/Tracks to perhaps solve this issue but it doesn't seem to work no matter what. I think it's because it has too many unexplained dependencies. Is it possible to list exactly what is needed (download links or so) or perhaps to rewrite it so that it doesn't require that many dependencies. I don't think a mapmaker script should need this many other things. Jo-Jo Eumerus (talk) 10:38, 2 May 2021 (UTC)

What do you mean by "too many unexplained dependencies"? Those mentioned in Wikipedia:WikiProject_Tropical_cyclones/Tracks#Prerequisites doesn't seem like many (of course, they have dependencies of their own, if you need to install them separately). MarMi wiki (talk) 16:36, 2 May 2021 (UTC)
Well, I think it's because that's a lot of dependencies for a program that puts icons into images. And no versions given for most of them. I guess what I am really asking about is whether someone can write a script that does all that without needing as many other programs. Jo-Jo Eumerus (talk) 09:05, 3 May 2021 (UTC)

Search on "bar" does not find "foo:bar"[edit]

A search on "bar" does not find "foo:bar" with a colon. Is that new? It's unfortunate with our use of namespace colons. For example, the archive search at top of this page on "wikiproject romania" [3] does not find the link Wikipedia talk:WikiProject Romania at Wikipedia:Village pump (technical)/Archive 188#Category:Castles in Iran. It is found on a search for "wikipedia talk:wikiproject romania" [4] or "talk:wikiproject romania" [5]. phab:T125487 says a similar issue was resolved in 2016. insource:"wikiproject romania" [6] does work. PrimeHunter (talk) 10:59, 2 May 2021 (UTC)

To be clear, this is not about finding the page "foo:bar". It's about finding the string "foo:bar" if it's present in a page which is searched for "bar". PrimeHunter (talk) 12:18, 2 May 2021 (UTC)
Some test cases:
Wikipedia talk0:WikiProject Romania0.
Wikipedia talk1:WikiProject Romania1.
Wikipedia talk2:WikiProject Romania2.
Wikipedia talk:WikiProject Romania3. MarMi wiki (talk) 17:00, 2 May 2021 (UTC)
MarMi wiki, I don't know the answer to your question, but I know how to find the answer, which is almost as good :-) The MediaWiki search team has office hours the first Wednesday of every month, which lucky for you is in a couple of days. More information on the Wikimedia Search Platform team page.
When you find the answer, please report back here, so others can benefit from your new-found knowledge. -- RoySmith (talk) 01:16, 3 May 2021 (UTC)
There wasn't any question, just couple of test cases (sorry for the spam it caused in page history).
Results: if the part before : is a valid namespace, part after : won't be found - even if it's in a plain text. MarMi wiki (talk) 16:18, 3 May 2021 (UTC)

When using mobile view, the article creation wizard preload does not work[edit]

(was: People can't create a new article on English Wikipedia)

Hi Wikipedia!

People can't create a new article on English Wikipedia. It doesn't appear the page that contains the link "Start the article wizard" but appears: The page x doesn't exist. You can create as a draft..."

We want to return the option for article wizard page or if not, the drafts created to have an option "Submit the draft for a review" in order to review the draft and move or not on the main articles, which this option doesn't exist on created drafts.

Thanks! — Preceding unsigned comment added by NSHPUZA (talkcontribs) 23:08, 2 May 2021 (UTC)

Previous thread at WP:VPPROP § People can't create a new article on English Wikipedia Suffusion of Yellow (talk) 23:41, 2 May 2021 (UTC)
I think I see the problem here. At [7], there's an inputbox where you type the name of your draft. It's supposed to preload Template:Afc preload/draft, but the mobile editor just ignores the preload parameter. So, the mobile editor is broken in another way.
@NSHPUZA: At the bottom of every page there is a "Desktop view" link. Follow that, then start over. Sorry, but the mobile site just doesn't work for certain tasks. Suffusion of Yellow (talk) 23:52, 2 May 2021 (UTC)
Suffusion of Yellow: Is that phab:T126190? (@xaosflux to close the loop.) –xenotalk 00:22, 3 May 2021 (UTC)
@Xeno: Yes, exactly. Thanks. Suffusion of Yellow (talk) 00:25, 3 May 2021 (UTC)
  • And notably, this does not prevent creating a new draft either, it only prevents the new draft from having preloaded text. — xaosflux Talk 00:48, 3 May 2021 (UTC)
    Are drafts without the preload ever reviewed by anyone? Or are they just deleted after six months? Suffusion of Yellow (talk) 00:50, 3 May 2021 (UTC)
  • I wonder if we can update Wikipedia:Article_wizard/CreateDraft to include a different button that forces the next page to use desktop view as an option... — xaosflux Talk 00:54, 3 May 2021 (UTC)
    Such as a link directly to reload it as desktop view - any good reasons not to? — xaosflux Talk 00:55, 3 May 2021 (UTC)
    Works for me, even with a "real" mobile browser. That will lock them into the desktop site until they click "mobile view" again, but that's a feature, not a bug, IMO... Suffusion of Yellow (talk) 01:06, 3 May 2021 (UTC)
We've had this complaint about the media uploader as well.... has there been a recent change to these two areas? Seems like our mobile viewers/editors are being neglected with recent changes. Agree best to force them into desktop view if we can't update modules/templates to work properly in mobile view.Moxy-Maple Leaf (Pantone).svg 01:11, 3 May 2021 (UTC)
we can easily update templates and modules. But ppl need to actually do it. We didn't for 10 years, so ... —TheDJ (talkcontribs) 19:54, 3 May 2021 (UTC)

Tech News: 2021-18[edit]

15:42, 3 May 2021 (UTC)

As a note, error is unlikely to be affected as above note suggests... --Izno (talk) 16:23, 3 May 2021 (UTC)

A list of pages onwiki which will affected by warning and success removals:

I'll leave talk page notices soonly? --Izno (talk) 17:09, 3 May 2021 (UTC)

I've left a user talk page note for the above users as well as a note at WP:IANB. Izno (talk) 18:23, 3 May 2021 (UTC)
There are a lot of old discussions that use these (at least error) too when talking about errors. Perhaps we should just add it locally. Anomie 20:18, 3 May 2021 (UTC)
I'm not too worried about old uses of the class, and also not that particular class anyway per discussion on the Phabricator task (this Tech News probably should have been reworded). Hence why I didn't go hunting for uses of error. The other classes are used sufficiently not-often that losing them probably isn't going to kill anyone. Izno (talk) 21:22, 3 May 2021 (UTC)
A naïve partial search [13] shows thousands of uses in wikitext for .error. I agree with @Anomie that we should probably define this locally. – SD0001 (talk) 07:28, 4 May 2021 (UTC)
Thanks for the talk page message. I've fixed User:Mr. Stradivarius/gadgets/SpamUserPage.js and User:Mr. Stradivarius/gadgets/Draftify.js. — Mr. Stradivarius ♪ talk ♪ 03:41, 4 May 2021 (UTC)

Saved data[edit]

When I start a new section on a talk page, as I start to type a heading i get a list of what I might want to type there. Recently, the words "Saved data" have started appearing above that list. One time, I thought I had clicked on the desired text only to find out there was no heading.— Vchimpanzee • talk • contributions • 21:59, 3 May 2021 (UTC)

"Saved data" must be added by your browser. It shows previous texts you have entered in that browser. It's not a Wikipedia feature. PrimeHunter (talk) 22:05, 3 May 2021 (UTC)
Wherever it came from, it's new.— Vchimpanzee • talk • contributions • 22:21, 3 May 2021 (UTC)
Probably a browser update. I see it in Microsoft Edge but don't know whether it's new. I normally use Firefox. PrimeHunter (talk) 23:09, 3 May 2021 (UTC)
It's certainly browser-dependent, and moreover, the table of previous texts is local to that particular browser on that specific device - if you have two browsers installed on the same device, say Firefox and Opera, they can't access each other's tables. They may also behave differently: some browsers look for a match from the start of the string, others will look for a match anywhere within the string.
One quirk is that Firefox, at least, keys the table to the id= value of the entry window. As you will be aware, there are two main ways of adding text to a discussion page:
  • Use the tab titled "New section" (or "+", etc.) which produces a large edit box, above which is a one-line box labelled "Subject/headline" - this one-line box is a <input id="wpSummary" ... /> tag
  • Use the "Edit" tab, or any "edit" link which produces a large edit box, below which is a one-line box labelled "Edit summary (Briefly describe your changes)" - this one-line box is a <input id="wpSummary" ... /> tag
Note that both of these tags have the same value for the id= attribute - a consequence of this in Firefox is that these two input items share a table of previous texts. --Redrose64 🌹 (talk) 11:51, 4 May 2021 (UTC)

Spaces in code[edit]

Previously I enquired about spaces between words and those where spaces were replaced by underscores, which I was informed were treated as the same by the Wikimedia software.

I chanced upon this edit where spaces were added into cite templates; I seldom use these templates as I don't find them helpful or easy to use (not alone, judging by the many red errors left by others) but I never include spaces. What's the objective in this edit, retro-actively? And what does/did it achieve?

Contrast the above with ostensibly the reverse from the same editor, although not within a template. There are many of the latter.

Thank you.--Rocknrollmancer (talk) 22:37, 3 May 2021 (UTC)

Well, the real answer is: what did the user say when you asked them? Asking a user about the user's behavior makes more sense to me than asking other people on a technical page about the user's behavior.
But I have an answer for you anyway (although I am, ultimately, guessing): they like spaces between parameters because it makes it easier (for them, anyway, but presumably others) to parse the wikitext while editing in Source Mode. I am quick to guess this because I often do the same thing in a paragraph I'm working on (but it's never the main edit I make). It looks like that's all they did on that page, which is frowned upon (see WP:Cosmetic edit). The removal of spaces before bullets is presumably that user's personal preference. There is no standard for this on WP. For that reason, it could cause friction with editors who have a conflicting personal preference. For the real answer, you could still ask that editor. — JohnFromPinckney (talk) 22:50, 3 May 2021 (UTC)
(edit conflict) They are cosmetic edits. Documentation usually has spaces before template parameters like Template:Cite web#Usage. It makes the wikitext more readable and allows browsers to line wrap there during edits. Removing spaces in list syntax is more controversial. Help pages like Help:List have spaces. I don't think they should be removed. PrimeHunter (talk) 23:02, 3 May 2021 (UTC)
{EC) ThanQ, JohnFromPinckney - as I'm not writing much in the way of prose, I try to appreciate other aspects whenever I encounter them, firstly by lateral thought. There's another similar-but-different example from a 'new' user that I didn't want to complicate matters by adding (has since made many edits, not newbie by my reckoning, but I only glanced). As you might've guessed, I don't care for the editor shown, which is why I take notice, and I'm not one to promote confrontation Face-smile.svg.--Rocknrollmancer (talk) 23:09, 3 May 2021 (UTC)
If you want to see where the 'new' user (new in Oct 2020, welcomed Dec 2020) was queried over spaces and the rationale(s) offered (I'm completely bemused), see here, here and here. Thanks.--Rocknrollmancer (talk) 23:49, 3 May 2021 (UTC)

Error when trying to create a particular template on bnwiki[edit]

We don't have any expert on bnwiki, so i am asking here. I'm trying to create this template on bnwiki. First it says there is an error. When i try to create this template and hit save, i'm getting edit conflict (I'm sure i didn't click twice). Any idea how to fix this? Please feel free to create this template with anything. --আফতাবুজ্জামান (talk) 00:01, 4 May 2021 (UTC)

I believe you are trying to copy Module:Arguments to a page that isn't in the module namespace. You already have bn:মডিউল:Arguments. --Trialpears (talk) 00:11, 4 May 2021 (UTC)
@Trialpears: Not module, i know we already have bn:মডিউল:Arguments. I'm trying to create Template:Arguments (similar to Template:Arguments here on enwiki). --আফতাবুজ্জামান (talk) 00:36, 4 May 2021 (UTC)
That looks like an error in the database. Visiting bn:Template:Arguments shows "Error" where it should have shown "টেমপ্লেট:Arguments" (that's "Template:Arguments"). Compare with what is shown at the nonexistent bn:Template:Bogus. I tried saving some text in bn:Template:Arguments and got the edit conflict error. On clicking edit, you see 'The revision #0 of the page named "টেমপ্লেট:Arguments" does not exist.' Johnuniq (talk) 02:18, 4 May 2021 (UTC)
The history of the nonexistent bn:Template:Bogus shows "There is no edit history for this page." while Template:Arguments history shows "No matching revisions were found." The page log show "No matching items in log." @Anomie: Do you want to offer an opinion? Is a Phabricator report warranted? Johnuniq (talk) 07:35, 4 May 2021 (UTC)
Maybe there are revision deleted or suppressed entries in the history or logs causing this? --Trialpears (talk) 08:31, 4 May 2021 (UTC)
That's a thought. @আফতাবুজ্জামান: Do you see anything extra when viewing the logs link in my above post? Johnuniq (talk) 09:45, 4 May 2021 (UTC)
Nothing extra, same as you. --আফতাবুজ্জামান (talk) 20:40, 4 May 2021 (UTC)
Shrug. Sounds like database corruption, like it has a page entry but no revisions. Anomie 11:27, 4 May 2021 (UTC)
Created http://phabricator.wikimedia.org/T281921 --আফতাবুজ্জামান (talk) 20:40, 4 May 2021 (UTC)

"Show disambiguation pages in orange" gadget failure?[edit]

I use this gadget (can be turned on in Special:Preferences) to avoid creating links to disambiguation pages and to quickly fix them when I see them. It works almost all of the time. However, at Morris (surname) (and now in this very section), the two redirects Pat Morris (disambiguation) and Patrick Morris (disambiguation) appear differently: the first one is in blue, the second in orange. The wikitext of both pages looks identical to me. Does anyone have an explanation? I use Monobook skin if it matters. —Kusma (t·c) 09:58, 4 May 2021 (UTC)

The gadget is just CSS, so it shouldn't be able to fail. Here's the HTML:
<a href="/wiki/Pat_Morris_(disambiguation)" class="mw-redirect" title="Pat Morris (disambiguation)">Pat Morris (disambiguation)</a>                                
<a href="/wiki/Patrick_Morris_(disambiguation)" class="mw-redirect mw-disambig" title="Patrick Morris (disambiguation)">Patrick Morris (disambiguation)</a>
As you can see, Pat Morris (disambiguation) isn't given the right CSS class. —Kusma (t·c) 13:57, 4 May 2021 (UTC)
According to mw:Extension:Disambiguator, .mw-disambig is added to pages containing the __DISAMBIG__ magic word, which I thought is added by {{R to disambiguation page}}, though that doesn't actually seem to be the case (or at least I can't find it in the template's code). Under that assumption, I moved the template to its own line, thinking that maybe being on the same line as the #REDIRECT made it not work, but that doesn't seem to have changed anything. – Rummskartoffel (talk • contribs) 14:26, 4 May 2021 (UTC)
The redirect cat is not needed, apparently the code follows redirects. User:Kusma/sandbox/r is a pure redirect to Patrick Morris, and is orange. —Kusma (t·c) 14:52, 4 May 2021 (UTC)
And the others are now both broken (i.e. blue). Does everything need to be on one line, or should we add the magic word to the rcat? —Kusma (t·c) 14:54, 4 May 2021 (UTC)
This is weird. It appears to not depend on the redirects at all but on the viewed page. If there is only one of the links then it gets mw-disambig and becomes orange with the gadget. If there are multiple links then some of them don't get mw-disambig. I don't know the system for which links get it but it sounds like a bug. PrimeHunter (talk) 15:26, 4 May 2021 (UTC)
At one time, the MediaWiki parser only processed templates if they occurred on the first line of redirect pages, which is why you often find templates like {{R to disambiguation page}} concatenated on that first line. The software was amended to process the whole page (and not just the first line) more than nine years ago, and it is now normal to arrange such templates one per line. But if the template is on the same line as the #REDIRECT [[]] directive, that shouldn't make any difference to how the template operates. There's just no point in moving the templates onto one line if they're already on separate lines.
The __DISAMBIG__ magic word is used to mark the disambiguation page itself, not redirects to such pages. It is not used bare: it's added by templates such as {{disambiguation}}, and should not be added to {{R to disambiguation page}} or any similar template. --Redrose64 🌹 (talk) 15:28, 4 May 2021 (UTC)
I have mentioned this at phab:T209249 where this issue has been ignored for a few years. —Kusma (t·c) 15:38, 4 May 2021 (UTC)

Read only time on 05-May-2021 at 06:00 AM UTC[edit]

Hi,

Some services will be in read-only for a short time on 2021-05-05 at 06:00 AM UTC.

During the restart time (expected to be around 60 seconds or so) all the components and extensions that use the x1 database will be read-only.

Things that might experience some issues when creating new writes:

  • New short urls cannot be created
  • Email bounces from lists might not get recorded
  • There might be issues with new translations
  • New items on the notification list might fail, some notifications may not be delivered
  • Reading lists might not record new items added to "bookmark" or "read it later" feature

Details: T281212 & T281375

A banner will be displayed on all wikis 30 minutes before this read-only time.

-- Kaartic [talk] 18:44, 4 May 2021 (UTC)

Template:Ran not working on mobile[edit]

I've noticed that this reference template {{ran}} (which is used on 99 articles [14]) doesn't work on mobile view. On mobile, a typical citation template creates a pop-up at the bottom of the screen when pressed, but this template does nothing when pressed. Any ideas on how to make this template produce these pop-ups on mobile, or failing that, make it jump down to the corresponding reference (perhaps a change to the template, mobile view, or both)? — Goszei (talk) 19:04, 4 May 2021 (UTC)

Because ran doesn't use the normal Cite-based system. Given what it does, I'd say it should be deleted in favor of {{notelist}}, a normal <references/>, or {{harv}} based system. Izno (talk) 19:16, 4 May 2021 (UTC)
In other words, it doesn't display because it doesn't use <ref>...</ref>, nor the equivalent {{tag:ref}} (which is how {{sfn}} manages it). --Redrose64 🌹 (talk) 19:26, 4 May 2021 (UTC)
It was nominated for deletion and closed as Keep in 2016, when it was in use in only one article. Nobody brought up its failure to function properly in mobile in that discussion, and I don't see that anyone has addressed the problem on the template's talk page. This bug may be fixable with a change to the template's code. – Jonesey95 (talk) 23:06, 4 May 2021 (UTC)
It does seem to work with the Reference Tooltips gadget on desktop (clicking also works as normal). — Goszei (talk) 23:52, 4 May 2021 (UTC)
The only way to add popups would be to use <ref>...</ref> in the template, but the reference system isn't designed for a template like this. For now, the reference should be removed from the template as it's not really producing a reference. This would also make the template work as expected on mobile. BrandonXLF (talk) 04:06, 5 May 2021 (UTC)

Table header text alignment: desktop vs mobile[edit]

This has been raised before, and it was escalated to Phab, but I couldn't find the outcome or even the task in the board it was said to been moved to. The issue is still outstanding. Basically, global table text alignments are applied to header rows in mobile but not desktop view. Editors working in desktop view may not be aware of that, and overlook the unintended effect in mobile view. (I'm not watching this page; please ping me if you reply) — 𝐆𝐮𝐚𝐫𝐚𝐩𝐢𝐫𝐚𝐧𝐠𝐚 (talk) 00:17, 5 May 2021 (UTC)

As you mentioned, phab:T240106 is still open on this, it is not unusual for phab reports to be open for a long time, sometimes in excess of a decade. — xaosflux Talk 00:22, 5 May 2021 (UTC)

VisualEditor browser speed comparison[edit]

Some operations on VisualEditor take a very long time (notably moving columns on very large tables like this one). Has anyone ever bothered benchmarking browsers on VisualEditor speeds? — 𝐆𝐮𝐚𝐫𝐚𝐩𝐢𝐫𝐚𝐧𝐠𝐚 (talk) 05:07, 5 May 2021 (UTC)

OneClickArchiver issue[edit]

OneClickArchiver has a technical issue... I've had similar issues with it before but this is the latest occurrence... I went to use it at Talk:John J. Pershing, which didn't have auto-archiving enabled. The app delivered the archived content to Archive 1 instead of Archive 5. I moved the content back to the main talk page and it was subsequently manually moved to the correct archive page, Archive 5 here but can something be done to adjust OneClick to move the content to the correct place the first time? Thanks, Shearonink (talk) 19:59, 5 May 2021 (UTC)

I've also seen another issue, where a page and it's talk page archives were moved, but the |archive= parameter wasn't updated, and later someone would come along with OneClickArchiver, and it would archive the content to the old archive location, which was now a redirect. For example, see here. I'm kinda of the opinion that OneClickArchiver should just be disabled entirely, I personally have never seen a legitimate usecase for it where Lowercase sigmabot III couldn't have done the same job. --rchard2scout (talk) 07:27, 6 May 2021 (UTC)
The problem with the OneClickArchiver is that it is a one-click archiver. What we need is a two-click archiver that informs the user in advance what archive the discussion would be sent to, and allows them to confirm or tweak the choice. – SD0001 (talk) 08:45, 6 May 2021 (UTC)
User:Σ/Testing facility/Archiver. Izno (talk) 22:42, 6 May 2021 (UTC)
What does Σ's Archiver do that OneClick does not... I read that page and, as I often say around here, I am very much an UnTech person. Can someone explain what it does better/differently than OneClick? Thanks, Shearonink (talk) 04:15, 7 May 2021 (UTC)
@Rchard2scout: Your issue is the same as one described above. --Redrose64 🌹 (talk) 12:12, 6 May 2021 (UTC)
Ah, you're right, it is. --rchard2scout (talk) 12:55, 6 May 2021 (UTC)
The thing is, not everyone knows how to set-up automatic archiving and when people do set it up, there can be issues with naming of archives and when a page gets renamed editors post about how the bot isn't doing its job...when the bot is just doing what it is told to do... All that is to say, OneClickArchiver is convenient and easy to use, no set-up the user just has to click away so disabling it without another bot stepping in...eeek. I do agree that a Two-Click Archiver is an awesome idea especially if it could step-in and take over where OneClick was installed...I think that's how Miszabot & lowercasesigmabot work together these days? Shearonink (talk) 15:22, 6 May 2021 (UTC)

Multiple images addition in infobox[edit]

I can't add {{Multiple image}} in infobox because of the width is incorrect. Compare these two images: File:Jax Jones (cropped).jpg and File:MartinSolveig.jpg and fix the width to suit in an infobox of the article Europa (musical duo). The Supermind (talk) 08:03, 6 May 2021 (UTC)

I have added it.[15] PrimeHunter (talk) 09:06, 6 May 2021 (UTC)

How to protect multiple articles at once?[edit]

If there's a list of titles (like added in this edit), is there some easy way to protect them all with a minimum of keystrokes? I'm thinking some javascript tool where you could drag-select them all, get a dialog with two questions ("semi, ECP, or full?" and "for how long?"), and then execute it all in one click. Surely somebody's written that already? -- RoySmith (talk) 13:04, 6 May 2021 (UTC)

AWB has protect options for admins I believe, but I doubt that would be more convenient for just 5 pages. --Trialpears (talk) 13:09, 6 May 2021 (UTC)
Twinkle has p-batch (but isn't great on a page with a large number of links you don't want protected); I've used it by copy-pasting the list to my sandbox before. — xaosflux Talk 19:30, 6 May 2021 (UTC)

Modern Vector (css skin)[edit]

To install the skin, place this in your vector.css page

{{subst:lusc|User:MediaJS/vector.css}} MediaJS (talk) (C) 13:07, 6 May 2021 (UTC)

Thanks for, um, minimizing the marketing. Can you give a hint as to why we would do this? What will happen? Is there a screenshot at, say, http://skins.wmflabs.org for us? — JohnFromPinckney (talk) 13:45, 6 May 2021 (UTC)
  • Administrator note: This script loads third party (external) components; this will send your browser and IP information to a site not covered under the WMF Privacy Policy. — xaosflux Talk 19:16, 6 May 2021 (UTC)
    • Why would we allow pages like that to be hosted at Wikipedia? It should be deleted. Johnuniq (talk) 23:39, 6 May 2021 (UTC)
      • @Johnuniq: we are very flexible about allowing scripts in userspace, we also have strong warnings to other about the risks involved if you actually import one. — xaosflux Talk 23:47, 6 May 2021 (UTC)

Harv warning script?...[edit]

Ok, I have a Harv errors gadget/Wiki-app enabled for my account and I wanted to look at the script and I can't find where it is installed on my subpages...so. Help me please. Someone who has more tech know-how than me please poke around my user pages or preferences or wherever and tell me where I put it. Thank you. Shearonink (talk) 18:02, 6 May 2021 (UTC)

It's importScript('User:Trappist the monk/HarvErrors.js'); // Backlink: [[User:Trappist the monk/HarvErrors.js]] in User:Shearonink/common.js (line 7) * Pppery * it has begun... 18:08, 6 May 2021 (UTC)
Ah bless you kind Wiki-TechWizard. I was thinking it was User:Ucucha/HarvErrors.js or something similar but I guess that was maybe a previous version? THANK YOU. Shearonink (talk) 18:14, 6 May 2021 (UTC)

Username issue[edit]

For some reason whenever I see my username anywhere on desktop mode, it appears in white on an orange background. — Preceding unsigned comment added by Qwerfjkl (talkcontribs) 18:23, 6 May 2021 (UTC)

How can you tell? You never sign your damned posts! — JohnFromPinckney (talk) 18:59, 6 May 2021 (UTC)
@Qwerfjkl: You've set this up for yourself using the code in User:Qwerfjkl/common.css -- John of Reading (talk) 19:29, 6 May 2021 (UTC)
Thanks! ― Qwerfjkl|   19:36, 6 May 2021 (UTC)

what am I missing?[edit]

In my sandox are three views of the same {{cite patent}} template. In the first <span> tag is this: id="CITEREFKozakai_Toshihiko2021" in which the year portion is wrong.

{{cite patent}} calls {{cite patent/core}} where we have this bit that contributes the year portion of the CITEREF anchor ID:

{{#time:Y|{{{IssueDate|{{{PublicationDate|}}}}}}}}}}

{{{IssueDate|}}} and {{{PublicationDate|}}} are provided to {{cite patent/core}} from {{cite patent}} in these:

|PublicationDate={{{publication-date|{{{pubdate|}}}}}}
|IssueDate={{{issue-date|{{{gdate|}}}}}}

In the sandbox example, neither of |issue-date= or |gdate= are provided nor is |publication-date=. |pubdate=2005-09-09 does make it to {{cite patent/core}} because both renderings of the example template have 'published 2005-09-09'. Yet, even so, the #time: parser function returns the current year instead of 2005 – the #time: parser is capable of doing the right thing:

{{#time:Y|2005-09-09}} → 2005

As a simple experiment, I hacked {{cite patent/core}} by adding this ahead of everything else in the template:

as written in the template: <code><nowiki>{{{IssueDate|{{{PublicationDate|}}}}}}</nowiki></code>
*{{#time:Y|{{{IssueDate|{{{PublicationDate|}}}}}}}} ← <code><nowiki>{{#time:Y|{{{IssueDate|{{{PublicationDate|}}}}}}}}</nowiki></code> – should use PublicationDate so should be 2005
*IssueDate:+{{{IssueDate|}}}+ ← <code><nowiki>+{{{IssueDate|}}}+</nowiki></code> – empty string
*PublicationDate: +{{{PublicationDate|}}}+ ← <code><nowiki>+{{{PublicationDate|}}}+</nowiki></code> – should show 2005-09-09
*both: +{{{IssueDate|{{{PublicationDate|}}}}}}+  ← <code><nowiki>+{{{IssueDate|{{{PublicationDate|}}}}}}+</nowiki></code>– should show 2005-09-09

inverted: <code><nowiki>{{{PublicationDate|{{{IssueDate|}}}}}}</nowiki></code>
*{{#time:Y|{{{PublicationDate|{{{IssueDate|}}}}}}}} ← <code><nowiki>{{#time:Y|{{{PublicationDate|{{{IssueDate|}}}}}}}}</nowiki></code>– should use PublicationDate so should be 2005
*both: +{{{PublicationDate|{{{IssueDate|}}}}}}+ ← <code><nowiki>+{{{PublicationDate|{{{IssueDate|}}}}}}+</nowiki></code>– should show 2005-09-09

When I preview my sandbox with the hacked template, I get this:

as written in the template: {{{IssueDate|{{{PublicationDate|}}}}}}
  • 2021 ← {{#time:Y|{{{IssueDate|{{{PublicationDate|}}}}}}}} – should use PublicationDate so should be 2005
  • IssueDate:++ ← +{{{IssueDate|}}}+ – empty string
  • PublicationDate: +2005-09-09+ ← +{{{PublicationDate|}}}+ – should show 2005-09-09
  • both: ++ ← +{{{IssueDate|{{{PublicationDate|}}}}}}+– should show 2005-09-09
inverted: {{{PublicationDate|{{{IssueDate|}}}}}}
  • 2005 ← {{#time:Y|{{{PublicationDate|{{{IssueDate|}}}}}}}}– should use PublicationDate so should be 2005
  • both: +2005-09-09+ ← +{{{PublicationDate|{{{IssueDate|}}}}}}+– should show 2005-09-09

In the 'as written' section above, the #time: parser function returns the current year and the 'both' case returns an empty string. When the order of {{{IssueDate|}}} and {{{PublicationDate|}}} are inverted, the #time: parser function returns the correct value as does the 'both' case.

Usually when I setout to write about these sorts of problems, I find where my knowledge and/or understanding are lacking before I click on Publish changes. Not so this time. Clearly {{{publication-date|{{{pubdate|}}}}}} works so why doesn't {{{IssueDate|{{{PublicationDate|}}}}}}? What am I missing?

Trappist the monk (talk) 19:11, 6 May 2021 (UTC)

{{Cite patent}} says:

|IssueDate={{{issue-date|{{{gdate|}}}}}}

This sets IssueDate to empty for your sandbox call. If IssueDate is set to anything, including empty, then {{{IssueDate|{{{PublicationDate|}}}}}} evaluates to the value of IssueDate and not PublicationDate. You only get PublicationDate if IssueDate is not set at all. PrimeHunter (talk) 20:22, 6 May 2021 (UTC)
IssueDate is not quite empty (possibly there's a null character that parser insert for empty parameter?). Compare "{{{IssueDate|no}}}" and "{{#if:{{{IssueDate|}}}|yes|no}}" in core (I modified cite patent/sandbox to |IssueDate={{{issue-date|{{#if:{{{gdate|}}}|{{{gdate}}}}}}}}, otherwise you would get "yes" at the #if compare)Must have been a mistake during testing. MarMi wiki (talk) 20:49, 6 May 2021 (UTC)
Oh yeah, I forgot that there's a difference between empty and not set parameter. Empty {{#time:Y}} or {{#time:Y|}} gives current year, so there you have it. MarMi wiki (talk) 21:27, 6 May 2021 (UTC)
It can for example be fixed by changing {{{IssueDate|{{{PublicationDate|}}}}}} to {{#if:{{{IssueDate|}}}|{{{IssueDate|}}}|{{{PublicationDate|}}}}}. PrimeHunter (talk) 21:58, 6 May 2021 (UTC)

Watched edits disappearing from watchlist[edit]

Probably WP:ITSTHURSDAY, but Special:Watchlist is behaving oddly. If I see a bad edit in there, use the WP:ROLLBACK feature and refresh the watchlist, the reverted edit gains the "Reverted" tag, and my edit shows with the "Rollback" tag, both of which are as expected. If I then enable "Hide my edits" and refresh, both of the abovementioned edits disappear, not just my edit. I have "Expand watchlist to show all changes, not just the most recent" enabled at Preferences → Watchlist, so the reverted edit should show whether mine is hidden or not. The two edits concerned are these. --Redrose64 🌹 (talk) 19:22, 6 May 2021 (UTC)

Even stranger, it also happens for rollbacks that other people made. For instance, these two edits both show if "Hide my edits" is not enabled; but if I enable it, the earlier of the two vanishes. --Redrose64 🌹 (talk) 19:35, 6 May 2021 (UTC)

I've found that it's not just rollback, but any form of undo. Also, an edit made by a logged-in user that gets tagged "Reverted" does not get hidden. Consider these six edits; disabling "Hide my edits" shows all six, but enabling it shows only one - the one by Bazza 7. --Redrose64 🌹 (talk) 19:53, 6 May 2021 (UTC)

Right, I think I have a better description. If there are edits by an IP which are tagged "Reverted", those edits are hidden when "Hide my edits" is enabled. They should not be hidden. --Redrose64 🌹 (talk) 20:04, 6 May 2021 (UTC)

For me, it goes even further. If I check "Hide my edits", all IP edits get hidden. Unchecking makes them reappear. – Ammarpad (talk) 20:30, 6 May 2021 (UTC)
Likewise - "hide my edits" makes IP edits disappear. DuncanHill (talk) 22:31, 6 May 2021 (UTC)
It does seem so, I hadn't carried out sufficient tests for that. --Redrose64 🌹 (talk) 23:25, 6 May 2021 (UTC)