Title: WP-PostRatings Author: Lester Chan Published: 8. Februar 2006 Last modified: 1. September 2026 --- Search plugins ![](https://ps.w.org/wp-postratings/assets/banner-772x250.png?rev=3639532) ![](https://ps.w.org/wp-postratings/assets/icon.svg?rev=978014) # WP-PostRatings By [Lester Chan](https://profiles.wordpress.org/gamerz/) [Download](https://downloads.wordpress.org/plugin/wp-postratings.2.0.2.zip) * [Details](https://de-ch.wordpress.org/plugins/wp-postratings/#description) * [Reviews](https://de-ch.wordpress.org/plugins/wp-postratings/#reviews) * [Installation](https://de-ch.wordpress.org/plugins/wp-postratings/#installation) * [Development](https://de-ch.wordpress.org/plugins/wp-postratings/#developers) [Support](https://wordpress.org/support/plugin/wp-postratings/) ## Description WP-PostRatings adds a rating control to any post, page or custom post type. Visitors pick a value, the vote is posted in the background, and the result appears in its place without a page load. ### Features * Ten rating shapes, drawn with CSS rather than shipped as images, so they stay sharp at any size and cost no HTTP requests — numbers among them, for a scale whose points are read rather than counted. * A scale, or a two-way up/down control, with the rated and unrated colours as settings. * Template tags and a shortcode for the highest rated, most rated, lowest rated and highest scoring posts, optionally within a category, a tag or a time range. * A rating log with sortable columns, filters, bulk delete and Screen Options. * Google rich snippet markup for the post and its aggregate rating. * A sidebar widget, and a section on the WP-Stats page when that plugin is installed. ### Donations I spent most of my free time creating, updating, maintaining and supporting these plugins, if you really love my plugins and could spare me a couple of bucks, I will really appreciate it. If not feel free to use it without any obligations. ### Usage The simplest way, and the only one that works in a block theme without editing template files, is the shortcode. Put it in the post or page you want rated: * `[ratings]` rates the post it appears in. * `[ratings id="1"]` shows the rating for post 1, wherever you put it. * `[ratings id="1" results="true"]` shows post 1’s result without letting anyone vote from there. To put ratings on every post automatically, a classic theme can call the template tag from `single.php`, `archive.php` or `index.php`, anywhere inside the loop: ``` ``` The settings live at **WP-Admin -> Ratings -> Settings**, which has a Settings tab and a Templates tab. ### Showing A Rating In A Block A **Ratings** block is available in the editor, under **Widgets**. Two settings in the sidebar: * **Post ID** — leave it at zero to rate the post the block sits in, which is what an empty `[ratings]` does, or give an id to show another post’s rating wherever you put the block. * **Show the result only** — displays the rating without offering to change it, for putting a post’s score somewhere it should not be voted from. This is what` results="true"` does. It renders on the server, so the preview in the editor is the real rating rather than an approximation, and changing your shape, colours or templates updates every post showing it without re-saving anything. The preview is deliberately not clickable: rating from the editor would record a real vote. **The shortcode still works and is not going anywhere.** `[ratings]`, `[ratings id="1"]` and `[ratings id="1" results="true"]` behave exactly as they always have, and a post already containing one needs no change. The block calls the same code the shortcode calls, so the two render identically — use whichever suits the post. ### WP-CLI ``` wp postratings list wp postratings list --limit=50 --format=json wp postratings get 42 wp postratings delete 42 --yes wp postratings delete --all --what=logs ``` A rating lives in two places — the running totals each post displays, and a row per vote in the log. `--what` chooses which to clear: `logs`, `data` or `both`, and `both` is the default. ### REST API ``` GET /wp-json/postratings/v1/post/ POST /wp-json/postratings/v1/post//rate ``` Reading is public, because a rating is public. Rating takes the same `wp_postratings_ -nonce` the rendered control already carries, passed as a `nonce` parameter, and is subject to the same eligibility and repeat-rating settings as rating through the page. Each response carries the rendered markup as well as the numbers, because your templates and your chosen shape decide what a rating looks like. **A refusal answers 403**, not 400 — a rating already cast, a rating off the end of the scale, a bad nonce. 400 is kept for a parameter this plugin never had a chance to look at. A post that does not exist answers 404, and so does one you are not allowed to rate — a draft belonging to somebody else answers exactly as a deleted post does, rather than confirming it is there. **These routes are an addition.** The `admin-ajax.php` `wp_postratings` action is unchanged and still supported. ## Screenshots [⌊Ratings -> Settings: the shape, the scale, who may rate, and how a repeat is spotted⌉⌊ Ratings -> Settings: the shape, the scale, who may rate, and how a repeat is spotted⌉[ Ratings -> Settings: the shape, the scale, who may rate, and how a repeat is spotted [⌊The Templates tab, holding the markup of the control and of every result⌉⌊The Templates tab, holding the markup of the control and of every result⌉[ The Templates tab, holding the markup of the control and of every result [⌊Ratings -> Logs, every vote with who cast it, filterable by user and by rating⌉⌊ Ratings -> Logs, every vote with who cast it, filterable by user and by rating⌉[ Ratings -> Logs, every vote with who cast it, filterable by user and by rating [⌊The control in a post with a star under the pointer, and the same rating read- only below⌉⌊The control in a post with a star under the pointer, and the same rating read-only below⌉[ The control in a post with a star under the pointer, and the same rating read-only below [⌊The Ratings block in the editor, previewing the control for the post it is pointed at, with the sidebar choosing that post and whether the rating can be cast or only read⌉⌊The Ratings block in the editor, previewing the control for the post it is pointed at, with the sidebar choosing that post and whether the rating can be cast or only read⌉[ The Ratings block in the editor, previewing the control for the post it is pointed at, with the sidebar choosing that post and whether the rating can be cast or only read ## Blocks This plugin provides 1 block. * Ratings A rating control for a post, or its result on its own. ## Installation 1. Install and activate the plugin. 2. Go to `WP-Admin -> Ratings -> Settings` and choose the shape, the scale and who is allowed to rate. 3. Show the control: type `[ratings]` into a post, add the **Ratings** block, or call` the_ratings()` from your theme. ## FAQ ### How do I change the colour of the ratings? Go to `WP-Admin -> Ratings -> Settings` and look under **Individual Rating Text and Value**. Each step on the scale has its own pair of colour swatches, in the ** Rated** and **Not rated** columns, which is what the old `stars_crystal` and `stars_dark` image sets were for. Hovering uses the rated colour. If you would rather tell «about to pick» apart from« already recorded», set `--wp-postratings-color-hover` in your theme. ### How do I change the size, spacing or hover colour? Anything beyond the two colours is a CSS custom property on `.wp-postratings`, so this is all it takes in your theme: ``` .wp-postratings { --wp-postratings-size: 24px; --wp-postratings-gap: 4px; --wp-postratings-color-hover: #f7c56b; } ``` Before 2.0.0 a different colour meant a whole extra folder of images, which is why the plugin shipped `stars`, `stars_crystal` and `stars_dark` separately. They are all the same shape now. ### How do I use my own rating shape? Register it with the `wp_postratings_shapes` filter. It then appears on the Ratings Settings screen like any built-in shape, and unlike the old approach of dropping a folder into `wp-content/plugins/wp-postratings/images/`, it survives an update. ``` add_filter( 'wp_postratings_shapes', function ( $shapes ) { $shapes['diamond'] = array( 'type' => 'scale', 'label' => 'Diamonds', 'path' => 'M12 2l10 10-10 10L2 12z', ); return $shapes; } ); ``` The path is SVG path data drawn in a 24×24 box. For an up/down control use `'type' => 'updown'` and supply `'up'` and `'down'` paths instead of `'path'`. For a scale whose points are numbers rather than a repeated glyph, use `'type' = > 'numeric'` and supply no path at all — the position is the glyph: ``` add_filter( 'wp_postratings_shapes', function ( $shapes ) { $shapes['points'] = array( 'type' => 'numeric', 'label' => 'Points', ); return $shapes; } ); ``` A numeric shape is still a scale, so it appears under **Scale** on the settings screen and everything that reads a rating goes on reading it the same way. Only the drawing changes. ### Every visitor can rate over and over, or every rating log entry shows the same IP This is about the **Header That Contains The IP** field on the Ratings Settings screen. Leave it blank unless your site is genuinely behind a reverse proxy or CDN such as Cloudflare. Blank means the plugin uses the address your web server actually saw, which is what you want on a normal host. If you are behind a proxy, name the exact header your proxy sets, for example `HTTP_CF_CONNECTING_IP` for Cloudflare or `HTTP_X_FORWARDED_FOR` for most load balancers. Two things are worth knowing: * A visitor can send any header they like. If you name a header your own stack does not set and overwrite, anyone can put whatever they want in it and rate as many times as they please. * `X-Forwarded-For` is a list, `client, proxy1, proxy2`. As of 2.0.0 the plugin reads the first valid address in that list rather than storing the whole string. Before 2.0.0 it stored the whole string, which meant a visitor could append one more address and appear to be somebody new on every request. Because the stored value has changed shape, rating logs recorded through such a header before 2.0.0 will not match any more, and some visitors may be able to rate one more time. Logs recorded without the field set are unaffected. ### How To Change Schema Type? ``` ``` The default schema type is ‚Article‘, if you want to change it to ‚Recipe‘, you need to make use of the `wp_postratings_schema_itemtype` filter as shown in the sample code above. ### How To Add Your Site Logo For Google Rich Snippets ``` ``` By default, the plugin will use your site header image URL as your site logo. If you want to change it, you need to make use of the `wp_postratings_site_logo` filter as shown in the sample code above. ### How To Change The Text Screen Readers Announce? ``` add_filter( 'wp_postratings_ratings_image_alt', function ( $label ) { return $label; } ); ``` This is the description a screen reader reads out for a displayed rating, such as« 4 votes, average: 3.70 out of 5». Since 2.0.0 the ratings are drawn with CSS rather than images, so there is no `alt` or `title` attribute involved; the value becomes the `aria-label` on the rating. Returning an empty string removes it, which is what this filter was usually used for. Be aware that it leaves the rating with no accessible name at all, so anyone using a screen reader is told nothing about it. Prefer rewording it over removing it. ### How To Display Comment Author Ratings? ``` add_filter( 'wp_postratings_display_comment_author_ratings', '__return_true' ); ``` By default, the comment author ratings are not displayed. If you want to display the ratings, you need to make use of the `wp_postratings_display_comment_author_ratings` filter as shown in the sample code above. ### How To change the cookie expiration time? ``` function custom_rating_cookie_expiration() { return strtotime( 'tomorrow' ) ; } add_filter( 'wp_postratings_cookie_expiration', 'custom_rating_cookie_expiration', 10, 0 ); ``` The default cookie expiration if ‚time() + 30000000‘, if you want to change the lenght of the experation, you need to make use of the `wp_postratings_cookie_expiration` filter as shown in the sample code above. ### How Does WP-PostRatings Load CSS? Most restyling needs no CSS file at all any more: the colours are a setting, and the size, spacing and hover colour are custom properties. See the two questions above first. If you do want to replace the stylesheet wholesale, WP-PostRatings loads `wp-postratings. css` from your theme’s directory (or its `css/` subdirectory) when that file exists, and its own copy otherwise, so an upgrade will not overwrite your styles. Note the filename changed in 2.0.0: it was `postratings-css.css` before. A theme still shipping the old name is simply ignored, and the plugin’s own stylesheet loads instead. There is no separate RTL stylesheet any more either, because the rules use logical properties. ### My own code renders a rating and the page loads no stylesheet or script The head pass looks for the ratings widget, a `[ratings]` shortcode and the block, and anything rendering after it — a template tag, a rating in a loop page, the comment author strip — asks for the assets as it renders and gets them from the footer. Neither reaches rating markup fetched over `admin-ajax.php` or the REST API into a page that itself shows no rating: the fetch has no footer to enqueue into, and the page carried nothing for the head to find. The symptom is a rating that will not vote, drawn as bare radio buttons because every rating shape is a CSS mask in that stylesheet. Say so from the page that will hold the rating: ``` add_filter( 'wp_postratings_needs_assets', '__return_true' ); ``` Anywhere the rating can be predicted this early will do. Code that already runs later in the page — a `the_content` filter inserting a placeholder, say — can call WP_PostRatings_Template::request_assets() instead, which is the same request the render paths make and is picked up by the footer pass. ### How To Use Ratings Stats With Widgets? 1. Go to `WP-Admin -> Appearance -> Widgets` 2. The widget name is Ratings. ### To Display Lowest Rated Post ```
``` * Default: get_lowest_rated(‚both‘, 0, 10) * The value ‚both‘ will display both the lowest rated posts and pages. * If you want to display the lowest rated posts only, replace ‚both‘ with ‚post‘. * If you want to display the lowest rated pages only, replace ‚both‘ with ‚page‘. * The value 0 refers to the minimum votes required before the post get shown. * The value 10 will display only the top 10 lowest rated posts/pages. ### To Display Lowest Rated Post By Tag ```
``` * Default: get_lowest_rated_tag(TAG_ID, ‚both‘, 0, 10) * Replace TAG_ID will your tag ID. If you want it to span several categories, replace TAG_ID with array(1, 2) where 1 and 2 are your categories ID. * The value ‚both‘ will display both the lowest rated posts and pages. * If you want to display the lowest rated posts only, replace ‚both‘ with ‚post‘. * If you want to display the lowest rated pages only, replace ‚both‘ with ‚page‘. * The value 0 refers to the minimum votes required before the post get shown. * The value 10 will display only the top 10 lowest rated posts/pages. ### To Display Lowest Rated Post In A Category ```
``` * Default: get_lowest_rated_category(CATEGORY_ID, ‚both‘, 0, 10) * Replace CATEGORY_ID will your category ID. If you want it to span several categories, replace CATEGORY_ID with array(1, 2) where 1 and 2 are your categories ID. * The value ‚both‘ will display both the lowest rated posts and pages. * If you want to display the lowest rated posts only, replace ‚both‘ with ‚post‘. * If you want to display the lowest rated pages only, replace ‚both‘ with ‚page‘. * The value 0 refers to the minimum votes required before the post get shown. * The value 10 will display only the top 10 lowest rated posts/pages. ### To Display Highest Rated Post ```
``` * Default: get_highest_rated(‚both‘, 0, 10) * The value ‚both‘ will display both the highest rated posts and pages. * If you want to display the highest rated posts only, replace ‚both‘ with ‚post‘. * If you want to display the highest rated pages only, replace ‚both‘ with ‚page‘. * The value 0 refers to the minimum votes required before the post get shown. * The value 10 will display only the top 10 highest rated posts/pages. ### To Display Highest Rated Post By Tag ```
``` * Default: get_highest_rated_tag(TAG_ID, ‚both‘, 0, 10) * Replace TAG_ID will your tag ID. If you want it to span several categories, replace TAG_ID with array(1, 2) where 1 and 2 are your categories ID. * The value ‚both‘ will display both the highest rated posts and pages. * If you want to display the highest rated posts only, replace ‚both‘ with ‚post‘. * If you want to display the highest rated pages only, replace ‚both‘ with ‚page‘. * The value 0 refers to the minimum votes required before the post get shown. * The value 10 will display only the top 10 highest rated posts/pages. ### To Display Highest Rated Post In A Category ```
``` * Default: get_highest_rated_category(CATEGORY_ID, ‚both‘, 0, 10) * Replace CATEGORY_ID will your category ID. If you want it to span several categories, replace CATEGORY_ID with array(1, 2) where 1 and 2 are your categories ID. * The value ‚both‘ will display both the highest rated posts and pages. * If you want to display the highest rated posts only, replace ‚both‘ with ‚post‘. * If you want to display the highest rated pages only, replace ‚both‘ with ‚page‘. * The value 0 refers to the minimum votes required before the post get shown. * The value 10 will display only the top 10 highest rated posts/pages. ### To Display Highest Rated Post Within A Given Period ```
``` * Default: get_highest_rated_range(‚1 day‘, ‚both‘, 10) * The value ‚1 day‘ will be the range that you want. You can use ‚2 days‘, ‚1 month‘, etc. * The value ‚both‘ will display both the most rated posts and pages. * If you want to display the most rated posts only, replace ‚both‘ with ‚post‘. * If you want to display the most rated pages only, replace ‚both‘ with ‚page‘. * The value 10 will display only the top 10 most rated posts/pages. ### To Display Most Rated Post ```
``` * Default: get_most_rated(‚both‘, 0, 10) * The value ‚both‘ will display both the most rated posts and pages. * If you want to display the most rated posts only, replace ‚both‘ with ‚post‘. * If you want to display the most rated pages only, replace ‚both‘ with ‚page‘. * The value 0 refers to the minimum votes required before the post get shown. * The value 10 will display only the top 10 most rated posts/pages. ### To Display Most Rated Post In A Category ```
``` * Default: get_most_rated_category(CATEGORY_ID, ‚both‘, 0, 10) * Replace CATEGORY_ID will your category ID. If you want it to span several categories, replace CATEGORY_ID with array(1, 2) where 1 and 2 are your categories ID. * The value ‚both‘ will display both the most rated posts and pages. * If you want to display the most rated posts only, replace ‚both‘ with ‚post‘. * If you want to display the most rated pages only, replace ‚both‘ with ‚page‘. * The value 0 refers to the minimum votes required before the post get shown. * The value 10 will display only the top 10 most rated posts/pages. ### To Display Most Rated Post Within A Given Period ```
``` * Default: get_most_rated_range(‚1 day‘, ‚both‘, 10) * The value ‚1 day‘ will be the range that you want. You can use ‚2 days‘, ‚1 month‘, etc. * The value ‚both‘ will display both the most rated posts and pages. * If you want to display the most rated posts only, replace ‚both‘ with ‚post‘. * If you want to display the most rated pages only, replace ‚both‘ with ‚page‘. * The value 10 will display only the top 10 most rated posts/pages. ### To Display Highest Score Post ```
``` * Default: get_highest_score(‚both‘, 0, 10) * The value ‚both‘ will display both the most rated posts and pages. * If you want to display the most rated posts only, replace ‚both‘ with ‚post‘. * If you want to display the most rated pages only, replace ‚both‘ with ‚page‘. * The value 0 refers to the minimum votes required before the post get shown. * The value 10 will display only the top 10 most rated posts/pages. ### To Display Highest Score Post In A Category ```
``` * Default: get_highest_score_category(CATEGORY_ID, ‚both‘, 0, 10) * Replace CATEGORY_ID will your category ID. If you want it to span several categories, replace CATEGORY_ID with array(1, 2) where 1 and 2 are your categories ID. * The value ‚both‘ will display both the most rated posts and pages. * If you want to display the most rated posts only, replace ‚both‘ with ‚post‘. * If you want to display the most rated pages only, replace ‚both‘ with ‚page‘. * The value 0 refers to the minimum votes required before the post get shown. * The value 10 will display only the top 10 most rated posts/pages. ### To Display Highest Score Post Within A Given Period ```
``` * Default: get_highest_score_range(‚1 day‘, ‚both‘, 10) * The value ‚1 day‘ will be the range that you want. You can use ‚2 days‘, ‚1 month‘, etc. * The value ‚both‘ will display both the most rated posts and pages. * If you want to display the most rated posts only, replace ‚both‘ with ‚post‘. * If you want to display the most rated pages only, replace ‚both‘ with ‚page‘. * The value 10 will display only the top 10 most rated posts/pages. ### To Sort Highest/Lowest Rated Posts ``` $query = new WP_Query( array( 'meta_key' => 'ratings_average', 'orderby' => 'meta_value_num', 'order' => 'DESC', ) ); ``` Or pass the variables in the URL: `https://yoursite.com/?r_sortby=highest_rated& r_orderby=desc` Replace `desc` with `asc` for the lowest rated posts. ### To Sort Most/Least Rated Posts ``` $query = new WP_Query( array( 'meta_key' => 'ratings_users', 'orderby' => 'meta_value_num', 'order' => 'DESC', ) ); ``` Or pass the variables in the URL: `https://yoursite.com/?r_sortby=most_rated&r_orderby =desc` Replace `desc` with `asc` for the least rated posts. These examples use `WP_Query` rather than `query_posts()`, which the old ones called:` query_posts()` replaces the main query and WordPress has discouraged it for years. To sort the main query instead, use `pre_get_posts`. ## Reviews ![](https://secure.gravatar.com/avatar/23af80c24217b86df086d5192560602697e02a05134d034eff079f84e9577636? s=60&d=retro&r=g) ### 󠀁[No Support!](https://wordpress.org/support/topic/no-support-615/)󠁿 [jtlessons](https://profiles.wordpress.org/jtlessons/) 26. November 2024 Seems that Lester Chan is not supporting this plugin. I am currently unable to update the plugin in WordPress without issues. He is not responsive. The plugin was also supposed to report the ratings to Google which is does not. Why does WP allow abandoned plugins to remain on their site? If the plugins are not supported by the developers they should be removed. ![](https://secure.gravatar.com/avatar/29659578cb2fd5884aca83864aea74c868bcd7d777de706452ad7f5bbea93290? s=60&d=retro&r=g) ### 󠀁[Very great plugin](https://wordpress.org/support/topic/very-great-plugin-65/)󠁿 [Agnieszka](https://profiles.wordpress.org/hellowebscene/) 8. April 2024 Very great plugin, so far it works very well and meets expectations. The only thing I have a problem with is getting comfortable with adding custom icons, preferably as a path to the icon directory in the site theme instead of in the plugin. ![](https://secure.gravatar.com/avatar/e87e583b947894308616c624341d072b9b6743b0e6697153e5b508a0a82ace0a? s=60&d=retro&r=g) ### 󠀁[1 user – 1 vote](https://wordpress.org/support/topic/1-user-1-vote/)󠁿 [albertzzz2000](https://profiles.wordpress.org/albertzzz2000/) 1. November 2022 Один пользователь может оценить только 1 материал на сайте? Бред! Только зря потратил время на установку! ![](https://secure.gravatar.com/avatar/ab7a7d68f2e52843b4eb151c4dec61c3bf9e21d334870d9e06d049d19ea2ea1d? s=60&d=retro&r=g) ### 󠀁[表示しなくなった](https://wordpress.org/support/topic/%e8%a1%a8%e7%a4%ba%e3%81%97%e3%81%aa%e3%81%8f%e3%81%aa%e3%81%a3%e3%81%9f/)󠁿 [godcat](https://profiles.wordpress.org/godcat/) 27. Juli 2022 原因不明 ![](https://secure.gravatar.com/avatar/6931446730d875cef5e18a785b6c19ac0399b13129c699aae28444e060720295? s=60&d=retro&r=g) ### 󠀁[Nice](https://wordpress.org/support/topic/nice-4031/)󠁿 [marksjunior](https://profiles.wordpress.org/marksjunior/) 22. Juli 2021 Nice ![](https://secure.gravatar.com/avatar/2c964fff8e2c27ecfacc2b62fe1984250a1e7d3936cd29ddbf7b0680fce23181? s=60&d=retro&r=g) ### 󠀁[Very fast and with many functions](https://wordpress.org/support/topic/where-should-i-paste-the-codes-to-see-the-most-voted-publications/)󠁿 [gabrieluno](https://profiles.wordpress.org/gabrieluno/) 14. Juli 2021 I use it and recommend it [ Read all 179 reviews ](https://wordpress.org/support/plugin/wp-postratings/reviews/) ## Contributors & Developers “WP-PostRatings” is open source software. The following people have contributed to this plugin. Contributors * [ Lester Chan ](https://profiles.wordpress.org/gamerz/) “WP-PostRatings” has been translated into 14 locales. Thank you to [the translators](https://translate.wordpress.org/projects/wp-plugins/wp-postratings/contributors) for their contributions. [Translate “WP-PostRatings” into your language.](https://translate.wordpress.org/projects/wp-plugins/wp-postratings) ### Interested in development? [Browse the code](https://plugins.trac.wordpress.org/browser/wp-postratings/), check out the [SVN repository](https://plugins.svn.wordpress.org/wp-postratings/), or subscribe to the [development log](https://plugins.trac.wordpress.org/log/wp-postratings/) by [RSS](https://plugins.trac.wordpress.org/log/wp-postratings/?limit=100&mode=stop_on_copy&format=rss). ## Changelog ### 2.0.2 * NEW: A `wp_postratings_needs_assets` filter, for code that renders a rating where WP-PostRatings cannot see it coming. 2.0.0 loads the stylesheet and the rating script only where it finds the ratings widget, a `[ratings]` shortcode, the block, or a rating rendering during the page itself. Rating markup fetched over `admin- ajax.php` or the REST API into a page that shows no rating of its own is none of those, and got neither file — leaving a rating that cannot vote and, since every shape is a CSS mask, draws as a bare row of radio buttons. Returning true from the filter is how such a page asks for them. ### 2.0.1 * NEW: **Numbers is a rating shape again.** It was the one pre-2.0.0 image set with no shape to land on — every other set was a glyph repeated once per point, and a CSS mask cannot differ per position — so it was parked on circles, and a site that had chosen numbers came back from the update to five identical circles with no way to get the digits back. Numbers is now a shape of its own, offered under **Scale** beside the others, and the `numbers` image set maps onto it. It draws as one continuous bar of cells rather than five floating glyphs, and takes its colours from the Rated and Not rated settings like every other shape, so it has no palette of its own. Sites already migrated onto circles can simply select it; nothing about their ratings changes, only what those ratings are drawn with * NEW: `wp_postratings_shapes` accepts `'type' => 'numeric'`, for a scale drawn as its own positions. Such a shape needs no path, and the digits follow the site’s locale * FIXED: The shape picker grouped its rows by the shape’s exact type rather than by the control it is — a scale, or a pair of opposing actions. Any shape whose type was neither of the two words the radios offer landed in a group no radio could select and stayed hidden * NEW: A Settings link on the plugin’s row on the Plugins screen * FIXED: A visitor who may not rate is now told the actual reason. One template covers every refusal and it carried a single sentence written for one of them, so a site set to **Guests Only** refused a logged-in member and then told them to become a registered member — the one thing that would not have helped. The three reasons now read separately, and the sentence comes from a new `%RATINGS_PERMISSION%` variable. The update puts that variable into the stored Ratings No Permission Text in place of the old sentence, so an existing site gets the corrected wording without touching its settings — and a site that had reworded that sentence keeps its own wording untouched. * FIXED: The numbers shape drew its box two different ways — the sides as a border on the container, the top and bottom as inset shadows on the bar inside it. Same colour, but the sides fell on the page background while the top and bottom fell on the bar’s own tint, so the sides came out at several times the contrast and the box read as two heavy verticals with nothing joining them. All four edges are now drawn together, and the bar is no longer two pixels narrower than the box around it. * FIXED: Only one request at a time runs the outstanding upgrade. Until the plugin records itself as current the check runs on every front-end request, and the part of it that adds the log table’s indexes reads the table’s index list and then alters the table — so on a busy site two requests could both find an index missing and both try to add it, the second waiting on the first for as long as the alter took. * CHANGED: A stylesheet named `wp-postratings.css` in the parent theme now overrides the plugin’s copy too; a child theme’s copy still wins over both * FIXED: The comment author ratings display, which a theme opts into with the ` wp_postratings_display_comment_author_ratings` filter, showed nothing at all on a block theme. It read the comment from a global that only a classic theme’s comment loop sets; a block theme renders each comment through the comment template block, which passes the comment along instead and leaves that global empty. The comment now comes from where the `comment_text` filter puts it, so the display works on both. * FIXED: The comment author ratings display, which is off unless a theme opts in, still cost its query: every page with a loop fetched every rating the displayed post had ever received, then threw them away. Sites that have not opted in no longer pay it — one query fewer on every page, and on a heavily rated post it was not a small one. * CHANGED: The stylesheet and script load only on pages that actually render a rating — from the template tags, the shortcode, the block, the widget, the statistics lists or the comment author display. Pages with no rating on them no longer carry either file; pages with one get both — in the head where the page’s content already shows a rating coming, in the footer for the renders the head cannot see. * FIXED: Nothing unpublished could be rated by anybody, including the people who wrote it. 2.0.0 required a post to be publicly viewable before it would accept a rating — which stops a stranger rating your drafts, and was the point — but it never asked who was rating, so a site whose editors rate their own drafts, pending or private posts got `Invalid Post ID` on every vote. A post you can already read is now ratable whether or not the public can see it, and the message no longer blames the post ID, which is rarely what is wrong with it. * NEW: `wp_postratings_is_ratable` filters whether a given post may be rated at all, for sites whose answer is neither of the two above. * CHANGED: The REST error code for a post that may not be rated is `wp_postratings_not_ratable` rather than `wp_postratings_no_such_post`. The status is still 404, deliberately: a 403 would tell a stranger that the draft exists. ### 2.0.0 * FIXED: Any post ID could be rated, not only a published one. A visitor who was never signed in could seed `ratings_users`, `ratings_score` and `ratings_average` onto a draft, a pending, a private or a trashed post — so it arrived already rated on the day it was published — and the unpublished title was copied into the log table, where the Logs screen then displayed it. On a site that had put`% POST_TITLE%` or `%POST_CONTENT%` into the text template, the reply returned unpublished content directly. Both the AJAX action and the REST route now require a post that is actually publicly viewable * NEW: A `wp postratings` WP-CLI command — `list`, `get` and `delete`, with `-- what=logs|data|both`. * NEW: A `postratings/v1` REST API for reading a post’s rating and casting one. The `admin-ajax.php` `wp_postratings` action is unchanged and still supported. * NEW: A **Ratings** block for the editor, with the post id and a results-only toggle in the sidebar. It renders on the server through the same code the shortcode does, so the editor preview is the real rating. The `[ratings]` shortcode is unchanged and still supported — the block is an addition beside it, nothing needs migrating, and posts already holding a shortcode need no edit. * BREAKING: Requires WordPress 6.8 and PHP 8.2. * BREAKING: The rating images are gone. All 16 image sets and their 121 GIF and PNG files are replaced by 10 shapes drawn with CSS, so ratings are sharp on every screen and cost no HTTP requests. Your chosen set is migrated automatically to the matching shape: stars, stars_crystal, stars_dark, stars_png and stars_flat_png all become `star`, thumbs becomes `thumb`, and so on. If you added your own folder to `images/` it will fall back to stars; see the FAQ for how to register a custom shape properly, which unlike the old folder survives an update. * BREAKING: The rating markup has changed completely. A scale is now a group of radio buttons and an up/down is a pair of buttons, so the control announces itself correctly to screen readers and works from the keyboard. Every class and element id is now prefixed with the plugin slug: `.post-ratings` is `.wp-postratings`,`. post-ratings-image` no longer exists at all, and the wrapper id is `wp-postratings- 123` rather than `post-ratings-123`. Colour, size and spacing are CSS custom properties, which is usually a one-line replacement; see the FAQ. * BREAKING: The vote images no longer carry inline `onmouseover`/`onclick` attributes; hovering and clicking are handled by one delegated listener. Custom CSS or JavaScript that targeted those inline handlers, or that called `current_rating()` or `rate_post()` directly, needs updating. * BREAKING: The `rate_post` action is renamed `wp_postratings_rate_post` and the old name is gone, with no deprecation shim. Its three arguments are unchanged. * BREAKING: Every class is renamed to `WP_PostRatings_*`, and the plugin’s own classes are no longer called `Postratings_*`. `RATINGS_IMG_EXT` is now `WP_POSTRATINGS_IMG_EXT`. * BREAKING: The settings screen moved to `WP-Admin -> Ratings -> Settings`, at ` admin.php?page=wp-postratings-settings`. Settings and Templates are the two tabs of that one page rather than two menu entries. * BREAKING: The option rows are renamed. The fifteen `postratings_*` rows become one `wp_postratings_options`, and the two separate version markers become one` wp_postratings_version`. Your settings are migrated automatically on the first load after the update. * BREAKING: The shared, unprefixed `stats_display` and `stats_mostlimit` option rows are no longer read. WP-Stats integration is now two settings of this plugin’s own, on the Settings tab, and WP-Stats asks each plugin for its section through the `wp_stats_sections` filter rather than reading anybody’s options. Update all seven WP-Stats-aware plugins together; see the Upgrade Notice. * BREAKING: If you set «Header That Contains The IP» (for Cloudflare, a load balancer or any reverse proxy), that header is now parsed as the forwarded-for chain it is, and only the first valid address in it is used. Previously the whole header value was stored, so a visitor could rate repeatedly just by appending another address to it. Existing rating logs recorded through such a header will no longer match, so some visitors may be able to rate once more. Leave the field blank unless you are actually behind a proxy. See the FAQ. * BREAKING: «Ratings Logging Method» is now «Check For Repeat Votes», and it no longer decides whether anything is logged. It never did anything but choose what a returning visitor is matched against, and the two readings pointed opposite ways: a site that picked «Do Not Log» or «Logged By Cookie» got no ratings log, no rows on the logs screen and no WP-Stats figures, which is not what either choice sounds like. **Every vote is now recorded whatever this is set to.** The choices read «Do Not Check», «Check By Cookie», «Check By IP Address», «Check By Cookie And IP Address» and «Check By Username»; the stored numbers are unchanged, so your setting means what it always meant. The option key inside `wp_postratings_options` is `check_method` rather than `logging_method`, migrated automatically. * BREAKING: The `wp_postratings_always_log` filter is gone. It asked for exactly the behaviour above, which is now the default, and a filter that forces the default does nothing. Sites that would rather _not_ keep the record have the opposite filter instead: return false from `wp_postratings_log_rating` and no row is written. The post’s own score and vote count are post meta and are updated either way. * BREAKING: The stylesheet is now `wp-postratings.css`, not `postratings-css.css`, and there is no separate RTL stylesheet. If your theme ships its own `postratings- css.css` override it will no longer be picked up; rename it, or better, use the colour setting and the CSS custom properties instead. * NEW: Rewritten as classes under `includes/`, so the plugin now works installed under any directory name. * NEW: Settings moved to the WordPress Settings API, with the options and templates screens merged into one tabbed page. * NEW: The rating log is now a standard WordPress list table, with sortable columns, bulk delete, a search box and Screen Options. * NEW: The scripts are vanilla JavaScript; the jQuery dependency is gone, and hovering the stars is pure CSS, so nothing runs on mouse move at all. * NEW: Rating colours are a setting, per rating rather than per site: each row of the rating table has its own rated and not-rated colour, with a Reset to default beside them. This replaces the old colour variants of the image sets, where changing colour meant choosing a different set of files. * NEW: `wp_postratings_shapes` lets you register your own rating shape. * NEW: `WP_POSTRATINGS_TRUST_PROXY` and the `wp_postratings_trust_proxy` filter opt into the usual reverse-proxy headers without naming one. «Header That Contains The IP» stays the narrow answer — exactly the one header your proxy sets — and still wins when both are given; the constant is the broad one, meaning «try the seven headers proxies commonly use». WP-Email, WP-Polls, WP-Ban and WP-UserOnline already worked this way; WP-PostRatings was the one that did not. * NEW: `wp_postratings_capability` filters the capability the plugin’s screens require, which is still `manage_ratings`. * NEW: The stylesheet honours `prefers-color-scheme: dark`, `prefers-contrast: more` and `prefers-reduced-motion: reduce`. * CHANGED: Ratings display a true percentage instead of being rounded to the nearest half image, so an average of 3.7 out of 5 now fills 74% of the stars rather than showing three and a half. * CHANGED: `RATINGS_IMG_EXT` and `wp_postratings_image_extension` no longer choose anything; there are no image files left to have an extension. The `wp_postratings_ratings_image_alt` filter stays, but it now sets the rating’s accessible label rather than an image’s alt and title text. * FIXED: The plugin requested an admin stylesheet that had been an empty file since 2020. * FIXED: The per-post lock file was never released, so one was left behind in the server’s temporary directory on every single rating. * FIXED: Uninstalling on a multisite network stopped after the first 100 sites, leaving the options and the rating table behind on every site after that. * FIXED: Activating network-wide also stopped after 100 sites. * FIXED: A rating outside the configured scale was recorded as a vote worth nothing, and warned on PHP 8. * FIXED: Comment author ratings never matched by IP, so they had been silently broken since ratings began being stored hashed. * FIXED: The «numbers» rating image set could not be saved; it reported success and reverted to stars. * FIXED: Post titles containing an apostrophe were stored in the log with a stray backslash. * FIXED: The rating log always claimed to be sorted «Descending» whichever order was chosen. * FIXED: Deleting all rating data left every post’s cache holding the values that had just been removed. * FIXED: Numerous PHP 8 warnings on the admin screens and in an unconfigured widget. * NEW: When an up/down post has no verdict to show, it shows you your own vote instead. A tie points nowhere, so rating a post down and landing on one drew a blank pair that looked exactly like the control you had just clicked — as though the vote had not been recorded. Your vote is the only direction that can honestly be attributed at that point, so it takes the shape and the label reads «You rated this down». A post that _does_ have a verdict keeps showing it: one that is 500 to 3 in favour must not read as a thumbs down to the single visitor who disagreed. Your vote comes from the «already rated» cookie, or from the rating log when the repeat-vote check is by username. It is deliberately never matched by IP address: behind a proxy or a mobile network many visitors share one address, so that would tell somebody who had never voted that they had * FIXED: An up/down rating with no verdict was drawn as a vote down. Zero is not a direction: a post nobody has rated, and a post with as many down votes as up, both average zero, and both showed a lit thumbs down. They now show the pair unlit. This also fixes what a site sees after switching from a scale to an up/ down control — an up/down vote is worth -1 or +1, so a score off a scale of stars is far too large to be one, and reading it as a direction showed every previously rated post as a thumbs up that no amount of voting down could shift. Such a post now shows the unlit pair until its up/down votes outweigh its history, and the vote count and score are reported exactly as stored throughout * FIXED: On a dark colour scheme the unrated shapes stayed the light grey chosen for a light page, and glared. The dark default is a custom property set on the container `the_ratings()` adds — but the widget, and the shortcode and block when asked for results only, print the rating without that container, so nothing they drew ever inherited it. The same was true of the high-contrast default ## Meta * Version **2.0.2** * Last updated **3 Wochen ago** * Active installations **20'000+** * WordPress version ** 6.8 or higher ** * Tested up to **7.1.1** * PHP version ** 8.2 or higher ** * Languages * [Czech](https://cs.wordpress.org/plugins/wp-postratings/), [Dutch](https://nl.wordpress.org/plugins/wp-postratings/), [English (US)](https://wordpress.org/plugins/wp-postratings/), [Estonian](https://et.wordpress.org/plugins/wp-postratings/), [Finnish](https://fi.wordpress.org/plugins/wp-postratings/), [French (Canada)](https://fr-ca.wordpress.org/plugins/wp-postratings/), [Japanese](https://ja.wordpress.org/plugins/wp-postratings/), [Moroccan Arabic](https://ary.wordpress.org/plugins/wp-postratings/), [Romanian](https://ro.wordpress.org/plugins/wp-postratings/), [Russian](https://ru.wordpress.org/plugins/wp-postratings/), [Spanish (Chile)](https://cl.wordpress.org/plugins/wp-postratings/), [Spanish (Mexico)](https://es-mx.wordpress.org/plugins/wp-postratings/), [Spanish (Spain)](https://es.wordpress.org/plugins/wp-postratings/), [Spanish (Venezuela)](https://ve.wordpress.org/plugins/wp-postratings/) und [Ukrainian](https://uk.wordpress.org/plugins/wp-postratings/). * [Translate into your language](https://translate.wordpress.org/projects/wp-plugins/wp-postratings) * Tags * [ajax](https://de-ch.wordpress.org/plugins/tags/ajax/)[post](https://de-ch.wordpress.org/plugins/tags/post/) [rating](https://de-ch.wordpress.org/plugins/tags/rating/)[ratings](https://de-ch.wordpress.org/plugins/tags/ratings/) [vote](https://de-ch.wordpress.org/plugins/tags/vote/) * [Advanced View](https://de-ch.wordpress.org/plugins/wp-postratings/advanced/) ## Ratings 4.3 von 5 Sternen. * [ 133 5-Sterne-Rezensionen ](https://wordpress.org/support/plugin/wp-postratings/reviews/?filter=5) * [ 15 4-Sterne-Rezensionen ](https://wordpress.org/support/plugin/wp-postratings/reviews/?filter=4) * [ 9 3-Sterne-Rezensionen ](https://wordpress.org/support/plugin/wp-postratings/reviews/?filter=3) * [ 3 2-Sterne-Rezensionen ](https://wordpress.org/support/plugin/wp-postratings/reviews/?filter=2) * [ 19 1-Sterne-Rezensionen ](https://wordpress.org/support/plugin/wp-postratings/reviews/?filter=1) [Your review](https://wordpress.org/support/plugin/wp-postratings/reviews/#new-post) [See all reviews](https://wordpress.org/support/plugin/wp-postratings/reviews/) ## Contributors * [ Lester Chan ](https://profiles.wordpress.org/gamerz/) ## Support Issues resolved in last two months: 4 out of 4 [View support forum](https://wordpress.org/support/plugin/wp-postratings/) ## Donate Would you like to support the advancement of this plugin? [ Donate to this plugin ](https://lesterchan.net/site/donation/)