Hi. First of all - thank you for your module - it meets all my needs :) .
My problem (Drupal 5.1): after submitting a story with fivestar CCK field added - I get such warnings:
>>>>>>>>>>>>>>
warning: Invalid argument supplied for foreach() in /var/www/site/site.com/modules/node/node.module on line 504.
warning: implode() [function.implode]: Bad arguments. in /var/www/site/site.com/modules/node/node.module on line 508.
user warning: You have an error in your SQL syntax; check the manual that corresponds to your MySQL server version for the right syntax to use near '' at line 1 query: SELECT n.nid, n.vid, n.type, n.status, n.created, n.changed, n.comment, n.promote, n.sticky, r.timestamp AS revision_timestamp, r.title, r.body, r.teaser, r.log, r.format, u.uid, u.name, u.picture, u.data FROM node n INNER JOIN users u ON u.uid = n.uid INNER JOIN node_revisions r ON r.vid = n.vid WHERE in /var/www/site/site.com/includes/database.mysql.inc on line 172.
warning: Invalid argument supplied for foreach() in /var/www/site/site.com/modules/node/node.module on line 504.
warning: implode() [function.implode]: Bad arguments. in /var/www/site/site.com/modules/node/node.module on line 508.
user warning: You have an error in your SQL syntax; check the manual that corresponds to your MySQL server version for the right syntax to use near '' at line 1 query: SELECT n.nid, n.vid, n.type, n.status, n.created, n.changed, n.comment, n.promote, n.sticky, r.timestamp AS revision_timestamp, r.title, r.body, r.teaser, r.log, r.format, u.uid, u.name, u.picture, u.data FROM node n INNER JOIN users u ON u.uid = n.uid INNER JOIN node_revisions r ON r.vid = n.vid WHERE in /var/www/site/site.com/includes/database.mysql.inc on line 172.
>>>>>>>>>>>>>>
Comments
Comment #1
pathognomonic commentedI'm having the same problem too. Have you found any work-arounds or solutions yet??
This looks like a great module. Just a little buggy.
Comment #2
elki-1 commentedI'm having the same problem too. I'd appreciate any guidance on fixing this.
Thanks!
e.
Comment #3
adawire commentedI have the same problem. Help!
Comment #4
quicksketchCould someone confirm the is still a problem in version 1.4?
Comment #5
quicksketchI reproduced the problem and corrected it with the patch in http://drupal.org/node/137887. Thanks!
Comment #6
robeano commentedThanks for the fix. I tested fivestar 1.5 successfully on Drupal 5.1 as well.