|
Brendan Pike
Member since:
09 January 2008
Posts: 36
|
Wednesday 26 August 2009 4:23:31 pm
Ability to change vote:
I think the ability to change your rating vote is useful, there are many uses where this could be valid. For example, perhaps you give an extension rating a vote of 2 but later the author improves it so you wish to then change your rating to 4. Having this as an option would be good.
Combined multiple ratings in a single object:
For example, you might wish to rate hotels you have stayed in but with more breakdown detail. You might provide separate ratings for Food, Service, Comfort and then in the template would need the ability to summarise these and show an average combined outcome score.
www.dbinformatics.com.au
We are always interested in hearing from experienced eZ PHP programmers and eZ template designers interested in contract work.
|
|
|
André R.
Member since:
14 January 2008
Posts: 145
|
Thursday 27 August 2009 6:28:39 am
Thanks for the feedback!
"Combined multiple ratings in a single object:"
This should already be possible, or so I though, but now it is:)
|
|
|
Carlos Revillo
Member since:
09 January 2008
Posts: 48
|
Wednesday 02 September 2009 7:58:14 am
Here are some ideas i have.
First. I would like to check if the user has rated BEFORE he can click any of the stars. if we allow them to click and then we show the message about 'what you did won't count' maybe they get upset...
Second. Thinking in accesibilitiy options, it would nice to have the possibility of voting without javascript enabled in your browser. This could easily (at least ar think so), changing the javascript:void(0) in the href for calls to a module with the params needed.
Third. It would nice to have the posibility or defining when a user will be allowed to vote again. i mean, something that 'you can't vote this again for this month' or something like that.
Thank you :).
|
|
|
André R.
Member since:
14 January 2008
Posts: 145
|
Wednesday 02 September 2009 1:57:44 pm
> First:
That should already be possible, using this:
|
|
|
Carlos Revillo
Member since:
09 January 2008
Posts: 48
|
Wednesday 02 September 2009 2:16:01 pm
Ok to all your replies. First one was related to the second one. the ajax call will do the job perflecty, but i would like to do it without javascript.
This reminds me a long talk we had some months ago about the posibility or having those viewCacheTweaks by class :). Problem with viewCacheTweaks: if we have 10.000 'article' nodes we'll have to add a entry in the ini for each one (correct me if i'm wrong).
It would be great, not only for ezstarrating but entire ezpublish, to have a way to don't cache specif parts of your template.
somekinda
|
|
|
André R.
Member since:
14 January 2008
Posts: 145
|
Thursday 03 September 2009 5:04:26 am
That won't happen before we change tempalte language, and even then it will not work when the page is fully cached (page / view cache).
As for the pr class discussion, that won't happen before we have expiry data for node cache that includes meta data like class identifier.
|
|
|
André R.
Member since:
14 January 2008
Posts: 145
|
Tuesday 08 September 2009 11:32:30 am
Ability to change vote is now implemented, this is enabled by default and can be turned off with site.ini[eZStarRating]AllowChangeRating
|
|
|
Gaetano Giunta
Member since:
09 January 2008
Posts: 152
|
Thursday 24 September 2009 7:59:46 am
+1 for adding the module view for non-ajax voting (and the corresponding hrefs on the star icons in the default template)...
|
|
|
Gaetano Giunta
Member since:
09 January 2008
Posts: 152
|
Wednesday 21 October 2009 8:53:00 am
Other idea: deprecate the fetch-by-starrating template operators, introduce proper fetch functions.
Not hard to do, not a lot of functionality gained, but it makes a helluva lot more sense...
|
|
|
Gaetano Giunta
Member since:
09 January 2008
Posts: 152
|
Wednesday 21 October 2009 9:02:24 am
also add depth support when using parent-node-id to fetch-by-starrating...
|
|
|
André R.
Member since:
14 January 2008
Posts: 145
|
Thursday 22 October 2009 1:15:32 am
"+1 for adding the module view"
Don't need a view, only need redirect support on ezjscore server calls.
"also add depth support when using parent-node-id to fetch-by-starrating... "
From inline doc:
|
|
|
Gaetano Giunta
Member since:
09 January 2008
Posts: 152
|
Thursday 22 October 2009 1:35:37 am
@ar: thanks, i have read it and that's what I'm currently using. It still is a (little) pain because it forces me to keep the whole hierarchy of the starting node fixed (or to fetch the node again just to get it), while with node_id + depth I could be more flexible. I could also specify node X + depth 2 levels, which I cannot do right now (feel free to correct me)
|
|
|
André R.
Member since:
14 January 2008
Posts: 145
|
Thursday 22 October 2009 1:51:16 am
Yes, but then I have to fetch the node for you to figure out node path.. :P By forcing a few rules, I make sure the fetch does not do any costly operations behind the scene like normal list / tree fetches does.
|
|
