Wikipedia:Village pump (technical): Difference between revisions

Policy

Technical

Proposals

Idea lab

WMF

Miscellaneous

• Table of contents
• First discussion
• End of page
• New post

Shortcuts

• WP:VPT
• WP:VP/T
• WP:TECHPUMP
• WP:PUMPTECH

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

If you want to report a JavaScript error, please follow this guideline. Questions about MediaWiki in general should be posted at the MediaWiki support desk. Discussions are automatically archived after remaining inactive for five days.

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

« Archives, 193, 194, 195, 196, 197, 198, 199, 200, 201, 202, 203, 204, 205, 206, 207, 208, 209, 210, 211, 212, 213

The preview image (the image displayed when hovering the mouse over the article link, not sure if that's the correct name) for the articles Escape the room and Interactive film is the same preview image as that of Debridement, although the former two articles have no images and are not related. It may affect other articles with no images, but does not affect all articles with no images. Bug observed while accessing English Wikipedia with the skin Vector 2022 (as well as Vector and Monobook) on Chrome 111.0.5563.111 on Windows 10. PriusGod (talk) 16:29, 29 March 2023 (UTC)[reply]

@PriusGod, this is unfortunately not a bug but instead vandalism that takes a bit to clear from the system. You should be able to WP:NULLEDIT affected pages to clear the cache. Izno (talk) 16:34, 29 March 2023 (UTC)[reply]

I think there is a discussion going on at WP:ERRORS related to this issue on the main page currently. I'm basically worthless on technical matters such as this, but if someone could read the current discussion and see if the problem may be fixed, that'd be great. Thanks! --Jayron32 18:02, 29 March 2023 (UTC)[reply]

@Jayron32, yes, that is the same issue as described here. As above, null editing the pages which have the templates that were vandalized will correct the issue. Izno (talk) 18:04, 29 March 2023 (UTC)[reply]

Which page is the affected one? The main page or the United States page? I'll be glad to pull the trigger on the fix, but I don't know which is the source of the problem. --Jayron32 18:05, 29 March 2023 (UTC)[reply]

@Jayron32, the one with the vandalized template. That would be the United States page in your question, I believe. Izno (talk) 18:08, 29 March 2023 (UTC)[reply]

Hey y'all. A discussion has been taking place at WP:ERRORS regarding the ITN blurb on the baseball world championship. People, including me, have noticed that article previews of the baseball teams of the US (and I guess Japan's too?) show this image, even on the mobile application version of Wikipedia. The image is not featured in both articles. @Jayron32 has stated that this issue isn't present for him and told me as such to go here, so I would like some input regarding what to do about this. - Knightsoftheswords281 i.e Crusader1096 ( Talk Contribs Wikis ) 18:33, 29 March 2023 (UTC)[reply]

pssst. Look up. --Jayron32 18:34, 29 March 2023 (UTC)[reply]

Whoops. - Knightsoftheswords281 i.e Crusader1096 ( Talk Contribs Wikis ) 18:35, 29 March 2023 (UTC)[reply]

Hi. I just found that the preview popups of Bopomofo, Gwoyeu Romatzyh, and Romanization all show the same thumbnail image (debribement). Zhaowei Wu (talk) 02:19, 30 March 2023 (UTC)[reply]

Yes, same issue. Caused by a different vandal. Izno (talk) 02:23, 30 March 2023 (UTC)[reply]

The preview image for Egyptiotes currently shows a fly on a piece of feces. I do not know how to fix the issue. Pearse16 (talk) 04:20, 1 April 2023 (UTC)[reply]

Template:Greeks was vandalized a day ago. The vandalism was quickly reverted but the page image uses caching. It's fixed now for that article after I purged it. PrimeHunter (talk) 04:46, 1 April 2023 (UTC)[reply]

This issues seems to be iOS-only, and it's reeally weird (has the energy of a low quality April Fools' prank gone awry).

The description shows as "consumption of feces" but there are no edits showing the description being edited to this. Editing the description fixes the issue, and then even if it gets reverted back to the old description (which wasn't showing before), it reverts back OK. It was happening on GPT2 (current page is OK as there have been edits as described above) and I noticed it on the Fried dough page (there are two edits there from me, changing short description and then changing it back). I can see it right now on the Hi-Line (Montana) page (on mobile only). The search snippet I found to get me to that page (which included "consumption of feces" showed a search snippet which seemed to come from the Coprophagia article. Strangefeatures (talk) 21:34, 2 April 2023 (UTC)[reply]

Looks like this was the other side effect of Wikipedia:Administrators'_noticeboard/Incidents#Vandalized_Preview_Pop_Ups_for_American_cuisine_and_a_Large_Number_of_Related_Articles - purgeing the page should fix it. Galobtter (pingó mió) 21:39, 2 April 2023 (UTC)[reply]

The GPT-2 temporary SD appears to have been caused by this edit to a template that is transcluded in that page. I am null-editing all pages that transclude that template and about a dozen other vandalized templates. It appears that somewhere over 1,000 pages were affected. – Jonesey95 (talk) 22:30, 2 April 2023 (UTC)[reply]

There is one account listed at the ANI thread, another IP linked above, and there is a second account here. -- zzuuzz ^(talk) 22:39, 2 April 2023 (UTC)[reply]

Take for example

• Take back control

Mouse over shows a gory image (WARNING, GORE) https://commons.wikimedia.org/wiki/File:Necrotizing_fasciitis_left_leg_debridement.JPEG that is not in the article and not relevant to it. Looks like a hack, tbh. Any ideas? 𝕁𝕄𝔽 (talk) 12:36, 5 April 2023 (UTC)[reply]

I suspect this is to blame for it appearing in the first place. I gave the article page a null edit and the image no longer appears on mouseover. Aidan9382 _(talk) 12:42, 5 April 2023 (UTC)[reply]

Rats, I didn't spot that. Maybe I was looking via mobile i/f at the time. TYVM. --𝕁𝕄𝔽 (talk) 13:50, 5 April 2023 (UTC)[reply]

Take a look at market fundamentalism. When I hover over it with page previews on, I get a cute little picture of a fly on shit. What's going on? --jpgordon^{𝄢𝄆𝄐𝄇} 02:32, 6 April 2023 (UTC)[reply]

We're seeing that as a pattern of vandalism of transcluded sidebar templates (see WP:ANI#Vandalized Preview Pop Ups for American cuisine and a Large Number of Related Articles). Is it still happening? DMacks (talk) 02:43, 6 April 2023 (UTC)[reply]

yup --jpgordon^{𝄢𝄆𝄐𝄇} 03:08, 6 April 2023 (UTC)[reply]

I managed to reproduce it, but then purged the cache and it was gone (that's one of the tricks mentioned in that previous thread). DMacks (talk) 07:20, 6 April 2023 (UTC)[reply]

Given the WMF has refused to do so, and given that they have ignored my comment that if they don't we will, although we would prefer they do as the solution will be cleaner, I think our only option is for us to do this ourselves.

Alexis Jazz has been kind enough to provide the CSS required for us to do this, which can be seen here.

A demonstration of this code can be seen here; note that the flash of unstyled content only appears for the demo, and putting the code in your own vector-2022.css style sheet or in MediaWiki:Vector-2022.css does not result in it.

I'm putting the code here for review by the broader community; if no one sees any issue with it then in line with the consensus at the Vector 2022 rollback RfC I will make an edit request at MediaWiki talk:Vector-2022.css. BilledMammal (talk) 20:21, 29 March 2023 (UTC)[reply]

phab:T332505 and phab:T332426 haven't been "refused" at this point, interested technical editors are welcome to contribute a patch for the first. — xaosflux ^Talk 21:09, 29 March 2023 (UTC)[reply]

The WMF has made it clear through comments at Wikipedia talk:Requests for comment/Rollback of Vector 2022#Proposal for next steps following the closure of the Vector 2022 RfC that they will not be implementing full width as default; I believe that we made the right choice in the introduction of the limited width and that, for readers, we are continuing to make the right choice in the decision to keep it as the default, emphasis mine.

Given this, and given their failure to reply to this comment, I don't see any reason to believe that this will change, regardless of whether the phab tickets remain technically open, and as such we need to do this ourselves. BilledMammal (talk) 21:13, 29 March 2023 (UTC)[reply]

The test would be if there was refusal to promote the patch, doing this server side would be much preferable then client-side hacks, especially for logged out users. As far as DIY, if you have a patch ready submit it and see. — xaosflux ^Talk 21:16, 29 March 2023 (UTC)[reply]

I don't have a patch, but I think a comment from the Chief Product and Technical Officer for the Wikimedia Foundation saying that they are continuing to make the right choice in the decision to keep it as the default is sufficient test; I doubt they'll suddenly reverse their opinion because a patch permitting such an option was provided.

I'm also not particularly eager to spend time learning the WikiMedia code base so that I could create such a patch, as I see no reason to believe it would be accepted - I also note Izno's comment about whether a solution for this would be better done in style sheets. BilledMammal (talk) 21:25, 29 March 2023 (UTC)[reply]

FWIW, I tested that code snippet on test2wiki, and it is not ready as-is, many pages got forced in to an even-narrower viewport that could not be recovered from. Anything like this would need very very extensive testing (think of how much went in to the client-side darkmode hack, and there are still errors reported constantly). — xaosflux ^Talk 00:40, 30 March 2023 (UTC)[reply]

Can you give an idea what sort of pages those appear in? I've also found an issue with preference/contribution/etc pages; I'm working on that one. BilledMammal (talk) 01:48, 30 March 2023 (UTC)[reply]

Figured out part of the reason there are issues on contribution/category/etc pages; it's disabled by default there. This does mean that there is a bug in that the toggle shows up even on those pages; I've submitted a bug report. BilledMammal (talk) 02:46, 30 March 2023 (UTC)[reply]

Mostly on every Special: page. Note, it isn't just the icon being there or not, that CSS made the entire page much worse. As I noted, this would need extensive testing across all pages and actions before we would ever consider it for production. — xaosflux ^Talk 09:51, 30 March 2023 (UTC)[reply]

Sorry, I wasn't clear; the bug with the toggle was unrelated except for the fact that I discovered it while looking into this. The reason it fails there is because by default the width toggle is disabled on pages in namespaces 12 and -1 (with the exception of user preferences); because this wasn't accounted for it resulted in some unexpected behavior.

Alexis Jazz has produced an updated script that fixes most of those issues, although I believe there are a couple still to resolve - I'll look into it further when I have time, and in the meantime hopefully it will become unnecessary because the WMF will agree to implement it on their end. BilledMammal (talk) 22:41, 30 March 2023 (UTC)[reply]

It also seems to break the full/limited width toggle for logged out users.. is the idea to prevent unregistered users from selecting a preference? — TheresNoTime (talk • they/them) 01:50, 30 March 2023 (UTC)[reply]

My tests suggest that it does work for logged out users, although there is still some work to be done per xaosflux - see the demonstration linked above. It could be that the version I'm currently working on broke something there? I've updated the link in the original post to a static container. BilledMammal (talk) 02:31, 30 March 2023 (UTC)[reply]

@Xaosflux: I looked into creating a patch, and believe I have something that would allow TNT's patch to work; see the bottom of phab:T332505. BilledMammal (talk) 07:42, 30 March 2023 (UTC)[reply]

@BilledMammal: I just wanted to note this somewhere; my interactions with Vector 2022 and the resultant RfC/discussions/etc. have been entirely in my capacity as a volunteer (and I include the above-mentioned patch in that). I'm always more than happy to help where I can though, up to and including writing patches and trying to "prod" the right people to take a look — TheresNoTime (talk • they/them) 08:19, 30 March 2023 (UTC)[reply]

Thank you, it is appreciated. BilledMammal (talk) 09:04, 30 March 2023 (UTC)[reply]

You might have to translate for us mere non-coding mortals. Would that make it the default for English Wikipedia? North8000 (talk) 21:18, 29 March 2023 (UTC)[reply]

Yes, this CSS would make full width the default on the English wikipedia if added to MediaWiki:Vector-2022.css. BilledMammal (talk) 21:25, 29 March 2023 (UTC)[reply]

Hi everyone, thank you for bringing this up. I just wanted to mention that the discussion on next steps is still ongoing on this page and we’re still working on the best way to proceed. We have presented a few different options for how all users can clearly choose which width they prefer, and which the community is currently discussing and weighing the pros and cons of. There is also discussion of how we can respect current existing user preferences on the width. We hope to allow a few more days for discussion and provide a summary and concrete next steps by Tuesday, April 4. @SDeckelmann-WMF is out this week, but will be back next week to continue the conversation. OVasileva (WMF) (talk) 01:01, 30 March 2023 (UTC)[reply]

@OVasileva (WMF): To clarify, are you saying that things have changed since 25 March and you will now be respecting the consensus to set the default for logged-out users as full width? BilledMammal (talk) 01:05, 30 March 2023 (UTC)[reply]

Alexis Jazz has produced an updated version of the CSS file, which may have fixed the issues you saw Xaosflux; so far, I'm not noticing any. It can be found here. BilledMammal (talk) 09:04, 30 March 2023 (UTC)[reply]

All this is so sad, and I bet most people are tired of it. So there was a well hidden RFC, where someone snuck in a second question somewhere near the bottom of the page. And some people answered what they liked better, and there were some good arguments like why any publication ever published had limited line length. Expectedly, no agreement was reached. But hey, there's consensus, and we'll make the English Wikipedia different from any other Wikipedia in the World, and we're gonna push it just so we can show who's the boss. That RFC was like me standing in the long return line at Costco the other day; guess what, everyone had to say something against Costco, 100% consensus! 300 people is by no means a majority of users. It's not even a majority of this Wikipedia's administrators. But okay, keep pushing your agenda, enjoy your 1.5 foot line lengths. 2604:CA00:16B:990E:0:0:662:4239 (talk) 18:11, 30 March 2023 (UTC)[reply]

You are implying that the majority of arguments either way where WP:ILIKEIT, which is not the case. They presented considerations that involve the implications of the changes on the experience of all users, not just the preferences of the RfC's participants. It is also strange that you are calling one of the most participated-in RfCs of all time "well hidden," and the second question was there almost from the start. small jars tc 09:18, 31 March 2023 (UTC)[reply]

well hidden the RfC was listed at WP:CENT, notified at every applicable noticeboard and talk page, even including Donald Trump’s talk page for some reason, and reached WP:300 levels for support, WP:200 for oppose, and over 150 participants in the second question alone. Aaron Liu (talk) 02:01, 2 April 2023 (UTC)[reply]

English Wikipedia was already different from the rest of the world long before a Vector 2022 was ever considered. Every wiki is unique. Not sure what you were heading at there. Tvx1 21:24, 2 April 2023 (UTC)[reply]

I personally would wait to see what WMF does before diving into CSS. It is WP:NOTAVOTE, it is a consensus process. Whatever we do we should take into account practical considerations, like different screen sizes and devices. Maybe set the "limited width" to only take effect as soon as the screen is extended beyond a specific screen resolution (like 1080px)? This is a good compromise between those that want some fixed width and those that want unlimited width. Then we do not have to worry about window resizing or any of that nonsense. It could be an in-between toggle. Aasim - Herrscher of Wikis ❄️ 14:30, 31 March 2023 (UTC)[reply]

Then the contention would be that the width that you need to go to before fixed width takes effect is wider than the scientific optimum. small jars tc 15:41, 31 March 2023 (UTC)[reply]

We already have a consensus on the matter. A “compromise” here is unacceptable. Default width needs to be default. Toa Nidhiki05 22:03, 31 March 2023 (UTC)[reply]

Please also note that a hacky workaround like this can easily break if the skin gets redesigned. Vector 2022 is still a new skin, and there will certainly be changes to make the skin stable. We should certainly give it time to evolve to meet the needs of the community and its readers. I know of many of my tools that have broken because of redesigns. Let's not make this hack be one of them. Aasim - Herrscher of Wikis ❄️ 22:32, 31 March 2023 (UTC)[reply]

It’s almost like the skin isn’t ready for prime time. But regardless, WMF can resolve this but implementing unlimited width. I hope they do so. Toa Nidhiki05 01:27, 1 April 2023 (UTC)[reply]

V22 has been in the works for years and always based on v10, a sudden redesign to the width is very unlikely. Aaron Liu (talk) 02:02, 2 April 2023 (UTC)[reply]

Maybe not right now, but when they fully deploy? This will certainly be something that will need to be considered given the skin is still a WIP. I have a feeling the Vector 2022 that you see in seven or eight months will be a different skin than the Vector 2022 you see right now. Aasim - Herrscher of Wikis ❄️ 17:02, 2 April 2023 (UTC)[reply]

I don’t think they would make such a major change to limited width, a very small (code-wise) feature, after working on this skin for so long Aaron Liu (talk) 11:22, 3 April 2023 (UTC)[reply]

While technically any workaround would be our problem, in practice the WMF will need to be careful not to break it as they have a strong interest in not breaking enwiki. BilledMammal (talk) 18:09, 7 April 2023 (UTC)[reply]

1. Go to https://en.wikipedia.org/wiki/Wikipedia:April_Fools/April_Fools%27_Day_2023?&useskin=vector

• Page is out of date, at the bottom it says "This page was last edited on 31 March 2023, at 23:22 (UTC)."

2. Click on the (refresh) on the top template to go to https://en.wikipedia.org/w/index.php?title=Wikipedia:April_Fools/April_Fools%27_Day_2023&action=purge

3. Click "Yes" to purge the cache

• The page redirects to the default mobile view at https://en.wikipedia.org/wiki/Wikipedia:April_Fools/April_Fools%27_Day_2023
• The page is up to date, bottom of the page says "This page was last edited on 1 April 2023, at 00:17 (UTC)."

4. Go back to https://en.wikipedia.org/wiki/Wikipedia:April_Fools/April_Fools%27_Day_2023?&useskin=vector to restore desktop view

• The page is out of date again, bottom of the page says "This page was last edited on 31 March 2023, at 23:22 (UTC)."
  • This is not fixed by Ctrl+F5 or clearing browser cache.

91.129.111.163 (talk) 00:26, 1 April 2023 (UTC)[reply]

•  Works for me however, you must have an account to use "purge". — xaosflux ^Talk 22:24, 3 April 2023 (UTC)[reply]

  I don't think that's true, appending ?action=purge to a normal (non-query) URL has been suggested on this page in the past as being fine for IPs to use; indeed, WP:PURGE does not say that it's for logged-in users only. I tried testing it logged-out, but my IP is currently rangeblocked. I need to try it from a different machine, or maybe reboot my router. --Redrose64 🌹 (talk) 08:52, 4 April 2023 (UTC)[reply]

  @Redrose64 notice the (purge) permission is on "Users" not on "*". IP's can do a nulledit though. — xaosflux ^Talk 10:14, 4 April 2023 (UTC)[reply]

  I didn't say anything about a purge tab, I was referring to altering the URL in the address bar. I'm on a different machine now, and before I logged in I went to a page, appended ?action=purge to the URL, and was presented with a box containing "Purge this page", "Clear the cache of this page? (What does this do?)" and the button Yes; below the box was the text "Purging a page clears the cache and forces the most current revision to appear. For pages with random components, it also forces a new random selection.". --Redrose64 🌹 (talk) 11:37, 4 April 2023 (UTC)[reply]

  @Redrose64 welp, yup - and it's been like that for a while - just the documentation is a mess - phab:T291316 also called for a revert of that lack-of-permission thing, but that is probably going to eventually be declined. — xaosflux ^Talk 13:36, 4 April 2023 (UTC)[reply]

  Further testing shows that whilst the button is clickable, doing so fails silently. So, IPs can't purge pages, although they may not know that. --Redrose64 🌹 (talk) 16:05, 4 April 2023 (UTC)[reply]

  @Redrose64 yea, seems like something is amiss with all that - perhaps they can "submit" the purge request, but then it fails. How are you sure that it failed? — xaosflux ^Talk 16:29, 4 April 2023 (UTC)[reply]

  Go to Category:Empty categories awaiting deletion, pick a subcategory, follow the link to that page. Check the bottom line of the pink box, and if there is an obvious discrepancy (e.g. This page was last edited by ... at 04:59, 1 April 2023 (UTC) (38 seconds ago)), that's one to test with. If it doesn't, try another subcategory.

  Return to Category:Empty categories awaiting deletion, right-click on the same link and select "Open Link in New Private Window" (or your browser's equivalent) which treats you as logged out. Check that the bottom line of the pink box still shows a discrepancy. Append ?action=purge to the URL, and when the box appears, click Yes and see if the bottom line has changed - for me it doesn't.

  Now close that private window, follow the link in the normal way, and again purge the page by appending ?action=purge to the URL and observe that this time, the text "(38 seconds ago)" changes to "(3 days ago)" or similar. --Redrose64 🌹 (talk) 21:03, 4 April 2023 (UTC)[reply]

• URLs of the format https://en.wikipedia.org/wiki/<title>?useskin=vector are non-canonical and are not updated by MediaWiki when a page is updated or a manual purge is issued. For those curious, the list of URL formats that get purged are mostly listed here. Legoktm (talk) 05:46, 8 April 2023 (UTC)[reply]

MediaWiki message delivery 23:37, 3 April 2023 (UTC)[reply]

Quiddity (WMF) or other WMF staff: are there release notes coming for the new version of MediaWiki? They are a bit overdue. – Jonesey95 (talk) 12:56, 5 April 2023 (UTC)[reply]

@Jonesey95: Hmm, it should be automated. I'll check/ask what's broken. Thanks. Quiddity (WMF) (talk) 17:21, 5 April 2023 (UTC)[reply]

This branch cut initially failed because of some of the deploy services on toolforge being down. I'm assuming that has something to do with it. —TheDJ (talk • contribs) 08:17, 6 April 2023 (UTC)[reply]

I had seen that, but then the deployment proceeded, and according to https://versions.toolforge.org/ it is complete, but still no release notes. Strange. – Jonesey95 (talk) 12:01, 6 April 2023 (UTC)[reply]

The automated job which normally does this failed — I've manually created it via the make-deploy-notes script. Logged T334211 for reference. — TheresNoTime (talk • they/them) 13:43, 6 April 2023 (UTC)[reply]

FWIW, I've pushed out __ARCHIVEDTALK__ to some of the major talk archive temples, will take a while for transcluded pages to get updated. — xaosflux ^Talk 13:58, 6 April 2023 (UTC)[reply]

And I've now done mw-archivedtalk for most of them. {{collapse top}} and {{collapse}} are currently used in mainspace and shouldn't be, so while it wouldn't hurt to add it to those, those do also need to be fixed.... Izno (talk) 21:19, 7 April 2023 (UTC)[reply]

Ah this explains why my recent changes page no longer has colored highlighting and doesn't have the thing I can press to refresh the page anymore. Dang... Gatemansgc (TɅ̊LK) 00:00, 7 April 2023 (UTC)[reply]

@Gatemansgc Do you mean the New filters for edit review? That should still work properly, and works for me in testing it just now. Quiddity (WMF) (talk) 00:17, 7 April 2023 (UTC)[reply]

My browsers are old! I didn't think Wikipedia would no longer work for me! Eventually I'll be moving to a new computer but for now I don't get the highlighting or javascript based refresh. Gatemansgc (TɅ̊LK) 00:28, 7 April 2023 (UTC)[reply]

You should be able to run a recent version of Firefox. The latest version (111) is listed as compatible with Windows 7, which was released in 2009, and on Mac OS Sierra (10.12), which can run on any Mac made in 2010 or later. – Jonesey95 (talk) 01:56, 7 April 2023 (UTC)[reply]

Starting today my watch list is acting screwy. Normally it has dots next to edits I haven't looked at.....but that is (now) there regardless if I have looked at the edit or not.....it doesn't differentiate between edits you have/haven't looked at. And also normally a option is there saying something like "Mark all changes as seen". But that isn't there anymore. Anyone know what is going on? Thanks.Rja13ww33 (talk) 01:20, 7 April 2023 (UTC)[reply]

@Rja13ww33: you wouldn't happen to be using an old (e.g. Internet Explorer) web browser would you..? — TheresNoTime (talk • they/them) 01:25, 7 April 2023 (UTC)[reply]

Yes, a older version of Google chrome. (Not to mention the fact I am still on Windows 7.)Rja13ww33 (talk) 01:28, 7 April 2023 (UTC)[reply]

You might be affected by this recent change — support for ES5 has recently been dropped. You may need to update to a supported browser — TheresNoTime (talk • they/them) 01:35, 7 April 2023 (UTC)[reply]

Thanks. I figured it was something like that.Rja13ww33 (talk) 01:37, 7 April 2023 (UTC)[reply]

Modern Firefox (current version 111) still supports Windows 7, though it needs Microsoft security update KB4474419. Chrome 109, released a few months ago, also supports it, but is the last version to do so. I'd recommend upgrading; I can't see a reason to use an old version of Chrome of all browsers. (Firefox has some cliffs here and there that would make natural cutoffs like Firefox 56.) Izno (talk) 01:47, 7 April 2023 (UTC)[reply]

Yeah, I should probably upgrade. I still use a older version of windows based on a (work) program I use....but that shouldn't stop me from getting a newer browser.Rja13ww33 (talk) 02:02, 7 April 2023 (UTC)[reply]

Lately, I've noticed that on a few occasions, when I've edited a page or posted on a talkpage, which is on my watchlist. It gets bumped off the watchlist. Is there a limit to how many pages, one can have on their watchlist? I've currently 121. GoodDay (talk) 20:39, 4 April 2023 (UTC)[reply]

There almost certainly is a limit to how many pages can be on a given watchlist, but it's much higher than 121. Do you have an example of a page which has been recently "bumped off" your watchlist? — TheresNoTime (talk • they/them) 20:50, 4 April 2023 (UTC)[reply]

The most recent, was the Charles III page. GoodDay (talk) 22:18, 4 April 2023 (UTC)[reply]

Make sure you didn't accidentally hit the "star". I've done that. BTW I have just under 2,000 on mine with no problems. North8000 (talk) 20:58, 4 April 2023 (UTC)[reply]

Also, after entering the edit summary, don't uncheck "Watch this page" before saving. --Redrose64 🌹 (talk) 21:06, 4 April 2023 (UTC)[reply]

The range for "maximum" size is usually in the realm of 10-20k pages, but that maximum size is soft, caused by database timeouts and the like. There is no hard limit on how large your watchlist can be. Izno (talk) 22:28, 4 April 2023 (UTC)[reply]

I've got 27,461 on mine. DuncanHill (talk) 22:37, 4 April 2023 (UTC)[reply]

I reached about 24,000 before I decided to cut it down. It wasn't that the watchlist itself was failing, but that Special:EditWatchlist always timed out and Special:EditWatchlist/raw took an annoyingly-long time to (i) load; (ii) allow me to edit (even going to the bottom and typing one more row was slow); (iii) save the changes. --Redrose64 🌹 (talk) 23:03, 4 April 2023 (UTC)[reply]

I've been steadily trimming mine since I hit 25,000... DuncanHill (talk) 23:05, 4 April 2023 (UTC)[reply]

25,000.... jeez! — TheresNoTime (talk • they/them) 10:21, 5 April 2023 (UTC)[reply]

@GoodDay watch that you aren't setting 'temporary' watches when you don't mean to. — xaosflux ^Talk 22:43, 4 April 2023 (UTC)[reply]

I'll try to be more careful. It's quite possible that I have been accidently hitting a wrong button. GoodDay (talk) 22:45, 4 April 2023 (UTC)[reply]

I used to have this problem of mysterious disappearances from my Watchlist, and I'm 98% convinced, via Occam's Razor, that it was human error on my part. I'm a big fan of rapidly hitting Tab-(type edit summary)-Tab-Tab-Tab-Tab-Enter to save an edit, and sometimes, if one of the Tab presses doesn't register, or if I hit a stray key along the way, I end up de-selecting the "Watch this page" checkbox. YMMV. Some people make a habit of saving the entire contents of their raw Watchlist to a user subpage every once in a while, just in case weird stuff like this happens. – Jonesey95 (talk) 23:54, 4 April 2023 (UTC)[reply]

Am I alone in experiencing severe memory leaks with Wikipedia? I have a few tabs open; they start out using 100-200MB of RAM, but after they've been open for a few hours, each tab take anywhere from 1.7GB to 4.2GB of RAM. This is a consistent pattern I've experienced for months, using V2010, V22, all Betas enabled (i.e. 2017 wikitext), all Betas disabled (i.e. 2010 wikitext), all non-default gadgets turned off, and a clean common.js file. This memory ballooning applies to articles in edit mode, or articles I'm just reading.

It's excruciating, because my SSD is completely being trashed, with consistently 40GB of swap just because of Wikipedia (and that's with only a dozen tabs open, no other app running). My SSD's going to die within less than half its expected lifetime if this isn't fixed. Chrome's "Memory" Dev Tool says the tabs' JS heaps only take 20MB, so I don't know how to diagnose this any further. DFlhb (talk) 11:35, 5 April 2023 (UTC)[reply]

@DFlhb: You might find this phabricator task helpful (doesn't appear to be any solutions mentioned there, though). It may also be worth adding a comment to that task, iff the symptoms described there match what you're experiencing. Please be sure to include as much information as possible if you do — namely your browser/operating system (and versions) — TheresNoTime (talk • they/them) 12:29, 5 April 2023 (UTC)[reply]

Done, thanks. DFlhb (talk) 13:02, 5 April 2023 (UTC)[reply]

has there been a tool (any userscript or gadget?) to format some text for easy copying? something visually like this:

abcd

Copy to clipboard

i note this has been asked long ago: Wikipedia:Village_pump_(technical)/Archive_94#Copying_pro-forma_templates Wikipedia:Village_pump_(technical)/Archive_110#Link_to_copy_page_content_to_clipboard?. RZuo (talk) 14:28, 5 April 2023 (UTC)[reply]

@RZuo nothing widespread, problem is that in most cases what this would need is to wrap the text to be copied in some sort of identifier (like a span with a class), then run a script that looks for that, generates the button, and does the copy. So why is this a problem? Because it won't work for anyone not running the script, and it won't work unless the text is marked up (which would also only be useful for people running the script). If it was for a unique case (like a single page of marked up things, the page could be loaded with an onclick script. — xaosflux ^Talk 14:50, 5 April 2023 (UTC)[reply]

"why is this a problem? Because it won't work for anyone not running the script..."

that's the same for any gadget not enabled by default.

anyway, i asked just in case i reinvent the wheel. thx for the assurance. i'll go try figuring this out with my limited coding skills. XD --RZuo (talk) 10:35, 6 April 2023 (UTC)[reply]

@RZuo, why do you want to do that? WhatamIdoing (talk) 22:13, 6 April 2023 (UTC)[reply]

because i want to easily copy a whole chunk of text? without manually selecting it with my cursor and then pressing ctrl+c? a template that has to be copypasted often? just like what other users that had asked the same question before would want to do? RZuo (talk) 12:09, 7 April 2023 (UTC)[reply]

@RZuo: I've created User:Nardog/CopyCodeBlock. It adds a copy button at the top right corner of each code block that is only visible while the mouse is inside the block. Nardog (talk) 12:59, 7 April 2023 (UTC)[reply]

It seems that something is causing Data:Interstate 74 in North Carolina.map to crash and leave the text "Map" on Interstate 74 in North Carolina and the map on List of Interstate Highways in North Carolina which uses the same data file as well. DiscoA340 (talk) 04:15, 6 April 2023 (UTC)[reply]

Opening the image directly gives: "Cannot read property '1' of undefined". Checking what I can find. —TheDJ (talk • contribs) 08:18, 6 April 2023 (UTC)[reply]

This data has a feature that is of the type GeometryCollection. GeometryCollections are rather rare and behave somewhat different from other features, so I expect that recent work introduced a bug here. I'll file a ticket. —TheDJ (talk • contribs) 08:32, 6 April 2023 (UTC)[reply]

@TheDJ Thank you, keep me posted. DiscoA340 (talk) 01:29, 7 April 2023 (UTC)[reply]

Would anyone be interested in reconstructing magic _ _TOC__ so that level2 headings create new columns?
The output would look like this, done manually just as an example, excuse the greek).
I would like to do it, but I don't know programming. Perhaps, not so useful for encylopaediae, but for dictionaries -with repetitive standard headings-, extremely suitable. Thank you!! from el.wiktionary Sarri.greek (talk) 04:26, 6 April 2023 (UTC)[reply]

ToolsDB is going read-only starting in about a half hour from now (1700Z). The outage is expected to last about an hour. More details here. I don't know exactly what tools use the database, but I would expect to see a lot of tools and bots not working properly during this time. -- RoySmith (talk) 16:31, 6 April 2023 (UTC)[reply]

@Xaosflux maybe you could do another watchlist message? -- RoySmith (talk) 16:33, 6 April 2023 (UTC)[reply]

@RoySmith I put it back, but reused the last cookie, not bothering with an edit notice here yet either. — xaosflux ^Talk 16:38, 6 April 2023 (UTC)[reply]

Is that why my watchlist is screwed up? It's not marking changes as seen.Rja13ww33 (talk) 18:04, 6 April 2023 (UTC)[reply]

Tracked in Phabricator
Task T333471

This is completed. The tech folks have requested that if you see any problems, add a comment to T333471 or ask in #wikimedia-cloud. @Rja13ww33 my guess is this wouldn't have affected your watchlist, as it doesn't (as far as I know!) use ToolsDB. -- RoySmith (talk) 18:17, 6 April 2023 (UTC)[reply]

I figured it was connected because it started today. I will ask around.Rja13ww33 (talk) 18:23, 6 April 2023 (UTC)[reply]

I recently updated my preferences, and don't recall everything I added. I did an edit and there were no taskbars above or below the edit window. I suspect that I turned on a gadget that is incompatible with the taskbars. I need advice on how to proceed. -- Shmuel (Seymour J.) Metz Username:Chatul (talk) 19:42, 6 April 2023 (UTC)[reply]

Can you report the content of you browser's JavaScript console as described in Wikipedia:Reporting JavaScript errors? Ruslik_Zero 20:27, 6 April 2023 (UTC)[reply]

Wiki markup is very difficult to read when the full text of footnotes (explanatory text and especially dense blocks of citation metadata) is included inline in paragraphs of prose. If citation templates are written compactly without line breaks they create a kind of "wall" of dense syntax which adds visual clutter and is hard to read and makes the surrounding paragraph also hard to read, while if the templates are fully expanded with a line for each parameter they take up a ridiculous amount of space, also making the paragraph very difficult to read. So for long articles I sometimes like to move the footnotes down to the <references>...</references> tag or {{reflist |refs=...}} template at the bottom of the page, to help clean up the source markup.

This has the advantage of making the markup much more legible and also separating all of the footnote contents making them easier to compare or modify systematically. However, it also has some downsides: It splits the footnote content (sometimes very) far from the paragraphs where they are referenced, it makes the footnotes not appear when a single section is being edited/previewed, and sometimes requires making an edit to a whole page instead of a single section or splitting one edit into two pieces, one to the body copy and another to the footnote content. Such separation also doesn’t tend to last, as other editors will (perfectly reasonably) afterward go on adding citations/notes defined inline.

Is there any compromise method, a way to define footnotes outside of a paragraph but still within the same section? That is, some way of defining <ref name=foo> elements which defines but does not directly display a numbered superscript link? (Perhaps the ref tags could be wrapped in some other template?) –jacobolus (t) 21:18, 6 April 2023 (UTC)[reply]

No. Izno (talk) 21:29, 6 April 2023 (UTC)[reply]

Is there any way such a feature could ever be implemented using some kind of template magic? (Or barring that, by adding a feature to Mediawiki?) It seems like it would be very helpful. –jacobolus (t) 21:43, 6 April 2023 (UTC)[reply]

No, template magic can not be used.

Many things can possibly be added to MediaWiki. This is not the thing I'd want a programmer to spend time on, but it is open source, so if someone wants it and can convince the relevant component's maintainer that it is valuable, then it will get merged and deployed. Izno (talk) 21:57, 6 April 2023 (UTC)[reply]

@Jacobolus, I suggest that you try the visual editor (works like Google Docs/Microsoft Office), and if you want to work in wikitext, have you tried the colored syntax highlighting? WhatamIdoing (talk) 22:16, 6 April 2023 (UTC)[reply]

I definitely do not want to use the visual editor. Thanks though. –jacobolus (t) 22:21, 6 April 2023 (UTC)[reply]

In that case, you might find that syntax highlighting (look in the toolbar for something that looks like a highlighter marker) helps, because you can more easily see which things are text and which things are formatting. I understand that it's possible to set custom colors, e.g., if you wanted to make something very light colored. WhatamIdoing (talk) 19:59, 7 April 2023 (UTC)[reply]

So I made this simple template: Template:Registered editors by edit count. The table has since been expanded by others. One of the editorial decisions that we had to make was whether to base the percentages on {{NUMBEROFUSERS}} or on the number of users who have ever successfully saved an edit. I went with the magic word, but now I want to complexify the template by having a sort of magic display/tab/collapse something, so you would normally see these numbers, but if you click on the <magic something>, then it would show you a different table, with the percentages based on the number of successful editors, rather than the number of successful account registers. I'm looking for a magic solution because I don't want the viewer to have to wait for the page to reload.

So you would normally get:

but when you click the magic something, you would then see something like this instead:

Can anyone recommend a good way to do that? WhatamIdoing (talk) 22:25, 6 April 2023 (UTC)[reply]

This can either be done with a second template/page or it can be done in JavaScript, and the latter would take work.

Alternatively, I don't really see why you don't just put the successful editors version in the same table in 3 more columns. Izno (talk) 22:44, 6 April 2023 (UTC)[reply]

The only way I can think of to do this with CSS and without Javascript requires using an HTML input element, which isn't supported within wikitext, so it would require implementation via an extension. Using Javascript would of course require it to be loaded, either by default or through a special link. I agree that the easiest thing to do is to just add more columns or have both tables, one below the other. isaacl (talk) 22:52, 6 April 2023 (UTC)[reply]

I suppose that, in the "one below the other" approach, the tables could be wrapped in collapse templates (one defaultly open and the other defaultly closed). WhatamIdoing (talk) 20:02, 7 April 2023 (UTC)[reply]

PrimeHunter has helpfully pointed out that the requisite Javascript code is already being loaded on English Wikipedia, so the difference is just what type of user interface seems best. isaacl (talk) 04:23, 8 April 2023 (UTC)[reply]

{{Switcher}} is based on User:Jackmcbarn/switcher. It can be used on other things than images. It's tricky to pass a table in a template parameter so I didn't use the template below. PrimeHunter (talk) 23:22, 6 April 2023 (UTC)[reply]

...a minor inconvenience for someone who's experienced that problem on-and-off on Miraheze. (Specifically, User talk:Juustila from just a few minutes ago, posted via WP:Twinkle.) Can the second edit be deleted as a duplicate of the first? (Contributing here with Microsoft Edge through laptop.) --Slgrandson (How's my egg-throwing coleslaw?) 23:44, 6 April 2023 (UTC)[reply]

@Slgrandson, the second edit replaced the first because it was one minute later, so the signature timestamp was slightly different. I don't see the problem with just leaving as it is. — Qwerfjkltalk 10:41, 8 April 2023 (UTC)[reply]

Diff. If it had been registered in the same minute it would have been a null edit and not be logged anywhere. The revision numbers are 39 apart. There were 87 edits ([12] to [13]) in the minute of the first save. That indicates around 27 seconds between the two saves. I guess there were connection issues or other lag and Twinkle retried the edit but the first one actually saved. I don't see reason to delete the edit. PrimeHunter (talk) 11:14, 8 April 2023 (UTC)[reply]

I am experiencing difficulties with the coordinates for Barton Broad. If they are placed at the bottom of the article, the "Infobox park" at the top of the article shows a map with a red area indicating the outline of the Barton Broad nature reserve. If I place the coordinates in the infobox, however, the red area disappears. I have tried playing around with the parameters to coord, but with no success. I am aware that placing the coords in the infobox works for some articles (eg Hainault Depot), although that uses an "Infobox Railway Depot" rather than the park variety. Can anyone explain what is going on, please, and is there a way to fix it? For the moment, I have commented out the coords in the infobox. Bob1960evens (talk) 13:26, 7 April 2023 (UTC)[reply]

Adding |mapframe-wikidata=yes and fixing the coordinates seems to have done the trick. – Jonesey95 (talk) 15:34, 7 April 2023 (UTC)[reply]

Thanks for the assistance. I don't think I would have guessed the solution myself. Bob1960evens (talk) 16:53, 10 April 2023 (UTC)[reply]

Is it feasible to create a table encapsulated in "div style=overflow-x:auto" to have previous and next buttons like in this example? Qwerty284651 (talk) 01:33, 8 April 2023 (UTC)[reply]

No. Izno (talk) 01:41, 8 April 2023 (UTC)[reply]

@Izno, well, that settles that. 😅 Qwerty284651 (talk) 12:56, 8 April 2023 (UTC)[reply]

I know that there are limitations with Visual Editor and templates but I've started to notice it acting weird on a few specifically. If you edit certain templates with Visual Editor, it will most of time, mess up the parameter spacing and hidden comments that may also be in the template. Below are the templates which are effected by this (there may be more but these are the one I've used the most).

Template:Infobox settlement: Removes parameter spacing; messes up hidden comments (Example).

Template:Infobox U.S. county: Same thing as above (likely the same for Template:Infobox U.S. state).

Template:Jct: How the template is viewed in VE mode means the parameter order get reversed (Example).

Template:US Census population: May mess up the parameter spacing (Example).

Other: If imputing bullet points manually, user can create multiple different bullet "charts" which don't merge into a single "chart" (Example).

To my best knowledge, these issues don't hurt the contents of the template if in "Read" mode (expect for the bullet point issue), but it does mess up the template layout which could be a problem for other users. I'm concerned that, due to the nature of the issue and amount of bytes it add/removes, Wikipedia might incorrectly ping newer users edits as vandalism and led to edit reverts or bans (which is unfair since many don't know). I've tried to minimize using VE with templates now but I've seen many others who use VE and unintentionally mess up the template(s). All in all, not an immediate concern, but it might be good to investigate the issue in the future. Thank you for your time; have a good day. DiscoA340 (talk) 23:15, 8 April 2023 (UTC)[reply]

VisualEditor is disabled in template space as mentioned at Wikipedia:VisualEditor#Limitations. All your examples were made in userspace which is more used for other things so VisualEditor shouldn't be disabled there. PrimeHunter (talk) 23:36, 8 April 2023 (UTC)[reply]

@PrimeHunter I recreated said issues there so I wouldn't bother editors but I can give examples on regular articles if that's necessary. DiscoA340 (talk) 23:44, 8 April 2023 (UTC)[reply]

Editing a template means to edit the template page. I thought your post was about that but it's apparently just about editing template calls in other pages. PrimeHunter (talk) 18:12, 9 April 2023 (UTC)[reply]

Infobox settlement is due to this recentish edit, and only changes the whitespace. Similarly for an even earlier edit on US census (harder to see, but it does make clear that it is a block-formatted template, which is what causes the whitespace adjustment).

Infobox US county does not have any TemplateData. Do you have an actual diff?

I do not see what you mean about Jct. Additionally, it also does not have TemplateData, so it will mostly default to whatever parameters you put in. Izno (talk) 23:57, 8 April 2023 (UTC)[reply]

@Izno My apologies, Template:Infobox U.S. county is fine with spacing but doesn't create a new line for each new parameter added (Example). U.S. State seems to be fine on second thought; Jct is also fine (must've been something with my edits, oh well). DiscoA340 (talk) 00:14, 9 April 2023 (UTC)[reply]

Ok, so infobox US county will do that because there is no TemplateData, which means it defaults to inline formatting. Izno (talk) 00:17, 9 April 2023 (UTC)[reply]

I recently wrote a python script that parses Wikipedia:Spoken articles into a podcast RSS feed, currently published at https://wcast.me/sw (paste that into your podcast app and check it out! ) with MIT-licensed source code at https://github.com/xenotropic/spoken-wikipedia-rss (Open an issue if it doesn't work with your app). I created it to use personally, but it also just to fill an apparent hole. Wikipedia has 1600+ recordings of articles in English, and podcast RSS is the main way people look for audio in the world these days, for good reasons (used by apps designed for the purpose, download management, keeping track of what one listened to, etc.).

My question is: does it make sense for that RSS file to be hosted on Wikipedia somewhere? I don't mind hosting the RSS file, but neither do I really want to. There is an apparent logic that Wikipedia would host an index of its own content; there are various other RSS feeds that Wikipedia publishes. It also would be nice if the RSS feed could not be buried in "external links" at the bottom of whatever pages where it is referred to.

If so, how would I go about this? Is this a sensible thing to make a bot out of? So something that runs on my server but writes a file to wikipedia or commons? (Are there examples of bots that write RSS to Wikipedia? Or even of RSS being hosted/updated like that on Wikipedia? Might be MIME-type issues). Or is there some method by which I could propose that Wikipedia itself "adopt" the code and just run it internally? It's a single python file with 200 lines of code, so not a huge thing to review. The main dependency is on the structure of the Spoken Articles page itself, but that seems fairly stable. morrisjm (talk) 01:03, 9 April 2023 (UTC)[reply]

Template:Kotobank is broken.....0mtwb9gd5wx (talk) 03:16, 9 April 2023 (UTC)[reply]

What's wrong with it? * Pppery * _{it has begun...} 03:58, 9 April 2023 (UTC)[reply]

I turned of notifications for topics being archived by accident. How do I turn them back on? I know it's a toggle button in Preferences, but don't know where exactly. Qwerty284651 (talk) 05:38, 9 April 2023 (UTC)[reply]

Note there is a search box on the preferences page. You may be able to find the appropriate setting that way. isaacl (talk) 06:00, 9 April 2023 (UTC)[reply]

It's the option "Talk page archiving" in the Notifications section of Preferences. the wub "?!" 09:20, 9 April 2023 (UTC)[reply]

@The wub, thanks. Qwerty284651 (talk) 18:41, 9 April 2023 (UTC)[reply]

I asked at HelpDesk and was told "You can try the MediaWiki Support Desk or make a bug report at MediaWiki", but before venturing into that alien territory (which presumably would lead me to Phab) I thought I would ask here.

I often edit from my Android Samsung mobile phone, as well as from my PC. I find that on my phone I cannot edit various talk pages other than article talk or user talk. This has been the case for some months; I raised it as a problem, I think in a zoom chat, and was asked for screenshots. Today I have at last discovered how to get a screenshot on this phone, so can read the error messages at leisure. So ...

I want to edit Draft talk:Honest History (magazine). If I use the "reply" link, I get a red box above my input saying "invalid response from server". If I click "read as wiki page" and do an ordinary edit (not VE), I get a red box saying "Error, something unexpected happened upon loading the preview. Please close and try again."

What is happening here? Can I fix it? Or are mobile editors considered to be an underclass who don't need access to backstage areas like Draft Talk?

To be honest I don't really know whether I'm using Chrome or the app: I start off by clicking a Chrome icon saved onto my home screen which gets to my watchlist, but then keep swapping between different configurations, in and out of "read as wiki page" and "View article in browser / on desktop" in an attempt to do whatever I'm trying to do: all a bit of a nightmare. I have another icon which might be the app but gets me to similar pages. In most cases I can find a workround, but contributing to Draft Talk pages, and various other Wikipedia Talk (non-article, non-user) pages, seems to be beyond the possible. PamD 09:54, 9 April 2023 (UTC)[reply]

@PamD assuming you are using a browser, scroll all the way to the bottom of the page and click the "Desktop" link to get a more full set of controls. If you prefer to use mobile web exclusively just uninstall the app from your mobile device. The edit you made to this page right now appears to be NOT in the app, and NOT in the mobile ui. — xaosflux ^Talk 14:43, 9 April 2023 (UTC)[reply]

@Xaosflux I was editing on the desktop by the time I got here, and am now. This earlier edit was from my phone. Going in and out of the desktop version doesn't help on talk pages: clicking "desktop" at the bottom produces the same page, clicking "Read as wiki page" gets the banners displayed but makes no other difference. If I click on the "reply" option I get an input box, when I type and hit the blue "Reply" I get a red error box saying "Invalid response from server". Consistently on the Draft Talk page mentioned above, but I've encountered it elsewhere too. PamD 15:08, 9 April 2023 (UTC)[reply]

This sounds a bit like an ad blocker thatis accidentally triggering on the javascript request made on the talk page. —TheDJ (talk • contribs) 08:02, 10 April 2023 (UTC)[reply]

File:Helen martins.jpg was deleted due to being unused. However, that is only because a bot mistakenly removed the only use of the image in [14] after a page name swap that didn't update the links. Is there a way to restore the image? Aaron Liu (talk) 19:56, 9 April 2023 (UTC)[reply]

You can ask the administrator that deleted the image to undelete it. Ruslik_Zero 20:20, 9 April 2023 (UTC)[reply]

Or any other administrator with half a brain. WP:REFUND for future reference, if you don't feel like gambling. —Cryptic 20:25, 9 April 2023 (UTC)[reply]

Just a small note to let you know that I've made a minor edit to MediaWiki:Userjsdangerous. We've been standardizing interface message boxes across MediaWiki for better accessibility and consistency so this change makes the message box you see when you edit JavaScript/CSS consistent with other message boxes across the site.

This results in a slight color change and padding change but no change to the text. Please let me know if there's any problem relating to this change. Jon (WMF) (talk) 16:52, 10 April 2023 (UTC)[reply]

This change removed the same styling in MediaWiki:Clearyourcache which has a transclusion of the page that is conditional on page load (so it would not have been noticed). Fixed. Izno (talk) 19:30, 10 April 2023 (UTC)[reply]

MediaWiki message delivery 20:03, 10 April 2023 (UTC)[reply]