Closed (fixed)
Project:
Voting API
Version:
6.x-2.x-dev
Component:
Code
Priority:
Normal
Category:
Bug report
Assigned:
Unassigned
Reporter:
Created:
28 May 2010 at 13:02 UTC
Updated:
25 Mar 2014 at 07:37 UTC
Jump to comment: Most recent, Most recent file
Comments
Comment #1
zualas commentedCurrently using a workaround with a views PHP customfield to print fivestar fields:
Comment #2
zualas commentedSeems to be fixed in the latest version of Views
Comment #3
METZGERR commentedconfirmed, value does not change (or be saved) with the dev version of views.
however the latest regular release works just fine.
Comment #4
7wonders commentedStill seems to be a problem but the workaround works. Any idea how to do the workaround using clickable widget with text option?
Comment #5
zualas commentedNot sure what your requirements are, but you could try theme('fivestar_widget'). Anyway, all widget options are listed in the functiom fivestar_theme() in fivestar.module file. Hope that helps.
Comment #6
jelenex commentedActually, the problem is in VotingAPI.
Here's a quick patch - tested with latest Views 3.x. Not sure if it doesn't break anything with View 2.x
Comment #7
summit commentedHi,
Ported this issue to Voting Api, because the patch stated is within Voting Api, if this is not ok, sorry for my mistake.
Having this problem also. Thanks for going into this!
greetings,
Martijn
Comment #8
janis_lv commented#6 does the trick.
ty
Comment #9
dagmarDuplicate of #764634: Voting field handler settings not saving with Views 3.x
Comment #10
Q2U commentedFor what it's worth: I (manually) applied jelenex's #6 patch to Voting API 6.x-2.3 (2009-Aug-15) votingapi_views_handler_field_value.inc. I then edited the view which was failing to save the "Fivestar (display only)" value correctly.
After I made my edit I reloaded my view and I selected the "Fivestar (display only)" value from the dropdown list and saved my changes at which time a boatload of errors was thrown (sorry I failed to make note of the errors) but the "Fivestar (display only)" value saved correctly! I then undid the changes I had made to votingapi_views_handler_field_value.inc. (I restored the original pre-edited version). I then reloded my view and the errors were no longer present and the "Fivestar (display only)" vaslue was still saved correctly (of course).
So if you have to run Voting API 6.x-2.3 (2009-Aug-15) you can (1) manually install the #6 patch, (2) make and save your "Fivestar (display only)" changes , and then (3) uninstall the patch (revert to the original version of votingapi_views_handler_field_value.inc.).
But after you are all done don't edit your "Fivestar (display only)" value setting again or you will (of course) revert to the same problem you started with.
Comment #11
beumont commentedI have installed the newest version of Views 6.x-3.x-dev and the 6.x-2.x-dev but its still not working. Can anyone please I need this :(
Comment #12
cptX commentedI verify that this problem is still here with 6.x-3.x-dev and 6.x-3.0-alpha3. With views 2 no problem at all. I'm using voting api 6.x-2.3 .
Comment #13
ymeiner commentedI do not know if this is my version but i cannot see the appearance select box on my website. drupal 7, views 3.
i used the following code in the tpl to create the widget:
Comment #14
2noame commentedSame problem. Currently using Views 6.x-3.0 and Voting API 6.x-2.3. Refuses to save anything but "default appearance" in view when trying to make a new one, but displays all already set just fine.
Comment #15
Enrique.Ruiz commentedSame problem. Refuses to save anything but "default appearance" in view. Drupal 6.25. Views 6.x.3.0. Voting API 6.x-2.3. Fivestar 6.x-1.19.
Comment #16
Enrique.Ruiz commentedMany thanks ymeiner! I have the same problem. Where do you place this code in the tpl? Would it work with Drupal 6?
Comment #17
nanor commentedTo use Fivestar module in Drupal 7 + Views 3 + Fivestar 7.x-2.0-alpha2 . Just add a field in your content type and from “Type of data to store.” drop down select fivestar field .
And in views just add rating/stars filed from your content type . No need for complex relationships.
You might not see the stars in the Live preview, but you will when you actually go to see your view page or block or whatever your view display is.
Comment #18
relaxpor commentedExcuse me, How could i fix by this solution?
i mean which file or where should i modify or append.
Thank ypu
Comment #19
torotil commentedAs per comment #17 this seems to be handled via fields. So for 7.x-2.x there is nothing to do. The patch for 6.x-2.x has already been applied.
Comment #21
charlie charles commentedHas this been fixed yet?
Comment #22
shabbir commentedHi guys,
anyone still wondering how to do it with Drupal 7.24 + Five Star 7.x-2.0-alpha2 + Views 7.x-3.7, here is a work around,
copy the below code at the end of your fivestar.module file and save it, it will show the "Appearance" dropdown and you can select the
"five stars (with clickable text)" it is been tested at my end and it runs smoothly.
P.s. first try it in your non production site in your local machine and remove the php tag while copy pasting.
Comment #23
shabbir commentedThe reason why we are not able to see the drop down in the views is because the fivestar.module file does not have any function to show it for in the views (D6 has it). So in order to handle it in views we need to create views handler so that we can select it in the views.
Regards,
Shabbir