Last modified: 2006-06-24 13:08:58 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 6423 - Null edits to user talk pages trigger newtalk flag
Null edits to user talk pages trigger newtalk flag
Status: RESOLVED FIXED
Product: MediaWiki
Classification: Unclassified
Page editing (Other open bugs)
unspecified
All All
: Normal normal (vote)
: ---
Assigned To: Nobody - You can work on this!
:
Depends on:
Blocks:
  Show dependency treegraph
 
Reported: 2006-06-24 09:07 UTC by Kyle Moore
Modified: 2006-06-24 13:08 UTC (History)
0 users

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


Attachments

Description Kyle Moore 2006-06-24 09:07:50 UTC
I don't know how many people realize this, and I don't know how risky it is to
file it as a bug, but purging the caché (or editing it without making any
changes) of a user talk page will fire a message alert. If a troll were to get
ahold of this and write a script, it would be rather annoying and we would never
know who it was (without access to the server log, anyway). A message alert
should only be triggered if there is actually a change in the text of the page.
Comment 1 Rob Church 2006-06-24 12:46:00 UTC
Unable to reproduce with a regular action=purge, but the null edit thing *does*
trigger the new talk flag.
Comment 2 Rob Church 2006-06-24 13:08:58 UTC
...and should now be corrected in SVN trunk, r14996.

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


Navigation
Links