Page MenuHomePhabricator

Watchlist view has lag after deleting entries are marking entries read
Closed, ResolvedPublic

Description

Author: paul

Description:
My watchlist contained 101 pages. I deleted 35 pages. Then I got a list with the
deleted pages and the message "you are watching 101 pages". I had to click on
"Watchlist" again, then I got the correct number "you are watching 66 pages".


Version: 1.8.x
Severity: normal

Details

Reference
bz4074

Event Timeline

bzimport raised the priority of this task from to Medium.Nov 21 2014, 8:57 PM
bzimport set Reference to bz4074.
bzimport added a subscriber: Unknown Object (MLST).

chris.mckenna wrote:

Changing OS/Hardware to "All" as this happened to me when I massacred my
watchlist on en.wp from 3776 to 836 pages. After the long list of pages that
were removed it still said "you are watching 3776 page". This was using linux.

robchur wrote:

Could this not be browser caching being stupid?

I don't think so. The watchlist doesn't contain the removed items, and there is
also a list of removed articles, so it is not a caching issue (at least, not at
the client side).

jimmy.collins wrote:

On my local testwiki it worked correctly, but on
http://de.wikipedia.org/wiki/Spezial:Watchlist and
http://en.wikipedia.org/wiki/Special:Watchlist I have the same problem.

Maybe depending on the squid servers?

The count and such are read from the slave servers, which will most
likely be reading state from before the DELETE query ran on the master.

Perhaps the sensible thing is to rewrite the interface for editing the
watchlist, which was a quick hack a few years ago. ;)

jimmy.collins wrote:

*** Bug 6949 has been marked as a duplicate of this bug. ***

jimmy.collins wrote:

*** Bug 7542 has been marked as a duplicate of this bug. ***

ezyang wrote:

Since Bug 7542's been marked a duplicate, I'd like to add a little comment. I'm
also going to change the bug summary to be a bit more geeneral

A stop-gap fix would be to emit header('Location: ' . $watchlist_url), which
would simulate the refresh.

Resolving this as fixed, because it works for me, both on a Wikimedia wiki, as well as on a wiki running (near) trunk elsewhere. If any issues would remain, it would be due to a specific MediaWiki setup.