Wikipedia talk:Watchlist notices

Page contents not supported in other languages.
From Wikipedia, the free encyclopedia
WikiProject iconWikipedia Help NA‑class Mid‑importance
WikiProject iconThis page is within the scope of the Wikipedia Help Project, a collaborative effort to improve Wikipedia's help documentation for readers and contributors. If you would like to participate, please visit the project page, where you can join the discussion and see a list of open tasks. To browse help related resources see the Help Menu or Help Directory. Or ask for help on your talk page and a volunteer will visit you there.
NAThis page does not require a rating on the project's quality scale.
MidThis page has been rated as Mid-importance on the project's importance scale.

Restoring dismissed watchlist notices?[edit]

How can dismissed watchlist notices be un-dismissed? The old trick of deleting Wikipedia watchlist cookies doesn't work. --Lexein (talk) 16:21, 20 October 2012 (UTC)[reply]

Short of viewing MediaWiki:Watchlist-details directly (which I've sometimes done to remind myself which messages are presently open), I don't know. Please note that this page isn't watched by very many people; so I've posted a request at WP:VPT#Restoring dismissed watchlist notices?. --Redrose64 (talk) 15:24, 21 October 2012 (UTC)[reply]
If you really want to restore the message on the watchlist: The source of the Watchlist-details page gives a cookie number for each entry. If you inspect your browser's cookies you will find a cookie from en.wikipedia.org for a hidden item, for example hidewatchlistmessage-134 for the current election discussion. Removing that cookie restores the entry. --Mirokado (talk) 17:14, 21 October 2012 (UTC)[reply]
I've just noticed that Lexein has already said this was not working. It did for me just now. --Mirokado (talk) 17:46, 21 October 2012 (UTC)[reply]
  • Thanks all. I see that the notice I was interested in is really gone from Watchlist-details, so the cookie trick probably would have worked. Seeing the notice trumps restoring the dismissed message; in that light, I've boldly added a short note at the bottom. --Lexein (talk) 19:47, 21 October 2012 (UTC)[reply]
  • I never cease to amazed at the obscure things Mirokado knows. He's a veritable coal mine of information. EEng 00:43, 5 January 2017 (UTC)[reply]

Current notice link hard to see - accessibility issue. Plus, can't find it in the four usual places[edit]

Moved to MediaWiki_talk:Geonotice.js#Moved_discussion -- please watchlist that discussion page. --Lexein (talk) 15:39, 5 December 2012 (UTC)[reply]

Signpost issue 7[edit]

The Signpost issue 7 was published about two hours ago. Could we please have the watchlist notice bat-beacon activated? ☆ Bri (talk) 03:18, 30 June 2018 (UTC)[reply]

 Done @Bri: up, but I think of it more as a grail-shaped beacon :D — xaosflux Talk 03:21, 30 June 2018 (UTC)[reply]

Bug in the system?[edit]

Starting yesterday, I have an alert that will not open. My bar shows I have one alert (over the bell icon). Clicking to open it, however, opens my notices (which have all been read). An idea what's going on? - SummerPhDv2.0 18:38, 28 June 2019 (UTC)[reply]

@SummerPhDv2.0: if you use monobook skin, see Wikipedia:Village_pump_(technical)#Stuck_alert/notification. Else, sometimes these things just get stuck mysteriously and you can clear it in Special:Notifications. — xaosflux Talk 18:50, 28 June 2019 (UTC)[reply]
Got it. Thanks, Xaosflux! - SummerPhDv2.0 20:09, 28 June 2019 (UTC)[reply]
The same thing happens to me from time to time (I use Vector), but it seems to fix itself, not sure if it's a cache issue or what. - FlightTime (open channel) 20:14, 28 June 2019 (UTC)[reply]

Are you sure[edit]

@Trackinfo: this is the page for discussing the content of the notice, not the functioning of the watchlist, I'm moving your question to WP:VPT for follow up. — xaosflux Talk 21:05, 8 November 2019 (UTC)[reply]

RFC of interest[edit]

An ongoing discussion of interest to watchers of this page is happening here. –MJLTalk 13:53, 26 February 2020 (UTC)[reply]