ezstarrating: star ratings for content #

This page is for site builders who let visitors rate content. ezstarrating adds a Star Rating datatype (ezsrrating). Add the attribute to a content class, and visitors can rate objects of that class from 1 to 5 stars.

• Each user may vote once per session.
• Ratings are stored in the table ezstarrating_data and recalculated into a per-object average.
• Templates can show the rating, and the extended attribute filter ezsrRatingFilter sorts and fetches by rating.
• It depends on ezjscore: the rating call is the ezjscore function ezstarrating_rate, with ezstarrating_user_has_rated.

Set it up #

1. Activate the extension (ActiveExtensions[]=ezstarrating) and regenerate autoloads: php bin/php/ezpgenerateautoloads.php -e.
2. Create the rating table from extension/ezstarrating/sql/<engine>/ (mysql, postgresql, oracle; a SQLite schema was added in 6.0.3).
3. Grant the roles that may vote the policy module ezjscore, function call, limitation ezstarrating_rate.
4. Add a Star Rating attribute to the class to be rated.
5. Clear the caches and open an object of that class: the stars appear.

What changed in the Exponential 6 releases #

About 6.0.3:

• The rating classes declared protected constructors over the public constructor of eZPersistentObject, which PHP 8 refuses when the class is loaded. They are public again; ezsrRatingObjectTreeNode calls the persistent object constructor, and the empty PHP 4 style constructors are gone.
• ezsrRatingObject::stats() kept its cache in a function static, which a persistent worker (Velocity) carries from one request to the next. It now lives in a static class property, so it stays bounded, shows new votes and never crosses databases.

Related pages #

• sevenx_themes_simple: the simple theme's rating view loads the jQuery script
• Backend ezjscore services
• Velocity engines
• Chronicle and release notes
• Change ledger
• Behaviour changes of the extensions
• Months: 2026-09, 2026-10 (all extensions)