3
The notification settings for each Rating form are set via the notify, admin_template and owner_template parameters.
The values which admin_template and owner_template correspond to are the notifications you setup in the Rating module control panel.
So, say you setup two different email notification templates called admin_notification and ...
3
I don't believe so, no. Rating stores its data in its own database table, indexed to each entry via entry_id only, so the channel that entry lives in should not matter.
2
You could display or not display the fields using a conditional based on the channel_id.
2
It's possible to ignore the built-in {stars} and {starts_overall_avg} tags and just output the numbers using the {rating} and {overall_avg} tags instead.
This allows you to do some clever things such as add variable class names to elements depending on the rating. Your CSS can then use these class names to alter the display of the data. For example:
<p ...
2
I think you would need to write a custom plugin for this. It should be simple enough to pass an entry ID to a plugin, and then from the plugin query for the needed rating data and follow an algorithm to calculate the rating you need.
2
You can delete a rating using the {exp:rating:delete} tag: http://www.solspace.com/docs/rating/delete/
After deleting the rating, the user can try and rate again. That would be the "unvote".
2
You could do it with conditionals inside the rating:entries loop to test to see if the rating field is filled:
{if review}
Show the rating entry
{/if}
In the example above "review" is the name of the review field.
But that means you won't get an accurate {if rating_no_results} because the tag could still return results that are not displayed due to the ...
2
Rating doesn't have a feature for calculating an average of rating fields for a single Rating entry (only an average of all ratings, for all fields, for a Channel entry is possible using {overall_avg}).
You'll have to do this manually, through PHP or a plugin that specializes in calculations.
Your solution above would work:
{exp:ce_str:ing math_lite}({...
2
What you have is correct (unless you're missing the closing {/if} for the screen name check like Ahmad pointed out). However, I am assuming you have this Rating:Entries tag placed inside a Channel:Entries loop, within the same template?
If so, what's happening is that variables between the 2 tags are colliding, and you'll need to use an embed instead:
Main ...
1
Try:
$helpful.find(".ajax-response").load(link, function(response, status, xhr) {
$helpful.find(".voters").hide();
$helpful.find(".ajax-response").html(response.message);
});
Ajax submissions return a JSON array as a response. You need the correct key (in this case .message) in this array to display only text.
Another method for general-purpose ...
1
Realistically, the best way to go about this would be to do this in stages. I'd make a clone of the original site. Then upgrade it to EE2 and Rating 3.x. Then upgrade that site to EE3 and Rating 4.x. You could either then work with that site for the new build, or copy over those updated database tables to the new site.
But definitely don't attempt to copy ...
1
As per the docs (and as Jim says) Try using the `form:attribute parameter. Something like this :
form:data-abide=""
Might work, might strip the empty tag, however even if not this should get it on the form, it's just if Abide will recognise the data attribute with the 'false' value set.
form:data-abide="data-abide"
Otherwise, without rereating the form ...
1
Use the {exp:rating:entries} tag and sort by date. I'm not sure how you'd filter out those that don't have at least one vote though.
1
The issue was that {exp:rating:rank} was inside a {exp:channel:entries} tag pair.
Since both tags share the same Channel Entries library and have many variables and tags in common, you will run into variable clashes. In other words, EE will be confused about which variables to parse for which tag pair, etc. Use {exp:rating:rank} outside of {exp:channel:...
1
Try {if rating_no_results} ... {/if}, which is the "no results" conditional used in the other Rating tags. Looks like the "comment" part should be removed in the docs.
1
An empty value or the absence of a value will trigger the server-side "required" routine. Both your "select a rating" and "N/A" options have the same value and will trigger the error.
Using the required="" parameter in this case will therefore not work in your situation. Users who select "N/A" would trigger the required error, similarly to those leaving the ...
1
Sounds like this would be an issue with anything using POST variables in the EE query module and using pagination, not just with the Rating module. What if the search term was in the URL as a regular segment and you used that in the EE module? eg. http://mysite.com/rating/search/keyword/great, then
{exp:query sql="SELECT * FROM exp_rating WHERE ...
1
You would probably have to hack mod.rating.php to make that happen.
search for stars_avg_rating
I don't think this would be a small undertaking.
1
The best way to beat form spam for EE imho is to use http://devot-ee.com/add-ons/accessible-captcha, which turns captcha into a much better working q&a. This has solved all automated spam for me.
1
I'm assuming the goal is to get the channel_short_name to use in your global variable. An SQL query might be the quicker way to get to this value, and would avoid using embeds which hinder performance.
For example, this query might help:
{exp:query sql="SELECT ch.channel_name AS channel_short_name
FROM exp_ratings r
LEFT JOIN exp_channels ch ON ch....
1
Assuming you're using the latest versions of ExpressionEngine (2.6.x) and Rating (3.2.x), you can display the status of the rating submission by using the {rating_status} variable within the {exp:rating:entries} tag.
This was not documented for some reason, so I will be documenting it now. :)
1
I have seen other instances where people did not want to "vote up" the rating itself, but they wanted to "like" the product itself that you may be able to rate.
In order to get this functionality, people have used the Solspace Favorites plug-in.
Just thought I would add this info in case people run across this need too.
1
It would appear so!
http://www.solspace.com/docs/rating/rating_vote_stats/
This does exactly what I need.
1
To solve this issue, I ended up creating two channels:
1) Magazine
2) Edition
and a relationship field between the two.
So for the example data, Magazine channel contains entries for National Geographic, Sports Illustrated, etc. Edition channel contains 2013 National Geographic, 2012 National Geographic, etc, etc.
Only top voted, non community-wiki answers of a minimum length are eligible
