Come together with the global Drupal community in Rotterdam, 28 Sept – 1 Oct 2026. Sessions, contribution, connection, and Early Bird savings until 8 June.Fivestart CCK casts zero votes (effectively resetting them) when review node (i.e. containing fivestar field) is unpublished with status=0. This works for simple setups but there are problems for advanced uses. Add workflow module with node access and you will have situation where review node must always have status=1 (i.e. be published in Drupal core terms) for node access rules to apply. Then you have broken voting because reviews that did not pass moderation yet already cast their votes. I think everyone who has good knowledge of Drupal knows that $node->status has just poor implementation in Drupal and many advanced setups include additional means to flag node as "published".
I think there must be some means to control if vote should be cast depending on review node state. What about some custom hook ?
| Comment | File | Size | Author |
|---|---|---|---|
| #1 | fivestar-field-vote-alter.patch | 662 bytes | crea |
Comments
Comment #1
crea commentedAttached patch adds support for hook_fivestar_field_vote_alter() and is generally safe. Alteration happens in fivestar_field() because information about review node is not passed into _fivestar_vote_cast().
Comment #2
crea commentedComment #3
dbt102 commentedDrupal 6 is now end of life, and is no longer supported. So Drupal 6 issues for Fivestar are being closed as "Closed (won't fix)". However, we don't want users who are porting from Drupal 6 to 7 to feel unwanted, so if you have any migration issues, please open them as Drupal 8 issues.