Per Nergård (MVP)
Apr 26, 2013
  3643
(0 votes)

CMS 7 Subscriptions “bug”

The other day the first task was to build a subscription page. The Alloy demo templates doesn’t contain an example so I needed a quick brushing up on the topic.

The conclusion is that subscriptions work in the same way as in older versions of EPiServer. Not an extremely well documented area but that might be the topic of another post.

So our subscription template needs a property named “EPSUBSCRIBE-ROOT”.

So now the problems begins. In C# we can’t use a hyphen (-) in class or property names. We have the same issue with the property  “EPSUBSCRIBE-EXCLUDE” that is optional to include on pages that should not be sent out in the subscription job.

EPiServer has created a bug for this issue.

To get around this until EPiServer has released a fix we have to create the properties through admin mode.

Apr 26, 2013

Comments

Arild Henrichsen
Arild Henrichsen Nov 8, 2013 03:05 PM

Note this is also a problem in CMS 6 when using PageTypeBuilder. The latest official release of PTB (2.0) does not support hyphenated property names such as EPSUBSCRIBE-ROOT, although several developers have requested, and proposed, a workaround. See http://pagetypebuilder.codeplex.com/workitem/6913 for issue report and http://pagetypebuilder.codeplex.com/sourcecontrol/list/patches for a proposed patch. (Disclaimer: untested)

You can download the PTB source code from http://pagetypebuilder.codeplex.com/releases/view/79210 and add the necessary modifications.

Please login to comment.
Latest blogs
From Prompting to Production: Optimizely Opal University Cohort and the Future of Agentic MarTech

Most organizations today are still playing with AI. They experiment with prompts, test ideas in isolated chats, and occasionally automate a task or...

Augusto Davalos | Apr 28, 2026

Six Compelling Reasons for Upgrading to CMS 13

Most software updates ask you to keep up. Optimizely CMS 13 asks something different — it asks whether your digital strategy is built for a world...

Muhammad Talha | Apr 28, 2026

Optimizely CMS 13 breaking changes: GetContentTypePropertyDisplayName

When upgrading from CMS 12 to 13, resolving property display names may not work as before. Here’s what changed.

Tomas Hensrud Gulla | Apr 27, 2026 |

Accelerate Optimizely DAM Adoption: Unlocking Business Value with Metadata Bulk Import

Accelerating Optimizely DAM Adoption How a Metadata-Driven Bulk Import Utility Unlocks Real Business Value Executive Summary For enterprises runnin...

Vaibhav | Apr 27, 2026