London Dev Meetup Rescheduled! Due to unavoidable reasons, the event has been moved to 21st May. Speakers remain the same—any changes will be communicated. Seats are limited—register here to secure your spot!

smithsson68@gmail.com
Jan 24, 2010
  10518
(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
Routing to a page in SaaS CMS

More early findings from using a SaaS CMS instance; setting up Graph queries that works for both visitor pageviews and editor previews.

Johan Kronberg | Apr 14, 2025 |

Developer Meetup - London, 24th April 2025

Next Thursday, 24th April will be Candyspace 's first Optimizely Developer Meetup, and the first one held in London this year! We've have some...

Gavin_M | Apr 14, 2025

Successful Digitalization for SMEs: How Optimizely One can Revolutionize Your Business Processes

"Achieve digital excellence with Optimizely One: Boost efficiency, delight customers, secure growth." In today's digital world, it's crucial for...

Frank Hohmeyer | Apr 11, 2025

Personalized Optimizely CMS Website Search Experiences Azure AI Search & Personalizer

In the last blog, we discussed Integrating the Optimizely CMS website with Azure AI search. Now let’s take a bit more advanced topic to serve...

Naveed Ul-Haq | Apr 10, 2025 |

Integrating Optimizely CMS with Azure AI Search – A Game-Changer for Site Search

Want to elevate your Optimizely PaaS CMS site’s search capabilities? Azure AI Search could be just the tool you need! In this blog, I’ll discuss......

Naveed Ul-Haq | Apr 9, 2025 |

Opensource release: New Package Explorer for Optimizely CMS

The import/export ".episerverdata" packages have been around as far as I can remember - and even though they might seem a bit outdated, it's still...

Allan Thraen | Apr 9, 2025 |