Please see:
Other than the left margin what differences, if any, is your screenreader showing in the 2 sections.
Testing for accessibility problems. --Timeshifter (talk) 23:05, 15 June 2021 (UTC)
:What is your understanding of screen readers that you think the left margin is going to be evident? Has it still not occurred to you that the emphasis on the visual is leading you to focus on inappropriate solutions? — JohnFromPinckney (talk / edits) 23:44, 15 June 2021 (UTC)
::I have no idea what you are talking about. I am not emphasizing the visual. That's obvious, since I am asking for people with screenreaders to check out the 2 sandbox options, and tell us if their screenreader notices anything more than the indented left margin on one of the options. If the screenreader notices that at all. --Timeshifter (talk) 23:55, 15 June 2021 (UTC)
:::The question is a bit contrary to your intent: by saying "Other than the left margin..." you're implying screen readers will behave differently based on the left margin size. (The left margin makes no difference to the underlying document model and won't affect screen readers. Incorrect HTML will affect the document model, and it can cause unexpected behaviour.) But in the larger scheme of things, the tables don't really comprise a list. If they did, they should be marked up that way even if not being displayed side-by-side. It would be better not to put the tables into a list solely to take advantage of the default padding of list items. isaacl (talk) 00:22, 16 June 2021 (UTC)
::::I am concerned about accessibility problems. And simplifying things. If it causes no accessibility problems, then simple is better. User Prime Hunter proposed an even simpler solution with templates. So that is a 2nd option. The left margin is a problem when the 2 side by side tables are in a narrow screen and the tables wrap (one drops below the other). A horizontal scroll shows up sooner when there is a left margin. --Timeshifter (talk) 00:35, 16 June 2021 (UTC)
:::::The list markup is extraneous. You can add the "display:inline-table" style property directly to the table (see [https://en.m.wikipedia.org/w/index.php?title=User:Isaacl/side_by_side_table_example&oldid=1028782491&mobileaction=toggle_view_mobile User:Isaacl/side by side table example]). isaacl (talk) 00:36, 16 June 2021 (UTC)
:::::On a side note, PrimeHunter is just suggesting to hide the details of additional wrapper HTML inside templates. However with the style property applied directly to the table, no wrapper HTML is needed. isaacl (talk) 00:47, 16 June 2021 (UTC)
::::::{{u|Isaacl}}. See Help:Table#Side by side tables. "style=display:inline-table
can not be added within the table wikitext, because long captions will mess things up in mobile portrait view, or other narrow screens. It must be added outside the table wikitext."
::::::Look at [https://en.m.wikipedia.org/w/index.php?title=User:Isaacl/side_by_side_table_example&oldid=1028782491&mobileaction=toggle_view_mobile User:Isaacl/side by side table example] in mobile view and narrow your browser window until you see the problem.
::::::The problem does not exist at User:Timeshifter/Sandbox153.--Timeshifter (talk) 01:42, 16 June 2021 (UTC)
:::::::I put both pages in tabs in the same window and switched back and forth as I changed the window width. I don't see any differences. (Even if there were differences, it doesn't make semantic sense to put the tables into a list solely to take advantage of the styling of list items.) isaacl (talk) 01:51, 16 June 2021 (UTC)
:::::::I do see a difference on my mobile device. Rather than wrapping the tables in list items, they ought to be wrapped in <div> elements, as I did in [//en.wikipedia.org/w/index.php?title=User:Isaacl/side_by_side_table_example&oldid=1028781696 my original test]. isaacl (talk) 01:58, 16 June 2021 (UTC)
(unindent). Wow, that's great, isaacl. I added the example on the bottom here:
I did not need the padding. Instead one can leave a space between the ending and beginning div tags. Or put them on 2 different lines:
--Timeshifter (talk) 02:20, 16 June 2021 (UTC)
:Also, isaacl, someone who uses a screen reader (Graham87) says that the div example works fine. See [https://en.wikipedia.org/w/index.php?title=User_talk%3ATimeshifter&type=revision&diff=1028803316&oldid=1028801896 talk diff]. Here is the div example below. I pasted it here so that others can check it out too.
{{Static row numbers}}
class="wikitable sortable static-row-numbers" border=1 style=text-align:right
|+ Total number of matches played in official competitions only. |
Player
!Matches
!Goals |
---|
style=text-align:left|Guðmundur Hrafnkelsson
|407
|0 |
style=text-align:left|Guðjón Valur Sigurðsson
|364
|1,875 |
{{Static row numbers}}
class="wikitable sortable static-row-numbers" border=1 style=text-align:right
|+ Total number of goals scored in official matches only. |
Player
!Goals
!Matches
!Average |
---|
style=text-align:left|Guðjón Valur Sigurðsson
|1,875
|364
|5.15 |
style=text-align:left|Ólafur Stefánsson
|1,570
|330
|4.76 |
Everybody: Narrow your browser screen to see the tables wrap (one drop below the other). Works in mobile view too. The relevant div wikitext:
--Timeshifter (talk) 13:23, 16 June 2021 (UTC)
Classic vector skin font size
How come there are still issues with the font size when using the classic vector skin gadget (e. g. as to the rendering of references and categories)?--Hildeoc (talk) 14:08, 15 June 2021 (UTC)
:{{ping|Hildeoc}} Hard to say without links, browser information, what "gadget" this is about exactly, etc. --AKlapper (WMF) (talk) 17:10, 15 June 2021 (UTC)
::{{re|AKlapper (WMF)}} See "Preferences → Appearance → Vector classic typography (use only sans-serif in Vector skin)". Browser: Firefox (current). I just checked once again, and the problem is that with that gadget enabled, the font size of regular text on any English Wikipedia page is simply tiny.--Hildeoc (talk) 18:08, 15 June 2021 (UTC)
:::Ah, this is about "Vector classic typography (use only sans-serif in Vector skin)" on Special:Preferences#mw-prefsection-gadgets. Indeed. Someone needs to increase font-size: 0.8125em;
for .mw-body-content, #bodyContent
in MediaWiki:Gadget-VectorClassic.css, I guess. --AKlapper (WMF) (talk) 18:31, 15 June 2021 (UTC)
::::Fortunately, this has been fixed by now. Thanks for your interest. Best wishes--Hildeoc (talk) 16:25, 16 June 2021 (UTC)
New talk page message notification
{{tracked|T274428}}
Did someone change the text in the orange box that comes up when someone leaves you a new talk page message, and if so, could we change it back (or for me to change my stylesheet to change it for myself)? It's longer now and "Talk" is randomly capitalised. Anarchyte (talk) 06:47, 16 June 2021 (UTC)
:The software default has changed (see [https://github.com/wikimedia/mediawiki-extensions-Echo/commit/3a351cfb4fab9fb9d81ecdcb2638f29c843c26be#diff-1a490f08504158838befaa816ee8d5c08dff9e694d5a568ce4b0a4398dcc563eL67 commit]). Can be overridden locally by editing Mediawiki:echo-new-messages, but I think the proper course of action should be to take it upstream to have the caps fixed for all wikis. – SD0001 (talk) 09:12, 16 June 2021 (UTC)
::It's capitalized because "You have a new Talk page message" is shown instead of the normal "Talk" link. It does look odd but I wouldn't call it random and I'm neutral on the capitalization. PrimeHunter (talk) 10:04, 16 June 2021 (UTC)
:::No, that makes no sense to me. "You" is already capitalized. Nardog (talk) 10:23, 16 June 2021 (UTC)
:This is being discussed at phab:T274428#7140021. A patch has been proposed to go back to the previous wording. Legoktm (talk) 19:08, 16 June 2021 (UTC)
HTTP 502
Is there any reason why Wikipedia appeared to be inaccessible around one hour ago? All other websites were working properly, but every time I tried to go to any Wikipedia page, a WMF error page showed up instead. LSGH (talk) (contributions) 10:19, 15 June 2021 (UTC)
:There were some network connectivity issues with the Asia-Pacific datacenter (T284986) so if that's your closest then it could be the cause. I expect there will be a public incident report soon. the wub "?!" 15:31, 15 June 2021 (UTC)
::{{reply to|The wub}} Thanks. The incident report is not yet available, but someone [https://gerrit.wikimedia.org/r/c/operations/dns/+/699957 identified] the cause to be a router issue. How is it that only Wikipedia was affected while other WMF sites were not affected? LSGH (talk) (contributions) 03:11, 16 June 2021 (UTC)
:::One possible explanation is that you were not logged in to those other sites and saw cached pages, while the connectivity issue between the edge datacenter and rest of the network prevented non-cached requests (including all logged-in requests) from being properly served by MediaWiki itself. Majavah (talk!) 13:01, 17 June 2021 (UTC)
RfC location on validity of generated HTML
I am locked in a weird argument with another editor about whether Wikipedia should serve valid HTML or not, and what qualities wikitext needs to/does not need to/should not have. We're so entrenched in our opinions that I think I'm going to make my first RfC. My question (placed here, since HTML generation is kind of a technical matter) is: where would such an RfC be most appropriate? Help talk:HTML in wikitext? Somewhere else? — JohnFromPinckney (talk / edits) 19:21, 15 June 2021 (UTC)
:{{re|JohnFromPinckney}} so - it depends on what you want to "change". If you want a new technical functionality added, metawiki/phab/mailing lists would be a better place. If you want to change the manual of style about what type of markup is preferred then somewhere related to MOS may be best. Your premise of {{tq|whether Wikipedia should serve valid HTML}} though sounds like a software bug (i.e. if we are "serving" invalid html in our rendered pages to viewers) - if the bug is coming from something we've done on-wiki - then place it near where that it, if the bug is coming from the linter/rendering engine/etc - then open a bug report. Fixing technical malfunctions doesn't normally require as much of a consensus gathering exercise like changing the manual of style would. One thing you've done well is to think about this ahead of time - and really what page hosts the RfC isn't super important, so long as it is advertised at any of the venues that are applicable and ends up being well-attended. — xaosflux Talk 20:48, 15 June 2021 (UTC)
::Thanks, xaosflux. Probably before an RfC (now that I think more about it) I should just find a good place to get some discussion going. I'm not sure I want to change anything; I'd like to know if I'm the only person here who thinks the HTML we emit should be valid or not. If I am, then I'll have to decide how long to tilt at that windmill. If I'm not alone, I'd like to see where it's codified as policy/guideline/MoS item/whatever. And if it's not codified, but the community finds it important, then I'll try to get something formal.
::And I'm not talking about a software bug; my colleague thinks
elements (which they add manually into the wikitext) don't need
or
so insists on removing them or reverting my additions. I say the resultant page is invalid HTML (although my browser seems to display it nicely) and so is wrong for us to do (and recommend, for example, on Help talk:Table). — JohnFromPinckney (talk / edits) 21:34, 15 June 2021 (UTC)
:::A bare {{tag|li|o}} that occurs outside of any enclosing {{tag|ol}} or {{tag|ul}} pair is indeed invalid. See [//www.w3.org/TR/html51/grouping-content.html#the-li-element HTML 5.1 spec], the part beginning "Contexts in which this element can be used". --Redrose64 🌹 (talk) 22:02, 15 June 2021 (UTC)
::::Yes, Redrose64, I am aware that it's invalid, the argumentative editor doesn't care. And GhostInTheMachine, I agree, there's very little need here, but that doesn't stop our colleague from preferring it. The difficulty I'm having is convincing them that there is value in emitting valid HTML. In the discussion started on their talk page, they are demanding some evidence that screen readers have problems with broken HTML, or that weird code causes accessibility problems. Quote from that editor "I see none". :-( — JohnFromPinckney (talk / edits) 22:41, 15 June 2021 (UTC)
::Use wiki markup, not
tags. See :Category:Articles with HTML markup — GhostInTheMachine talk to me 22:27, 15 June 2021 (UTC)
:In some cases MediaWiki does emit invalid HTML, see mw:Parsing/Notes/HTML5 Compliance. We do try to follow HTML5, but I don't think strict compliance is a real goal yet. Legoktm (talk) 22:35, 15 June 2021 (UTC)
::There are others you can find lying around in :phab:tag/html5/. Izno (talk) 22:51, 15 June 2021 (UTC)
:{{u|JohnFromPinckney}}, What do you mean by "valid HTML"? At a minimum, I think everybody would agree that it needs to be well formed, and as far as I can tell, it meets that. Even when you try to intentionally break things like [https://en.wikipedia.org/w/index.php?title=User:RoySmith/sandbox&oldid=1028770637 this] (view the source to see what I mean).
:
:Beyond that, it gets more complicated. For example, when I paste the URL for this page (i.e. https://en.wikipedia.org/wiki/Wikipedia:Village_pump_(technical)#RfC_location_on_validity_of_generated_HTML) into [https://validator.w3.org/ W3C's validator], it comes up with 171 errors, the vast majority of which seem to be due to our bizarre formatting markup using * and : as wiki salad. If that's what you're concerned about, I suspect it's not worth the effort at this point to worry about it. -- RoySmith (talk) 22:50, 15 June 2021 (UTC)
::Talk pages are known to be aberrant on the point, so it's not an interesting comparison. John is specifically (and correctly) identifying that the <li> element in question must be contained inside either a <ul> or <ol> element, which is worth worrying about in the mainspace. Izno (talk) 22:57, 15 June 2021 (UTC)
::As I understand it, the issue is the side-by-side tables example at Help:Table. I copied the example to User:Isaacl/table example to isolate it. The MediaWiki software doesn't try to fix it up, and it remains malformed HTML in the generated output. isaacl (talk) 23:40, 15 June 2021 (UTC)
:::According to [https://www.w3schools.com/html/html_paragraphs.asp this w3schools page] without
is also malformed HTML. But
Help:HTML in wikitext says: "Note that the closing tag {{tag|p|c}} is not strictly necessary for MediaWiki installations that output HTML 5 (such as Wikipedia)." --
Timeshifter (
talk) 00:06, 16 June 2021 (UTC)
::::Yes, but the reason it's not strictly necessary is the the Mediawiki parser will automatically close the
for you, such that the page output does not contain invalid HTML code. (See [https://en.wikipedia.org/w/api.php?action=parse&page=User:Writ_Keeper/sandbox here] for an example.) It doesn't do that for uncontained
, so that's not a relevant comparison here. Writ Keeper ⚇♔ 00:38, 16 June 2021 (UTC)
:::::{{replyto|Writ Keeper}} Even if the Mediawiki parser did not automatically close the {{tag|p|o}}, the page output would not be invalid HTML. If you refer to the [//www.w3.org/TR/html51/grouping-content.html#the-p-element HTML 5.1 spec] it has a whole paragraph headed "Tag omission in text/html" which is quite comprehensive - there are very few situations where the omission of a {{tag|p|c}} would not be valid. In XHTML it was quite true that omitting a {{tag|p|c}} tag was invalid (in fact, all closing tags were mandatory), but the MediaWiki software was switched from outputting XHTML to HTML5 in September 2012. --Redrose64 🌹 (talk) 07:57, 16 June 2021 (UTC)
::::{{replyto|Timeshifter}} That w3schools page says nothing of the kind - the five letters "valid" are absent, and the {{tag|p|c}} tag is mentioned eight times - all of which are in examples, it is not used in text. The {{tag|p|o}} tag is found ten times - eight of which are in examples, paired with the aforementioned {{tag|p|c}} tags, one is in a summary label and just one is in the text. There is nothing that explicitly states that {{tq| without
is also malformed HTML}} or any variant on that. --
Redrose64 🌹 (
talk) 07:57, 16 June 2021 (UTC)
::::I know w3schools regularly comes up at the top of a search results list, but I do not consider them authoritative. My go-to place is the W3C, to which there is absolutely no connection. — JohnFromPinckney (talk / edits) 10:37, 16 June 2021 (UTC)
:::::I personally prefer and recommend MDN. I have found it to be very reliable, and it specifically provides accessibility advice for many topics. – Rummskartoffel 11:39, 16 June 2021 (UTC)
:In this case the MOS (Wikipedia:Manual_of_Style/Lists#List_styles) appears to allow html list elements when needed, but as seen in the examples they should be encapsulated in the list parent. — xaosflux Talk 22:55, 15 June 2021 (UTC)
I want to thank everyone who chimed in here and below and at Timeshifter's talk. I appreciate the extra experience and knowledge. — JohnFromPinckney (talk / edits) 10:37, 16 June 2021 (UTC)
:{{ping|JohnFromPinckney}} I happened to find this XfD discussion just now, while tracking down an entirely unrelated issue. Strange coincidence. On the topic of where to go for HTML and CSS questions, I usually use W3Schools because of their easy readability. But, yeah, when I really want to dig into the details, W3C is certainly the authoritative reference. -- RoySmith (talk) 13:32, 17 June 2021 (UTC)
#ifexist as css
I just noticed this: {{tq2|For some use cases it is possible to emulate the ifexist effect with css, by using the selectors a.new
(to select links to unexisting pages) or a:not(.new)
(to select links to existing pages).}}
Has anyone taken a stab at putting that into a template? I'd imagine it'd use a WP:TemplateStyles css to declare the class and hide the redlinks (though I see there was some controversy about doing that 13 years ago). — 𝐆𝐮𝐚𝐫𝐚𝐩𝐢𝐫𝐚𝐧𝐠𝐚 ☎ 23:24, 16 June 2021 (UTC)
:Manipulating the base link color is generally not user-friendly UI (that we ignore it for sports is a sports issue... we just shoot for basic color contrast accessibility). So... why would we want to make something like this? Izno (talk) 00:38, 17 June 2021 (UTC)
::Bc {{pf|ifexist}} is expensive?
::What I had in mind is setting {{mono|{{(}}display: none{{)}}}} on what's {{mono|.new}}, as {{u| Dragons flight}} suggested it 13 years ago (unless that's what you meant by {{tq|manipulating color}}). — 𝐆𝐮𝐚𝐫𝐚𝐩𝐢𝐫𝐚𝐧𝐠𝐚 ☎ 02:53, 17 June 2021 (UTC)
:::Can you provide specific examples where #ifexist is being used to hide links to non-existing pages? isaacl (talk) 03:04, 17 June 2021 (UTC)
::::Sure: {{tl|flaglist+link}}. The template puts a dagger (or more) next to the country name when it has a main article for the topic in which it is listed. — 𝐆𝐮𝐚𝐫𝐚𝐩𝐢𝐫𝐚𝐧𝐠𝐚 ☎ 03:50, 17 June 2021 (UTC)
:::::Still pondering on whether or not this type of presentation is a good idea or not, but in the meantime, the tables where you've used it should have a legend to explain the meaning of the symbol. (The documentation of the template also needs more detail.) isaacl (talk) 14:21, 17 June 2021 (UTC)
SockBlock inaccessible on mobile
{{tracked|T202919}}
Please see {{slink|Template talk:SockBlock|Inaccessible on mobile}}. I'm posting this here to get more eyes on the issue, and hopefully formulate an appropriate edit request. In short, {{tl|SockBlock}} cannot be viewed on mobile unless the desktop website is used, or by opening into the edit window for source material. Unfortunately, I don't have the technical know-how to be able to convert the template properly. Ideas welcome. Sdrqaz (talk) 17:27, 17 June 2021 (UTC)
:{{ping|Sdrqaz}} that template uses Template:Tmbox, with various x-box classes that are suppressed on mobile. A quick look in to phab:T202919 suggests that this is from configurations held off-wiki. — xaosflux Talk 18:14, 17 June 2021 (UTC)
::Thanks, {{u|Xaosflux}}; I did suspect that it was due to {{tl|tmbox}}. Given that the Phabricator task is "low"-priority and doesn't really capture the problem (the task is for those which are configured differently instead of being invisible altogether), would it be possible on our end to make a workaround (like {{tl|uw-sockblock}})? This template is used as a block notice, after all. Sdrqaz (talk) 18:35, 17 June 2021 (UTC)
:::{{re|Sdrqaz}} I suggest you bring this up at Template talk:Tmbox which is more watched and attended, the "better" solution may be a parameter on that template to change the classes. — xaosflux Talk 18:40, 17 June 2021 (UTC)
::::I'm sorry but are you sure? That talk page has 62 watchers and this one has over 3,000. Moreover, it seems to be an issue inherent to {{tl|tmbox}}; moving away from it for {{tl|sockblock}} seems the best solution. Sdrqaz (talk) 19:11, 17 June 2021 (UTC)
:::::I meant that TT:Tmbox > TT:SockBlock. — xaosflux Talk 20:28, 17 June 2021 (UTC)
At the very least, could we update out documentation so all of our message boxes clearly say whether they are visible on mobile or not? A quick ctrl-f mobile gave me zero information about this. For things that we want to be visible on mobile, we should use code that makes them visible on mobile. —Kusma (talk) 19:25, 17 June 2021 (UTC)
Internal module editing infobox has a typo
{{Resolved|Edit notice was updated. — xaosflux Talk 10:54, 18 June 2021 (UTC)}}
When you edit a module, the second infobox says "Editors can experiment in this modules's sandbox (edit | diff) and testcases (edit) pages." when it should be "Editors can experiment in this module's sandbox (edit | diff) and testcases (edit) pages.". Alexiscoutinho (talk) 20:14, 17 June 2021 (UTC)
:{{works for me}} and it looks right in Module:Documentation/config. Are you seeing this still? — xaosflux Talk 20:35, 17 June 2021 (UTC)
::{{re|Xaosflux}} I should have noticed that this is page dependent. It seems like only modules with a sandbox and/or testcases page have it, for example, [https://en.wikipedia.org/w/index.php?title=Module:Medical_cases_chart&action=edit Medical cases chart] and [https://en.wikipedia.org/w/index.php?title=Module:Bar_box&action=edit Bar box]. I don't know where this infobox is defined. Alexiscoutinho (talk) 22:43, 17 June 2021 (UTC)
:::Fixed in Template:Editnotices/Namespace/Module.[https://en.wikipedia.org/w/index.php?title=Template:Editnotices/Namespace/Module&diff=1029105033&oldid=886362331] PrimeHunter (talk) 22:48, 17 June 2021 (UTC)
2010 wikitext editor toolbar produces broken Wiki links
{{tracked|T285144}}
How come when inserting a copied Wiki link to a lemma with special characters like https://en.wikipedia.org/wiki/%C3%9Cbermensch
(for the article Übermensch) and selecting To a wiki page
in the "Insert link" form of the 2010 wikitext editor toolbar, the output is still a faulty link %C3%9Cbermensch
with a warning saying The requested page title contains invalid characters: "%C3".
– as has been the case for many years now? This seems to happen in all Wikis, by the way. (Has there ever existed a corresponding Phab ticket or anything similar dealing with this issue?)--Hildeoc (talk) 21:29, 16 June 2021 (UTC)
:{{re|Hildeoc}} this sounds like GIGO. Why would try to insert an external link to an internal article in to an article? This seems to work fine if you just insert the article name. — xaosflux Talk 13:41, 17 June 2021 (UTC)
::{{re|Xaosflux}} It's actually somewhat easier to just paste the URL into the form, and have it automatically transformed into a Wiki link – isn't that exactly what that function is supposed to be used for …?--Hildeoc (talk) 14:10, 17 June 2021 (UTC)
:::No, if I understand you here is what you are doing:
:::#Pasting a full URL in to the INSERT LINK function
:::#Changing the selector to "To a wiki page" (despite not actually putting in a wiki page)
:::#Seeing the error
:::Now, notice that if you don't but a percent-encoded URL in that step 1 the next steps end up being:
:::#Get a warning that "Page does not exit"
:::#End up inserting a bad string such as https://en.wikipedia.org/wiki/Apple
::::Displays as: https://en.wikipedia.org/wiki/Apple
:::So even if it wasn't for the refusal to accept your percent encoded url here, the output is still undesirable, you didn't put in a "wiki page" so your output is not a "wiki page". — xaosflux Talk 14:32, 17 June 2021 (UTC)
::::{{re|Xaosflux}} But with URLs linking to Wiki lemmas without special characters the conversion into Wiki links works perfectly fine (except for the automatic addition of underscores for spaces, which don't affect the validity of the converted links created, though), and to me that's a very useful thing. Notice that the form automatically shows the following message when you paste a Wikipedia URL: The URL you specified looks like it was intended as a link to another wiki page. Do you want to make it an internal link?
--Hildeoc (talk) 14:41, 17 June 2021 (UTC)
:::::Which version of which tool bar are you using? That's not what I got. — xaosflux Talk 15:22, 17 June 2021 (UTC)
::::::{{re|Xaosflux}} 2010 wikitext editor (checked under Preferences → Editing).--Hildeoc (talk) 16:05, 17 June 2021 (UTC)
:{{re|Hildeoc}} Are these the steps to reproduce?
:# Use the insert tool bar link button
:# Put in a percernt-encoded internal link
:# Select that you want this to be "to an external web page"
:# Click Insert Link
:# Get the intercept dialog that this may be internal, asking if you want it to be an internal link
:# Select "Internal link"
:# Get to where you are stuck
: Where you would prefer that the extension un-percent-encodes the string after step 6? — xaosflux Talk 12:53, 18 June 2021 (UTC)
::{{re|Xaosflux}} Yes, exactly! Ideally, the killer would be if the rendering of underscores indicating spaces would be omitted as well …--Hildeoc (talk) 13:01, 18 June 2021 (UTC)
:::{{re|Hildeoc}} OK, that will require a software change to :mw:Extension:WikiEditor. I've opened a feature request here: phab:T285144. Feel free to subscribe to the FR, correct anything I put wrong on it, or add to it. Please note, there are currently 97 requests in the backlog for that extension, so it could be a long time for someone to work on this. — xaosflux Talk 13:14, 18 June 2021 (UTC)
::::Dear xaosflux, how can I thank you? This is really nice of you – thank you so much for taking the time and trouble to take care of that! I've just created a Phab account and subscribed to your request. I do hope it will be considered at some point. For the time being, I wish you all the best--Hildeoc (talk) 13:27, 18 June 2021 (UTC)
Accounting of deleted (legit) templates in contributions
I've seen a couple of similar discussions, but they are very old. Every time I talk about deleted contributions below I mean DEPRECATED TEMPLATES.
- Is showing private (only user who did it can see) deleted contributions still a concern to the point of not being worth moving this discussion forward?
- Does the "number of edits" counter in Preferences count deleted contributions?
- Is it acceptable to undelete a deprecated template, to blank and redirect it, only so that its edit history is preserved (and contribs)?
Alexiscoutinho (talk) 14:26, 18 June 2021 (UTC)
: (1) Yes, keep in mind almost all deletions are entire pages that have many contributors. (2) yes. (3) it really depends, "deprecated" alone isn't usually a reason to delete something - deletions are carried out under the deletion policy, most deletions should be logged as to the reason it was deleted and there are various reasons to undelete something. You can read all about that in the Wikipedia:Deletion policy and the guidance at Wikipedia:Requests for undeletion. (Bonus #4) Don't worry about accounting for contribution "edit counts" - all sorts of things can impact it, and at over 500 edits the exact figures don't really matter for anything important. See Wikipedia:Edit count and the links on that page for way too much on that topic. — xaosflux Talk 15:49, 18 June 2021 (UTC)
::It generally has been the policy to delete unused templates, even if previously used. It does break old versions of pages, though, so I wish there was a bit of a better way. But leaving template namespace filled with things long-ago deprecated really isn't ideal. Elli (talk | contribs) 15:51, 18 June 2021 (UTC)
:::{{re|Elli}} I think it would be nice if Wikipedia had a separate old/historical branch where all the old stuff lives. This would keep the namespaces clean and wouldn't break old revisions and people's hearts. Alexiscoutinho (talk) 20:10, 18 June 2021 (UTC)
OneClickArchiver archiving the wrong discussion
I'd ask at User talk:Evad37/OneClickArchiver.js but {{U|Evad37}} doesn't seem to have been active since the beginning of this month.
I tried archiving a discussion at WP:ANI with OneClickArchiver and it's {{dif|1029265926|archiving the wrong one}}. The automated edit summary is labelling the discussion that I want to archive, though, so it seems like some sort of heading detection issue. Anyone know what the problem is? {{pping}} —Tenryuu 🐲 ( 💬 • 📝 ) 22:36, 18 June 2021 (UTC)
Link not working
[http://en.wikipedia.org/w/index.php?action=edit§ion=new&preload=User:Ocaasi/WikiLoveinstallscript1&title=Special%3AMyPage%2Fcommon.js This] link isn't working, it says that section editing is not enabled. ― Qwerfjkl | 𝕋𝔸𝕃𝕂 (please use {{tlx|reply to|Qwerfjkl}} on reply) 22:18, 18 June 2021 (UTC)
:{{reply to|Qwerfjkl}} It isn't supposed to work. It has section=new
in the url but JavaScript pages don't have sections. Where did you see the link? PrimeHunter (talk) 22:31, 18 June 2021 (UTC)
::Actually, it may have worked previously and enabled users to add code to the bottom of a JavaScript page by leaving the heading field empty. PrimeHunter (talk) 22:48, 18 June 2021 (UTC)
:::@PrimeHunter: User:Ocaasi/WikiLoveinstallscript ― Qwerfjkl | 𝕋𝔸𝕃𝕂 (please use {{tlx|reply to|Qwerfjkl}} on reply) 06:19, 19 June 2021 (UTC)
Ability to present one or another or two tables
There is a discussion going on at wikiproject basketball regarding presentation of statistical data for players in basketball articles. I won't reprise all of the discussion, but some editors prefer only ratios for certain statistics. While I support the inclusion of ratios, there are times I think it's helpful to see the statistics as totals per year. While showing both might be an obvious answer, the inclusion of all fields in a single table generates an unwieldy sized table.
I'd like to explore an option to eat our cake and have it too.
I'm intrigued by the presentation in many info boxes about locations that gives you the option of showing one of several maps or all maps with a simple click of a radio button. As an example, see the info box for Alliance,_Ohio, which allows you to choose whether you want to present a map of Ohio, a map of the United States, a map of North America, or all three. While I can see that this is done with a switch, I haven't figured out whether this same concept could be applied to tables.
In short, I'm trying to figure out if I can set up something so that a single table (probably defaulting to the ratios) is presented but the user has option to switch to the totals table or to see both.
I've presented example data in User:Sphilbrick/Stats_options. The first table labeled "ALL" is not what I want as it is too wide, although it does reflect the standard presentation in typical schools media guides or record books. What I would like to do is have both tables available, the one labeled "Ratios" and the one labeled "Totals", with one showing as a default and the ability with a radio burtton to switch to the other or see both simultaneously. I am concerned about Wikipedia:Manual of Style/Accessibility issues. My hope is that the broad acceptance of the map option means the accessibility concern doesn't apply. (As a related point, I had some initial concerns about the header row showing popup abbreviations, but I see MOS explicitly allows that MOS:NOHOVER.)
Can someone tell me if this is feasible and if so how to implement it?
As a secondary technical question, I generally like to use the visual editor to add tables by constructing them in Excel and then copying and pasting them. I haven't figured out how to handle the heading row using visual editor. Is there something I'm missing?--S Philbrick(Talk) 14:11, 17 June 2021 (UTC)
: Are you looking for {{tl|switcher}}? * Pppery * it has begun... 14:14, 17 June 2021 (UTC)
::{{u|Pppery}}, That sounds promising. Not immediately obvious how to shoe horn and entire table into a single row but I'll try S Philbrick(Talk) 14:24, 17 June 2021 (UTC)
::{{u|Pppery}}, Looks promising, User:Sphilbrick/sandbox but I made it work by putting the individual tables and a separate page and transcoding them. This would work as a one-off but not workable for hundreds of articles so I need to figure out how to include the data in the template. S Philbrick(Talk) 14:37, 17 June 2021 (UTC)
::: Yeah, passing complicated wikitext to templates is a pain. I managed to get it to work anyway by using {{tl|wikitable}} and escaping the = to {{tl|{{=}}}} in scope="col"
, producing Special:PermaLink/1029041109 * Pppery * it has begun... 14:50, 17 June 2021 (UTC)
::::{{u|Pppery}}, I will look into that. S Philbrick(Talk) 14:54, 17 June 2021 (UTC)
::{{u|Pppery}}, I found that I can add the tables to the article as hidden data. see User:Sphilbrick/Stats example in the Alternative stats section, now I have to learn how to do a partial transclusion, but I do have to run out to see my grandson, so later. S Philbrick(Talk) 14:53, 17 June 2021 (UTC){{od}}
I thought I'd try including the two tables in the article in a special section that would be hidden, then transclude the two tables into the switcher template but that attempt failed miserably. I'm guessing that it is not acceptable to do a tranclusion on a page that incorporates information from that same page; I got a template loop error.
I did find an approach that works, see User:Sphilbrick/Stats example, but I'm worried that this will be frowned upon because I dropped the tables into sub pages then transluded.
According to Wikipedia:Subpages in the section on disallowed uses:
{{talk quote block|Using subpages for permanent content that is meant to be part of the encyclopedia.}}
I think the rationale is that a reader should never have to visit a sub page to see relevant content but that doesn't apply in this case given the transclusion. It does mean that updates to information by editors would require visiting there but editors unlike readers are not going to have any difficulty locating the data.
I put together a simple example so that it's visible here rather than having to go to the user page to see it:
{{Switcher
| {{Wikipedia:Village pump (technical)/test table 1}}
| Ratios
| {{Wikipedia:Village pump (technical)/test table 2}}
| Totals
}}
--S Philbrick(Talk) 14:40, 18 June 2021 (UTC)
{{u|Pppery}}, I have some success with your {{tl|wikitable}} suggestion. Here's a toy example:
{{Switcher
| {{wikitable| class="wikitable"
|+{{{caption|Ratios}}}
!YEAR
! scope{{=}}"col"|{{abbr|GP|Games played}}
! scope{{=}}"col"|{{abbr|MPG|Minutes per game}}
! scope{{=}}"col"|{{abbr|APG|Assists per game}}
! scope{{=}}"col"|{{abbr|BK|Blocks per game}}
|-
|1995-96
|34
|18.56
|1.15
|0.59
|-
|1996-97
|28
|17.86
|1.25
|0.54
}}
| Ratios
| {{wikitable| class="wikitable"
|+{{{caption|Totals}}}
!YEAR
! scope{{=}}"col"|{{abbr|GP|Games played}}
! scope{{=}}"col"|{{abbr|MIN|Minutes}}
! scope{{=}}"col"|{{abbr|A|Assists}}
! scope{{=}}"col"|{{abbr|BK|Blocks}}
|-
|1995-96
|34
|631
|39
|20
|-
|1996-97
|28
|500
|35
|15
}}
| Totals
}}
An example with real data can be seen in User:Sphilbrick/Stats example
The only downside is that it requires me to construct the tables manually, line by line and using the sub pages allows me to copy and paste tables from Excel, but I have a feeling the community is not going to accept sub pages. Any thoughts? Thanks for your help, one of these two options should work.--S Philbrick(Talk) 11:22, 19 June 2021 (UTC)
File at ENWP
How I can see original upload//log/page for this image (it was moved to Commons)? Current file has comment "I created this myself 20/4/08" by Taopman. What could a comment from those years mean? I found source which says that take a picture was only possible on 27 April 2007. Eurohunter (talk) 12:24, 19 June 2021 (UTC)
:The file was moved, which makes it a bit harder to find. Original log is here: [https://en.wikipedia.org/wiki/Special:Log?type=&user=&page=File%3ABasshunter2-1-.jpg]. The original license information was {{tlx|self|cc-by-3.0}}. There is nothing else in the deleted history. —Kusma (talk) 12:45, 19 June 2021 (UTC)
Discussion about using CSS margins to modify kerning
There is a discussion at Template talk:Nihongo#Template-protected_edit request on 7 June_2021 — Kerning issues about the use of CSS margins to modify kerning within the Nihongo template. Some technical insight would be appreciated. — Goszei (talk) 06:26, 14 June 2021 (UTC)
:Reaching out a second time, since there is little participation (only 4 editors so far) for this wide-reaching and highly-visible change. Discussion has now turned to whether the currently-live implementation (applying a 0.2em margin around parenthesis for certain letter-based cases in the Nihongo template) should be reverted, kept, or modified. — Goszei (talk) 01:18, 20 June 2021 (UTC)
Harv cite issues, Harv errors abound...
Harv cites are not my jam but when Harv errors and warnings litter an article it annoys me so I try to fix them. That being said, since they are not my jam, they are often a source of frustration to me because I usually cannot easily figure out exactly what is wrong. So, O Wiki Technical/Coding Mavens Who Understand All The Niceties of Harvard/Sfnm/etc Citations... could someone PLEASE take a look at Chester A. Arthur and tell me why it is littered with 44 "Harv errors"? I [https://en.wikipedia.org/w/index.php?title=Chester_A._Arthur&diff=1029385507&oldid=1029374319 tried to fix] one - the Abbot cite - but was unsuccessful. If you could explain it here, maybe step-by-step in somewhat plain English so my addled brain can understand that would be awesome. If you don't mind, please don't fix the issues at the article - explain it here and I'll get at it myself. I know it's probably something incredibly simple but I am just not seeing what the issue is at the moment. Thanks. Shearonink (talk) 17:24, 19 June 2021 (UTC)
:With the version of the script you have installed, it correctly identifies that items in the Further reading section that you are citing with a Harv template should be in a separate section above the Further reading section. Perhaps "Works cited" or "Bibliography". The point of a further reading section is to contain works that you did {{em|not}} cite but have included for 'further' reading. Izno (talk) 17:41, 19 June 2021 (UTC)
::Like Izno said, that's because you have references in a further reading section, instead of a bibliography section (or similar). Headbomb {t · c · p · b} 17:46, 19 June 2021 (UTC)
:::Just for the record, I did not set the references up and I have had little to do with the article until (maybe) today. Chester A. Arthur is a featured article and the present referencing layout is how I found it. Btw, there is already a References section but it only has 2 Refname references + a single Sfn reference sitting in it... . Shearonink (talk) 17:59, 19 June 2021 (UTC)
::::Figured out [https://en.wikipedia.org/w/index.php?title=Chester_A._Arthur&diff=next&oldid=1029393408 what will work]. Thx Wiki-Mavens. Shearonink (talk) 18:10, 19 June 2021 (UTC)
:::::Just so. Izno (talk) 18:32, 19 June 2021 (UTC)
::::::For the record, there were and are (at this writing) no short citation errors in that article. – Jonesey95 (talk) 03:59, 20 June 2021 (UTC)
Table ID
{{tl|Excerpt}} Gives the impression that I can transclude a specific table if it has an ID.
:tables — Tables to transclude. By default all tables are transcluded. Same syntax as when transcluding paragraphs, but also: tables=Stats2020 — Transclude the table with id 'Stats2020'
I've looked at Help:Table But I'm not clear how to create the ID. Is it done with an anchor?--S Philbrick(Talk) 16:46, 20 June 2021 (UTC)
:My intended usage has a flaw so nevermind. S Philbrick(Talk) 18:38, 20 June 2021 (UTC)
Template:Campaignbox is not visible on mobiles and tablets even if desktop mode is turned on
{{resolved|Chrome "desktop view" is not Wikipedia's "Desktop" mode; the former does not request additional content such as navboxes, the later does (and works). — xaosflux Talk 07:52, 19 June 2021 (UTC)}}
When I look at War of the Fifth Coalition on my Android mobile with Chrome Version 91.0.4472.101, I cannot see the result of the template "Campaignbox Napoleonic Wars" and I get no warning that something cannot be displayed. Even if I turn on desktop mode I cannot see any result of any campaignbox. The same is true for my Android tablet with Amazon Silk. The campaignboxes are very important to allow the user to navigate easily from article to article. Ruedi33a (talk) 14:54, 18 June 2021 (UTC)
:What does desktop mode mean to you? What is the URL you are visiting? Izno (talk) 15:29, 18 June 2021 (UTC)
::War of the Fifth Coalition in desktop mode according to Chrome on my mobile___=en.m.wikipedia.org/wiki/War_of_the_Fifth_Coalition, no campaign box
::War of the Fifth Coalition not in desktop mode according to Chrome on my mobile=en.m.wikipedia.org/wiki/War_of_the_Fifth_Coalition, no campaign box
::War of the Fifth Coalition url manually edited_____________________________=en.wikipedia.org/wiki/War_of_the_Fifth_Coalition, campainbox is visible but you cannot read it as the letters are too small unless you enlarge this part of the screen: visible but unusable for a simple user Ruedi33a (talk) 18:24, 18 June 2021 (UTC)
:::It works for me at [https://en.wikipedia.org/wiki/War_of_the_Fifth_Coalition] (link from following the Desktop view). Can you verify you successfully made it to the desktop mode (that your url is not en.m.wikipedia...). — xaosflux Talk 15:39, 18 June 2021 (UTC)
::::You are right, Chrome does not change the url correctly... Ruedi33a (talk) 18:08, 18 June 2021 (UTC)
:::::You shouldn't just use the browser's toggle if you're currently viewing the mobile version of a page. You should use the toggle at the bottom of the page itself ("Desktop"), which serves you the desktop version no matter what the browser's preferences are. Nardog (talk) 20:52, 18 June 2021 (UTC)
::: Works for me on desktop, too. Would it be possible to make it to where such templates appear on mobile w/o going to desktop mode? It seems that those templates are likely useful even for mobile viewers. Hog Farm Talk 15:46, 18 June 2021 (UTC)
::::{{re|Hog Farm}} feel free to join in 5 year old task phab:T124168 about wanting navigation boxes in mobile. — xaosflux Talk 15:53, 18 June 2021 (UTC)
= navboxes editors vs developers - take 99 =
:::::The fundamental problem with mobile seems that Wikipedians like to manually write things that work on the desktop with no regard for mobile. Developers then just code something automatic (like hiding certain boxes, or switching certain orders around, or the automated suggestions that replace some navboxes) to work around some problems with what Wikipedians have created. It might be possible to harness the power of Wikipedians to improve the mobile experience (Wikipedia's success is to use smart human labour instead of algorithms), but I wouldn't even know where to find the documentation. —Kusma (talk) 16:08, 18 June 2021 (UTC)
::::::Not only that, navboxes also take up an exorbitant amount of the data of page delivery, especially on the more popular articles. Downloading that on a phone is not fun —TheDJ (talk • contribs) 17:48, 18 June 2021 (UTC)
::::::Navboxes originated in the time before iPhones and the subsequent dominance of mobile Internet surfing. They just never made the jump from a design perspective. And also the size. I was going to play around with at least fixing the display part on MediaWiki wiki after navbox there got (fully) TemplateStyled, but {{U|TheDJ}} stopped working my edit requests ;). Izno (talk) 17:56, 18 June 2021 (UTC)
:::::::I'm not saying we should display standard navboxes on mobile (I'm not sure we should display them on desktop tbh), I'm trying to say we should design human-curated navigation tools that work well on mobile. —Kusma (talk) 20:12, 18 June 2021 (UTC)
::::::::If we knew what (good) human-curated navigation tools looked like, we probably would... Izno (talk) 21:10, 18 June 2021 (UTC)
:::::::::I don't think we'd do worse than mw:Reading/Web/Projects/Related pages. —Kusma (talk) 21:34, 18 June 2021 (UTC)
::::::::::Maybe we should have a new class navbox-mobile
which is similar to navbox
but renders on mobile. {{tl|Navbox}} and other templates could have an option for which class to use. Editors would probably disagree which navboxes are important enough to show on mobile so we would get one more thing to fight over. PrimeHunter (talk) 22:56, 18 June 2021 (UTC)
:::::::::::No, thank you. Forking things makes no sense. Izno (talk) 02:36, 19 June 2021 (UTC)
::::::::::::I was unclear. I meant for navbox-mobile
to render on both desktop and mobile, not forking to only render on mobile. PrimeHunter (talk) 09:50, 19 June 2021 (UTC)
:::::::::::::No, the point I'm making is that must require a fork, because it's 'navbox' that causes these not to display on mobile. And it's not "display: none" CSS, it's "MobileFrontend rips the HTML out entirely". Izno (talk) 16:48, 19 June 2021 (UTC)
::::::::::::::No, my idea would not require a fork. I'm suggesting that {{tl|Navbox}} and friends get a new optional parameter, e.g. |mobile=yes
. If the parameter is set then they add a new class navbox-mobile
instead of adding navbox
. navbox-mobile
should have the same styling as navbox
so it renders the same on desktop, but it also renders on mobile since navbox
is no longer present. This assumes the mobile developers don't decide to also omit navbox-mobile
from mobile. We can make a guideline about only using |mobile=yes
on small or essential navboxes. Individual navbox templates may pass on the parameter, e.g. using {{tlx|Academy Award Best Actor|mobile=yes}} on Academy Award for Best Actor to render on that article in mobile, but not on the biographies. PrimeHunter (talk) 20:59, 19 June 2021 (UTC)
:::::::::::::::{{u|PrimeHunter}}, would that not require forking the navbox style into two classes though which would then need to be kept updated in parallel? I assumed that is what Izno meant. firefly ( t · c ) 21:08, 19 June 2021 (UTC)
::::::::::::::::I assumed Izno meant forking a lot of navbox templates. Defining an extra CSS class should be simple whether or not we call it forking. PrimeHunter (talk) 23:51, 19 June 2021 (UTC)
::::::{{replyto|Kusma}} {{tq|The fundamental problem with mobile seems that Wikipedians like to manually write things that work on the desktop with no regard for mobile.}} This is simply not true. The {{tlx|campaignbox}} template has been using class="navbox"
for many years, and did so long before the devs started writing a special skin for mobile displays and provided the https://en.m.wikipedia.org/ domain to go with it. It was the devs who made a deliberate decision that any element belonging to the navbox class should not be displayed in mobile. So don't blame Wikipedians. --Redrose64 🌹 (talk) 07:19, 19 June 2021 (UTC)
:::::::@Redrose64: Sorry, I think my point did not come across. I was trying really hard to AGF with the devs and may have overshot. I'm just saying, there are good reasons why the devs chose a few years ago not to display navboxes. That they replaced them by RelatedPages still strikes me as bizarre (and somewhat insulting, I don't like being replaced by algorithms). The question is what we should do now. The most obvious solution to me is having separate navboxes, which according to @Izno {{tq|makes no sense}}. The next obvious solution is to cull and cut down desktop navboxes until they make sense also on mobile, and to display them everywhere again. —Kusma (talk) 08:34, 19 June 2021 (UTC)
::::::::(As to "forking", I agree that asking desktop editors to edit something separate that is only visible on mobile isn't going to work. But maybe there's something else we can do). —Kusma (talk) 09:52, 19 June 2021 (UTC)
::::::::A social solution won't work. It's been a decade and editors are still happily making very large navboxes. :\ Izno (talk) 16:51, 19 June 2021 (UTC)
:::::::::I assume the majority of these editors are blissfully unaware that this might be a problem. —Kusma (talk) 12:41, 20 June 2021 (UTC)
::::::::It was a good decision not to display navboxes on mobile, they spread and grow like a cancer; in a few years every article will have a list of nearly all wikipedia articles in it. We already have infoboxes that are 5 screens long on mobile. I mean, who goes to wikipedia to *read* all these identifiers here? Ponor (talk) 12:50, 20 June 2021 (UTC)
:::::::::{{tl|Ended Turkish television series}} has 640 links to the Turkish Wikipedia. PrimeHunter (talk) 18:01, 20 June 2021 (UTC)
::::::::FWIW, I've always like the navboxes and have found them extremely useful both as a reader and an editor to find related topics, and I use them all the time. As for the mobile version, I have no need for it even on mobile devices, and improvements in mobile phone technology that seemed to demand a mobile version in the first instance when they became capable of handling web pages now are making it obsolete. Hawkeye7 (discuss) 00:20, 21 June 2021 (UTC)
First I have to thank everybody joining this discussion about my question. I started as an ignorant human being and now I am on the long, cumbersome way to become a Wikipedian.
Summary: As a simple user I did not know the link "Desktop" hidden at the bottom of every wiki page. I have tried it now once and the result on my mobile was disastrous: the normal text is OK, the text of the infoboxes and campaignboxes is too small to be readable and must be increased manually. I will never use desktop mode again. If a wikipedian will say to me use "Desktop" mode to see the campaignboxes, I will know that this is an answer out of The Hitchhiker's Guide to the Galaxy: absolutely correct but does not help at all. The situation is that a user sees only 95-99% of this kind of wiki article on his mobile/tablet and gets no warning.
I suggest this solution: The simple infobox is a perfect replacement to solve the problem but the infobox seems to be too boring and too ugly for wikipedians. Compare Template:French invasion of russia mobile with Template:Campaignbox Napoleon's invasion of Russia. I suggest to replace each campaignbox with an infobox or something better than infobox that is visible on a mobile/tablet. Ruedi33a (talk) 11:00, 19 June 2021 (UTC)
:We already have a meta-template for this, it's {{tl|sidebar}}. That template also does not display on mobile, basically for the same reasons as the navbox above. I do not think this solution will do anything, and it's likely to be deleted locally anyway due to being a fork or converted to use sidebar, which will subsequently remove it from mobile. "I want to see these on mobile" isn't good enough to solve the problem. Izno (talk) 16:54, 19 June 2021 (UTC)
Could someone give me a non-technical current consensus please? For example Ruedi33a has created {{tl|Peninsular War 1810 1811 mobile}} (currently transcluded from 16 articles) to replace {{tl|Campaignbox Peninsular War (1810–1811)}} (currently transcluded from one article). That is just one example of the [https://en.wikipedia.org/w/index.php?title=Special:Contributions&offset=&limit=500&target=Ruedi33a&namespace=10&tagfilter=&start=&end= many new "mobile" templates they have created]. Is there any consensus for this? FDW777 (talk) 11:45, 20 June 2021 (UTC)
:{{re|FDW777}} well this is the tech page, so not sure what you are looking for. I don't think we should be misusing infobox classes to house a navbox though. — xaosflux Talk 12:07, 20 June 2021 (UTC)
::that is, if certain "contained conflicts" etc are integral to articles about conflicts, they should get integrated in to Template:Infobox military conflict. — xaosflux Talk 12:09, 20 June 2021 (UTC)
:::Template:Infobox military conflict contains a campaignbox parameter that allows campaign boxes to be included. Some campaigns are important enough to have many articles and some are not. But not all articles using a particular campaignbox is a campaign; only the top level one. Hawkeye7 (discuss) 00:29, 21 June 2021 (UTC)
:::I think my use of non-technical may have confused the issue, I was looking for a simple answer in layman's terms since a lot of the terminology is over my head. Is this change from {{tl|Campaignbox Peninsular War (1810–1811)}} to {{tl|Peninsular War 1810 1811 mobile}} something that actually needs doing from a technical standpoint? FDW777 (talk) 12:11, 20 June 2021 (UTC)
::::TFD opened on that at Wikipedia:Templates_for_discussion/Log/2021_June_20#Template:Peninsular_War_1810_1811_mobile. — xaosflux Talk 16:07, 20 June 2021 (UTC)
::::Are WP:MILHIST aware of what has been happening? --Redrose64 🌹 (talk) 23:35, 20 June 2021 (UTC)
:::::Yes. See Wikipedia talk:WikiProject Military history#"Hubs". This was considered a more appropriate forum for the discussion. Hawkeye7 (discuss) 23:59, 20 June 2021 (UTC)
review/approve-a?
Which combination of page protections, user rights, and actions produces review/approve-a in the logs? -- RoySmith (talk) 00:07, 21 June 2021 (UTC)
: It appears to mean any autoconfirmed user making an edit to a Pending Changes-protected page that doesn't have any pending edits (and thus their edit being automatically approved) * Pppery * it has begun... 00:16, 21 June 2021 (UTC)
::Thanks. I'm seeing these on Tim Duncan, so that makes sense. -- RoySmith (talk) 01:06, 21 June 2021 (UTC)
Article paragraphs
Since the last time when I open an article, the paragraphs open automatically, please fix the bug and make it open manually. Mohmad Abdul sahib☆(message☎me!) 19:38, 19 June 2021 (UTC)
:Mohmad Abdul sahib, try going to Special:MobileOptions and turning off "Expand all sections". See if that fixes your issue. – Rummskartoffel 20:54, 19 June 2021 (UTC)
::User:Rummskartoffel good, but Why did I not receive a notification of your reply?Mohmad Abdul sahib☆(message☎me!) 14:29, 20 June 2021 (UTC)
:::Mohmad Abdul sahib, the notification was successfully sent on my end. Try checking your notification settings at {{myprefs|Notifications}}. – Rummskartoffel 16:26, 20 June 2021 (UTC)
:::: {{re|Mohmad Abdul sahib}} Notifications to mobile users are not very prominent, and in some cases are not shown at all. See the discussion at Wikipedia:Village_pump_(WMF) RudolfRed (talk) 02:50, 21 June 2021 (UTC)
Help on "nested templates"
Firstly, Im not sure if this is the correct forum for "how to..." questions - if not, please re-direct me!
I have created a template related to the civil war and mercenary involvement in the Congo in the 1960's - this is the template, let's call it Target Template:
{{Template:Congo Conflict: 1960 - 1968|state=collapse}}
The section titled "Main Operations and Battles" contains a list of events that is described in another template - below is the one concerned - lets call this one Source Template:
{{Template:Congo Crisis|state=collapse}}
The "Source Template" data for "Main Operations and Battles" is the primary data and is maintained in "Source Template" by unknown editors. To keep "Target Template" up to date, I can (a.) copy all the "Main Operations and Battles" wiki-links from "Source Template"' to "Target Template" [this is what I have done] and check from time to time that any changes made to "Source Template" is manually replicated to "Target Template;" or (b.) nest the data from "Source Template" directly inside "Target Template" so that it is only maintained in "Source Template."
I want to use option (b.) - please assist in letting me know how to do this? Farawayman (talk) 20:09, 16 June 2021 (UTC)
:Since the data is stored as an identical list in both templates, you could make a sub-template (e.g. Template:Congo Crisis/data) that contains only that list and have both Template:Congo Crisis and Template:Congo Conflict: 1960 - 1968 {{small|(that name seems a bit unwieldy to me, by the way, why not just call it something like Template:Congo Crisis navigation)}} transclude that template as the value for their respective relevant parameters. You should probably obtain consensus on Template talk:Congo Crisis before making such a change, though. – Rummskartoffel 20:45, 16 June 2021 (UTC)
:See Help:Labeled section transclusion. PrimeHunter (talk) 20:46, 16 June 2021 (UTC)
::Rather complicated, but I'll give it a try. Thanks Rummskartoffel and PrimeHunter Farawayman (talk) 14:14, 17 June 2021 (UTC)
:::Doesn't seem to work for templates - one has to use the "# tag" function instead..... I think we will have to maintain the data in two places! Please see attempt at Source Template Farawayman (talk) 23:29, 17 June 2021 (UTC)
::::There appears to be an undocumented limitation: Labeled section transclusion doesn't work when the marked section is part of a template parameter. PrimeHunter (talk) 01:53, 18 June 2021 (UTC)
::::: Yes, there is a limitation when transcluding from templates that I never quite understood. A workaround is to use lua to to get the section content. I set up something that works in {{tl|section/sandbox}} a couple of years ago but there was no follow-up. I've used it to show that it works in this case in {{tl|Congo Conflict: 1960–1968/sandbox}}. There are a number of other modules (e.g. Module:Excerpt) that might be suitable and more developed. — Jts1882 | talk 08:17, 18 June 2021 (UTC)
::::::Please see comment at Template talk:Congo Crisis - we are going the right way!!! Need to make it work outside of sandbox now. Thanks to all. Farawayman (talk) 01:47, 19 June 2021 (UTC)
::::::: The partial translusion of a labelled section within a template parameter can be done with the existing template ({{tl|excerpt}}) (using Module:Excerpt) using the same Lua method I used (but with more checks and options). I've used that to make the change to {{tl|Congo Conflict: 1960–1968}}. — Jts1882 | talk 08:24, 19 June 2021 (UTC)
:::::::: A better solution is to use Module:Transcluder directly. Excerpt uses this module, but wraps the content returned with additional HTML. — Jts1882 | talk 10:11, 21 June 2021 (UTC)
Show all
Is there a gadget to expand all collapsed sections on a page, including nested ones? An article like My Little Television needs over 50 clicks to show all its content, which can be inconvenient when searching. I could probably throw some JavaScript together to fiddle with the mw-collapsible-* classes but the idea seems too obvious to be original, so I expect this wheel has already been invented. Certes (talk) 17:00, 20 June 2021 (UTC)
:$('.mw-collapsed').each(function () { $(this).data('mwCollapsible').expand() }); would do it, but they shouldn't be collapsed in the first place per MOS:DONTHIDE. Nardog (talk) 17:09, 20 June 2021 (UTC)
::Thank you; that works beautifully as a bookmarklet and will save me much clicking. Certes (talk) 13:54, 21 June 2021 (UTC)
Copying text
I, being a mobile user, cannot copy text from a page's normal view, and have to into editing mode to do it, which can be problematic on pages using {{PAGENAME}} and similar. Is there a way around this? ― Qwerfjkl | 𝕋𝔸𝕃𝕂 (please use {{tlx|reply to|Qwerfjkl}} on reply) 15:05, 21 June 2021 (UTC)
:Maybe try a different web browser or app? I have no trouble copying text in the Read mode on mobile view (using Safari on iOS or Firefox on Mac OS). – Jonesey95 (talk) 15:22, 21 June 2021 (UTC)
[[m:Special:MyLanguage/Tech/News/2021/25|Tech News: 2021-25]]
Latest tech news from the Wikimedia technical community. Please tell other users about these changes. Not all changes will affect you. Translations are available.
Recent changes
- File:Octicons-tools.svg The
otrs-member
group name is now vrt-permissions
. This could affect abuse filters. [https://phabricator.wikimedia.org/T280615]
Problems
- You will be able to read but not edit German Wikipedia, English Wikivoyage and 29 smaller wikis for a few minutes on 22 June. This is planned between [https://www.timeanddate.com/worldclock/fixedtime.html?iso=20210623T0500 5:00 and 5:30 UTC]. [https://phabricator.wikimedia.org/T284530]
Changes later this week
- File:Octicons-sync.svg The new version of MediaWiki will be on test wikis and MediaWiki.org from {{#time:j xg|2021-06-22|en}}. It will be on non-Wikipedia wikis and some Wikipedias from {{#time:j xg|2021-06-23|en}}. It will be on all wikis from {{#time:j xg|2021-06-24|en}} (calendar).
Tech news prepared by Tech News writers and posted by bot • Contribute • Translate • Get help • Give feedback • Subscribe or unsubscribe.
15:47, 21 June 2021 (UTC)
Graphs
How to create such graphs? I know that external application for it is needed. Eurohunter (talk) 22:46, 21 June 2021 (UTC)
:Use Template:Graph:Chart, with the "type = line" parameter option. No need to create an file. Use the xAxisTitle and yAxisTitle parameters to name the axis.--Snævar (talk) 00:42, 22 June 2021 (UTC)
:: {{re|Snævar}} Thanks but probably only 1-2 could be used for article and on Commons there could more of them (extension). Eurohunter (talk) 11:05, 22 June 2021 (UTC)
Raw link
I'm looking for a template to strip formatting from a wikilink and give me the raw target. {{tl|Delink}} works quite well but for piped links it gives me the label instead of the target.
For example, I want:
I did try using Module:String a regular expression but the pipe character is confusing things. Thanks — Martin (MSGJ · talk) 06:49, 22 June 2021 (UTC)
:It would seem that you should be able to modify delinkWikilink(s)
at Module:Delink#L-38 to do that because titlearea
(poorly named, that) gets the target article name so you could return it after Module:Delink#L-59?
:—Trappist the monk (talk) 11:51, 22 June 2021 (UTC)
::An additional function on that module would be great, if you had time to implement please — Martin (MSGJ · talk) 12:46, 22 June 2021 (UTC)
:::Hacked the sandbox:
:::*{{delink/sandbox|Liloan|wikilinks=}} ← {{delink|Liloan|wikilinks=}}
:::*{{delink/sandbox|Liloan|wikilinks=no}} ← {{delink|Liloan|wikilinks=no}}
:::*{{delink/sandbox|Liloan|wikilinks=yes}} ← {{delink|Liloan|wikilinks=yes}}
:::*{{delink/sandbox|Liloan|wikilinks=target}} ← {{delink|Liloan|wikilinks=target}}
:::*{{delink/sandbox|Liloan|wikilinks=target}} ← {{delink||wikilinks=target}}
:::*{{delink/sandbox|Liloan, Cebu|wikilinks=target}} ← {{delink|Liloan, Cebu|wikilinks=target}}
:::that what you want?
:::—Trappist the monk (talk) 14:09, 22 June 2021 (UTC)
::::Amazing, thank you! — Martin (MSGJ · talk) 17:04, 22 June 2021 (UTC)
:::::Ok, I'll update the live version of the template.
:::::—Trappist the monk (talk) 19:06, 22 June 2021 (UTC)
:By String ({{tlx|!}} is a {{!}}
):
:{{mlx|String|match|s{{=}}Liloan|pattern{{=}}%[%[([^]{{tlx|!}}]+)|plain{{=}}0|nomatch{{=}}}} MarMi wiki (talk) 22:21, 22 June 2021 (UTC)
Gif question
If anyone can help, there is a gif I'm using on Cai Lun's article. However, at FAC, two users have expressed that it goes rather quickly between images (an insight I agree with); I attempted to use [https://ezgif.com/maker this website] to slow down the process to five seconds per image, but when I uploaded it, it became exact some speed. Any advice or solutions would be appreciated—and apologies if this is the wrong forum for such a query. Best - Aza24 (talk) 22:38, 22 June 2021 (UTC)
:Runs at a very comfortable 5s per frame for me. FF on Vista(!) on a low-memory notebook. — JohnFromPinckney (talk / edits) 23:48, 22 June 2021 (UTC)
::Indeed! I seem to have been nothing but impatient, it probably took a second for it to update is all. Aza24 (talk) 00:20, 23 June 2021 (UTC)
Tooltip for WikiMiniAtlas coordinates inside a File template is cut off
When WikiMiniAtlas coordinates are inside a File template in an article, the tooltip is cut off by the image box and is not shown outside of it, as can be seen on this page. I tested this on Windows 10 in Firefox, Chrome and Edge. Does anyone else have this problem? DxhaFFer (talk) 14:37, 22 June 2021 (UTC)
Gallery widths
{{tracked|T214320}}
Is there any way to get a gallery to display on a specified number of lines (for desktop)? I got the one here to display nicely on one full line on my display, but when I tried a different monitor it went onto a second line. There doesn't seem to be anything at Help:Gallery tag, so I'm thinking it might be necessary to use some HTML in the widths parameter or something like that. {{u|Sdkb}} talk 23:08, 22 June 2021 (UTC)
:Why don't you want me (or some other users) to easily see Walker Beach, looking south? What's wrong with the gallery wrapping responsively so I don't have to horizontally scroll? — JohnFromPinckney (talk / edits) 23:51, 22 June 2021 (UTC)
::{{Re|JohnFromPinckney}} I'm not looking to require horizontal scrolling, I'm looking for the pictures to be adaptively resized. {{u|Sdkb}} talk 00:29, 23 June 2021 (UTC)
:::That doesn't sound like it would work very well on mobile, or on narrow desktop screens/narrow browser windows. — Goszei (talk) 00:46, 23 June 2021 (UTC)
:::Ah, sorry, I hadn't understood that. Are you helped by the cats example at Help:Pictures#Galleries? you may also find something useful at mw:Help:Images. — JohnFromPinckney (talk / edits) 00:51, 23 June 2021 (UTC)
::::Looking further, I found the "perrow" parameter; it just doesn't seem to work for galleries in packed mode. @Goszei, for mobile/smaller devices, the galleries will definitely need to go onto multiple lines; the thing I'm trying to prevent is just the situation where 6 photos are on one line and 1 goes onto the next. {{u|Sdkb}} talk 03:01, 23 June 2021 (UTC)
:::::I found the relevant phab task: phab:T214320. No action since Jan. 2019. {{u|Sdkb}} talk 03:18, 23 June 2021 (UTC)
TemplateScript error
{{resolved}}
I get
Uncaught ReferenceError: pathoschild is not defined
at :5:89
at domEval (/w/load.php?lang=en&modules=startup&only=scripts&raw=1&skin=vector:11)
at runScript (/w/load.php?lang=en&modules=startup&only=scripts&raw=1&skin=vector:13)
at enqueue (/w/load.php?lang=en&modules=startup&only=scripts&raw=1&skin=vector:11)
at execute (/w/load.php?lang=en&modules=startup&only=scripts&raw=1&skin=vector:14)
at doPropagation (/w/load.php?lang=en&modules=startup&only=scripts&raw=1&skin=vector:6)
when running this code:
pathoschild.TemplateScript.add({
name:'ScriptInstallation',
script: function(editor) {
editor
.prepend('== Installation ==')
.prepend(';Method 1:')
.prepend('Get ScriptInstaller, then navigate to {{FULLPAGENAME}}.js and click "Install" at the top.')
.prepend(';Method 2:')
.prepend('(This can be used on any-language Wikipedia.)')
.prepend('# Place {{tlx|lusc|1{{=}}{{FULLPAGENAME}}.js}} on the bottom of Special:MyPage/common.js or Special:MyPage/skin.js.')
.prepend('# Press "Publish Changes".')
.prepend(';Method 3:')
.prepend('(This can only be used on the English Wikipedia.)')
.prepend('# Place {{tlx|iusc|1{{=}}{{FULLPAGENAME}}.js}} on the bottom of Special:MyPage/common.js or Special:MyPage/skin.js.')
.prepend('# Press "Publish Changes"')
.appendEditSummary('Added script installation text')
.clickDiff();
}
});
―
Qwerfjkl | 𝕋𝔸𝕃𝕂 (please use {{tlx|reply to|Qwerfjkl}} on reply) 17:27, 21 June 2021 (UTC)
:What do you believe pathoschild should be? Is this code part of a larger script? — GhostInTheMachine talk to me 17:53, 21 June 2021 (UTC)
::@GhostInTheMachine This is made using TemplateScript. ― Qwerfjkl | 𝕋𝔸𝕃𝕂 (please use {{tlx|reply to|Qwerfjkl}} on reply) 18:10, 21 June 2021 (UTC)
::: The code above assumes that {{code|pathoschild.templatescript.js}} is already loaded. Your common.js calls the loader and then runs the above code straight away. This does not give any time for {{code|templatescript.js}} to be fetched and so it has not yet defined the {{code|pathoschild}} object. Take a look at mw.loader.using or TemplateScript as a gadget or framework for ways to defer your code to after the script has loaded — GhostInTheMachine talk to me 19:01, 21 June 2021 (UTC)
::::@GhostInTheMachine Thanks, that fixed it. How do you add a new line e.g. editor.prepend('some text{newline]')
? ― Qwerfjkl | 𝕋𝔸𝕃𝕂 (please use {{tlx|reply to|Qwerfjkl}} on reply) 13:22, 23 June 2021 (UTC)
:::::@Qwerfjkl: Use {{code|\n}} to create a line break, e.g. {{code|lang=js|editor.prepend("Line 1\nLine 2")}}. – Rummskartoffel 15:20, 23 June 2021 (UTC)
::::::@Rummskartoffel Thanks, I was using /n
. {{facepalm}} ― Qwerfjkl | 𝕋𝔸𝕃𝕂 (please use {{tlx|reply to|Qwerfjkl}} on reply) 15:42, 23 June 2021 (UTC)
Updated blank map with national borders?
Is there updated version of [https://commons.wikimedia.org/wiki/File:The_Spectre_charts_map.png this] blank map with national borders? The other question is how to edit it expect Paint? Eurohunter (talk) 18:52, 23 June 2021 (UTC)
Odd watchlist note
When I check my watchlist the Navajo line has an odd note beside it - a small clock symbol - and when I hover over it "30 days left on your watchlist" shows up. When did that start and why? Vsmith (talk) 16:14, 23 June 2021 (UTC)
:Hey, Vsmith, this is the relatively new [https://www.mediawiki.org/wiki/Help:Watchlist_expiry watchlist expiry] feature. I think that, wehn one interacts with a page via Twinkle as [https://en.wikipedia.org/w/index.php?title=Navajo&diff=1030020682&oldid=1030016573 you did with Navajo here], Twinkle uses that new feature to add the page to your watchlist for 30 days, after which it'll disappear. This can be changed in your Twinkle preferences, as described in the Twinkle documentation. Writ Keeper ⚇♔ 16:20, 23 June 2021 (UTC)
::Thanks, wasn't aware of that ... I'll avoid that twinkle bit or twiddle with prefs. I've got a huge watchlist that needs trimming ... tried once, but Wiki timed out trying to load it :) Vsmith (talk) 17:56, 23 June 2021 (UTC)
:::{{re|Vsmith}} try raw mode here: Special:EditWatchlist/raw. — xaosflux Talk 18:53, 23 June 2021 (UTC)
:: This is a great addition. There are loads of pages on my watchlist where I made an edit and wanted to see any follow-up and years later they are still there. Setting the watch to a week or a month is very useful. — Jts1882 | talk 19:46, 23 June 2021 (UTC)
Proposal: Show amboxes (article message boxes) by default on mobile devices
On desktop, amboxes are considered important enough to display even to non-editors. This is used by non-editors to recognize when there are potential issues with an article on WP. But on the mobile versions of Wikipedia, the amboxes are hidden or relegated to a subpage (E.g. on the Wikipedia iOS app, amboxes are not displayed but instead there is a link "page issues" at the end of the article.)
My opinion is, we should give amboxes similar prominence on mobile that we give them on desktop. I.e. display them at the top of the page or section. 15:44, 20 June 2021 (UTC) TOA The owner of all ☑️
:The mobile display of ambox, as well as certain other elements on the mobile version, is still basically being controlled by the Wikimedia Foundation's developers. I believe that your suggestion that we do here will be overridden with code that they control on the mobile version. :MW:Reading/Web/Projects/Mobile Page Issues probably best describes what they have been specifically doing with ambox. :MW:Reading/Mobile Friendly Content probably best describes what they are trying to accomplish overall: basically, the MediaWiki software was not initially designed with responsive web design by default, and many existing elements are only optimised for desktop browsers, so they still want to find ways make these things more mobile friendly. Thus, you might want to instead post your suggestion at :MW:Talk:Reading/Web/Projects/Mobile Page Issues. Zzyzx11 (talk) 02:01, 24 June 2021 (UTC)
Page tagged for speedy, did not get added to watchlist
I recently tagged a page for speedy deletion using those tabs at the top of the page (can't remember what they are called). The tagging happened correctly, the creator was messaged, but the page itself did not then appear on my watchlist. I'm sure when I've done this before the pages were added to my watchlist. DuncanHill (talk) 23:21, 22 June 2021 (UTC)
:Judging from your contribs, those tabs are probably Wikipedia:Twinkle. Some of the CSD don't cause the page in question to be put on the watchlist by default, but you can configure that on a per-criterion basis at Wikipedia:Twinkle/Preferences#speedy. – Rummskartoffel 12:00, 23 June 2021 (UTC)
::{{re|Rummskartoffel}} Thanks - yes Twinkle is it, and thanks for the pointer to the settings page, very useful DuncanHill (talk) 02:48, 24 June 2021 (UTC)
Freenode IRC servers 'takeover'
{{User:ClueBot III/DoNotArchiveUntil|1624568478}}
Background
- https://www.kline.sh/
- https://www.vice.com/en/article/m7ev8y/freenode-open-source-korea-crown-prince-takeover
- https://boingboing.net/2021/05/19/freenode-irc-staff-quit-after-new-owner-seizes-control.html
Traditionally, WMF projects and volunteers coordinated on Freenode IRC servers. Should we migrate (or aim to migrate) these projects to Libera Chat instead? Headbomb {t · c · p · b} 20:13, 20 May 2021 (UTC)
= Discussion =
The question here is to address what we should general aim to try to do. I'm well aware each project is independent and can setup IRC channels wherever they want. However, we could decide that we encourage specific servers and discourage others, and try to migrate the 'official' Wikipedia/Wikimedia IRC channels to Libera instead of Freenode. Headbomb {t · c · p · b} 20:17, 20 May 2021 (UTC)
:I don't see that this needs an RFC? Wikimedia group contacts have already announced they will migrate to Libera on meta. Izno (talk) 20:22, 20 May 2021 (UTC)
::This affects a lot more than what the WMF does. For example, there's #wikipedia-bag, #wikipedia-en-afc in templates like {{tl|AfC welcome}} (including substed version of it), etc. etc. etc. Headbomb {t · c · p · b} 20:41, 20 May 2021 (UTC)
:::So, why would we go somewhere else? Who has the knowledge in the community for that? Who wants to volunteer for that? Izno (talk) 20:46, 20 May 2021 (UTC)
::::See the above articles. As for who has the knowledge, there's busloads of technical users here that can help with this. Headbomb {t · c · p · b} 20:48, 20 May 2021 (UTC)
:::::Ok, let me spell it out then: A) We don't need an RFC. An RFC is a waste of the community's time on the point. B) Plain common sense is "go where WMF says they're taking the main channels". Izno (talk) 20:53, 20 May 2021 (UTC)
::::::[https://lists.wikimedia.org/hyperkitty/list/cloud-announce@lists.wikimedia.org/thread/DWDCL4PY446RUGR7EJKKPBJLOT45QFMI/ Also see here]. -- RoySmith (talk) 21:04, 20 May 2021 (UTC)
:::If I understand correctly, the channels were set up by the individual channel operators? So I suggest they can come up with a proposed plan and publicize it. I imagine most people will be fine with that, but in the event anyone objects, it can be discussed further. (Just as at meta, there may be interest in other chat tools, but that shouldn't stop any transition plan under these specific circumstances.) isaacl (talk) 21:06, 20 May 2021 (UTC)
:Wikimedia is migrating to Libera Chat, [https://meta.wikimedia.org/w/index.php?title=Wikimedia_Forum&type=revision&diff=21476411&oldid=21475994 that was announced by the IRC Group Contacts] already. See IRC/Migrating to Libera Chat for some of the technical details, it'll of course take time to update documentation, links etc. Legoktm (talk) 21:43, 20 May 2021 (UTC)
:RfC tag removed per discussion above; if this is about notifying as many users as possible rather than inviting feedback, the Signpost and WP:AN are probably better places for a notification. There is one at Wikipedia:Administrators'_noticeboard#IRC_security,_Oversight_notice. ~ ToBeFree (talk) 22:49, 20 May 2021 (UTC)
::{{replyto|ToBeFree}} You didn't remove it, you commented it out. There is a difference. --Redrose64 🌹 (talk) 19:25, 21 May 2021 (UTC)
:::...and I had even looked at that section. File:Emoji_u1f604.svg Thanks for removing it. ~ ToBeFree (talk) 19:27, 21 May 2021 (UTC)
Enhanced watchlist on mobile
Is there a setting to make the enhanced watchlist (that which groups changes to the same page) show up on mobile? Cheers. — 𝐆𝐮𝐚𝐫𝐚𝐩𝐢𝐫𝐚𝐧𝐠𝐚 ☎ 03:17, 24 June 2021 (UTC)
:{{u|Guarapiranga}}, yes you can enable that in your Preferences > Recent changes > Advanced options. enjoyer -- talk 21:54, 25 June 2021 (UTC)
::Thanks, {{u|Enjoyer of World|enjoyer}}. I do have it set, though (globally). I get the grouping on desktop (Vector) but not mobile (Minerva). — 𝐆𝐮𝐚𝐫𝐚𝐩𝐢𝐫𝐚𝐧𝐠𝐚 ☎ 22:18, 25 June 2021 (UTC)
Updated Special pages
{{resolved|Fixed server side. — xaosflux Talk 08:29, 26 June 2021 (UTC)}}
{{tracked|T285538|resolved}}
Hello, Tech folks,
Special:WantedCategories and Special:UnusedCategories always update every 3 days, starting on the first day of the month but they haven't updated today. I have no idea what bot or program is responsible for updating Special pages and these pages have no edit history to check. They have talk pages but not ones that anyone ever checks. Any ideas? Is there a general lag today? Liz Read! Talk! 19:52, 25 June 2021 (UTC)
:{{re|Liz}} this happens on the back-end by a cron job, {{tq|the Job gets run every three days, but can take more than a day to get through the list.}} So unless it is a couple of days over, its not worth raising a phab ticket yet. — xaosflux Talk 20:10, 25 June 2021 (UTC)
::Hmmm, seems to be globally delayed. Looking if there is already a ticket. — xaosflux Talk 20:14, 25 June 2021 (UTC)
:phab:T285583 opened on this. — xaosflux Talk 20:20, 25 June 2021 (UTC)
::Wow, that's great, Xaosflux. Thank you. It's great we have this forum to ask questions for those of us not technically-minded. Liz Read! Talk! 20:22, 25 June 2021 (UTC)
:::{{re|Liz}} OK, just FYI this is now phab:T285538; which is marked 'resolved' - but please note that only means the underlying problem is resolved, not the instance of the problem. So the job that updates these is allegedly running now, but it may take time to realize the update. — xaosflux Talk 20:25, 25 June 2021 (UTC)
::::If anything is urgently needed, please poke someone and we can get a member of SRE to run it but otherwise it will just pick up on its next normal run. ~ RhinosF1(Chat) / (Contribs) 20:27, 25 June 2021 (UTC)
::::Legoktm has just pushed an early/additional run of the job to update special pages. ~ RhinosF1(Chat) / (Contribs) 20:30, 25 June 2021 (UTC)
:::::Thank you both! Liz Read! Talk! 21:05, 25 June 2021 (UTC)
::The pages still haven't updated. Do you think the system will wait until June 28th to update these pages? Liz Read! Talk! 03:21, 26 June 2021 (UTC)
:::@Liz: the pages updated now, it just took a while. And it should be back on the normal schedule going forward. Legoktm (talk) 07:33, 26 June 2021 (UTC)
Edit lead section only
{{resolved|Gadget is working. — xaosflux Talk 10:55, 24 June 2021 (UTC)}}
I thought once upon a time, we were able to just open the lead section and edit it. I don't see such a link now. Did I imagine such a thing existed? Did I change some preference that took it away? I use Modern skin. — Maile (talk) 02:22, 24 June 2021 (UTC)
:{{re|Maile66}} Is it not available in the "Appearance" section of Special:Preferences#mw-prefsection-gadgets? Sdrqaz (talk) 03:12, 24 June 2021 (UTC)
::Yes, it's there all right. And I apparently already had it checked. But in editing any article, that lead section link is not available. Not in Chrome, and not in Firefox. Hmmmm. — Maile (talk) 10:04, 24 June 2021 (UTC)
:{{works for me}} {{ping|Maile66}} the gadget places the [edit]
link at the end of the page title. Are you using the desktop site? Which skin are you using? — xaosflux Talk 10:19, 24 June 2021 (UTC)
::I'm using Modern skin, and have been using it for years. What is the desktop site? — Maile (talk) 10:32, 24 June 2021 (UTC) Nevermind. It was there all along, but I was looking in the wrong place. — Maile (talk) 10:33, 24 June 2021 (UTC)
:::I can totally understand not seeing it. Putting the link next to the title is not an intuitive place for "click me to edit the lead". If I didn't know what it was, I would guess it was either "click me to edit the title" (i.e. rename the article), or "click me to edit the whole article" (i.e. a duplicate of the Edit link in the header bar). -- RoySmith (talk) 14:32, 24 June 2021 (UTC)
::::{{re|RoySmith}} it does have a tool tip label of "Edit lead section", and all other sections have the edit link next to the header name. I suppose it could inject a new L2 header called something like "== Lead ==" and put it there maybe? If you have some good ideas for improvement, please feel free to follow up at MediaWiki talk:Gadget-edittop.js. — xaosflux Talk 14:42, 24 June 2021 (UTC)
:::::File:Screenshot_showing_UI_idea_for_editing_lead.png
:::::Ah, so it does. I never noticed that before. Perhaps instead of just the tooltip, it could alter the displayed text? -- RoySmith (talk) 14:50, 24 June 2021 (UTC)
::::::It currently makes use of a single message file there, likely so that it is translated automatically. Drop your suggestion at MediaWiki talk:Gadget-edittop.js and maybe someone will look in to it (or feel free to sandbox a new script if you would like). — xaosflux Talk 08:32, 26 June 2021 (UTC)
:::::::Yup, I commented there as well. Note, I'm not complaining. I mostly stick to the backend because it's a lot easier than UI :-) -- RoySmith (talk) 16:05, 26 June 2021 (UTC)
Proposal for a bot to substitute uses of [[Template:Date]] in articles as a one-time run
I've filed a BRFA that proposes a task to substitute all uses of {{tl|date}} in mainspace, given that (a) its documentation says that it should only be used within other templates, and (b) there is no need to use the template in articles, simply writing out the date serves the same purpose.
This is technically a cosmetic task, as the rendered wikitext wouldn't change - I would hope that some latitude can be extended given that it would be a one-time run, and is "enforcing" (for want of a better word) existing documentation. Of course, we may decide that the documentation doesn't accurately reflect consensus - in that case the BRFA can be withdrawn/denied and the documentation updated.
It may be best for comments to be made at the BRFA to keep things in one place, although I'm equally happy for the discussion to happen here. Thanks! firefly ( t · c ) 17:20, 27 June 2021 (UTC)
CSS alignment question
Does anyone know how to get the shortcut box at Wikipedia:Task Center to the top of the page without pushing the header box off-center? {{u|Sdkb}} talk 20:54, 27 June 2021 (UTC)
:Not fundamentally possible without resorting to CSS in the task center page itself. I do not think you want to do that. Izno (talk) 21:55, 27 June 2021 (UTC)
::Is there a reason I wouldn't want to do that? This problem of trying to add elements to the side without disturbing elements in the center keeps on coming up, and I haven't memorized exactly how to solve it but I'm pretty sure it's solvable. {{u|Sdkb}} talk 22:52, 27 June 2021 (UTC)
:::You can do it in code (but someone else may revert the changes) or in your custom css (Special:Preferences#mw-prefsection-rendering):
:::If you just want to move shortcuts before the header, move the div with it before the header, and put {{tlx|clear}} (or apply the style clear
to the div) just after the div.
:::If you want to put shortcuts to float on top of the header, use position:absolute
(with z-index:1
to make it on top). MarMi wiki (talk) 23:43, 27 June 2021 (UTC)
Crosswiki notifications and the responsive monobook skin
I use the responsive monobook skin, which changes several things depending on the size of my window/screen. When I receive a crosswiki notification, it shows up as a little blue "1" in the notifications inbox in both designs. However, if I click on it to see the notification, I can only see it in the classic design. There is no "notifications from another wiki" message in the small-screen/mobile version (but all notifications from enwiki are visible there). There seems to be no way to find out what a crosswiki blue 1 is about without changing screen size / turning off the responsive design. Is this intentional? If no, can this be fixed? If yes, why? Could crosswiki notifications at least have a different colour? (So I know I can't read them on my phone and will have to wait until I get back to my desktop). The software telling me I have messages but sometimes not telling me what they are isn't great. —Kusma (talk) 08:57, 19 June 2021 (UTC)
:The problem also occurs in Vector, actually. The only information about crosswiki notifications is in the "Recent activity" box, which disappears without a trace when the screen/window size is too small. So if you get a crosswiki ping, you can't tell where it came from and you can't clear it from your inbox. I dpn't quite know where to report this. —Kusma (talk) 18:52, 24 June 2021 (UTC)
::Maybe somewhere related to mw:Extension:Echo? – Rummskartoffel 14:07, 25 June 2021 (UTC)
:::I'll try, but it could be argued that this is not a bug in Echo, but in the skins. —Kusma (talk) 14:27, 27 June 2021 (UTC)
Turning Javascript off makes the "Recent activity" box on Special:Notifications disappear. Does anybody know which piece of code produces it? —Kusma (talk) 11:29, 28 June 2021 (UTC)
:Echo/modules/ui/mw.echo.ui.CrossWikiUnreadFilterWidget.js and its sibling files, I think. – Rummskartoffel 11:47, 28 June 2021 (UTC)
::Thanks! So it is a bit of an add-on, not a core function of Echo? And why does it disappear on small screens? —Kusma (talk) 13:21, 28 June 2021 (UTC)
:::That I don't know for sure, but my guess is that it is a core function, but one that just doesn't work without JS, so that there's no point loading it with JS off. The reason it disappears seems to be phab:diffusion/ECHO/browse/master/modules/styles/mw.echo.ui.NotificationsInboxWidget.less$104, initially added for phab:T140687 in phab:rECHO8a69d86d181a87aa7113e8e488f062ab24517e63, hiding the sidebar on screens less than 982 px in width. On mobile (i.e. en.m.wikipedia.org instead of en.wikipedia.org), regardless of screen size or skin, a "Filter notifications" button is added that provides access to "Recent activity". – Rummskartoffel 14:16, 28 June 2021 (UTC)
Adding .mw-echo-ui-notificationsInboxWidget-sidebar {display:block;}
to User:Kusma/monobook.css unhides the Recent activity box. It is a rather ugly workaround (I have to scroll to the side on my phone), but I don't speak CSS so I can't fix this. Thank you {{U|Rummskartoffel}} for the help! —Kusma (talk) 14:51, 28 June 2021 (UTC)
[[m:Special:MyLanguage/Tech/News/2021/26|Tech News: 2021-26]]
Latest tech news from the Wikimedia technical community. Please tell other users about these changes. Not all changes will affect you. Translations are available.
Recent changes
Problems
- You will be able to read but not edit the Wikimedia wikis for a few minutes on 29 June. This is planned at [https://www.timeanddate.com/worldclock/fixedtime.html?iso=20210629T1400 14:00 UTC]. [https://phabricator.wikimedia.org/T281515][https://phabricator.wikimedia.org/T281209]
Changes later this week
- File:Octicons-sync.svg The new version of MediaWiki will be on test wikis and MediaWiki.org from {{#time:j xg|2021-06-29|en}}. It will be on non-Wikipedia wikis and some Wikipedias from {{#time:j xg|2021-06-30|en}}. It will be on all wikis from {{#time:j xg|2021-07-01|en}} (calendar).
Future changes
Threshold for stub link formatting
, thumbnail size
and auto-number headings
can be set in preferences. They are expensive to maintain and few editors use them. The developers are planning to remove them. Removing them will make pages load faster. You can read more and give feedback.
- A toolbar will be added to the Reply tool's wikitext source mode. This will make it easier to link to pages and to ping other users. [https://phabricator.wikimedia.org/T276609][https://www.mediawiki.org/wiki/Talk_pages_project/Replying#Status_updates]
Tech news prepared by Tech News writers and posted by bot • Contribute • Translate • Get help • Give feedback • Subscribe or unsubscribe.
16:30, 28 June 2021 (UTC)
:I don't know if it will help, but I want to draw VPT editors' attention to the first item under "Future changes". The proposal is to eliminate custom the thumbnail size preference for editors (under Prefs - Appearance). The phab task states that only 4% of editors active in the last 30 days have this preference set, and it makes pages load slowly for us, so they want to get rid of it. See {{phab|T284920}} for details. – Jonesey95 (talk) 20:47, 28 June 2021 (UTC)
Blurry Wikipedia logo for Skin:Timeless
{{tracked|T279645}}
The Wikipedia logo shown on the left-hand-side panel with Skin:Timeless is a [https://en.wikipedia.org/static/images/mobile/copyright/wikipedia.png PNG image], but all other Wikimedia projects with Skin:Timeless use an SVG image for their logo. As the PNG logo is bitmap, the Wikipedia logo becomes blurry on higher-resolution displays, yet the SVG logo of Wikipedia is available. I also noticed that this issue happens across all Wikipedias so there should be a global solution for it. 🐱💬 11:32, 28 June 2021 (UTC)
:This is phab:T279645. PrimeHunter (talk) 11:39, 28 June 2021 (UTC)
:Also Wikipedia:Village pump (technical)/Archive 188#The logo looks blurry in Timeless skin. --Redrose64 🌹 (talk) 20:50, 28 June 2021 (UTC)
Pinging all members of a user category
At the current FARC for Duke University, I'm wondering if there's any easy way to simultaneously ping all 50 members of Category:Wikipedians by alma mater: Duke University. I've seen this done fairly often at Wikidata, but I'm not sure if the same functionality exists here. If not, I think it'd be a nice thing to create. We would probably want to build a safeguard to prevent abuse by limiting it to categories with, say, less than 100 members. {{u|Sdkb}} talk 20:18, 28 June 2021 (UTC)
: Template:Mass notification (the equivalent of Wikidata's Template:Ping project) exists, but isn't used much and requires the relevant groups to be set up manually rather than getting them from a category. However, for reasons I explained back in December, templates can't access the contents of categories, so what you are asking for isn't possible. * Pppery * it has begun... 20:34, 28 June 2021 (UTC)
::What is easily doable is something like the following:
let api = new mw.Api();
await api
.get({
action: "query",
format: "json",
list: "categorymembers",
cmtitle: "Category:Wikipedians by alma mater: Duke University",
cmnamespace: "2",
cmlimit: "50",
formatversion: "2",
})
.then(response =>
response.query.categorymembers
.map(entry => `${entry.title.split("/")[0]}`)
.join(", ")
);
That leaves you with a string like this: User:Example, User:Example, User:Example ...
, which you can then just paste as wikitext. – Rummskartoffel 21:21, 28 June 2021 (UTC)
:::Thanks both. For my use case, how do I run that script? For helping others, I left another note at phab:T285612phab:T199126 to see if that spurs any progress. {{u|Sdkb}} talk 21:59, 28 June 2021 (UTC)
::::I usually just paste these kinds of things into my browser console ad-hoc, but I've thrown together a quick user script that adds a link to the portlet (left sidebar, at least on Vector and Monobook) under "Tools". If you click it when on a category that contains users, it'll pop up an alert box with the generated wikitext, from where you can copy it. It's not very pretty, and if you click it elsewhere, it'll probably break, but it should get the basic job done unless your browser's from the stone age. – Rummskartoffel 22:37, 28 June 2021 (UTC)
:::::@Rummskartoffel, thanks so much for putting that together! It doesn't seem to make anything show up for me, but if there's not an obvious bug, don't worry about it; the chance of reaching anyone through this willing to save Duke from delisting is pretty close to zero no matter what. {{u|Sdkb}} talk 03:29, 29 June 2021 (UTC)
::::::@Sdkb: That's because you didn't install it correctly 😜. Your common.js tries to import the documentation page (thanks for creating that, by the way), not the script itself. Try importScript( "User:Rummskartoffel/generate pings.js" ); instead. – Rummskartoffel 08:48, 29 June 2021 (UTC)
:::::::Ack, {{selftrout}}! {{u|Sdkb}} talk 08:52, 29 June 2021 (UTC)
::::What does phab:T285612 have to do with this? — xaosflux Talk 22:38, 28 June 2021 (UTC)
:::::I think they meant phab:T199126. Writ Keeper ⚇♔ 22:42, 28 June 2021 (UTC)
::::::Oops, yeah, that's the one I meant; thanks for catching and finding the correct link. There's a lot of problems on phabricator these days haha {{u|Sdkb}} talk 23:45, 28 June 2021 (UTC)
::::With regards to upper limits: there's a maximum number of people to ping built into the notification system. It just barely works for this category of 50, but any attempt to ping 51 people would fail (per mw:Manual:Echo) Vahurzpu (talk) 23:08, 28 June 2021 (UTC)
:Out of curiosity, why is "pinging" preferable to using WP:AWB (or Special:MassMessage) to message each of these editors? -FASTILY 22:27, 28 June 2021 (UTC)
::One edit instead of 50, and less chance of producing fragmented discussion? —Kusma (talk) 22:43, 28 June 2021 (UTC)
:::How would an invitation to participate in a WP:FAR discussion produce "fragmented discussion"? Just my 2c: pinging doesn't leave much of a paper trail and seems like a sneaky way to canvass; if you must canvass, might as well be open about it. -FASTILY 23:00, 28 June 2021 (UTC)
::::On the contrary, pinging is visible exactly where the discussion is taking place. Leaving 50 messages on talk pages may make people reply to the message on their talk pages instead of at the centralised discussion. —Kusma (talk) 23:05, 28 June 2021 (UTC)
::::But for "paper trail" reasons, the OP's suggestion to be able to ping the members of a category should probably not be implemented, unless there is a way to find out category membership at a given time in the past. —Kusma (talk) 23:11, 28 June 2021 (UTC)
Incorrect timeframe in notice
Where is the message that currently displays "Technical maintenance will be performed soon 05:00 UTC - 05:30 UTC During this time you might not be able to save any edits."? It's wrong; 05:00 UTC was more than eight hours ago. Judging by Tech News above, it should read 14:00 UTC to 14:30 UTC - can we get this changed? --Redrose64 🌹 (talk) 13:40, 29 June 2021 (UTC)
:I have a feeling that User:SGrabarczuk (WMF) might know; there are twelve minutes left. --Redrose64 🌹 (talk) 13:48, 29 June 2021 (UTC)
:: Fixed, sorry for inconvenience, and thanks for noticing. Do bear in mind that in practice, the read-only may last up to... 2 minutes, just as it was last year :) SGrabarczuk (WMF) (talk) 13:51, 29 June 2021 (UTC)
:::{{ty}} --Redrose64 🌹 (talk) 13:52, 29 June 2021 (UTC)
Why browsing wikipedia is much, much slower when logged in?
I have noticed this for quite a while so decided to do a quick test with it today (it's not meant to be super comprehensive so bear with me).
I open Phillip Davey with my dev tool opened and "Disable cache" checked. I then refresh the page 10 times to see the average loading time. Then I repeat it after logged out.
The difference is very obvious: ignoring any resources, only look at the first HTTP request for the HTML:
- Logged in: the average time is 520 ms.
- Logged out: the average time is 15 ms.
I understand it can't be as fast, but this is pretty bad and very noticeable when just browsing around. Is there anyway to improve it? Thanks! --fireattack (talk) 14:47, 28 June 2021 (UTC)
:Wildly uneducated question: do you have a lot of scripts and gadgets active? Are they hindering a speedy load? — JohnFromPinckney (talk / edits) 15:00, 28 June 2021 (UTC)
:Why would you keep the "Disable cache" checked? When you're logged in, more resources (such as gadgets you've enabled) are loaded so uncached loading time is expected to be larger. But the difference will be that much only on the first load if caching is enabled.
Also, there are a couple of preferences (see phab:T284917, phab:T284920, phab:T284921) that disable server-side caching and greatly slow down page loads. – SD0001 (talk) 15:01, 28 June 2021 (UTC)
::Good to know. Disabled, thanks. — 𝐆𝐮𝐚𝐫𝐚𝐩𝐢𝐫𝐚𝐧𝐠𝐚 ☎ 22:18, 28 June 2021 (UTC)
::Except... I can disable the global setting of thumb sizes, but can't disable it at enwiki; can only choose one. What's this referring to? {{tq2|An ad-hoc analysis among users of en.wikipedia.org who have edited in the last 30 days shows that about 4% of active editors have the "thumb size" option set.}} — 𝐆𝐮𝐚𝐫𝐚𝐩𝐢𝐫𝐚𝐧𝐠𝐚 ☎ 22:24, 28 June 2021 (UTC)
:: {{Replyto|SD0001}} to make the test more consistent. The result isn't much different without it, though, since the HTTP request for the page itself won't be (browser-side) cached anyway (it mainly affects the resource like JS or media). I checked the preferences you linked, I didn't enable any of them (except for the thumb size, which I didn't find a disable option. I use the default 220px). --fireattack (talk) 03:36, 29 June 2021 (UTC)
:Caching in general is not available for logged-in users. Some preferences (in addition to SD0001's) and all the gadgets you can enable, as well as simply not being set up for it from a data center level (that's :mediawikiwiki:Wikimedia Performance Team/Active-active MediaWiki, which means your traffic goes to the singular data center equipped for logged in edits). Izno (talk) 16:17, 28 June 2021 (UTC)
::Yes, for many operations your request has to travel all the way to the USA, which is a much longer/slower path for those far outside the USA than just getting some cached data from a geo localised caching center. —TheDJ (talk • contribs) 10:27, 29 June 2021 (UTC)
:This is a long-standing known issue due to the traditionally monolithic mediawiki architecture- all operations, including reads that are not cached, have to go to the primary datacenter. There is an Epic task {{phabricator|T270223}} that will mitigate that, talking the first step towards being able to serve read-only traffic from a remote (closer to you) datacenter. This, however is a complex issue, that has been prepared for a long time and will require a lot of work to be made possible (for example, what looks as a read only request sometimes gets converted to read-write, or has to write its cache, and consistency has to be kept between multiple geographically distributed locations)- as it requires new hardware, changing the application request workflow, and the data architecture for the application to be more "distributed".
:However, being able to make the site faster for contributors is the main goal of such a project. One thing that may not be seen is that anonymous browsing (readers without account) has been made much faster in the last years as more CDN trafic caching sites have been opened- and now it should be the turn of improving the experience for logged-in users, too. The Performance team is hard working at making this possible. Some extensions may need adjustments to take advantage of this and you could help with feedback and code! --JCrespo (WMF) (talk) 15:10, 29 June 2021 (UTC)
Wikipedia displaying as text only when Adblock enabled
Anyone else having this issue or is it just me? Satellizer el Bridget (Talk) 03:22, 29 June 2021 (UTC)
:no lots of people. Please complain with Adblock. —TheDJ (talk • contribs) 10:23, 29 June 2021 (UTC)
::There is this [https://www.theverge.com/2021/6/28/22554495/adblock-plus-filter-lists-wiki-reddit-twitter The Verge article] about this. --Trialpears (talk) 10:26, 29 June 2021 (UTC)
:::Adblock Plus should be avoided at all costs, [https://www.theverge.com/2016/9/13/12890050/adblock-plus-now-sells-ads they're sellouts] and run ads. If you haven't already, switch to uBlock Origin -FASTILY 21:50, 29 June 2021 (UTC)
:::{{replyto|Satellizer}} Not only that, there's absolutely no point in having ABP enabled for any wikimedia site - not long after installing it, I switched it off for en.wikipedia.org, en.wiktionary.org, commons.wikimedia.org, meta.wikimedia.org and several others because they never run adverts in the accepted sense - our occasional fundraisers are easily dismissed, and things like yesterday's notice about the read-only period I do need to see. Every time I see that red octagon on a Wikimedia site (such as those), it gets clicked and disabled. --Redrose64 🌹 (talk) 07:27, 30 June 2021 (UTC)
[[WP:SWEEP]] queries
At WikiProject Sweep, we're still stuck at the stage of trying to determine the criteria of the list of pages to be swept. Would anyone be able to answer or know where we could go to find the results of these queries?
- What percentage of articles created prior to 20 September 2012 have been edited by at least 3 extended-confirmed editors who have made a non-minor edit? What does a sample of these pages look like?
- What about for 5 EC editors, 10 EC editors, or 25 EC editors?
Cheers, {{u|Sdkb}} talk 09:04, 29 June 2021 (UTC)
:@Sdkb I'm not sure I understand the criteria. I assume you mean, "editors who were EC at the time they made their edit". If so, that sounds like a very expensive query, since you'd have to re-evaluate each editor's EC-ness as of the time of each edit. "Once EC, always EC", so you could do some caching, but, my first guess is this is probably still an intractable problem.
:It would be hugely more efficient if the criteria were "editors who are EC now". I assume you're using EC as a proxy for "is trustworthy". Let's assume that somebody who's trustworthy now was always trustworthy (even if they hadn't accumulated the editing history to demonstrate it yet). According to WP:EDITORS#Number of editors, there's only about 57k EC users (not sure if that includes admins; if not, then add another 1k), so if we can make that assumption, it would be a huge optimization.
:Reality check: there's 41M accounts, and 57k EC users. So only about 0.1% of accounts ever reach EC? Is that plausible? -- RoySmith (talk) 15:35, 29 June 2021 (UTC)
::EC was implemented on 2016-04-05, and former editors who made their last edit before then do not have it, even if they'd be eligible. That should cut the number down quite a bit. – Rummskartoffel 16:18, 29 June 2021 (UTC)
:::@RoySmith, you're correct; I'm using EC as a proxy for "experienced enough to know to tag/AfD the article if it's clearly warranted." EC at the time of the edit would be ideal, but if that's not possible, EC overall would seem like a decent alternative—except for the issue that @Rummskartoffel pointed out. We don't want to exclude active editors who retired before 2016, which could be quite a few of the main contributors to WP's earliest articles. Maybe we could trying using autoconfirmed instead raise the numbers to 5, 10, 25, and 50? Sorry I'm not able to give a single precise request for the query; the thing about this one is that it's hard to tell exactly what we want until we've seen the result with a few different settings and examined whether it seems too wide or narrow. {{u|Sdkb}} talk 06:53, 30 June 2021 (UTC)
::::You may want to exclude some of the top script/AWB users from your queries. I would expect that thousands of articles have been touched by Ser Amantio, Koavf, Magioladitis, BHG and Rich Farmbrough, making edits that are "minor" in some sense but not necessarily minor in the sense of the checkbox. I don't expect that any of them vouches for the notability of all articles they touch. And that's fine. It just means that there is no simple and reliable automatic way to say "this article has been looked at" just by ECness of the editors touching it. —Kusma (talk) 08:58, 30 June 2021 (UTC)
:::::I agree about gnome edits and automated edits that don't get marked as minor. For example, I was surprised to discover recently that HotCat doesn't mark its edits as minor. -- RoySmith (talk) 11:47, 30 June 2021 (UTC)
:::::: Interesting, I didn't know that some of those aren't marked as minor. I believe all semi-automated edits are marked with a tag, and hopefully that has always been the case, in which case excluding those edits should be possible. {{u|Sdkb}} talk 13:32, 30 June 2021 (UTC)
:::::::Tags were introduced in 2009, according to Wikipedia:Tags. —Kusma (talk) 14:21, 30 June 2021 (UTC)
::::::For what it's worth, the help page states we shouldn't mark category changes as minor, so if you follow that HotCat shouldn't (standard caveat that it's not a policy or guideline etc). There'll also be edits that should've been marked as minor but couldn't, such as those made from the mobile website. Sdrqaz (talk) 13:39, 30 June 2021 (UTC)
:::::::Yeah, I would exclude anything marked as minor or bot (do bots earn autoconfirmed???), plus anything we can recognize as somebody on a gnoming mission like updating cats, adding short descriptions, etc. Most of these things are done in a semi-automated way with some tool support, and the tools usually add a recognizable comment to the edit description (like HotCat does). -- RoySmith (talk) 13:47, 30 June 2021 (UTC)
Only displaying [[Template:Contains special characters]] when needed?
Would it be possible to perform some sort of check so that {{tl|Contains special characters}} is only displayed when someone actually lacks the rendering support needed to display them? It's unneeded otherwise, and as rendering technology has improved over time, this has become increasingly common. {{u|Sdkb}} talk 06:34, 30 June 2021 (UTC)
:I doubt that'd be possible without doing some really hacky things, cf. [https://stackoverflow.com/q/9005580/9859881 this StackOverflow question]. – Rummskartoffel 14:46, 30 June 2021 (UTC)
Image not displaying in the article "[[Plough]]"
{{tracked|T285875}}
Please refer to this discussion. The image :File:Young_Folks%27_History_of_Rome_illus090.png does not seem to want to render correctly on any pages. Can someone with technical knowledge please fix? Thanks. -- Ϫ 08:37, 30 June 2021 (UTC)
:I'm not seeing a problem on https://en.wikiquote.org/wiki/Agriculture, https://hu.wikipedia.org/wiki/Eke, or https://ta.wikipedia.org/wiki/%E0%AE%8F%E0%AE%B0%E0%AF%8D. My guess is there was a transient problem and you've got the broken image cached locally. Could you try emptying your browser cache and see if that helps.
:There's an outside chance this is related to {{phab|T270209}}. If you know how to examine your browser console, could you open it up and see if you get the same kind of errors as noted in that ticket? -- RoySmith (talk) 15:05, 30 June 2021 (UTC)
In fact, many similar images in commons:User:Helix84/gallery don't seem to display either. -- Ϫ 08:41, 30 June 2021 (UTC)
:Looks like something goes wrong when trying to request the thumbnail from the server: [https://upload.wikimedia.org/wikipedia/commons/thumb/a/a1/Young_Folks%27_History_of_Rome_illus090.png/120px-Young_Folks%27_History_of_Rome_illus090.png I get a 429 when trying to manually navigate to it]. Dunno what to do about this or if it's worth a Phab ticket, though. – Rummskartoffel 14:56, 30 June 2021 (UTC)
::With so many examples being available on commons - I'd open a phav ticket. Just put it in simple language, but provide clear examples - someone will clean up the tech details. — xaosflux Talk 15:15, 30 June 2021 (UTC)
Cross origin errors when accessing Wikidata
I'm trying to query Wikidata in an enwiki gadget. Sadly it just throws CORS errors, the "Access-Control-Allow-Origin" header is missing. I don't get it.. does this mean it's impossible to query Wikidata in an enwiki gadget? — Alexis Jazz (talk or ping me) 21:16, 27 June 2021 (UTC)
:Even with [https://doc.wikimedia.org/mediawiki-core/master/js/#!/api/mw.ForeignApi mw.ForeignApi]? Nardog (talk) 21:19, 27 June 2021 (UTC)
::{{u|Nardog}}, I think I finally have it working. I added origin=https%3A%2F%2Fen.wikipedia.org to the URL. mw.ForeignApi should do something similar but screws up the script in other ways. (if I remove the await it breaks, if I don't the script won't load) So I'll just stick with origin=https%3A%2F%2Fen.wikipedia.org. Don't understand why this has to be specified. Like evilmiddleman.com can't add origin=https%3A%2F%2Fen.wikipedia.org to the request URL because that would be lying which would be an insurmountable ethical hurdle for evilmiddleman.com? Well whatever, it works now. — Alexis Jazz (talk or ping me) 22:55, 27 June 2021 (UTC)
:::@Alexis Jazz evilmiddleman.com would need to add origin=evilmiddleman.com, not origin=https%3A%2F%2Fen.wikipedia.org. In which case, the API will refuse the request since evilmiddleman.con is not on the CORS whitelist.
On WMF wikis (which are on the CORS whitelist), you can just add origin=*
. There's a phab ticket somewhere that seeks to make this requirement unnecessary. – SD0001 (talk) 08:14, 28 June 2021 (UTC)
:::This is documented here: Manual:CORS It's basically there because otherwise we would have to Vary on each and every api request of the Origin header, and especially because we need to vary on authenticated and non-authenticated responses of cross site requests (or something like that). —TheDJ (talk • contribs) 08:19, 28 June 2021 (UTC)
::::{{u|TheDJ}}, I don't quite understand. If the origin parameter is compared to something else (and it appears it is as visiting [https://www.wikidata.org/w/api.php?origin=https%3A%2F%2Fen.wikipedia.org&action=wbgetentities&format=json&ids=Q1 an api request with defined origin] directly results in the error {{tq|'origin' parameter does not match Origin header}}), why doesn't it just check that something else? A passed parameter can't be trusted anyhow. — Alexis Jazz (talk or ping me) 19:12, 30 June 2021 (UTC)
Grouping references
Hey there,
I've a contentious statement that is supported by a lot of sources, and I'm trying to group them in a note so we don't have a whole list in-line. Is there a better way to do this than [https://en.wikipedia.org/w/index.php?title=Talk:Jan_%C5%BBaryn&diff=1030894137&oldid=1030890796 this]? Specifically, is there a way of exposing the refs in the note, so that they're immediately visible when hovering with the mouse pointer?
Thanks. François Robere (talk) 08:46, 30 June 2021 (UTC)
:See Wikipedia:Citing sources#Bundling citations. Nardog (talk) 08:54, 30 June 2021 (UTC)
:: Thanks. François Robere (talk) 20:18, 30 June 2021 (UTC)
Template error
There is a bug in one of the unblock templates, I posted about it on the talk page but I don't think anyone is watching it as it was empty. Any help at Template talk:Unblock-un on hold would be greatly appreciated. HighInBC Need help? Just ask. 06:17, 1 July 2021 (UTC)
:{{u|HighInBC}}, it looks to me as though in the [https://en.wikipedia.org/w/index.php?title=User_talk:CityofCroftonPR&oldid=1031209137#June_2021 case linked] the template simply wasn't filled in properly; the demonstration value of blocking administrator
was left in place. I've tried using the template and filling in the parameters and it appears to work as expected. I could however be missing something! firefly ( t · c ) 06:25, 1 July 2021 (UTC)
:{{u|HighInBC}}, in the template code the accept template uses {{{3|{{{reason|original unblock reason}}}}}}
(line 23) to get the unblock reason, which is correct, but the decline template uses {{{1|{{{reason|original unblock reason}}}}}}
(line 27) to get the unblock reason, which is wrong as parameter 1 is where the blocking administor's name goes. To fix this, you would just need to replace the shown code on line 27 with the shown code on line 23. – BrandonXLF (talk) 06:44, 1 July 2021 (UTC)
::Thank you Firefly and BrandonXLF for the help. I have tested it in my sandbox and it seems to have worked. I implemented the change in the temple itself[https://en.wikipedia.org/w/index.php?title=Template%3AUnblock-un_on_hold&type=revision&diff=1031368907&oldid=991171756]. Oh lawd I hope I did not break the entire unblock system! HighInBC Need help? Just ask. 07:01, 1 July 2021 (UTC)
::And it also seems to be working [https://en.wikipedia.org/w/index.php?title=User_talk:Ambassador_Foundation&oldid=1031369698 in the wild]. HighInBC Need help? Just ask. 07:07, 1 July 2021 (UTC)
Search busy
I keep getting an error message, "An error has occurred while searching: Search is currently too busy. Please try again later." In other tries it is super slow. Abductive (reasoning) 02:33, 30 June 2021 (UTC)
https://en.wikipedia.org/w/index.php?search= is currently failing, a first, in my experience. .... 0mtwb9gd5wx (talk) 05:57, 30 June 2021 (UTC)
:Yep, I experienced as well. Let's hope it's only temporary and resolved quickly. {{u|Sdkb}} talk 06:31, 30 June 2021 (UTC)
::As a data point, it seems to work for me now. firefly ( t · c ) 06:33, 30 June 2021 (UTC)
:::Datum point. One datum, two data. Hawkeye7 (discuss) 08:10, 30 June 2021 (UTC)
::::{{small|Dat-um sounds good! DesertPipeline (talk) 15:21, 30 June 2021 (UTC) }}
:::::A couple of days ago, much of the server infrastructure behind wikipedia was moved from one data center to another, which might account for transient performance problems like this. If these failures still happening for you, a phab ticket should be opened (if you don't have phab access, post here and I can open the ticket for you). -- RoySmith (talk) 11:45, 1 July 2021 (UTC)
Category:Articles containing undetermined-language text
Why does Ollagüe appear in :Category:Articles containing undetermined-language text? Jo-Jo Eumerus (talk) 15:19, 1 July 2021 (UTC)
: Because you passed {{para|native_name}} but not {{para|native_name_lang}} to the infobox. * Pppery * it has begun... 15:29, 1 July 2021 (UTC)
::Thanks, remedied this now. Jo-Jo Eumerus (talk) 15:46, 1 July 2021 (UTC)
Mass Message
{{tracked|T93049}}
Hey! So I was sending a mass message, and while my log states that I only sent one message, why does MediaWiki MassMessage Delivery sometimes send the message later again, to certain pages on the message list, but not to all pages, for example, I sent a message at X o clock, only once. Then a few hours later, I did not send another message, via mass message, and the same message will get sent again. Even though I only sent it once, and my log only shows I sent it once. This has happened 2 times now. Is there a way to fix this? --つがる Talk to つがる:) 🍁 21:41, 2 July 2021 (UTC)
:{{re|つがる}} can you be more specific in your examples? I see you sent a message here: LogId:119014629. Can you point to the duplicate log entry, or the edit made by the service you don't think you have occurred? — xaosflux Talk 22:26, 2 July 2021 (UTC)
:This is bug phab:T93049, MassMessage does not always send two posts, it is inconsistent.--Snævar (talk) 08:52, 3 July 2021 (UTC)
Timezone switcher
The OpenStreetMap conference, "State of the Map", has an impressive, easy to use, tool for switching timezones on its [https://2021.stateofthemap.org/programme/ programme page].
Could we use that, or something very like it, on Wikipedia and sister projects, for our events? The tools I've seen used by us for such things seem much more clunky. Andy Mabbett (Pigsonthewing); Talk to Andy; Andy's edits 10:52, 3 July 2021 (UTC)
PROD or BLPPROD logs
Hi, If the articles have been deleted uner PROD or BLPROD, where can we find the hist diff/log for the nomination of PROD/BLPROD edits? Thaks in advance. Cassiopeia(talk) 09:32, 3 July 2021 (UTC)
:{{replyto|Cassiopeia}} Whilst the deletion (if it occurs) is logged, the nomination is not; this is because it is a normal page edit - see WP:PROD#During nomination and WP:BLPPROD#Nominating. --Redrose64 🌹 (talk) 09:57, 3 July 2021 (UTC)
::{{u|Redrose64}} Thank you for your quick reply. May be I rephrase my question. I wan to find the hist diff of the nomination edit of a deleted PROD/BLPPROD page. since the article is deleted, which means the history page of the deleted page is also deleted. Could we able to find the hist diff anywhere else besides the creator talk page where we place a notification of the PROD/BLPPROD notification? Thanks in advance. Cassiopeia(talk) 10:11, 3 July 2021 (UTC)
:::Unless you can see deleted revisions, no. I.e., be an administrator. Izno (talk) 16:09, 3 July 2021 (UTC)
::::@CASSIOPEIA: Non-admins can see metadata of deleted revisions (via API or Quarry) – this is exposed via deleted-metadata-link.js. Since PRODs are usually done via twinkle, you can usually guess the edit in which the PRODing occurred by looking at edit tags. If the PRODing occurred via PageTriage, they're also recorded in the [https://en.wikipedia.org/wiki/Special:Log/pagetriage-curation page curation log]. – SD0001 (talk) 16:22, 3 July 2021 (UTC)
:::::{{u|SD0001}} Thank you for the info above. The thing is I am not a technical editor and not sure how to use and where to find the API/Quarry to find the PORD info by looking at the edit tag. I would appreciate if you could provide step by step instructions by using Bent Creek Country Club deleted page PRODing via Twinkle. Thanks in advance. Cassiopeia(talk) 02:21, 4 July 2021 (UTC)
::::::@Cassiopeia: Just click on that red link. Above the red box, you should see the text: "See deleted revisions: last edited by Nearlyevil665 at 17:48, 20 June 2021 (UTC) Look up snippet in PROD grid". Click on "deleted revisions" to see further info. The latest edit with tags: [ "twinkle" ]
is probably the edit that added the PROD. If you also want the diff ID for some reason, you can look for &drvprop=
in the URL and replace it by &drvprop=ids%7C
. – SD0001 (talk) 05:07, 4 July 2021 (UTC)
:::::::{{u|SD0001}} Thank you for your quick reply. I assume the "red link" you mentioned above was Bent Creek Country Club. However, what I get is [https://en.wikipedia.org/w/index.php?title=Bent_Creek_Country_Club&action=edit&redlink=1 this] and no "See deleted revisions: last edited by Nearlyevil665 at 17:48, 20 June 2021 (UTC)" or anything your mentioned above. Pls advise. Thanks in advance. Cassiopeia(talk) 05:23, 4 July 2021 (UTC)
::::::::@Cassiopeia That's weird, since you do have User:SD0001/deleted-metadata-link.js in your common.js. Check your browser console (see WP:JSERROR #6 on how to open it) to see if there are any errors in red. – SD0001 (talk) 05:32, 4 July 2021 (UTC)
Statistics stopped working
{{tracked|T286115|resolved}}
Statistics stopped working, see [https://dumps.wikimedia.org/other/pageviews/2021/2021-07/] - "pageviews-20210702-110000.gz" is the last file. --BlueDonny (talk) 05:45, 3 July 2021 (UTC)
:It seems to work now. --BlueDonny (talk) 07:19, 4 July 2021 (UTC)
Error preventing edit
This may be related to this discussion at the RedWarn talkpage.
When I try to edit pages, I cannot publish changes, which I think is due to this error:
mdlLogic.js:1 Uncaught URIError: URI malformed
at decodeURIComponent ()
at Function.t.EPPyTH (mdlLogic.js:1)
at t (mdlLogic.js:1)
at Object.mw.loader.load (:2:180)
at Object.preloadDeflate (:351:854)
at :40:348
―
Qwerfjkltalk 18:20, 3 July 2021 (UTC)
:As I said in {{§l||Scripts only working on certain pages}}, this error occurs in RedWarn code, so I recommend you ask the RedWarn developers. If you want to be sure whether it's really RedWarn that's stopping you from publishing, temporarily uninstall it and see if the problem still occurs. – Rummskartoffel 19:40, 3 July 2021 (UTC)
::@Rummskartoffel I have previously confirmed that it is RedWarn. ―Qwerfjkltalk 07:26, 4 July 2021 (UTC)
Night mode suggestion
Greetings.
I am with you one of the Arabic Wikipedia editors :), I work sometimes in a dark atmosphere (like now when writing to you) on a bright white screen, which annoys me a bit especially when I see the page of the site, I think we could coordinate with the rest of the other wikis or with programmers in Wikipedia in order to give this appearance, and make it Within the Appearance section of the preferences page for each Wikipedia user, with the ability to specify the time of their appearance (as it is present and familiar to you in the settings of computers (such as Windows 10) or mobile phones), and it is not hidden from you that these sites exist in other recent sites such as Twitter and YouTube.
Could you please accept this small suggestion :)?
Thank you and best regards. --A3bdula3ziz (talk) 01:39, 4 July 2021 (UTC)
:There is a gadget available you can try. Izno (talk) 02:00, 4 July 2021 (UTC)
::Special:Preferences#mw-prefsection-gadgets, do a find for "dark". – Jonesey95 (talk) 02:58, 4 July 2021 (UTC)
::: Thanks a lot to all :) --A3bdula3ziz (talk) 04:52, 4 July 2021 (UTC)
::::@A3bdula3ziz You can also try User:MusikAnimal/nightpedia. ―Qwerfjkltalk 07:29, 4 July 2021 (UTC)
Ohh that is nice. HighInBC Need help? Just ask. 07:34, 4 July 2021 (UTC)
Reference error #2
How do I get rid of the sfn error on User:Jo-Jo Eumerus/Eifuku? Jo-Jo Eumerus (talk) 20:56, 3 July 2021 (UTC)
: The problem is that you have two sources with the same author and year (the first bulleted entry in the sources list and ref 15), so the sfn doesn't know what to link to. The easiest solution is probably to add {{para|ref|none}} to the wikitext of ref 15, to explicitly state that the sfn should link to the other one. * Pppery * it has begun... 21:06, 3 July 2021 (UTC)
:{{replyto|Jo-Jo Eumerus}} As noted by Peppery, there are two similar sources: [{{cite report|last1=Cantwell|first1=Kasey|last2=Newman|first2=Jim|url=https://repository.library.noaa.gov/view/noaa/17556|year=2016|title=Okeanos Explorer ROV dive summary, EX1605L3, June 26, 2016}}]
- {{cite report|last1=Cantwell|first1=Kasey|last2=Newman|first2=Jim|url=https://repository.library.noaa.gov/view/noaa/17555|year=2016|title=Okeanos Explorer ROV dive summary, EX1605L3, June 25, 2016}} They're not identical: the one used as a ref has a URL ending in 17556 and a date of June 26 whereas the one in the Sources section has 17555 and June 25 respectively. The three instances of {{tlx|sfn|Cantwell|Newman|2016|5=p=3}} don't know which to link to.
:*If they relate to the 17556/June 26 one, remove the one in Sources.
:*If they relate to the 17555/June 25 one, add {{para|ref|none}} to the one in References.
:Alternatively, you could alter {{para|year|2016}} to {{para|year|2016a}} in one and to {{para|year|2016b}} in the other, and in the {{tlx|sfn}} alter {{para||2016}} to either {{para||2016a}} or to {{para||2016b}} whichever is applicable. --Redrose64 🌹 (talk) 22:33, 3 July 2021 (UTC)
::OK, did this with ref=none. I didn't realize that sfn wouldn't be able to see the letter at the end of the sfn template. Jo-Jo Eumerus (talk) 07:58, 4 July 2021 (UTC)
Admins can't delete large-revision pages?
If [https://en.wikipedia.org/wiki/Talk:Main_Page?action=delete] this is correct, I have a question. Does that mean that if I were to make over 5,000 edits to my user page, no one here would be able to delete it? And what if over 5,000 edits were made to an admin's own user page, and they couldn't delete it by their own request? This doesn't seem clear why the protection should be given in this case. Are there any exceptions to this? And can an admin send a screenshot of what happens when attempting to delete pages with 5k+ revisions? 54nd60x (talk) 12:26, 3 July 2021 (UTC)
:Then the admins simply go to :meta:Steward requests/Miscellaneous. We get this message for the record. Jo-Jo Eumerus (talk) 12:50, 3 July 2021 (UTC)
::{{ping|Jo-Jo Eumerus}} This doesn't seem right. That means that approximately 5k+ articles cannot be deleted by anyone here. I also noticed that the $1 in the message seems to vary across different wikis, so why did we decide to set the limit there so that it would impact so many articles? 54nd60x (talk) 06:12, 4 July 2021 (UTC)
:::No, the limit is 5k on every WMF wiki. The number might be put into a different perspecive in the translated messages (english is the original), but the limit itself is the same. It is an performance decision (as in performance of the server) and not a big deal either, the stewards will still make the same action as an admin would.--Snævar (talk) 06:53, 4 July 2021 (UTC)
::::{{ping|Jo-Jo Eumerus|Snævar}} Also another question to deletion. Is it technically possible for an admin to delete {{-r|Gadget:Invention, Travel, & Adventure}}? Just curious about the technical parameters as I know that .css and .js user subpages and MediaWiki pages can be deleted by sysops, but not edited. 54nd60x (talk) 08:43, 4 July 2021 (UTC)
:::::No, and attempting will display MediaWiki:Namespaceprotected. — xaosflux Talk 08:48, 4 July 2021 (UTC)
Apparently the 5k limit is not all. There is also an special deletion in place when pages exceed 1000 revisions. When an page that big gets deleted, that is put into Job queue and the revisions are deleted in batches, from oldest to newest. Even if the page gets edits or even moved from the point that the admin requests for deletion, then that action is still archived just like with an normal deletion, and any subsequent deletions of the same page whilst this process is underway does not affect the process - that was actually tested by the developers. There is a note on pages like those that there is an deletion in progress. See phab:T198176.--Snævar (talk) 10:38, 4 July 2021 (UTC)
If my memory serves me right very large pages were deleted in the past, either by accident or due to compromised accounts. It was highly disruptive causing a lot of load on the database servers as well as taking a long time to restore. This was very long ago, back when being here for 2 years made you an old timer. HighInBC Need help? Just ask. 08:52, 4 July 2021 (UTC)
:Indeed, the restriction was added back in 2008, after an admin tried to delete the sandbox. Graham87 10:24, 4 July 2021 (UTC)
::Oh yes I remember now. It was shocking to not be able to edit for half an hour. HighInBC Need help? Just ask. 10:48, 4 July 2021 (UTC)
Problems with mobile search in Chrome for iOS
I have problems with mobile search on Chrome in iOS, with the articles I frequently read not appearing with incomplete search strings, but appearing only when complete. For example, when typing in COV and expecting to see COVID-19, COVID-19 pandemic and related articles in results, I would see Covariance, Coventry, Covina, etc. Is this a bug, problem with browser, or something else?-TagaSanPedroAko (talk) 07:07, 3 July 2021 (UTC)
:More information is needed I think. Have you searched for "Cov" before and then clicked on an covid search result ? The mobile search will remember past searches and make decisions on cases like that (it is a fairly recently added feature). I do not think it takes popularity in consideration (that is, ordering results by pageviews), which would work in this case.--Snævar (talk) 08:52, 3 July 2021 (UTC)
:: Yes. When I type the first three letters of COVID, I would expect COVID-19 and related entries should show up, but now, they only appear if I enter the whole thing.-TagaSanPedroAko (talk) 09:04, 3 July 2021 (UTC)
:::Ok, so the search does in fact order by traffic of pages and the history boosted search is an Android app thing. It should still show COVID-19 ahead of covariance tho. Filed a bug at phab:T286111.--Snævar (talk) 13:21, 3 July 2021 (UTC)
::::{{re|Snævar}} It’s not only COVID-related articles are affected by the bug. It also affects every article I frequently read both when logged in and logged out, that when I partially enter the name (or redirect) of an article I frequently read, I can’t see it until I type the whole term. I’ll give further examples. When I first enter the word “heart dis” and expecting to see Cardiovascular disease, I no longer see it unless I type the whole search term “heart disease”. Same also with “ill”, where I’m expecting “illegal drug trade” to appear in third or so place in results, but I see other articles with the first letters “ill”, the Ill disambiguation page, and the illegal drug trade in Colombia pages instead. It appears the issue is new; I haven’t encountered that with previous partial search entries in the last few days.-TagaSanPedroAko (talk) 15:09, 3 July 2021 (UTC)
:::::I am also having the same issue with search bar. When I type something it no longer shows up (believe it's called autocomplete) in the upper right hand search bar/box. Is someone at Wikipedia working on fixing this problem? 158.222.185.250 (talk) 22:16, 3 July 2021 (UTC)
= Search text problem =
The past few hours if i type a name into the upper-right search bar it doesn't show up. For example if i type Julian Assange his name doesn't appear but "Julian Assange Show" does. are other users experiencing this weird issue?? 158.222.185.250 (talk) 11:55, 3 July 2021 (UTC)
:It works for me. Did you have a space after "assange"? If so, then the title which matches the space (the show) will appear first but "Julian assange" [sic] should be the second option. Certes (talk) 12:14, 3 July 2021 (UTC)
:Depending on how you browse, you may be experiencing #Problems with mobile search in Chrome for iOS. Certes (talk) 15:14, 3 July 2021 (UTC)
::I browse using Edge not Chrome. I'm still experiencing the problem, is Wikipedia working on fixing this autocomplete text issue with the search bar? 158.222.185.250 (talk) 22:10, 3 July 2021 (UTC)
:::The issue affects other browsers as well, I was able to reproduce it on Firefox. There is no upper right search bar on mobile web (it is in the upper center), so this is an desktop search issue here.--Snævar (talk) 07:22, 4 July 2021 (UTC)
= Problems with autocomplete in search =
I also want to reiterate problems I've been having with the search function today, as users here and here have. One way the problem manifest itself to me recently was that it required not only a complete string to return the article I was looking for; it required case sensitivity as well. For example, if searching for the article Light of a Clear Blue Morning, typing "light of a clear blue morning" or even "Light of A Clear Blue Morning" does not return it in the search bar. It must be complete and correct title case for the article to appear at all. This is not the only problem I have encountered with search today, but it is a specific anecdote that might shed some light on the nature of the problem.
It does not appear to be limited to Chrome on iOS, as has been previously speculated. This problem occurs for me across two devices, neither of which match those specifications.--Sunshineisles2 (talk) 23:22, 3 July 2021 (UTC)
:{{+1}} on Edge. Schazjmd (talk) 23:35, 3 July 2021 (UTC)
::There were some changes announced to search in :m:Tech/News/2021/23. I don't think it would account for the behavior described here, but... The change described in {{phab|T219550}} does mention that it changes how case is handled. -- RoySmith (talk) 23:51, 3 July 2021 (UTC)
:I am also here to complain about an apparent negative change in how search and case interacts. When there isn't a redirect already created for a difference in case from the target title, the article no longer seems to appear, as OP describes. — Goszei (talk) 00:26, 4 July 2021 (UTC)
::On Windows Chrome, by the way. I've also noticed other autocomplete abnormalities that I don't think were there before. Example: when searching the string "Barack Obama", the article does not appear in results until the last letter is entered (a total failure of autocomplete?) — Goszei (talk) 00:38, 4 July 2021 (UTC)
::As of right now, the negative changes seem to have been reversed. — Goszei (talk) 20:28, 4 July 2021 (UTC)
:Yes, encountering this issue since the past few days. The search wants the complete string, you don't get suggestions on an incomplete string or case changed ones. Making the search suggestion useless. Changing to "Classic prefix search" in prefs does fix this though. Gotitbro (talk) 00:46, 4 July 2021 (UTC)
Remdesivir
Every version of Remdesivir, since creation, when I start to edit it, displays:
Lua error in Module:Sanctions at line 60: attempt to index field '_topicData' (a boolean value).
when I copy to sandbox this does not happen. .... 0mtwb9gd5wx (talk) 19:27, 4 July 2021 (UTC)
:@0mtwb9gd5wx, apparently the editnotice {{tl|Editnotices/Page/Remdesivir}} is broken. —Kusma (talk) 19:32, 4 July 2021 (UTC)
::The reason for the error message is [https://en.wikipedia.org/w/index.php?title=Module:Sanctions/data&curid=64642823&diff=1029022843&oldid=1028839818 this edit] by @Dreamy Jazz, don't know whether that was in error or whether the Remdesivir edit notice should be removed. —Kusma (talk) 19:41, 4 July 2021 (UTC)
:::{{ping|Dreamy Jazz}} {{ping|ProcrastinatingReader}} {{ping|GeneralNotability}} {{ping|Go Phightins!}} :Module:Sanctions/data breaks Remdesivir, see: :Template:Editnotices/Page/Remdesivir .... 0mtwb9gd5wx (talk) 20:19, 4 July 2021 (UTC)
::::I've temporarily reverted the change pending a fix for the editnotices, anyone may redo it once this is fixed. GeneralNotability (talk) 20:22, 4 July 2021 (UTC)
:::::Currently working on {{tl|tl}}'ing out or replacing uses as appropriate. Dreamy Jazz talk to me | my contributions 20:45, 4 July 2021 (UTC)
::::::Done using AWB to replace, remove or {{tl|tl}} out uses as appropriate, and so I've re-removed the covid topic area per GN above. Will double check for any Lua errors with this text, but I should not have missed any non-subst'ed uses. Dreamy Jazz talk to me | my contributions 21:25, 4 July 2021 (UTC)
:::{{u|Kusma}}, {{ec}} hi. I had used the search function to search for this error when I removed the covid gs from the data template. Obviously it took some time for pages to catch up and my search had not found all uses. The edit to remove the covid gs from the data template was because it has been superseded by WP:COVIDDS. Uses of the the GS editnotice with the covid topic need to be replaced with {{tl|COVID19 DS editnotice}} or {{tl|ds/editnotice}}. I will do another search for this error and fix any occurrences I find. In the case of this article the expiry parameter was set to a month in an edit in April last year, however, I think this editnotice should stay so I'll replace it. Dreamy Jazz talk to me | my contributions 20:20, 4 July 2021 (UTC)
::::Sounds good. Part of the reason I pinged you was that I have no clue what the state of play is with Covid sanctions and so was hoping you'd know better what to do :) —Kusma (talk) 20:35, 4 July 2021 (UTC)
Google Chrome text fragments
Context: [https://arstechnica.com/gadgets/2020/06/google-pushes-text-fragment-links-with-new-chrome-extension/]. Google Chrome has implemented this "text fragment" URL feature for a year now, and it is today used within at least [https://en.wikipedia.org/w/index.php?search=insource%3A%2F%5C%3A%5C%7E%5C%3Atext%2F&title=Special%3ASearch&ns0=1 9,260 articles]. When a URL with this ":~:text=" string is clicked in Chrome, the page will be jumped to the corresponding text (strangely, my search shows these also have been added in inter-wiki links). They don't work in browsers other than Chrome, and don't even work all the time in Chrome (at least for me).
Google Search has been appending this string to its results in order to jump people to the text in webpages visible in the results snippet. It appears that editors have copy and pasting these URL's and leaving the extraneous string in; a small sampling of my search shows that they almost always have no correspondence with the text that is being verified, and so I think editors have been mostly been leaving this in the URL by complete accident. For this reason, I think they should be removed en masse, perhaps a task handled continuously by a bot (or AWB?). I would be given some pause if they were being used like a citation template's |quote parameter, but that doesn't appear to be the case at all, with almost all uses being apparently accidental.
What should be done about these, if anything? — Goszei (talk) 07:50, 3 July 2021 (UTC)
: Probably not much. As far as I can tell, these text fragment links degrade harmlessly to normal links to the intended webpage if the browser does not handle them, or the target webpage has since changed. It would be worth adding a note to our guidelines about internal links to make it clear that text fragment links are vulnerable to changes in the text of an article and internal links should always use ID references as the target. It might also be worth adding a note of some sort in other guidelines about references and external links — GhostInTheMachine talk to me 09:48, 3 July 2021 (UTC)
:In theory, this is a wonderful feature that could be very helpful to our readers. Firefox has an add-on for it, and I hope that other browsers will implement it soon. If links are being created to the wrong point on the page, those individual links need attention, but let's not throw the baby out with the bathwater. The worst that can happen is to position the window at the wrong point in the page, which compares with the legacy behaviour of always showing the top. (I usually rant against browser-specific features, especially from the dominant supplier, but this one seems portable, beneficial and harmless.) Certes (talk) 12:22, 3 July 2021 (UTC)
::{{(y)}} Ditto. — 𝐆𝐮𝐚𝐫𝐚𝐩𝐢𝐫𝐚𝐧𝐠𝐚 ☎ 13:12, 3 July 2021 (UTC)
:::Seems to be an optional (non-normative?) option for URLs, see [https://wicg.github.io/scroll-to-text-fragment/]. Given that its use appears to be on the increase, is it worth putting a check in {{tl|cite web}} that detects if the URL has a text fragment and asks the editor if they really need it?--Verbarson (talk) 20:27, 3 July 2021 (UTC)
:::Sorry, sloppy thinking. The check needs to be in the Source Editor function that prompts for and constructs the {{tl|cite web}} template, not in the template itself.--Verbarson (talk) 08:13, 5 July 2021 (UTC)
Disappeared languages
I noticed that on the desktop version of vec.wiki are disappeared the languages links to the other Wikipedia languages editions. How can I solve? --62.18.11.223 (talk) 20:08, 2 July 2021 (UTC)
:The language links still exist, but they have been moved; you can find them on the right, near the top of the page, just opposite the article title. Here is an image with the position of the menu visually highlighted. This change is a feature of the updates to the Vector skin being done as part of the Desktop Improvements, which Venetian Wikipedia is an early adopter of. If you have an account, you can switch back to the old version in your preferences. – Rummskartoffel 21:01, 2 July 2021 (UTC)
::{{ec}} it looks like vecwiki is using a "new" version of Vector skin that moved that around. To restore the old view you will have to create an account, then click on "Torna al vecchio aspetto" on the side bar to go the the section of your user preferences where you can turn that off and restore the prior display. — xaosflux Talk 21:09, 2 July 2021 (UTC)
- N.B. from phab:T282026,
&useskinversion=1
may be used to for the old version on a page load if needed. — xaosflux Talk 12:02, 5 July 2021 (UTC)
[[m:Special:MyLanguage/Tech/News/2021/27|Tech News: 2021-27]]
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
- The next issue of Tech News will be sent out on 19 July.
Recent changes
- AutoWikiBrowser is a tool to make repetitive tasks easier. It now uses JSON.
Wikipedia:AutoWikiBrowser/CheckPage
has moved to Wikipedia:AutoWikiBrowser/CheckPageJSON
and Wikipedia:AutoWikiBrowser/Config
. Wikipedia:AutoWikiBrowser/CheckPage/Version
has moved to Wikipedia:AutoWikiBrowser/CheckPage/VersionJSON
. The tool will eventually be configured on the wiki so that you don't have to wait until the new version to add templates or regular expression fixes. [https://phabricator.wikimedia.org/T241196]
Problems
- InternetArchiveBot helps saving online sources on some wikis. It adds them to Wayback Machine and links to them there. This is so they don't disappear if the page that was linked to is removed. It currently has a problem with linking to the wrong date when it moves pages from
archive.is
to web.archive.org
. [https://phabricator.wikimedia.org/T283432]
Changes later this week
- The tool to find, add and remove templates will be updated. This is to make it easier to find and use the right templates. It will come to the first wikis on 7 July. It will come to more wikis later this year. [https://meta.wikimedia.org/wiki/WMDE_Technical_Wishes/Removing_a_template_from_a_page_using_the_VisualEditor][https://phabricator.wikimedia.org/T284553]
- There is no new MediaWiki version this week.
Future changes
- Some Wikimedia wikis use Flagged Revisions or pending changes. It hides edits from new and unregistered accounts for readers until they have been patrolled. The auto review action in Flagged Revisions will no longer be logged. All old logs of auto-review will be removed. This is because it creates a lot of logs that are not very useful. [https://phabricator.wikimedia.org/T285608]
Tech news prepared by Tech News writers and posted by bot • Contribute • Translate • Get help • Give feedback • Subscribe or unsubscribe.
17:31, 5 July 2021 (UTC)
Scripts only working on certain pages
Certain scripts ({{no ping|Ohconfucius}}'s formatgeneral, Sources, and Common Terms, as well as TemplateScript) only show up on pages with &action=submit
appended to their URL, as well as some random text. File:ScriptErrorScreenshot.PNG ― Qwerfjkl | 𝕋𝔸𝕃𝕂 (please use {{tlx|reply to|Qwerfjkl}} on reply) 13:41, 23 June 2021 (UTC)
:@Qwerfjkl: That's probably intentional. See e.g. User:Ohconfucius/script/formatgeneral#Actions: {{tq|Once you are in edit mode, there is a button ... }}. Unless I'm misunderstanding and they don't work in edit mode. – Rummskartoffel 17:09, 23 June 2021 (UTC)
::@Rummskartoffel They don't work in [https://en.wikipedia.org/wiki/Wikipedia:Village_pump_(technical)?action=edit#Scripts_only_working_on_certain_pages this] edit mode but they do in [https://en.wikipedia.org/w/index.php?title=Wikipedia%3AVillage_pump_(technical)&action=submit this] edit mode. ― Qwerfjkl | 𝕋𝔸𝕃𝕂 (please use {{tlx|reply to|Qwerfjkl}} on reply) 17:31, 23 June 2021 (UTC)
:::Huh. In that case, dunno. For me, they work in both, and don't add random stuff. – Rummskartoffel 18:01, 23 June 2021 (UTC)
::::@Rummskartoffel This also happens on the default 'create page' editor, but none of the buttons do anything. ― Qwerfjkl | 𝕋𝔸𝕃𝕂 (please use {{tlx|reply to|Qwerfjkl}} on reply) 20:24, 23 June 2021 (UTC)
::::([https://en.wikipedia.org/w/index.php?title=Wikipedia:Village_pump_(technical)1&action=edit&redlink=1 This] edit mode.) ― Qwerfjkl | 𝕋𝔸𝕃𝕂 (please use {{tlx|reply to|Qwerfjkl}} on reply) 17:01, 24 June 2021 (UTC)
:::::Are there any error messages in the browser console? Otherwise, the only thing I can think of would be to revert your common.js to a version where it worked and then add the scripts in question again one-by-one until you find the one that breaks it. – Rummskartoffel 14:05, 25 June 2021 (UTC)
I get this:
{{collapse top|Large output dump}}
load.php?lang=en&modules=ext.CodeMirror|ext.CodeMirror.data|jquery%2Coojs-ui-core|jquery.ui&skin=vector&version=pg4sw:63 Uncaught TypeError: Cannot read property 'indexOf' of undefined
at Array. (:760:12)
at Object.ARA_Functions.getSuggestions (:380:24)
at Object.ARA_Functions.scan (:299:45)
at HTMLDocument. (:22:16)
at mightThrow (load.php?lang=en&modules=ext.CodeMirror|ext.CodeMirror.data|jquery%2Coojs-ui-core|jquery.ui&skin=vector&version=pg4sw:60)
at process (load.php?lang=en&modules=ext.CodeMirror|ext.CodeMirror.data|jquery%2Coojs-ui-core|jquery.ui&skin=vector&version=pg4sw:61)
mdlLogic.js:1 Uncaught URIError: URI malformed
at decodeURIComponent ()
at Function.t.EPPyTH (mdlLogic.js:1)
at t (mdlLogic.js:1)
at Object.mw.loader.load (:2:180)
at :6:11
at Object. (:1:724)
at mightThrow (load.php?lang=en&modules=ext.CodeMirror|ext.CodeMirror.data|jquery%2Coojs-ui-core|jquery.ui&skin=vector&version=pg4sw:60)
at process (load.php?lang=en&modules=ext.CodeMirror|ext.CodeMirror.data|jquery%2Coojs-ui-core|jquery.ui&skin=vector&version=pg4sw:61)
Uncaught TypeError: Cannot read property 'end' of null
at jQuery.fn.init.getCaretPosition (:106:580)
at jQuery.fn.init.$.fn.textSelection (:201:237)
at jQuery.fn.init.$.fn.wikiEditor (load.php?lang=en&modules=ext.wikiEditor&skin=vector&version=10s2l:11)
at Object.mw.addWikiEditor (load.php?lang=en&modules=ext.wikiEditor&skin=vector&version=10s2l:5)
at HTMLDocument. (load.php?lang=en&modules=ext.wikiEditor&skin=vector&version=10s2l:5)
at mightThrow (load.php?lang=en&modules=ext.CodeMirror|ext.CodeMirror.data|jquery%2Coojs-ui-core|jquery.ui&skin=vector&version=pg4sw:60)
at process (load.php?lang=en&modules=ext.CodeMirror|ext.CodeMirror.data|jquery%2Coojs-ui-core|jquery.ui&skin=vector&version=pg4sw:61)
Uncaught URIError: URI malformed
at decodeURIComponent ()
at Function.t.EPPyTH (mdlLogic.js:1)
at t (mdlLogic.js:1)
at Object.mw.loader.load (:2:180)
at Object.preloadDeflate (:158:106)
at load.php?lang=en&modules=ext.visualEditor.articleTarget%2Ccore%2CdesktopArticleTarget%2Cmwsave%2Cmwtransclusion&skin=vector&version=1ga9r:9
{{collapse bottom}}
:on [https://en.wikipedia.org/wiki/Wikipedia:Village_pump_(technical)?action=edit#Scripts_only_working_on_certain_pages this] edit mode. Some of these error messages may be related to a discussion at the RedWarn talkpage. —Qwerfjkltalk 16:31, 29 June 2021 (UTC)
::As was mentioned above, you should remove all of your scripts and then activate then one by one to find the one that is malfunctioning. If it is one you copied from someone else, they may be the best to help you with it. — xaosflux Talk 16:37, 29 June 2021 (UTC)
::These look like they've got something to do with RedWarn – "mdlLogic.js" is a file it uses. – Rummskartoffel 16:57, 29 June 2021 (UTC)
:::{{ping|Rummskartoffel}} AFter testing this on my alt, I found that these pages load differently for an unknown reason which I couldn't locate. To clarify, this only appeared on the page which has the edit summary (show preview, show diff) on the same page as the editing window. (Or at least, before the big blue 'Publish changes' button is pressed.) ―Qwerfjkltalk 19:17, 5 July 2021 (UTC)
::::I'm afraid I can't help you much more apart from repeating what I've already told you. It's going to come down to you finding, using the method I told you above, the script that causes the issue. That may be RedWarn, which does appear to run into some kind of problem, at least, or it may be any other script. Once you've found the problematic script, I or someone else can try and figure out why it breaks the others. – Rummskartoffel 21:05, 5 July 2021 (UTC)
Do i exist?
Very minor question, but puzzling me nonetheless. In discussion at the current RfA someone mentioned XTools Admin Score; as one does, i took a look and, curious, entered mine own account. It [https://xtools.wmflabs.org/adminscore/en.wikipedia.org/LindsayH says] that the account is 0 days old. So i looked at Special:List Users, which [https://en.wikipedia.org/wiki/Special:ListUsers?username=LindsayG&group=&wpsubmit=&wpFormIdentifier=mw-listusers-form&limit=500 also gives] no creation date for LindsayH. Am i missing something very simple (most likely), or is there something wrong with my account? Thanks; happy days, LindsayHello 19:06, 3 July 2021 (UTC)
:It has the same for me, {{u|LindsayH}}. I recall seeing a mention somewhere that accounts created early on (before some sort of software change) can't currently have their ages computed. Sorry, I forget what the technical details are. Schazjmd (talk) 19:21, 3 July 2021 (UTC)
::Thank {{U|Schazjmd|you}}. I did wonder if that might be it, but the same list page shows creation dates for LindsayJ, LindsayJo0307, and LindsayK.123, to take three at random, all of which were created prior to mine. Maybe it's something more "special" about you and me {{Smiley|wink}} happy days, LindsayHello 19:28, 3 July 2021 (UTC)
::: {{re|LindsayH|Schazjmd}} Accounts that were created before the user_registration
field was added to the database (in December 2005) did not have that filed filled in. Where such accounts had edits, the timestamp of the first edit was used to fill in the field as a guess. But if you created your account before but did not make any edits until after, you won't have a registration date recorded. There's a bug open about filling the rest in ({{phab|T20638}}), but it seems unlikely anyone will get around to it since they haven't for so long yet. Anomie⚔ 19:29, 3 July 2021 (UTC)
:::: Mystery solved, thanks {{u|Anomie}}! I knew it was something techy... {{smiley}} Schazjmd (talk) 19:34, 3 July 2021 (UTC)
:::::Recēnseō, ergo sum. --Redrose64 🌹 (talk) 22:47, 3 July 2021 (UTC)
::::::I second Schazimd's thanks; Anomie, what a fount of knowledge. I deliberately gave the section a provocative/silly heading; Redrose64, i'm so glad it provoked a good joke from you; happy days, LindsayHello 05:24, 4 July 2021 (UTC)
:::::::I have a script or gadget that displays first and last edit dates on an editor's user page and I was wondering why some editors had no start dates. Learned something today! Liz Read! Talk! 00:37, 6 July 2021 (UTC)
Problem with River Lugg references
There seems to be a problem with some refs on the River Lugg article. I have used {{sfn |Jacklin |2015 |p=2}} twice, and Jacklin is defined in the bibliography. However, I am getting a "Cite error: The named reference "FOOTNOTEJacklin20152" was defined multiple times with different content (see the help page)." message. This is not normally a problem, since I have used {{sfn |Priestley |1831 |p=697}} twice in the same article, and that is ok. Any suggestions as to how to fix it? Thanks. Bob1960evens (talk) 09:40, 6 July 2021 (UTC)
:{{Fixed}} - you had an extra pipe character in one of the {{tl|sfn}} instances. -- John of Reading (talk) 10:02, 6 July 2021 (UTC)
::Thanks. I looked at it several times and never spotted that. Bob1960evens (talk) 11:04, 6 July 2021 (UTC)
Module parser not accepting "in" table key direct indexing
Why does the parser error with something like myContainer.in(key)
, but not with myContainer['in'](key)
? Is this a bug? Alexiscoutinho (talk) 21:01, 6 July 2021 (UTC)
:Likely because {{code|lang=lua|in}} is a Lua keyword. See mw:Extension:Scribunto/Lua reference manual#Tokens.
:—Trappist the monk (talk) 21:15, 6 July 2021 (UTC)
::I still don't get why valid names are required to use the dot notation. Is there even an ambiguous case where the parser wouldn't know if the user means the token or the table key? Alexiscoutinho (talk) 22:05, 6 July 2021 (UTC)
:::I doubt asking here is going to get you an answer about how parsing works at a basically theoretical level. Izno (talk) 23:25, 6 July 2021 (UTC)
:::Your link answers the question because it prominently shows: "The following keywords are reserved and may not be used as names". The reason for that rule would be buried in the details of how the Lua byte-code compiler works. Johnuniq (talk) 23:41, 6 July 2021 (UTC)
Thanks :) I've decided to use myContainer.has(key)
instead, which is much better. Alexiscoutinho (talk) 01:41, 7 July 2021 (UTC)
Should a broken tool, no longer being developed, be allowed to edit Wikipedia?
DAB Solver [http://69.142.160.183/~dispenser/view/Dab_solver tool link] was developed by :User:Dispenser/Dab_solver. I saw "was" because I understand the tool is no longer being maintained. Yesterday it caused a storm in a teacup with an oversensitive editor who objected when I reverted a change that replaced a disambiguation link (not ideal) with a redirect (not idea) and instead I put the correct link in there. I also noticed that in the background, with the person using the tool being unaware, it is changing correct instances of {{tl|Cite web}} (and its cite siblings) with {{tl|cite web}} - despite the fact that other tools/bots change it from lowercase to uppercase. Given that the tool isn't being maintained, is not properly fixing dab links as it advertises, and is doing odd things in the background, should it be allowed to continue editing or be blocked? 10mmsocket (talk) 08:05, 6 July 2021 (UTC)
:Just to note this does not seem to be happening only with Dab solver. It seems to be appearing whenever older-style cite parameter labels exist on a page. Whenever the page gets edited at all, the cite <param> labels are changed from Cite to cite. But actually isn't cite web, etc., the norm, anyway? I agree it is probably an unneeded, maybe annoying thing, but I do no think it's correct that other tools will then change it back? Surely that is not right?
:If I use the ref tool, like so: [{{cite web |title=Synonyms of oversensitive {{!}} Thesaurus.com |url=https://www.thesaurus.com/browse/oversensitive |website=www.thesaurus.com |access-date=6 July 2021 |language=en}}] all the parameter labels in the template are already lower case. I guess I just don't understand what it's all about.
:(I am the "teacup-oversensitive user" who was startled to be told they had "broken templates", with increasingly peremptory 2nd, 3rd, etc., "cease and desist" notices, before the first had barely had time to pop up for me. Lots of scary accusations and doom-laden orange bars, rather less explaining!) All over to you, the real WP-ers, now. Best, 49.177.30.125 (talk) 08:37, 6 July 2021 (UTC) Did I do the that mess above, somehow? 49.177.30.125 (talk) 08:40, 6 July 2021 (UTC)
:While unmaintained Dab Solver works well. The tool doesn't select the links, the user does. So if sub-optimal links are being chosen that's not the fault of the tool. The other issues e.g. changing C to c in template titles can be avoided by unchecking the box that says "Apply common fixes" at the top of [http://69.142.160.183/~dispenser/view/Dab_solver the tool]. Nthep (talk) 13:06, 6 July 2021 (UTC)
::Good point about the "apply common fixes". And again I take your point that the user needs to be more careful in choosing the right link - although the tool itself doesn't make any distinction between links to valid pages or links to redirects. I guess less experienced click-happy editors just get carried away and don't see the train wreck they're leaving in their wake. Fixing the tool would be best IMO, but at least I know now how to advise the inexperienced editors using it incorrectly. Many thanks. 10mmsocket (talk) 13:11, 6 July 2021 (UTC)
{{reflist-talk}}
:
:I don't know that this is the correct venue for this topic – not really 'technical' but more 'policy' I think. Still, tools that break stuff, especially those tools that are no-longer maintained (WP:REFILL is a prime example of that) should not be allowed to run. Yeah, I know, the editors who operate those tools are responsible for the edits that the tools make; but much too often, {{em|much}} too often, those tool operators accept whatever the tool suggests regardless of the results which leaves it to others to correct. I grow weary of cleaning up after such edits. I don't know how the IP editor created the citation above, but it is clearly wrong: {{!}} Thesaurus.com
does not belong in {{para|title}} because that is not the title of the page that readers see. Been seeing more and more of these kinds of citations.
:—Trappist the monk (talk) 12:56, 6 July 2021 (UTC)
::{{ping|Trappist the monk}} the {{!}} Thesaurus.com
titles most likely come from the User:V111P/js/WebRef script for generating cites from web pages. I know, because I sometimes use said tool, that it has a tendency to append the name of the publication in the title with that exclamation mark, even in cases where it also puts that publication name in the {{para|work}} parameter. I have no idea why, but I try to always remove it from the title myself. — Amakuru (talk) 13:07, 6 July 2021 (UTC)
:::Thanks, posted a comment there.
:::—Trappist the monk (talk) 13:26, 6 July 2021 (UTC)
:::Amakuru, Trappist: The tool isn't "appending" or "adding" the website name, it's obviously reading the <title>
element from the target and using it unchanged for {{para|title}} instead of trying to figure out what the human reader sees as the title when viewing the page content. It's hardly mysterious, IMO. — JohnFromPinckney (talk / edits) 14:38, 6 July 2021 (UTC)
::::Just because the tool is fetching information from {{tag|title}} doesn't make that information correct. On the example page, for example, there are two {{tag|title}} tags:
:::::{{code|lang=html|1=
OVERSENSITIVE Synonyms: 246 Synonyms & Antonyms for OVERSENSITIVE {{!}} Thesaurus.com}} – source for browser tab
:::::{{code|lang=html|
Thesaurus.com}}
::::and there is this which appears to be the source for {{para|title}} in the example above but doesn't match that text in the browser tab:
:::::{{code|1=}}
::::Wrong information, no matter how easily used in a cs1|2 template is still wrong information. Permitting these tools to create malformed citations, like the one above, is a disservice to the encyclopedia and a burden imposed on other editors who have to cleanup the mess.
::::—Trappist the monk (talk) 20:00, 6 July 2021 (UTC)
:::::Its not malformed, it's slightly incorrect and easily fixed. More easily than a bare reference. Just fix the citation and move on. —TheDJ (talk • contribs) 21:33, 6 July 2021 (UTC)
::::::No. It is malformed. Why should I have to fix, again, and again, and again, something that the tool-drivers created. The problem is that, all too often, the tool drivers (not just newbies but also some very very experienced editors) can't be bothered to fix what the tools create so it falls to others to make the fix. That is at best discourteous and at worst disruptive and detrimental to the encyclopedia. If I wrote a bot that performed as poorly as some of these tools perform, the community would rise up and shutdown the bot. Yes, I know, the tool drivers are (in theory at least) responsible for the edits that the tools they drive make. Alas, too many of them don't bother to fix the crap that is produced. I know this because I have fixed way too much of the junk.
::::::—Trappist the monk (talk) 21:56, 6 July 2021 (UTC)
- Just on a point of order, {{u|10mmsocket}} you are incorrect that it is "bad form to introduce redirects into articles". At most it's harmless, and in some cases it's preferable to have a redirect rather than an actual link to the article per MOS:RDR. Certainly the IP was doing good work and improving the encyclopedia by fixing links to dab pages, and a wet fish is due to you for attacking them for that. Cheers — Amakuru (talk) 13:14, 6 July 2021 (UTC)
- :I love fish, thanks. You do of course make a point, which I note. However, if the IP editor hadn't been overly sensitive this wouldn't have been an issue. While we all strive to be civi here, it is sometimes impossible not to offend some people. 10mmsocket (talk) 13:20, 6 July 2021 (UTC)
- Every change to CS1|2 has the potential to break tools and bots. Since CS1|2 is changing all the time, any tool or bot not actively maintained should be suspended, the environment here is too dynamic to rely on users to fix mistakes manually. -- GreenC 00:07, 7 July 2021 (UTC)
- If any decision being made results in editors adding a reference with something like an extraneous template parameter vs not adding a reference (or even only adding a bareurl), I'm going to tend to support the former in most cases. — xaosflux Talk 09:43, 7 July 2021 (UTC)
Editing modes
{{resolved}}
I've run into some errors, and after testing on my alt, it appears I'm opening edit pages differently. By default, th editing pages load with a toolbar at the top, but in my slt, it has features at the top, and the publish, show changes etc. buttons at the button. How do I get the latter editing mode as my default? (The latter editing mode also appears to have an older UI, and is similar to the Convenient Discussions one.) ―Qwerfjkltalk 20:59, 6 July 2021 (UTC)
:You can identify the editors in question: here —TheDJ (talk • contribs) 21:26, 6 July 2021 (UTC)
::Thanks, that helped me fix the issue! ―Qwerfjkltalk 15:41, 7 July 2021 (UTC)
Script not working
This:
mw.hook('convenientDiscussions.commentsReady').add(function () {
// comments_in_local_time.js import code
importScript('User:Gary/comments in local time.js'); // Backlink: User:Gary/comments in local time.js
});
doesn't seem to load comments in local time. This is being loaded after Convenient Discussions. ―Qwerfjkltalk 06:21, 6 July 2021 (UTC)
:I think we've given you this advice before: unload ALL of your scripts and then try the one you want. When you have issues with someone else's personal script that you've imported the best place to start asking questions about it is on their talk page. As you are loading a very large number of personal scripts in User:Qwerfjkl/common.js it is certainly likely they will collide with each other, or that you are trying to use them outside the method their author intended them to be used with; even single syntax errors may cause everything in your script file to break. You may get another response here - but because you are choosing to use so many personal scripts at once, that is the risk you take. — xaosflux Talk 10:21, 6 July 2021 (UTC)
::Ahh! My eyes! HighInBC Need help? Just ask. 10:24, 6 July 2021 (UTC)
::{{re|Qwerfjkl}} I didn't mean to come off harsh there, This just seems like it's approaching a "when I hit myself it hurts -- well stop hitting yourself" situation. A venue that may get you better support for this type of discussion is Wikipedia talk:User scripts, it is mostly attended to by other user-script enthusiasts such as yourself. If you have a general site-wide tech issue, or see a problem with one of the site-wide gadgets, VPT is the right spot though! — xaosflux Talk 10:28, 6 July 2021 (UTC)
:::@Qwerfjkl: Xaosflux is exactly correct IMO; when you have this many scripts, it's not really reasonable for us to debug everything for you. That said, I'm guessing the reason this script isn't executing is that I don't see any hook named "convenientDiscussions.commentsReady" in User:Jack who built the house/convenientDiscussions.js, which is presumably where you're expecting that hook to come from. So you're attaching the script in a handler to a hook that never seems to be fired. Writ Keeper ⚇♔ 13:49, 6 July 2021 (UTC)
::::I don't think that's the culprit. The import code is documented at c:User:Jack who built the house/Convenient Discussions#Compatibility. The local JS just loads the script on Commons, where you can find the firing code ([https://github.com/jwbth/convenient-discussions/blob/5f7e65a9a8e379d88c02718af41d4936d827b1a7/src/js/processPage.js#L424 here]'s the unminified version). Nardog (talk) 14:31, 6 July 2021 (UTC)
:Along with the things already mentioned (~200 scripts? How can you find the actual article text?), I noticed somewhat by chance, that you even have duplicated entries. Lines 46 and 48 appear to be identical (replacing the same script commented out at line 12), although there's no benefit in installing it twice. I'm rather amazed that any scripts work in that huge pile, not that the last one installed doesn't. — JohnFromPinckney (talk / edits) 14:24, 6 July 2021 (UTC)
:I have the same snippet in my common.js, except that it's using User:SD0001/comments in local time.js instead of the Gary version – I think this fork is better compatible with Conv Discussions, but the Gary version was also working for me so not sure if this would solve the issue for you. – SD0001 (talk) 15:09, 6 July 2021 (UTC)
::@SD0001 Thanks, using your script worked! I've also cleaned up my common.js page a bit. I only asked here in case I'd misunderstood how to load the comments in local time script. Sorry for not making that clear. ―Qwerfjkltalk 15:48, 6 July 2021 (UTC)
:As another CD-related error, this:
o/w/api.php?titles=r&origin=*&format=json&formatversion=2&uselang=content&maxage=86400&smaxage=86400&action=query&prop=revisions|info&rvprop=content&rvlimit=1:1 Failed to load resource: net::ERR_NAME_NOT_RESOLVED
has been fulling up my console (reaching over 100 messages), and also preventing me from viewing messages posted with CD. ―Qwerfjkltalk 15:54, 6 July 2021 (UTC)
::Can you provide more details about this error? It doesn't seem to come from Convenient Discussions.{{pb}}> preventing me from viewing messages posted with CD
Can you elaborate? Jack who built the house (talk) 17:02, 6 July 2021 (UTC)
:::@Jack who built the house to clarify, once I click {{button 2|Reply}}, it doesn't show the comment as posted, even though it has. It appears as if I have done nothing (after loading a bit) and reclicking the button can post a comment multiply times. An error message saying {{red|check your console}} also appears. ―Qwerfjkltalk 18:57, 6 July 2021 (UTC)
::I think that's because the path "o/" doesn't exist on enwiki (unless one of the scripts uses other server). And it probably comes from that convoluted script in 2nd line of your common.js. MarMi wiki (talk) 18:51, 6 July 2021 (UTC)
:::@MarMi wiki That script is SD0001's Making user scripts load faster. ―Qwerfjkltalk 19:18, 6 July 2021 (UTC)
::::That page specifically says to bring up questions at User talk:SD0001/Making user scripts load faster, I suggest you go there. — xaosflux Talk 23:39, 6 July 2021 (UTC)
:Might be related this Phabricator error:
{{collapse top|Large output dump}}
load.php?lang=en&modules=jquery%2Coojs-ui-core|jquery.ui&skin=vector&version=1a0i7:135 GET https://phabricator-bug-status.toolforge.org/queryTasks?callback=jQuery36009011871784048877_1625672516298&ids=%5B93049%2C286115%2C285766%5D&_=1625672516299 net::ERR_ABORTED 500
send @ load.php?lang=en&modules=jquery%2Coojs-ui-core|jquery.ui&skin=vector&version=1a0i7:135
ajax @ load.php?lang=en&modules=jquery%2Coojs-ui-core|jquery.ui&skin=vector&version=1a0i7:129
jQuery.ajax @ load.php?lang=en&modules=jquery%2Coojs-ui-core|jquery.ui&skin=vector&version=1a0i7:150
(anonymous) @ VM1236:266
(anonymous) @ VM1236:267
runScript @ load.php?lang=en&modules=startup&only=scripts&raw=1&skin=vector:12
execute @ load.php?lang=en&modules=startup&only=scripts&raw=1&skin=vector:14
doPropagation @ load.php?lang=en&modules=startup&only=scripts&raw=1&skin=vector:6
requestIdleCallback (async)
requestPropagation @ load.php?lang=en&modules=startup&only=scripts&raw=1&skin=vector:7
setAndPropagate @ load.php?lang=en&modules=startup&only=scripts&raw=1&skin=vector:7
implement @ load.php?lang=en&modules=startup&only=scripts&raw=1&skin=vector:19
(anonymous) @ VM1236:1
domEval @ load.php?lang=en&modules=startup&only=scripts&raw=1&skin=vector:11
(anonymous) @ load.php?lang=en&modules=startup&only=scripts&raw=1&skin=vector:17
requestIdleCallback (async)
asyncEval @ load.php?lang=en&modules=startup&only=scripts&raw=1&skin=vector:17
work @ load.php?lang=en&modules=startup&only=scripts&raw=1&skin=vector:18
enqueue @ load.php?lang=en&modules=startup&only=scripts&raw=1&skin=vector:11
load @ load.php?lang=en&modules=startup&only=scripts&raw=1&skin=vector:20
(anonymous) @ load.php?lang=en&modules=startup&only=scripts&raw=1&skin=vector:68
(anonymous) @ load.php?lang=en&modules=startup&only=scripts&raw=1&skin=vector:68
{{collapse bottom}}
which appears before the other erros.
―Qwerfjkltalk 15:45, 7 July 2021 (UTC)