Last modified: 2013-04-22 16:16:31 UTC

Wikimedia Bugzilla is closed!

Wikimedia has migrated from Bugzilla to Phabricator. Bug reports should be created and updated in Wikimedia Phabricator instead. Please create an account in Phabricator and add your Bugzilla email address to it.
Wikimedia Bugzilla is read-only. If you try to edit or create any bug report in Bugzilla you will be shown an intentional error message.
In order to access the Phabricator task corresponding to a Bugzilla report, just remove "static-" from its URL.
You could still run searches in Bugzilla or access your list of votes but bug reports will obviously not be up-to-date in Bugzilla.
Bug 24292 - New Messages count is not updated after marking all threads as read
New Messages count is not updated after marking all threads as read
Status: RESOLVED FIXED
Product: MediaWiki extensions
Classification: Unclassified
LiquidThreads (Other open bugs)
unspecified
All All
: Normal enhancement (vote)
: ---
Assigned To: Alex Monk
:
Depends on:
Blocks:
  Show dependency treegraph
 
Reported: 2010-07-06 20:23 UTC by Huji
Modified: 2013-04-22 16:16 UTC (History)
6 users (show)

See Also:
Web browser: ---
Mobile Platform: ---
Assignee Huggle Beta Tester: ---


Attachments
Chrome screenshot (91.34 KB, image/png)
2012-11-05 18:07 UTC, Steven Walling
Details

Description Huji 2010-07-06 20:23:21 UTC
Simply put, once you click the "Mark all as read" button on your Special:NewMessages, the "New Messages (N)" link at the top of the page is not updated and the "(N)" part is not removed.
Comment 1 Brandon Harris 2010-09-09 20:43:45 UTC
This smells like an Adam issue.
Comment 2 Siebrand Mazeland 2011-04-30 14:10:40 UTC
The unread count is only updated after a page load. Do you mean it's not updated after a page load, or do you expect the count to be updated dynamically/AJAX style?
Comment 3 Huji 2011-04-30 14:45:49 UTC
It means it should be updated by AJAX.
Comment 4 Steven Walling 2011-09-30 19:36:59 UTC
I am getting this error on mediawiki.org currently. (I tried clearing my browser data etc.)
Comment 5 Thehelpfulone 2012-06-22 19:45:07 UTC
Reassign to default per bug 37789
Comment 6 Helder 2012-08-05 21:05:20 UTC
(In reply to comment #4)
> I am getting this error on mediawiki.org currently. (I tried clearing my
> browser data etc.)

I think that would be bug 31251 (which is not about the implementation of an AJAX update), since you reloaded the page and the wrong info was still there.
Comment 7 Steven Walling 2012-11-05 18:07:28 UTC
Created attachment 11306 [details]
Chrome screenshot
Comment 8 Steven Walling 2012-11-05 18:07:55 UTC
As you can see from the attachment I just added, this issue is still coming up, and it's quite annoying. Please fix.
Comment 9 Siebrand Mazeland 2012-11-05 21:16:55 UTC
(In reply to comment #8)
> it's quite annoying. Please fix.

There are no paid resources allocated to LiquidThreads, there are no active volunteer developers on it, the original developers have abandoned the extension and this is absolutely not the most annoying or even visible problem out of the 120+ open bugs and 240+ open issues on LiquidThreads, either. Just doing some expectation management here: Don't expect anything to be done about this issue, unless you feel like scratching your own itch.
Comment 10 Steven Walling 2012-11-05 21:18:31 UTC
(In reply to comment #9)
> (In reply to comment #8)
> > it's quite annoying. Please fix.
> 
> There are no paid resources allocated to LiquidThreads, there are no active
> volunteer developers on it, the original developers have abandoned the
> extension and this is absolutely not the most annoying or even visible problem
> out of the 120+ open bugs and 240+ open issues on LiquidThreads, either. Just
> doing some expectation management here: Don't expect anything to be done about
> this issue, unless you feel like scratching your own itch.

If this is true, then why in god's name are we still using it on mediawiki.org?
Comment 11 Helder 2012-11-06 00:44:35 UTC
(In reply to comment #10)
> If this is true, then why in god's name are we still using it on mediawiki.org?
Because it is still more functional than using wiki pages to discuss/watch discussions.
Comment 12 Huji 2012-11-11 15:51:29 UTC
Check Gerrit change #32914 for a starting point for fixing this bug. I might not have the time to finish myself in near future, but this lays the ground plan for a fix.
Comment 13 Alex Monk 2013-02-17 15:53:05 UTC
I tried to clean that up and make it work, but in the end gave up and redid it myself (this time using no extra API calls, less code). It's ready for review now.
Comment 14 Alex Monk 2013-02-24 14:25:17 UTC
Merged by Siebrand.

Note You need to log in before you can comment on or make changes to this bug.


Navigation
Links