Last modified: 2006-04-29 21:40:54 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 5760 - bot edits on user talk page should not trigger "you've got new message"
bot edits on user talk page should not trigger "you've got new message"
Status: RESOLVED DUPLICATE of bug 3224
Product: MediaWiki
Classification: Unclassified
General/Unknown (Other open bugs)
unspecified
All All
: Normal enhancement (vote)
: ---
Assigned To: Nobody - You can work on this!
:
Depends on:
Blocks:
  Show dependency treegraph
 
Reported: 2006-04-29 11:00 UTC by Rémi Kaupp
Modified: 2006-04-29 21:40 UTC (History)
0 users

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


Attachments

Description Rémi Kaupp 2006-04-29 11:00:41 UTC
When an edit is made by a bot on a [[User talk: page, it should not trigger the "you've 
got new message" flag. This would allow minor edits to be done without useless 
notifications, such as link corrections after mass page moves.
Comment 1 Rob Church 2006-04-29 16:02:07 UTC
I'm inclined to resolve this WONTFIX. A number of bots on, for instance, the
English Wikipedia, have the purpose of delivering messages to a number of users,
for whatever reason. Said users would still want notification of the new
messages status.

In addition, I'd be inclined to think that all alterations to the user's talk
page should be notified, but I'm open to persuasion on this point.
Comment 2 Brion Vibber 2006-04-29 21:40:54 UTC

*** This bug has been marked as a duplicate of 3224 ***

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


Navigation
Links