Closed (fixed)
Project:
Fivestar
Version:
5.x-1.11
Component:
Code
Priority:
Normal
Category:
Bug report
Assigned:
Unassigned
Reporter:
Created:
14 Mar 2008 at 18:18 UTC
Updated:
26 Apr 2008 at 13:01 UTC
Jump to comment: Most recent file
I am using Fivestar rating module together with Ubercart (beta7) to display rating in Product page. I choose the rating display to be above the teaser and full node body, it displays correctly when I log in as admin/user. However, the display is not correct when I log out and view the Product page as anonymous user. The rating is displayed at the bottom of teaser and full node body (instead of above)
| Comment | File | Size | Author |
|---|---|---|---|
| #4 | fivestar_static_position.patch | 715 bytes | quicksketch |
Comments
Comment #1
quicksketchHmm, did you try clearing your page cache? Try turning off caching at admin/settings/performance or clearing the caches with devel module.
Comment #2
wkteng commentedHi quicksketch,
The cache is disabled but it doesn't help. I have also tried it with different browsers (IE7, Opera and Firefox) and same thing happened.
p/s: I am using Drupal 5.7
Comment #3
davemybes commentedI can confirm this behaviour. I am also on Drupal 5.7. Anonymous users are not allowed to vote, while authenticated users can. Fivestar is set to display above node content, as a clickable element. It is hidden for teasers. Cache was flushed, but nothing changed. There is no separate template file for the node type that has the fivestar widget on it.
Interestingly, if I set the fivestar display to "Static above content", it displays correctly for all users. And then if I set it back to "Clickable widget above content", the display appears below the content for anon users again.
Lastly, if I allow anonymous users to vote, then the widget appears above the content as expected.
Comment #4
quicksketchincrn8 thanks! That's exactly the information I needed to actually nail this down. I noticed this happening over the past few weeks but hadn't figure out when it was happening. The solution looks like a one-liner, which I've already committed. Please try out this patch and let me know if the problem still exists.
Comment #5
davemybes commentedAwesome! That fixes it. I figured it would be a simple patch, but couldn't figure out what and where it should go. Great job, thanks.
Comment #6
davemybes commentedOh, right, you've committed this already. So its fixed then :)
Comment #7
wkteng commentedThanks for fixing this! it's been a few weeks and sorry that I did not give enough information when I reported this issue. I am new to Drupal. I will give more detailed description if I ever report any issue.
Comment #8
quicksketchThanks wkteng :)
Comment #9
wkteng commented