Last modified: 2009-08-14 14:53:33 UTC

Wikimedia Bugzilla is closed!

Wikimedia migrated from Bugzilla to Phabricator. Bug reports are handled in Wikimedia Phabricator.
This static website is read-only and for historical purposes. It is not possible to log in and except for displaying bug reports and their history, links might be broken. See T21388, the corresponding Phabricator task for complete and up-to-date bug report information.
Bug 19388 - Alert the user if he receive a reply anywhere in the discussion pages
Alert the user if he receive a reply anywhere in the discussion pages
Status: RESOLVED FIXED
Product: MediaWiki extensions
Classification: Unclassified
LiquidThreads (Other open bugs)
unspecified
All All
: Highest enhancement (vote)
: ---
Assigned To: Andrew Garrett
:
Depends on:
Blocks: 19699 20118
  Show dependency treegraph
 
Reported: 2009-06-25 02:09 UTC by Salem
Modified: 2009-08-14 14:53 UTC (History)
1 user (show)

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


Attachments

Description Salem 2009-06-25 02:09:30 UTC
Currently the user get an alert only if someone right in his/her talk page. But If I wrote a comment in any discussion page then someone wrote a reply to my comment then I should be alerted also. 
This can be easily done because the reply is usually preceded by ":" or "::" or ":::" etc. This will also help the conversation continue in one place.
Comment 1 Brion Vibber 2009-07-13 18:37:07 UTC
This'll be a lot easier to handle within a properly threaded discussion system; I'm gonna toss this over to the LiquidThreads development queue (Andrew, have we already implemented notification on in-thread replies or are we still just talking about it?)
Comment 2 Andrew Garrett 2009-07-13 19:14:22 UTC
It's done, just needs some tweaks to make sure that you watch all threads that you post.
Comment 3 Andrew Garrett 2009-07-16 16:54:05 UTC
(Batch change)

These bugs are, or are related to, my current priorities.
Comment 4 Andrew Garrett 2009-08-14 14:53:33 UTC
I've fixed remaining issues with this in r55019.

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


Navigation
Links