I searched over the posts from the last year and came up with 1 (one) thread. Here relating to one vote per user for ratings in the repository module. It basically says re-write the module with no further advice.

Here's my problem...

Im launching a community events and locations site with listings for bars, resteraunts, hotels, etc.. (on 2/1 yay...) and the community functions are critical to what the client needs, specifically the comments and **ratings**. In my alpha tests I took a 5-star rating, logged in as a regular user, and sunk it to 1-star with about 8 ratings clicks. I have a FIERCE competitor in the market and I wouldnt put it past him to sink every rating on the site.

I dont know that I would have chosen this solution knowing this up front.. it just seems so..duh.. that I didnt bother investigating it.

Has anyone come up with a solution that dosen't involve me firing up Visual Studio?

Thanks for listening to the whine and cheese party...sigh..

It's never easy is it?

Thanks for the reply. I surfed MediaAnt's Review Pro and it looks great, and good price too. Since Im so close to launch, I can't drop a new module on my designer but I will have it for ammo and an upgrade possibility.