smithsson68@gmail.com
Jan 24, 2010
  10942
(1 votes)

Page Rating example using Page Objects

At the EPiServer Techforum in Oslo last week, I showed a quick and dirty page rating feature for CMS 6 using Page Objects and Dynamic Content. The source code for that can be found here .

The project consists of 3 class:

  1. The Rating object. This is the Page Object that holds the rating data for the page
  2. The RatingDC which provides the IDynamicContent implementation
  3. The RatingControl which is the Dynamic Content User Interface control.

To test it out, copy the Rating assembly dll to a CMS RC1 site’s bin folder. Create a Rating folder under the site root folder and then copy the RatingControl.ascx to that. Under that folder create a folder called Images. To that folder copy the star.png file.

You will then need to register the Dynamic Content in the site’s episerver.config file as shown below:

<dynamicContent>
    <controls>
        <add description="Displays a Rating facility" name="Rating" type="EPiServer.Samples.RatingDC, Rating" />
    </controls>
</dynamicContent>
Jan 24, 2010

Comments

Björn Olsson
Björn Olsson Sep 21, 2010 10:33 AM

What happens with the cached PageData object when the page is saved using the same version? Is it left unchanged or removed from the cache?

Sep 21, 2010 10:33 AM

Hi,

At the moment all changes to page objects will involve the affected page being removed from the cache. We hope to make some small changes before CMS 6 is released so if only the actual object has changed (the item that is stored in the Dynamic Data Store) then we do not need to save the PageData and therefore the cache remains in tact.

Obviously, if new page objects are added or existing ones removed from the PageObjects collection on PageData that a save is required and the cache will still be emptied.

Paul.
/ Paul Smith

Sep 21, 2010 10:33 AM

Sounds good :) Removing the page from cache everytime someone votes wouldn't be very optimal, looking forward to the release of CMS6.

/BR
/ Björn Olsson

Please login to comment.
Latest blogs
AEO, GEO and SEO with Epicweb AI Assistant in Optimizely CMS

Traditional SEO remains important, but content must now also be optimized for answer engines and generative AI. This article explains how the Epicw...

Luc Gosso (MVP) | May 11, 2026 |

Accelerating Optimizely CMS and Commerce upgrades with agentic AI (Part 1 of 2)

How Niteco's Upgrade Machine   uses orchestrated AI coding agents to deliver a buildable baseline and a running CMS, then hands over for...

Hung Le Hoang | May 11, 2026

Commerce 15 and CMS 13: Optimizely’s Next Step Toward AI-Powered, Graph-First Commerce

Optimizely is preparing to release Commerce 15 in mid-May 2026 , positioning this as a foundational shift—not just an upgrade. The direction is...

Augusto Davalos | May 7, 2026

The future of Content: Introducing Optimizely CMS 13

Optimizely In the rapidly evolving landscape of digital experience, the "monolithic vs. headless" debate is being replaced by a more sophisticated...

Aniket | May 6, 2026

Hide built in scheduled job from the admin UI

Ok so this probably goes into the not so useful section but late last night I got a veery strong feeling that all projects I am  involved with have...

Per Nergård (MVP) | May 6, 2026

Optimizely CMS 11 Is Out of Support — and the Hard Part of the Upgrade Isn't the CMS

On 10 April 2026, Optimizely formally announced that CMS 11 was out of support — CMS 13 had reached GA on 31 March, and by policy only the two most...

Allan Thraen | May 6, 2026 |