Anonymous user can not vote: "Oops! There was an error in submitting your vote!"

Upgraded to 6.x-2.x-dev from 2010-Apr-19, anons still can not vote. Error message from Watchdog log:

.../vote/node/63/1/updown/alternate/3b21a3cdf9dd57db3cdce33a6b89e2e3
...
Could not vote on node 63, with value 1, tag updown and token 3b21a3cdf9dd57db3cdce33a6b89e2e3
...
.../vote/node/13887/1/updown/alternate/06ca14a69634cf2584d2ed4e52d89a9b
...
Could not vote on node 13887, with value 1, tag updown and token 06ca14a69634cf2584d2ed4e52d89a9b

I do have these lines in robots.txt:

Disallow: /vote/node
Disallow: /vote/node/

Anyone?

Thanks & greetings, -asb

I think I have this allowed.

Current permissions for "Anonymous user"

vud module:

• access vote up/down statistics: (not checked)
• administer vote up/down: (not checked)
• reset vote up/down votes: (not checked)
• use vote up/down: (checked)

vud_node module:

• administer vote up/down on nodes: (not checked)
• see vote up/down node stats: (not checked)
• use vote up/down on nodes: (checked)
• view vote up/down count on nodes: (checked)

Just upgraded to 6.x-2.x-dev from 2010-Apr-23, re-checking:

.../vote/node/54853/1/updown/alternate/4600dbdb1677bf567a819898a6603f20
Could not vote on node 54853, with value 1, tag updown and token 4600dbdb1677bf567a819898a6603f20

Greetings, -asb

Settings from ./admin/settings/voteupdown/node:

• Content types: (5 enabled, including 'article' and 'blog')
• Widget selection: 'Alternate'
• Widget and votes display: 'Both teaser and full'; 'Voting on teasers' (checked); When will the total vote count be displayed? 'Both teaser and full'
• Votes reset: 'No'

Steps to reproduce? Sorry, no idea. On my sites it behaves always like this.

It might be relevant that I'm already using 'Voting API' and 'Fivestar' on those sites; maybe 'Fivestar' and 'Vote Up/Down' can not be used together?

Settings from ./admin/settings/votingapi:

• Anonymous vote rollover: '1 day'
• Vote tallying: 'Tally results whenever a vote is cast'

Anything else I could check?

Greetings, -asb

OK, I set up a completely fresh Drupal 6.16 site to test this. That's what I got when installing it through 'drush':

# drush dl vote_up_down-6.x-2.x-dev
Project vote_up_down (6.x-2.x-dev) downloaded to /var/www/drupal/sites/all/modules/vote_up_down.                                                     [success]
# drush updatedb
<em>module</em> <em>vote_up_down</em> is incompatible with this release of Drupal, and will be disabled.                                                [warning]
UPDATE {system} SET status = 0 WHERE name IN (&#039;vote_up_down&#039;)                                                                                 [success]
No database updates required

At ./admin/reports/status this gave me a red warning once:

warning: call_user_func_array() [function.call-user-func-array]: First argument is expected to be a valid callback, 'vote_up_down_access' was given in /var/www/drupal/includes/menu.inc on line 452.

Logged out, clicked on the voting widget, logged in again, went to watchdog; ./admin/reports/event/213 says:

... .org/vote/node/2/1/vote/alternate/ba2175421d186e97c763da8195397cc2
Could not vote on node 2, with value 1, tag vote and token ba2175421d186e97c763da8195397cc2

So basically replicating the voting issue simply 'worked' even on a fresh Drupal installation.

If I understand correctly, anons have per default exactly one vote per day; thus I changed the "Anonymous vote rollover" at ./admin/settings/votingapi from "1 day" to "Immediately". Logged out; the click on the widget still wasn't counted, but also no error logged in watchdog.

During the configuration I stumbled over a setting not mentioned before:

• Voting API tag (/admin/settings/voteupdown): Default value is "vote", I changed this to "updown"

On the fresh site, I did not change the Voting API tag and hadn't installed other Voting-API-based modules like 'fivestar'. The fresh site also has no 'panels' module installed.

On the old site, I also tried to change this value from the changed "updown" to the default "vote", with no positive effect for the voting of anonymous users (This site is running the 'panels' pages, e.g. on the front page).

Next I switched from the "Alternate" widget to "Default"; this seems to work better on node pages, but not from inside a panels page. Also, these votes with the "Default" widget increased the counter on node pages, but weren't registered when reloading the page. Witchdog logged the usual "Oops! There was an error in submitting your vote!" errors.

The behaviour of panels pages is quite hard to test because several layers of caching are involved (Panels caching is mostly broken at the moment, thus I'm caching through views; also I have several Drupal caches enabled). Caching, oh geez, I'm running APC and memcached on all my sites, maybe even these have side effects. However, the freshly set up site runs on a host with APC, but hasn't memached integrated (no 'memcache' module, but an memcached instance is active on the host, though it shouldn't be used without Drupal integration).

Sorry, that's all I can say for the moment.

Greetings, -asb

This is still bugging me (see attached screeshot, excerpt from my watchdog log). Any ideas?

... and we switched to Pressflow a few days ago - #672566: Compatibility with Pressflow

So, I can not confirm this. I'm getting this.

Im geting this for Opera 10.53 (Win):

vud	25.05.2010 - 17:09	Could not vote on node 55153, with value 1, tag ...	Guest

...and for Firefox 3.6.3:

vud	25.05.2010 - 17:08	Could not vote on node 55162, with value 1, tag ...	Guest

Greetings, -asb

Are you following the issue queue? There are several new reports not mentioning Pressflow (#20, #22), one immediately before and one after you closed the issue. Also I'm getting this on non-Pressflow sites, so I can't see why #672566 would be "the real problem". I documented this months ago with a fresh Drupal 6.16 (#9), and this sandbox had definitely nothing to do with Pressflow.

Besides this, #672566 doesn't fix the issue on my Pressflow sites, either.

I understand that you as a developer need a procedure to reproduce the posted isssues, but simply ignoring the queue and closing the issue as "duplicate" doesn't help anyone. If this can not be fixed, I suggest to set this to an honest "won't fix".