Anders Hattestad
Apr 27, 2011
(1 votes)

How to use PropertyXhtmlString in a Dynamic Content in CMS 6 R2

I got a problem when I was trying to use the WYSIWYG editor inside the Dynamic Content editor. The problem it seems is that the SavePageHandler in the PageBase on the edit page is not set.

This result in that the check IsNewPage will fail when the editor tries to find the EditorCssPaths.

The quick fix to this is to make your own variant of the PropertyXhtmlString like this

Code Snippet
  1. public class PropertyXhtmlStringV2 : PropertyXhtmlString
  2. {
  3.     public override IPropertyControl CreatePropertyControl()
  4.     {
  5.         return new PropertyXhtmlStringV2Control();
  6.     }
  7. }
  8. public class PropertyXhtmlStringV2Control : PropertyXhtmlStringControl
  9. {
  10.     public override void CreateEditControls()
  11.     {
  12.         (this.Page as PageBase).SavePageHandler = new SaveCurrentPage(this.Page as PageBase);
  13.         base.CreateEditControls();
  15.     }
  16. }
Apr 27, 2011


Erik Nordin Wahlberg
Erik Nordin Wahlberg Apr 27, 2011 09:05 AM

There is a hotfix available from EPiServer as well.

Apr 27, 2011 09:18 AM

Bug #64001: Dynamic Content with public property of type XHTML.

Just for searchability :)

Fredrik Eckmar
Fredrik Eckmar Apr 27, 2011 09:41 AM

I was having this exact problem this morning.. great!

Anders Hattestad
Anders Hattestad Apr 27, 2011 12:09 PM

Is there a list aviable of all the hot fix'es. Are having problem with Property to select a file from a none version filesystem.

Apr 27, 2011 01:19 PM

We have a list of hotfixes that's not up to date :(

I would suggest to open a ticket with developer support and see if they have one for your issue.

Apr 27, 2011 02:03 PM

Anders - I reported something similar to the non-versioned filesystem bug you mention,,EPiServer%20CMS,64398,4b6d%2f5rOFe3dV6T%2boAg7%2bpGT9mk%3d

Its marked as fixed, but I haven't got a hotfix as yet. Apr 27, 2011 02:04 PM

Mark: I take it you've requested a hotfix from Support?


Apr 27, 2011 02:13 PM

Side note: Hotfixes do not undergo the same QA process as official releases, consequently there would be a risk involved having them generally distributed. The normal process for us managing a limitation would be to define the problem and root cause and then work around it if possible. The last option would then be to create a fix for the issue (if possible). Directing partners to dev. support also opens up for further traceability which naturally also helps us define and / or out rule certain aspects in future cases.

Andreas Ribbefjord
Andreas Ribbefjord Jan 17, 2012 01:30 PM

We just found out, that in our CMS 6 R2, we had to add a constructor with only a call to base() in order for the snippet above to not throw an exception.

Please login to comment.
Latest blogs
Delete a content – the right way

I stumped upon this blogpost Delete content directly from the Optimizely database – Tomas Hensrud Gulla by Tomas, an OMVP. While the post is helpfu...

Quan Mai | Feb 8, 2023 | Syndicated blog

The Content Revolution - Generative AI

Hi Optimizely Community,  For the past two decades, you and Optimizely have been at the forefront of content management - creating, managing,...

Alex Atzberger | Feb 6, 2023

Delete content directly from the Optimizely database

Do you know your way around the Optimizely CMS database? Deleting, or updating, content directly in the database is pretty straightforward, but of...

Tomas Hensrud Gulla | Feb 6, 2023 | Syndicated blog

Rolling your site out to China

How to rollout your website to the China market Continue reading →

Andrew Markham | Feb 5, 2023 | Syndicated blog