Per Nergård (MVP)
Sep 23, 2015
  2091
(0 votes)

Overview of properties and AllowedTypes attribute

When testing a website one important piece for me is to validate that all content areas have the correct allowed types. Since I'm a developer I have compared the code to the specification. But reading this blog post about getting a list of allowed page types for a specific page type (post here) inspired me to make a small tool for that.

In the process I added the allowed page types code and a silly feature that just prints the count of pages per page type (from the root page, and with FPW call).

It looks like this:

 Image siteinformation1.jpg

Image siteinformation3.jpg

Image siteinformation2.jpg

Code over at GitHub. I use CodeFile instead of CodeBehind so if you wan't to add it to your solution be sure to change it. If you just wan't to test it out just drop it in the root folder.

Sep 23, 2015

Comments

Sep 25, 2015 10:53 AM

Nice, simple and powerful!

valdis
valdis Sep 28, 2015 08:06 AM

Haven't checked the code- but would be nice to see a list of all page instances and links to it for "Page types - number of pages". Have you considered to "alter" built-in content type editor pages and provide this functionality also there? :) This can be done via Asp.Net web page adapters.

Per Nergård (MVP)
Per Nergård (MVP) Sep 28, 2015 01:38 PM

Hi Valids

Would be easy enough to add links to the pages since I do a simple FPWC call to get the count so I already have the list.

Haven't considered changing the built in content type editor pages but it's a good idea.

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