Support for Drupal 7 is ending on 5 January 2025—it’s time to migrate to Drupal 10! Learn about the many benefits of Drupal 10 and find migration tools in our resource center.
After upgrading to rc4 I cannot create new content if that content uses the fivestar module.
I get an undefined function error.
Here is the error message.
Fatal error: Call to undefined function fivestar_content_is_empty() in /html/modules/cck/content.module on line 803
I reverted to rc3 and it works again.
Comment | File | Size | Author |
---|---|---|---|
#5 | fivestar_content_is_empty.patch | 641 bytes | quicksketch |
Comments
Comment #1
yched CreditAttribution: yched commentedNot exactly sure why this would not reveal in RC3, but this is a bug in Fivestar. CCK field modules need to implement hook_content_is_empty() so that they can tell CCK which values it should consider as being empty.
Comment #2
drupaceous CreditAttribution: drupaceous commentedsame issue, subscribing
Comment #3
dan.thompson CreditAttribution: dan.thompson commentedI can confirm this bug.
Comment #4
ken69 CreditAttribution: ken69 commentedi have the same bug :( Please solve a problem
Comment #5
quicksketchI've committed the attached patch to correct the problem. I'll roll a 1.12 update or release a 1.13 version shortly.
Comment #6
Anonymous (not verified) CreditAttribution: Anonymous commentedAutomatically closed -- issue fixed for two weeks with no activity.
Comment #7
Brian294 CreditAttribution: Brian294 commentedIt looks like the patch works well. Thank you! :-)
Comment #8
sciman CreditAttribution: sciman commentedSame error today on fivestar_content_is_empty from a user who doesn't know much about patching things. Any chance for an update on the download? Thanks so much!
Comment #9
sciman CreditAttribution: sciman commentedI found this as a closed issue, but I experience the error in trying to attach a rating to a node in Drupal 6.4 with this 6.x-1.12 installed. I note a commitment to upgrade which is dated after the current release was posted, and yet I've not seen a 1.13?
Comment #10
quicksketchThat's right, this bug is fixed, but I haven't gotten out a 1.13 version. It contains an upgrade path that separates out comment support into a separate module, which I'm nervous about. Perhaps a beta version is appropriate.
Comment #11
Anonymous (not verified) CreditAttribution: Anonymous commentedAutomatically closed -- issue fixed for two weeks with no activity.