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.
In upgrading to 6.x-1.13, I ran the update only to get an error. It appears that fivestar_update_6104 is attempting to query the table {content_node_field} which simply doesn't exist in my database. Based on the comments, I suspect (but I don't know) that content_node_field is a CCK table, and I am not using the CCK module (believe it or not). If I am correct in my assumption, that upgrade should be wrapped with a test for module_exists('CCK') or something like that.
Comment | File | Size | Author |
---|---|---|---|
#3 | fivestar.install.patch | 1.37 KB | zroger |
Comments
Comment #1
quicksketchI think you're correct. Thanks for the detailed report of the problem.
Comment #2
NancyDruComment #3
zroger CreditAttribution: zroger commentedThis issue exists when upgrading from Drupal 5, even when CCK exists. This is caused by the CCK update which creates the content_node_field table running after the fivestar updates.
This patch adds the recommended module_exists() condition to fivestar_update_6104() as well as adding logic to fivestar_update_6100() to make sure that CCK updates have run first, if CCK is being used.
Comment #4
quicksketchThanks Roger! I also added the same if (content_exists()) check to the Drupal 5 version of fivestar_update_5703().