Last modified: 2013-01-08 23:23:33 UTC
A misleading "created" e-mail message is generated, when a watched page is actually moved in LiquidThreads: ---- Subject: translatewiki.net page Thread:Support/About WikiReader:How:license text/en has been created by Nike From: MediaWiki Mail <noreply@translatewiki.net> To: Purodha <...@...> ---- Dear Purodha, The translatewiki.net page Thread:Support/About WikiReader:How:license text/en has been created on 13 June 2012 by Nike, see https://translatewiki.net/wiki/Thread:Support/About_WikiReader:How:license_text/en for the current revision. This is a new page. Editor's summary: - Contact the editor: mail: https://translatewiki.net/wiki/Special:EmailUser/Nike wiki: https://translatewiki.net/wiki/User:Nike There will be no other notifications in case of further changes unless you visit this page. You could also reset the notification flags for all your watched pages on your watchlist. Your friendly translatewiki.net notification system -- To change your e-mail notification settings, visit https://translatewiki.net/wiki/Special:Preferences To change your watchlist settings, visit https://translatewiki.net/wiki/Special:EditWatchlist To delete the page from your watchlist, visit https://translatewiki.net/w/i.php?title=Thread:Support/About_WikiReader:How:license_text/en&action=unwatch Feedback and further assistance: https://translatewiki.net/wiki/:Contents ---- See also Bug 14901 - Email notification mistakes log action for new page creation
This is almost a duplicate of bug 14901 except that LQT is a very special case. An ad-hoc notification is needed so that it's understandable and it also can be sent to watcher of the target talk, see blocked bug.
Adding as blocker of bug 39480 because we use thread move heavily. Ryan, Fabrice, is this sort of thing something Echo will address?
Nemo: Sort of, but not directly. Echo will provide the notification framework that Flow will use to provide notifications. Flow is the eventual replacement for LQT. Someone could hack LQT to use Echo rather than it's own notifications, but it probably won't be done by the Foundation. Either way, this bug would need to be fixed on the LQT/Flow side. Echo would just be the messenger. Echo does generate some Notifications on its own, but only for some core functions. Any notifications related to Extensions are actually defined in the Extensions themselves (and either use Echo hooks or the Echo API to deliver the notifications). We don't have any plans to do any work on LQT, though. Your options are probably: 1. Convince Andrew Garrett (or a volunteer) to fix the bug 2. Disable LiquidThreads 3. Wait a year (or so) for Flow
