The logic for voting causes an issue for us.

Anonymous users who vote 2x / window (lets assume it is set to 1x/day) for a specific node will always overwrite their previous vote. If they then continually do this every day, then in a period of weeks, it is possible to only have 1 registered vote.

My suggestion is to add a new column to the votingapi table named "timestamp_vote_changed". The $criteria will then check against the original "timestamp" database column. If a vote is found, then only the "timestamp_vote_changed" column and any other relevant "value" columns are updated. Otherwise it will insert the new vote.

For averting spamming, this should still work as the majority of our spam votes comes from multiple IP addresses and not from an issue that 1 IP votes thousands of times on one node.

Critique on this method?

Kind regards, Jeremy

Comments

legolasbo’s picture

legolasbo
he/him
Primary language Dutch
Location Middelburg
commented
Issue summary: View changes
Status: Active » Closed (won't fix)

Drupal 6 is no longer supported. Closing old issues to clean up the issue queue.

Please reopen and update this issue if this is still an issue in the D7 or D8 version.