I would like to use this script when reviewing pending changes. However, when I see the pending changes, it only shows the diff, not the article with the changes implemented. Can an editor edit the my script so that it shows both the diff and article with the changes implemented? I don't know how to do it myself so I am asking for help. Interstellarity T 🌟 10:08, 21 June 2019 (UTC)(discussiontools-replybutton)

Not me, but DannyS712 can. --qedk (t 桜 c) 19:42, 21 June 2019 (UTC)(discussiontools-replybutton)

QEDK, Can you find someone else that can do it if DannyS712 can't do it? Interstellarity T 🌟 20:09, 24 June 2019 (UTC)(discussiontools-replybutton)

Interstellarity, Hi there i have fixed that issue. ___CAPTAIN MEDUSAtalk 13:14, 30 June 2019 (UTC)(discussiontools-replybutton)

I have just recently been having an issue: When I hit the preview button to check my edits then hit the publish button I get an edit conflict. When this first happened I treated it as such and it posted twice. After that I have reloaded and see it is already posted by only hitting the preview button. I have never had this issue, that was not a legitimate edit conflict, so am at a lose. Otr500 (talk) 16:09, 24 June 2019 (UTC)(discussiontools-replybutton)

Note: This has happened 4 times but when I previewed this edit then hit "publish changes" it worked fine. Otr500 (talk) 16:12, 24 June 2019 (UTC)(discussiontools-replybutton)

Apparently this is an issue only I am having but it is still ongoing. Otr500 (talk) 18:09, 28 June 2019 (UTC)(discussiontools-replybutton)

Wikipedia:Village_pump_(technical)#Incorrect_Edit_Conflicts related? Galobtter (pingó mió) 18:24, 28 June 2019 (UTC)(discussiontools-replybutton)

Very possible. Also whatever the issue is (I will have to look) it might be related to Wikipedia:Village pump (technical)#Block conflict that may just be another area where the edit conflict is occurring. Otr500 (talk) 12:19, 29 June 2019 (UTC)(discussiontools-replybutton)

I'm getting inexplicable edit conflicts today. Doug Weller talk 19:55, 30 June 2019 (UTC)(discussiontools-replybutton)

And again when I tried to post the above. Doug Weller talk 19:56, 30 June 2019 (UTC)(discussiontools-replybutton)

Again! Is it groundhog day? When this happens again I own't bother to mention it here. Doug Weller talk 19:57, 30 June 2019 (UTC)(discussiontools-replybutton)

I'd like to know if there is any bot or tool that can help me finding old vandalizing editions in a WP file history. Thanks. --Jotamar (talk) 23:56, 19 June 2019 (UTC)(discussiontools-replybutton)

When I said WP files, I meant WP pages. Can someone at least tell me, where should I ask my question? --Jotamar (talk) 19:01, 26 June 2019 (UTC)(discussiontools-replybutton)

Yes, Jotamar, probably WP:BOTREQ, how many edits are you looking for? There will be many millions. Fist step might be to look for edits preceding those with an edit summary of "rvv". Another good place to look is the edits prior to User:ClueBot's edits.

All the best: Rich Farmbrough, 10:49, 28 June 2019 (UTC).(discussiontools-replybutton)

If you already know specific vandalized text in an article and want the edit which added it then click "Find addition/removal" at the top of the page history. It used WikiBlame until recently but the tool has problems and another is currently used. It's discussed at MediaWiki talk:Histlegend#Wikiblame replacement. PrimeHunter (talk) 11:09, 28 June 2019 (UTC)(discussiontools-replybutton)

What I have in mind is some sort of heuristic tool, capable of finding a short list of possible vandalazing editions that have not been reverted, in a group of pages, for instance, the pages under one category. In less popular, poorly maintained pages, it's not uncommon that such an edition can be easily reverted even after months or years, but first you have to find them, and that takes up a lot of time. --Jotamar (talk) 13:48, 1 July 2019 (UTC)(discussiontools-replybutton)

I need help getting a reflist to fall at the bottom of the article. It is falling between 2 tables. [[1]]

I would like to understand why this happening so I can fix it myself in the future.

Thank you. Lore E. Mariano (talk) 14:02, 1 July 2019 (UTC)(discussiontools-replybutton)

Fixed by [2]. PrimeHunter (talk) 14:10, 1 July 2019 (UTC)(discussiontools-replybutton)

Thank you so much! Lore E. Mariano (talk) 14:40, 1 July 2019 (UTC)(discussiontools-replybutton)

Apparently there is a new bot creating cite errors. Article: WZ-551 Tag: Rescuing 14 sources and tagging 0 as dead. #IABot (v2.0beta15)

Is there a review process for new bots/tools? I have encountered many repeated errors that I assume are created by them. e.g. "coauthors=", "DUPLICATE_date". User-duck (talk) 17:39, 1 July 2019 (UTC)(discussiontools-replybutton)

Communication failure between the bot owner and the community at WT:CS1. I fixed the WZ-551 page that Gog the Mild edited and will leave it to that editor to similarly repair any other error caused by the tool.

—Trappist the monk (talk) 17:56, 1 July 2019 (UTC)(discussiontools-replybutton)

This is IABot via Oauth request by Gog the Mild. It was due to some miscommunications, my fault, iabot has been patched/rebooted and will look into fixing the errors added onwiki. -- GreenC 19:36, 1 July 2019 (UTC)(discussiontools-replybutton)

Edit conflict. I had just written:

Thank you Trappist the monk. That would have been from me clicking "Fix dead links" on the "Revision history" page and not checking the result thoroughly enough. I shall recheck my other recent clicks of that button.

GreenC, do I need to do anything, other than recheck previous uses of "Fix dead links", and/or cease using it? Thanks Gog the Mild (talk) 19:44, 1 July 2019 (UTC)(discussiontools-replybutton)

You are good, it's ok now. Looks like the bug lasted 3hrs and somewhere between 100-200 articles. I might script a quick fix or request something at AWB request wouldn't worry about manually repairing. -- GreenC 19:48, 1 July 2019 (UTC)(discussiontools-replybutton)

21:22, 1 July 2019 (UTC)

Progression of events was:

1. Editor created a link to de:Otto Kirn (in article Pandeism, correcting from wrong link to Otto Kern).
2. Translated Otto Kirn added here.
3. Wikidata updated for articles now in two languages.
4. Tagged as an orphan here.

Question: Why doesn’t English addition to Wikidata automatically prompt changing of links previously made to point other languages? Hyperbolick (talk) 19:49, 1 July 2019 (UTC)(discussiontools-replybutton)

The edit said [[:de:Otto Kirn]]. This explicitly tells to link the German Wikipedia. {{Interlanguage link|Otto Kirn|de}}} could have been used instead to test for an English article called Otto Kirn. It would only have examined whether the page name exists and not whether it's in a Wikidata item. As far as I know we have no template for the latter. It is possible to pull information from Wikidata so maybe it could be added as a feature in {{Interlanguage link}}. I don't think it's possible for an English template to look up the Wikidata item for a German article so Q24529752 would probably have to be a parameter. A bot could be coded to automaticlly add the parameter when it's not supplied. PrimeHunter (talk) 21:12, 1 July 2019 (UTC)(discussiontools-replybutton)

Could a bot check whenever a Wikidata item is connected from here? Got a notification here when it was, so somebody’s telling this Wiki. Hyperbolick (talk) 21:41, 1 July 2019 (UTC)(discussiontools-replybutton)

Could someone knowledgable comment here, centrally, on whether there are database issues beyond the apparently temporary ones outlined in the above Tech News, and if so, what are their extent and when do we think they will be resolved? It appears multiple bots have for some time not been running DB intensive tasks (such as certain Wikipedia:Database reports), and it is very difficult to parse through all the bot/report talkpage chatter to get a true picture of what is actually going on. Thanks in advance! UnitedStatesian (talk) 02:46, 2 July 2019 (UTC)(discussiontools-replybutton)

The database replicas are undergoing maintenance (see T222978). This involves taking one replica host out of service at a time. The other two hosts then have increased load, which leads to replication lag and increased query time (previously long queries could fail to complete). Maintenance is usually ongoing during the week and paused over the weekends. I would expect this to be an ongoing issue for a while. I don't know how long the maintenance will take, but the DBAs are reaching the end of the maintenance one the first replica. The database items in the Tech News are unrelated. — JJMC89 (T·C) 05:29, 2 July 2019 (UTC)(discussiontools-replybutton)

Dear All,

initially I turned to administrator regarding the issue, but unfortunetly he could not give an idea for solution. The details may be read there...Shortly, if I set it to list the changes back to 7 or 30 days, it is not working, just listing the last 250 changes, not more and I have as well no (previous/next) buttons...I need a solution, Thank You(KIENGIR (talk) 20:21, 1 July 2019 (UTC))(discussiontools-replybutton)

@KIENGIR: This is Wikipedia:Village pump (technical)/Archive 174#did something break watchlist and make it too short again?. --Redrose64 🌹 (talk) 20:36, 1 July 2019 (UTC)(discussiontools-replybutton)

@Redrose64:,

Thank you it helped, I applied similar tweaks descibred there (in the detailed settings changing to 30 days and enabling 1000 entries as maximum). though, still I don't have 30 days, I assume mainly because of the 1000 entry limitation (I don't know where would be the url to tweak it higher). Thus practically I could go back two weeks, so my initial problem has been solved (going back between 4-7 days)...maybe as an important note for the others or the developers, even this worked only by unchecking the "Expand watchlist to show all changes, not just the most recent" in the Advanced Options...(initially at the first tweak attempt, I automatically checked this box assuming it is essential, but anything written above did not work until it was unchecked, ironically it had a contraproductive effect despite it's name...(KIENGIR (talk) 10:39, 2 July 2019 (UTC))(discussiontools-replybutton)

Missing notification icons in MonoBook

I just spent ten minutes trying to figure out what was wrong on my end. If you're doing the same, it's not just you. See phab:T226503. Suffusion of Yellow (talk) 19:52, 25 June 2019 (UTC)(discussiontools-replybutton)

I'm getting it in MonoBook too. The appropriate CSS rules are present in the stylesheets:

.oo-ui-icon-bell, .mw-ui-icon-bell:before {
    background-image: url(/w/load.php?modules=oojs-ui.styles.icons-alerts&image=bell&format=rasterized&lang=en&skin=monobook);
    background-image: linear-gradient(transparent,transparent),url("data:image/svg+xml,%3Csvg xmlns=%22http://www.w3.org/2000/svg%22 width=%2220%22 height=%2220%22 viewBox=%220 0 20 20%22%3E%3Ctitle%3Ebell%3C/title%3E%3Cpath d=%22M16 7a5.38 5.38 0 0 0-4.46-4.85C11.6 1.46 11.53 0 10 0S8.4 1.46 8.46 2.15A5.38 5.38 0 0 0 4 7v6l-2 2v1h16v-1l-2-2zm-6 13a3 3 0 0 0 3-3H7a3 3 0 0 0 3 3z%22/%3E%3C/svg%3E");
}
.oo-ui-icon-tray, .mw-ui-icon-tray:before {
    background-image: url(/w/load.php?modules=oojs-ui.styles.icons-alerts&image=tray&format=rasterized&lang=en&skin=monobook);
    background-image: linear-gradient(transparent,transparent),url("data:image/svg+xml,%3Csvg xmlns=%22http://www.w3.org/2000/svg%22 width=%2220%22 height=%2220%22 viewBox=%220 0 20 20%22%3E%3Ctitle%3Etray%3C/title%3E%3Cpath d=%22M3 1a2 2 0 0 0-2 2v14a2 2 0 0 0 2 2h14a2 2 0 0 0 2-2V3a2 2 0 0 0-2-2zm14 12h-4l-1 2H8l-1-2H3V3h14z%22/%3E%3C/svg%3E");
}

Switching to Vector displays them properly, even though the CSS rules are virtually identical - the only differences are that the word "monobook" becomes "vector" in the first and third url(...) value. --Redrose64 🌹 (talk) 20:21, 25 June 2019 (UTC)(discussiontools-replybutton)

Um, did the fix also give a ton of scroll-space to the right of anyone else's window? I can now scroll for a very long time to the right, despite there being no content. Killiondude (talk) 23:42, 25 June 2019 (UTC)(discussiontools-replybutton)

@Killiondude: Yes, I see the same thing. (Firefox 67, Linux) Suffusion of Yellow (talk) 23:45, 25 June 2019 (UTC)(discussiontools-replybutton)

Ditto here, IE 11 in Windows. They were missing for a while, but now they've reappeared. I think they're blurrier than before, however. Could someone ping me and thank me for this edit, so I can see whether the number notifications look any different. Nyttend (talk) 23:53, 25 June 2019 (UTC)(discussiontools-replybutton)

@Nyttend: (ping) Suffusion of Yellow (talk) 00:06, 26 June 2019 (UTC)(discussiontools-replybutton)

Thank you. Things are somewhat different; the numbers looked normal, but when I clicked each one, it was momentarily surrounded by a little dark box. The same is true if I want to review past notifications and click either of the icons when I have nothing new. Nyttend (talk) 10:51, 26 June 2019 (UTC)(discussiontools-replybutton)

@Nyttend: You might be right about the extra blurriness, I'm not sure (I took some screenshots a few years ago: c:File:Vpt redrose64 alerts.PNG, c:File:Vpt redrose64 alerts2.PNG, c:File:Vpt redrose64 alerts3.PNG back when the car door was still in place, now replaced by the TV set icon). You're certainly right about the little dark box, it's blue and there are two for each icon, one enclosing the number and the other enclosing the icon.

@Killiondude: The super-wide scroll space was present for me on all pages until about an hour ago, it's now stopped appearing. --Redrose64 🌹 (talk) 13:06, 26 June 2019 (UTC)(discussiontools-replybutton)

You guys aren't getting the icons? I'm getting only the icons — not the actual pings. On the upside, I get all thanks twice. See below. (Using Monobook.) Bishonen | talk 21:38, 27 June 2019 (UTC).(discussiontools-replybutton)

@Bishonen: That's because this problem was fixed and the "fix" caused another problem. Try putting my "fix"-to-the-fix from the other thread in your monobook.css, and see if the links work as expected. Suffusion of Yellow (talk) 21:48, 27 June 2019 (UTC)(discussiontools-replybutton)

I'm sorry, Suffusion of Yellow, I don't see a fix-to-the fix in the other thread (you mean "Someone has broken Thanks", right?), and altogether, you're speaking a foreign language. Could you tell me what to do as if explaining to your mother? Bishonen | talk 21:59, 27 June 2019 (UTC).(discussiontools-replybutton)

@Bishonen: Sorry, there are too many threads about this right now. Try adding:

#pt-notifications-notice .mw-echo-notifications-badge, #pt-notifications-alert .mw-echo-notifications-badge {
	text-align: left;
}

to your monobook.css. Works for me, at least. Suffusion of Yellow (talk) 22:07, 27 June 2019 (UTC)(discussiontools-replybutton)

And it worked for me. Thank you very much, Suffusion of Yellow.

Re-pinging Suffusion of Yellow. Bishonen | talk 08:10, 28 June 2019 (UTC).(discussiontools-replybutton)

Suffusion of Yellow, I've just realized that my problem persists on Meta. Somebody pinged me, to test, and all I got was a three-year-old thanks. Can I put your magic code somewhere to fix that? (And hopefully Commons, Swedish Wikipedia, etc etc — I assume it's everywhere.) Bishonen | talk 19:30, 29 June 2019 (UTC).(discussiontools-replybutton)

@Bishonen: the problem on meta-wiki, (and most all other projects) should get cleaned up with the next release train. If it doesn't I'll put the hack on meta-wiki. If you need it urgently, you can hack your own monobook.css there (or just click a bit further to the left). — xaosflux ^Talk 19:38, 29 June 2019 (UTC)(discussiontools-replybutton)

@Bishonen: You can also put the same code in your meta:Special:MyPage/global.css. In theory this could cause display problems if you view some wikis in non-monobook skins, but I just tried in Vector and Timeless and I didn't see any problems. Suffusion of Yellow (talk) 19:42, 29 June 2019 (UTC)(discussiontools-replybutton)

@Bishonen: Wait, just realized that it's possible to have the fix only apply to monobook. Give me a few minutes to work it out. Suffusion of Yellow (talk) 19:45, 29 June 2019 (UTC)(discussiontools-replybutton)

┌──────────────────────────────────────┘@Bishonen: Ok, try putting:

.skin-monobook #pt-notifications-notice .mw-echo-notifications-badge, .skin-monobook #pt-notifications-alert .mw-echo-notifications-badge {
	text-align: left;
}

in your meta:Special:MyPage/global.css. Suffusion of Yellow (talk) 19:54, 29 June 2019 (UTC)(discussiontools-replybutton)

Suffusion of Yellow, now you're talking my language. It seems to work. Thank you. Bishonen | talk 20:20, 29 June 2019 (UTC).(discussiontools-replybutton)

Excessive width on monobook

So if you are using monobook, you may now constantly think there is something off the page to the right. See phab:T226597 for the report. Apparently this is a hack that the dev's put in to work around the notifications mess above. — xaosflux ^Talk 03:14, 26 June 2019 (UTC)(discussiontools-replybutton)

Merged to phab:T226594. — xaosflux ^Talk 03:41, 26 June 2019 (UTC)(discussiontools-replybutton)

Thank you. Just noticed this, and thought it was a broken ref spilling across the page I was on! Lugnuts ^{Fire Walk with Me} 06:54, 26 June 2019 (UTC)(discussiontools-replybutton)

Jeez. Hadn't noticed. Can't unsee now. Here's a temporary fix. —RainFall 07:13, 26 June 2019 (UTC)(discussiontools-replybutton)

#pt-notifications-notice .mw-echo-notifications-badge, #pt-notifications-alert .mw-echo-notifications-badge {
	text-indent: 0px !important;
}

Yesterday, when I responded to the thread above ("please ping and thank me"), I looked for this and it wasn't the case, but now it is. Nyttend (talk) 10:53, 26 June 2019 (UTC)(discussiontools-replybutton)

• I've added RainFall's fix temporarily to MediaWiki:Monobook.css after testing locally, revert if any new issues are caused (I tested with both notification types as well). — xaosflux ^Talk 11:58, 26 June 2019 (UTC)(discussiontools-replybutton)

Does the temporary fix actually work? I've still got the excessive width. DuncanHill (talk) 12:00, 26 June 2019 (UTC)(discussiontools-replybutton)

@DuncanHill: it took a min to update the central css, try force refreshing a page. — xaosflux ^Talk 12:01, 26 June 2019 (UTC)(discussiontools-replybutton)

@Xaosflux: Now working, thank you. DuncanHill (talk) 12:05, 26 June 2019 (UTC)(discussiontools-replybutton)

@Xaosflux: Now, when I click on the "talk" link to the right of the notifications, I get the Special:Notifications popup instead. It looks like the screen-reader text, hidden by color:transparent, is overlapping with the talk link. Suffusion of Yellow (talk) 21:24, 26 June 2019 (UTC)(discussiontools-replybutton)

@Suffusion of Yellow, DuncanHill, Nyttend, Lugnuts, and RainFall: OK, I reverted the .css in monobook.css, give it a few and see if it fixes that problem (resulting in the original problem) - seems like I'm having to argue with the dev team to get them to understand that the change they made is making the final page worse than before :( — xaosflux ^Talk 21:37, 26 June 2019 (UTC)(discussiontools-replybutton)

OK Talk is back, but so is super-wide-mode :( — xaosflux ^Talk 21:38, 26 June 2019 (UTC)(discussiontools-replybutton)

@Xaosflux: Argue with the The Knights Who Say "OOUI!"? Good luck! Suffusion of Yellow (talk) 21:52, 26 June 2019 (UTC) (discussiontools-replybutton)

I'd like to laugh, but it's so annoying that breaking changes are just rolled out. If WMF want's to deprecate monobook they need to just say it - else stop breaking it.... — xaosflux ^Talk 22:31, 26 June 2019 (UTC)(discussiontools-replybutton)

"Quick - we need a distraction from Framgate, BREAK THINGS!" DuncanHill (talk) 22:32, 26 June 2019 (UTC)(discussiontools-replybutton)

please please please, don't feed to conspiracy theorists ... — xaosflux ^Talk 22:41, 26 June 2019 (UTC)(discussiontools-replybutton)

deprecate monobook: WP:BEANS! Suffusion of Yellow (talk) 22:33, 26 June 2019 (UTC) (discussiontools-replybutton)

"Deprecate" would be too strong a word, but the end of official support for MonoBook was announced about half a dozen years ago.[7] Whatamidoing (WMF) (talk) 06:31, 27 June 2019 (UTC)(discussiontools-replybutton)

I suppose I can put that code in my own css file, but I'd prefer that talk page link not to work over the wide screen space. I use trackpad shortcuts to move backward and forward through browser tab history a lot on Wikipedia. Having all the space to the right pretty much disallows moving forward in the history via that shortcut. Killiondude (talk) 22:35, 26 June 2019 (UTC)(discussiontools-replybutton)

If someone can come up with another hack for it that doesn't break things I'll happily force it back out there. — xaosflux ^Talk 22:42, 26 June 2019 (UTC)(discussiontools-replybutton)

If somehow this breaks the fundraising banner Seddon (WMF) is working on I bet it will get immediate attention...ijs... — xaosflux ^Talk 22:43, 26 June 2019 (UTC)(discussiontools-replybutton)

For any of my over-the-top complaining on this, some of it is frustration - but I really would like to thank Catrope for their continuing efforts to resolve this. Last update, the width problem is fixed, but now there is an alignment issue with the areas to click (you have to click a little further to the left then you used to right now) - this is already reported to phab. — xaosflux ^Talk 03:46, 27 June 2019 (UTC)(discussiontools-replybutton)

Ah, I was wondering about that. I was trying to get to my userpage from the link at the top, and kept getting info about notifications... Risker (talk) 04:16, 27 June 2019 (UTC)(discussiontools-replybutton)

Related xkcd. The initial "fix" that caused this seems to be very problematic. Can we not revert back and make a proper, tested patch instead of applying these small hacks repeatedly? —RainFall 05:15, 27 June 2019 (UTC)(discussiontools-replybutton)

Hi all. I don't know if this is related, but I can't click on the link to my talkpage from the very top bar, it always goes to my notifications. This is in Firefox. Lugnuts ^{Fire Walk with Me} 06:29, 27 June 2019 (UTC)(discussiontools-replybutton)

@Lugnuts: the 'talk link' problem should be fixed now (at least in monobook). If you are still seeing it in monobook can you gather some more details: hover over "log out" and look at what the link would be, then slowly move your mouse to the left (over contribus/wl/pref/ etc..) and see if you get sandbox, then your talk link. If it is out of alignment let us know? The link to the "user page" is somewhat overlapping with notifications (See above) but should work if you approach it from its left edge. — xaosflux ^Talk 14:27, 27 June 2019 (UTC)(discussiontools-replybutton)

Thanks Xaosflux, that seems to be OK now. Lugnuts ^{Fire Walk with Me} 14:29, 27 June 2019 (UTC)(discussiontools-replybutton)

I've just noticed that "Notices" now fills up most of the space between "DuncanHill" and "Talk", and "Alerts" partially overlaps "DuncanHill". I don't generally notice them unless I actually have an alert or a notice, as I use the blackscreen gadget and the words "Notices" and "Alerts" helpfully display in black text on a black background. Since these recent changes they have started shewing up in orange (like the other links at the top) but only when I point my mouse at them. DuncanHill (talk) 15:08, 27 June 2019 (UTC)(discussiontools-replybutton)

@Xaosflux: This fixes all the overlap issues for me, in FF67/Linux:

#pt-notifications-notice .mw-echo-notifications-badge, #pt-notifications-alert .mw-echo-notifications-badge {
	text-align: left;
}

I don't know why; I was just trying things at random. Might be worth trying in some other browsers. Suffusion of Yellow (talk) 21:33, 27 June 2019 (UTC)(discussiontools-replybutton)

This code fixes all the things for me. :) Before inserting this, I couldn't access "alerts" (the bell) only "notifications" (the inbox icon). Killiondude (talk) 22:00, 27 June 2019 (UTC)(discussiontools-replybutton)

I noted it at phab:T226594 to see if there will be an upstream fix before we start band-aiding again. — xaosflux ^Talk 22:18, 27 June 2019 (UTC)(discussiontools-replybutton)

@Suffusion of Yellow: That stops the overlap, but the text stays black when I point at it. Could someone thank and/or/ping me so I can see what it looks like then? Thanks, DuncanHill (talk) 22:24, 27 June 2019 (UTC)(discussiontools-replybutton)

User:DuncanHill, you annoy.---Sluzzelin talk 22:26, 27 June 2019 (UTC)(discussiontools-replybutton)

Thanks both, thanks and pings seem to shew up well and be clickable. Someday I'll get around to mentioning the incompatibility with the blackscreen gadget. I have to highlight the notification to read who it's from. But that's been like that for ever. DuncanHill (talk) 22:28, 27 June 2019 (UTC)(discussiontools-replybutton)

@DuncanHill: Ideally, that should go in Special:MyPage/monobook.css instead of Special:MyPage/common.css, not I think it will make a big difference. Suffusion of Yellow (talk) 22:34, 27 June 2019 (UTC)(discussiontools-replybutton)

Thanks again, have moved it over. Seems to be much the same effect. DuncanHill (talk) 22:40, 27 June 2019 (UTC)(discussiontools-replybutton)

Message & notification icons in Modern skin

The message & notification icons in the modern skin seem to have been changed to something less than ideal. Any recent changes to the stylesheet that would have made this happen? FWIW browser is latest version of Firefox (67.0.4). Nthep (talk) 14:52, 27 June 2019 (UTC)(discussiontools-replybutton)

@Nthep: - so in summary - there is a bunch going on and this is coming from upstream not local styles. See phab:T226684 (and some of the discussion at phab:T226594) to catch up on the goings-on. — xaosflux ^Talk 14:57, 27 June 2019 (UTC)(discussiontools-replybutton)

Thanks. Nthep (talk) 15:10, 27 June 2019 (UTC)(discussiontools-replybutton)

@Nthep: Same as the monobook issues, should be fully fixed at the end of the week/next week depending on how they're doing deployments. Unless you don't like how we fixed it once it does change, in which case do please tell me. -— Isarra ༆ 15:55, 1 July 2019 (UTC)(discussiontools-replybutton)

Someone has broken Thanks

Now when I thank someone, instead of it happening all in the history page, it takes me to another page to ask me if I want to thank them, then to yet another page saying I have thanked them, and leaves me there and not where I was to start with and with no apparent way back. I expect it's an "improvement", but it makes life harder. DuncanHill (talk) 20:53, 27 June 2019 (UTC)(discussiontools-replybutton)

@DuncanHill: Works normally for me. What you are describing is the expected behavior if you have JavaScript disabled. It is possible that the JS for the "thanks" feature didn't load properly. Try WP:BYPASS, and see if it works again. Suffusion of Yellow (talk) 20:58, 27 June 2019 (UTC)(discussiontools-replybutton)

 Works for me - but the servers were just also having some hiccups, can you try again? — xaosflux ^Talk 20:59, 27 June 2019 (UTC)(discussiontools-replybutton)

I've been having intermittent weirdness of another type. On "Show preview", I've been getting a message that the servers are busy. If I refresh, it works fine. But the error has repeated numerous times today. I've been wondering if it's the new version of MediaWiki that Tech News mentioned would be on all wikis as of today. — Maile (talk) 21:00, 27 June 2019 (UTC)(discussiontools-replybutton)

(ec)I went back and in the page history it did not shew me as having thanked the person I had thanked. I tried again, nothing happened, then tried again and it behaved normally. I think there's a log somewhere where I can see if it went through, but can't remember where. DuncanHill (talk) 21:03, 27 June 2019 (UTC)(discussiontools-replybutton)

Hah! I found the thanks log, it's shewing me as having made the first thanks before I posted here, but not the second when I tried again. DuncanHill (talk) 21:06, 27 June 2019 (UTC)(discussiontools-replybutton)

This is not about thanks (I think), but I got first one, then two notifications today for apparently nothing. I mean, there's a little red "2" in the usual place, but when I look there's nothing new there. I think the second one may have been for AGK's mention of me here, since it turned up right as I was reading his motion, but I've no idea what the first one is. Anybody know what's going on? If an arb offers a motion to examine my conduct, and has as far as he knows pinged me about it, it would be nice to get that ping. Can I go somewhere to find it? Bishonen | talk 21:20, 27 June 2019 (UTC).(discussiontools-replybutton)

There's a Thanks log at this link. I don't think there's a ping log. People shouldn't rely on pings as 1) they don't always work at the best of times, 2) it's very rarely the best of times, and 3) I think you can turn notifications off. DuncanHill (talk) 21:26, 27 June 2019 (UTC)(discussiontools-replybutton)

There was a recent problem with notification (at least in Monobook) see here (look above), but I don't know whether there's a connection. I will henceforth thank and revert and ping users profusely and see how they react. ---Sluzzelin talk 21:27, 27 June 2019 (UTC)(discussiontools-replybutton)

Duncan, you better stop thanking me, or I will report you to ... ---Sluzzelin talk 21:31, 27 June 2019 (UTC)(discussiontools-replybutton)

(edit conflict) (edit conflict) (edit conflict) I use Monobook, Sluzzelin, I'm old school. You know what? I just realized that the little notifications digit — the red one — shows the thanks I've got, just like the blue digit does. So, I get thanks twice, and notifications never. Bishonen | talk 21:32, 27 June 2019 (UTC).(discussiontools-replybutton)

You can get a complete list of current and past notifications at Special:Notifications (which, frustratingly, works much better with javascript disabled). Doesn't help you realize there's new ones there if the main notice is broken, though. —Cryptic 21:57, 27 June 2019 (UTC)(discussiontools-replybutton)

@Sluzzelin: Wilco! DuncanHill (talk) 21:34, 27 June 2019 (UTC)(discussiontools-replybutton)

Bishonen, this happened to me (also a Monobook user) when someone replied to me in a topic which was archived in the time between their reply and when I saw the notification. Ever since then, whenever I go to a wiki project for the first time, there's a red number for notifications, even when there are none (because the default preference is to show cross-wiki notifications). On the bright side, I can always tell if it's my first visit to a project. BlackcurrantTea (talk) 07:48, 28 June 2019 (UTC)(discussiontools-replybutton)

@BlackcurrantTea:, my problem was solved by a kindly techy type in a thread above. I don't know if the same magic would help you, but it's probably worth trying. Bishonen | talk 08:06, 28 June 2019 (UTC)(discussiontools-replybutton)

Bishonen, thanks for the tip. That doesn't make a difference in my case, but it's not really a problem. BlackcurrantTea (talk) 08:36, 28 June 2019 (UTC)(discussiontools-replybutton)

Stuck alert/notification

At the top of every Wikipedia page I open are my control tabs: Username, Alerts, Notifications, Talk, Sandbox, Preferences, Beta, Watchlist, Contributions, Log out.

There is a red number over my Alerts tab, and the tab isn't working. When I click on it, it shows all the Notifications, as does the Notifications tab.

I can't get rid of that red number. It has worked fine until today. Help! -- BullRangifer (talk) 03:19, 28 June 2019 (UTC)(discussiontools-replybutton)

@BullRangifer: do you use Monobook for your skin? If so, see #Excessive width on monobook and specifically the last bit of code given that you can put into your css file to fix what the devs broke in the skin. Killiondude (talk) 03:23, 28 June 2019 (UTC)(discussiontools-replybutton)

Still a problem. -- BullRangifer (talk) 06:53, 28 June 2019 (UTC)(discussiontools-replybutton)

@BullRangifer: The problem is that although the bell and TV set icons are still links, their hotspots have shifted to the left by about their own width plus a bit more. So the TV set's hotspot is now where the bell is displayed. Therefore, to activate the bell, you click a little to its left - just over the letters "fer" should do it. --Redrose64 🌹 (talk) 11:05, 28 June 2019 (UTC)(discussiontools-replybutton)

Several patches for this were worked on and hopefully it will be fixed very soon! — xaosflux ^Talk 11:07, 28 June 2019 (UTC)(discussiontools-replybutton)

@Redrose64:, you're right! That's exactly what's happened. When will this be fixed? -- BullRangifer (talk) 14:18, 28 June 2019 (UTC)(discussiontools-replybutton)

@BullRangifer: My "fix" (developed using the tried-and-true XKCD method) should work, but you need to put it in your monobook.css, not your monobook.js. Isarra has submitted a patch which should fix this on all wikis, but it hasn't been reviewed yet and I don't know how long it will take to be merged. Suffusion of Yellow (talk) 17:45, 28 June 2019 (UTC)(discussiontools-replybutton)

I don't have that subpage, but I'll create it and give it a try there. Thanks. -- BullRangifer (talk) 20:11, 28 June 2019 (UTC)(discussiontools-replybutton)

That worked instantly! -- BullRangifer (talk) 20:14, 28 June 2019 (UTC)(discussiontools-replybutton)

I've worked out why the hotspots are overwide and overlapping. Whilst looking at DuncanHill's (unrelated) Blackskin problem with that gadget enabled, I happened to hover over the alerts icons - and behold! the text links "Alerts (1)" or "Notices (1)" become visible. It is those textual items that are invisibly appearing in front of the desired links. So to get the bell's link, you need to be to the left of the "N" of "Notices (1)". --Redrose64 🌹 (talk) 19:12, 28 June 2019 (UTC)(discussiontools-replybutton)

It'll be actually fixed here by the end of the week, or next week. Probably. Patch is merged; this is just the last place to get fixes when people aren't wildly swatting everything like lemurs. Mmm, lemurs. -— Isarra ༆ 15:50, 1 July 2019 (UTC)(discussiontools-replybutton)

• @Suffusion of Yellow: I'm trying your css hack at testwiki:MainPage, it should be live in a few mins - just as another stopgap until the phab ticket is resolved - feel free to go look for bugs there before it gets promoted locally here. — xaosflux ^Talk 20:19, 28 June 2019 (UTC)(discussiontools-replybutton)

I'm being over-notified.

Somebody rid me of those dang notifications, which won't go away. GoodDay (talk) 20:49, 28 June 2019 (UTC)(discussiontools-replybutton)

@GoodDay: Are you using the MonoBook skin? If so, please visit the test wiki, WP:BYPASS your cache, and see if everything works as expected over there. Suffusion of Yellow (talk) 21:08, 28 June 2019 (UTC)(discussiontools-replybutton)

I went to my All notifications & 'unread' them. It seems to have worked. GoodDay (talk) 22:05, 28 June 2019 (UTC)(discussiontools-replybutton)

Hack added to monobook.css

I'm adding Suffusion of Yellow's hack to MediaWiki:monobook.css for now - revert if it causes trouble. — xaosflux ^Talk 22:33, 28 June 2019 (UTC)(discussiontools-replybutton)

Working for me, at least. Suffusion of Yellow (talk) 22:46, 28 June 2019 (UTC)(discussiontools-replybutton)

Deployment update

Thanks to User:Isarra's efforts on Friday, we now have full fixes for the notification badge issues in the Monobook and Modern skins. About 15 minutes ago (at 23:36 UTC) I deployed the fixes for Monobook, these are now live on all wikis. I didn't deploy the fixes for Modern because those are a little more complicated and that skin isn't used as much as Monobook is. If I get a chance, I may be able to deploy those 24 hours from now, and otherwise they'll come with next week's regular weekly deployment train on Thursday July 11 (there is no train this week due to the July 4th holiday). Thanks to User:Isarra for writing proper fixes for these bugs, and to User:Xaosflux for putting interim fixes in MediaWiki:Monobook.css in the meantime. And, again, my apologies for this disruption; I was the reviewer on the change that broke this, and I should have caught the fact that it changed the badge structure and the main badge CSS but did not update the Monobook CSS to match. --Roan Kattouw (WMF) (talk) 00:02, 3 July 2019 (UTC)(discussiontools-replybutton)

Or there needs to be a setting in preferences to allow this. Scrolling is a pain. Half the page has to be scrolled to click the "show preview" button.

Weird thing is that the edit window here does not have the "Edit summary (Briefly describe your changes)" toolbar. It only has the "common edit summaries" toolbar.

So look at an article edit window, or an article talk page edit window. -- Timeshifter (talk) 08:34, 1 July 2019 (UTC)(discussiontools-replybutton)

If you begin editing by using the "new section" tab, then no, you don't get an edit summary window. Instead, a standard edit summary is constructed for you, consisting of the name of the new section wrapped in /* ... */ markers plus the words "new section". The edit summary window only appears when editing an existing section, or the whole page. --Redrose64 🌹 (talk) 16:25, 1 July 2019 (UTC)(discussiontools-replybutton)

Thanks, Redrose64. I see now. -- Timeshifter (talk) 08:42, 2 July 2019 (UTC)(discussiontools-replybutton)

Edit window length is not remembered

A related problem is that the wikitext edit window length is not remembered. I can drag it up or down in length. But when I open another article or talk page, and then open an edit window, it is back to being a very lengthy edit window.

This exacerbates the previous problem of the "Publish changes" toolbar being separated by almost half a page of edit summary and terms of use stuff.

Lots of scrolling to do multiple previews. I am using Firefox on a 21-inch LCD monitor. --Timeshifter (talk) 08:24, 1 July 2019 (UTC)(discussiontools-replybutton)

This in your CSS sets the edit box height:

textarea {height:15em}

User:Js/ajaxPreview#Installation adds a small preview button above the edit box. It makes other changes. PrimeHunter (talk) 09:59, 1 July 2019 (UTC)(discussiontools-replybutton)

Or you can use alt+shift+p to preview. Galobtter (pingó mió) 10:14, 1 July 2019 (UTC)(discussiontools-replybutton)

Thanks, PrimeHunter. I installed both, and they both work great. They both should be preferences. -- Timeshifter (talk) 08:38, 2 July 2019 (UTC)(discussiontools-replybutton)

@Timeshifter: It has previously been suggested (see e.g. this thread)) that a setting such as the above rule textarea {height:15em} should be made a user pref. Unfortunately, this is not feasible since a value of 15em is not suitable for every user - we do not know how high anybody else's screen is. --Redrose64 🌹 (talk) 18:30, 2 July 2019 (UTC)