Last modified: 2014-04-15 06:22:16 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 T41505, the corresponding Phabricator task for complete and up-to-date bug report information.
Bug 39505 - Specify why the user is receiving an email notification (enotif) for a thread
Specify why the user is receiving an email notification (enotif) for a thread
Status: NEW
Product: MediaWiki extensions
Classification: Unclassified
LiquidThreads (Other open bugs)
master
All All
: Low enhancement (vote)
: ---
Assigned To: Nobody - You can work on this!
:
Depends on:
Blocks:
  Show dependency treegraph
 
Reported: 2012-08-20 16:17 UTC by Nemo
Modified: 2014-04-15 06:22 UTC (History)
2 users (show)

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


Attachments

Description Nemo 2012-08-20 16:17:13 UTC
Due to bug 24288 and bug 21733, the user often doesn't know why he's receiving a notification and is completely clueless about it, especially if he wants to opt-out.
MediaWiki:lqt-enotif-newthread and MediaWiki:lqt-enotif-reply should have a footer like enotif_body, which currently is:

----

--
To change your e-mail notification settings, visit
{{canonicalurl:{{#special:Preferences}}}}

To change your watchlist settings, visit
{{canonicalurl:{{#special:EditWatchlist}}}}

To delete the page from your watchlist, visit
$UNWATCHURL

Feedback and further assistance:
{{canonicalurl:{{MediaWiki:Helppage}}}}

----

And in that case $UNWATCHURL should probably depend on whether the message has been received due to watchlisting the thread or the talk page.
If such a dynamic linking is too much, at least it should be noted that the user may be required to unwatch both the thread and the talk and also to change the prefences about both.

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


Navigation
Links