Page MenuHomePhabricator

Give ad-hoc email notification for thread move
Open, MediumPublic


A misleading "created" e-mail message is generated, when a watched page is actually moved in LiquidThreads:

Subject: page Thread:Support/About WikiReader:How:license text/en has been created by Nike
From: MediaWiki Mail <>

To: Purodha <...@...>

Dear Purodha,

The page Thread:Support/About WikiReader:How:license
text/en has been created on 13 June 2012 by Nike, see
for the current revision.

This is a new page.

Editor's summary: -

Contact the editor:

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 notification system

To change your e-mail notification settings, visit

To change your watchlist settings, visit

To delete the page from your watchlist, visit

Feedback and further assistance:

See also Bug 14901 - Email notification mistakes log action for new page creation

Version: unspecified
Severity: normal



Event Timeline

bzimport raised the priority of this task from to Medium.Nov 22 2014, 12:22 AM
bzimport set Reference to bz37583.
bzimport added a subscriber: Unknown Object (MLST).

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
Jdforrester-WMF lowered the priority of this task from Medium to Lowest.Aug 4 2016, 11:34 PM
Jdforrester-WMF added a subscriber: Jdforrester-WMF.

LiquidThreads has been replaced by StructuredDiscussions on all Wikimedia production wikis (except one, which will be done soon). It is no longer under active development or maintenance, so I'm re-classifying all open LQT tasks as "Lowest" priority.

Nemo_bis raised the priority of this task from Lowest to Medium.Aug 5 2016, 7:31 AM
Liuxinyu970226 lowered the priority of this task from Medium to Lowest.Mar 22 2019, 2:07 AM
Liuxinyu970226 added a subscriber: Liuxinyu970226.

Changing this without a Gerrit patch is a bit weired

Nemo_bis raised the priority of this task from Lowest to Medium.Mar 22 2019, 1:08 PM