Vulnerability in EPiServer.Forms

Try our conversational search powered by Generative AI!

smithsson68@gmail.com
Jan 24, 2010
  10102
(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
Google Read Aloud Reload Problems

Inclusive web experiences greatly benefit from accessibility features such as Google Read Aloud. This tool, which converts text into speech, enable...

Luc Gosso (MVP) | Dec 4, 2023 | Syndicated blog

Google Read Aloud Reload Problems

Inclusive web experiences greatly benefit from accessibility features such as Google Read Aloud. This tool, which converts text into speech, enable...

Luc Gosso (MVP) | Dec 4, 2023 | Syndicated blog

Import Blobs and Databases to Integration Environments

In this blog, we are going to explore some new extensions to the Deployment API in DXP Cloud Services, specifically the ability to import databases...

Elias Lundmark | Dec 4, 2023

Join the Work Smarter Webinar: Working with the Power of Configured Commerce (B2B) Customer Segmentation December 7th

Join this webinar and learn about customer segmentation – how to best utilize it, how to use personalization to differentiate segmentation and how...

Karen McDougall | Dec 1, 2023

Getting Started with Optimizely SaaS Core and Next.js Integration: Creating Content Pages

The blog post discusses the creation of additional page types with Next.js and Optimizely SaaS Core. It provides a step-by-step guide on how to...

Francisco Quintanilla | Dec 1, 2023 | Syndicated blog

Stop Managing Humans in Your CMS

Too many times, a content management system becomes a people management system. Meaning, an organization uses the CMS to manage all the information...

Deane Barker | Nov 30, 2023