Last modified: 2013-04-03 01:07:17 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 T48820, the corresponding Phabricator task for complete and up-to-date bug report information.
Bug 46820 - Don't allow someone to thank the same person twice for the same revision
Don't allow someone to thank the same person twice for the same revision
Status: RESOLVED DUPLICATE of bug 46690
Product: MediaWiki extensions
Classification: Unclassified
Thanks (Other open bugs)
unspecified
All All
: Unprioritized normal (vote)
: ---
Assigned To: Nobody - You can work on this!
:
Depends on:
Blocks:
  Show dependency treegraph
 
Reported: 2013-04-03 01:06 UTC by Steven Walling
Modified: 2013-04-03 01:07 UTC (History)
2 users (show)

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


Attachments

Description Steven Walling 2013-04-03 01:06:02 UTC
Currently, if the user hard refreshes the page or opens another view of the same revision (say, diff view when you were previously on History), you can thank the same user twice for the same revision. 

This is potentially very confusing, since it appears like your previous thank you did not take effect. We should do our best to disallow this. 

I understand that, in order to keep this feature lightweight, we're not creating database tables etc. to keep a log of thanks. And that's probably good since it could easily grow right along with revision tables once enabled. 

As an interim solution, I'd support even a half-measure like preventing duplicate thanks for 24 hours at least, such as by remembering the thank yous for the duration of your session (tied to the session cookie, maybe using memcached, etc.).
Comment 1 Alex Monk 2013-04-03 01:07:17 UTC

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

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


Navigation
Links