"inactive Fivestar Rating field that uses a Stars widget." After re-enabling fivestar
| Project: | Fivestar |
| Version: | 6.x-1.18 |
| Component: | Code |
| Category: | bug report |
| Priority: | normal |
| Assigned: | Unassigned |
| Status: | closed |
For reference, I'm using:
Drupal Core 6.14
Ubercart 6.x-2.0-rc6
Fivestar 6.x-1.18
Voting API 6.x-2.3
Anyway - I just upgraded from Drupal Core 6.13 to 6.14. When I did, the Fivestar field on my product pages disappeared, despite all Voting & Fivestar modules being re-enabled.
When I go to the "Manage Fields" section of my Product content type, I see the following errors:
"This content type has inactive fields. Inactive fields are not included in lists of available fields until their modules are enabled."
"Product Rating (field_product_rating) is an inactive Fivestar Rating field that uses a Stars widget."
Similarly, this field (field_product_rating) no longer shows up on my list of fields.
I do not know what is driving this error. The only thing I can think of is that when I created this field, the widget was called a "Fivestar" widget (I think), and now the system seems to be looking for a "Stars" widget.
Any help would be greatly appreciated.
#1
Same happens to me. Just upgraded to Drupal 6.14 from 6.10... Using the same modules that brycesenz is.
#2
This has apparently been an issue before with FiveStar during updates. I found a workaround here:
http://drupal.org/node/327041#comment-1354364
If you're able to get into your MySQL tables, there are two fields that control FiveStar activation. During the upgrade, they're apparently getting set to 0 and need to be manually reset to 1. Pretty easy to do if you've got phpMyAdmin or some other interface with your database. I had a similar problem, followed the steps (described in detail at the node address above), and things are back to normal. Worth noting for future upgrades until it gets fixed.
#3
Thanks for the issue reference.
A potentially easier interim solution is to visit update.php and run Fivestar update 6105.
#4
#5
We should probably implement hook_enable and re-activate the inactive fields. Also, marking #607532: Temporarily disabling Fivestar module leave CCK fields as "inactive" as a duplicate.
#6
Apparently Fivestar does correctly implement hook_enable and content_notify(), but content_associate_fields() doesn't make the fields available without including fivestar_field.inc first, so I added it to our implementation of hook_enable. I was able to re-create and solve the problem described here with the attached patch. It would be great to get a review before committing this.
#7
After further thought and getting a "sounds good" from quicksketch, this is committed in the 1.x and 2.x/HEAD branches. People affected by this issue can either apply this patch, wait for the nightly dev snapshot to be re-rolled or await the next official release sometime this week.
#8
Automatically closed -- issue fixed for 2 weeks with no activity.