Per Nergård (MVP)
Sep 17, 2013
  2487
(0 votes)

CMS7 tool for assisting in verifying block appearance in content areas.

In CMS7 we got blocks which is great for all customers who get more flexible solutions.

Since there today isn’t any real nice solution to limit which blocks can go into a contentarea this introduces a bigger challenge for implementing the html / css and validating that everything looks fine.

Depending on the site and customer we can have page types which have none to maybe even only consist of contentareas. In combination with a lot of different blocks there are a lot of possible combinations to verify.

To make this process easier I have created a small tool. It  generates test pages of your chosen page types adding the blocks you have chosen to all contentareas.

Prerequisites:

Note if you have page types with [Required] properties you need to either temporarily remove the required attribute or maybe use the #debug preprocessor statement to set default values so the page type at least don’t crash.

  1. Create a folder in the global block folder that contains “testblocks” in it’s name. Here you create all blocks that you want to use in the tool.
  2. Below the start page create a page with “testblocks” in the name. This will be the container for where the tool creates pages.

 

The tool

  1. The first thing you need to do is choose a page type which the tool uses for generating container nodes for structuring up test pages. This type should have no limitations as to what page types can be created below it.
  2. Then you choose which blocks you want to generate test pages for.
  3. Then you choose which page types to use when generating test pages.
  4. The fourth option decides how the test pages should be generated.  Example further down in this post.

 

Overview

 

Example 1

Here we want to generate test pages for all blocks and all page types and group them by block.

Option1

Result example 1

 

Result1

Example 2

In example 2 we want to use all blocks and two page types but here we want to add all chosen blocks to each of the page types contentareas.

Option2

Result example 3

Result2_1

result2_2

It’s created as a EPiServer.SimplePage. Just download the code and drop it the site root, change the name space and compile and you’re ready to go.

I hope you find it useful. Any feedback appreciated. The code is over at the code section.

Sep 17, 2013

Comments

Please login to comment.
Latest blogs
Optimizely CMS 13: Why Search & Navigation Now Means Graph Migration

Optimizely CMS 13 makes Graph a required part of the platform. Here is what that means in practice for teams moving from Search & Navigation, with ...

Wojciech Seweryn | Apr 8, 2026 |

Jhoose Security Module V3.0.0 – Site-Level Security Configuration for Optimizely

Jhoose Security Module updated for Optimizely CMS 13, introducing separate packages for CMS 12 and 13 with ongoing support and enhancements.

Andrew Markham | Apr 6, 2026 |

Searchable settings page

In my current project which has been actively developed for quite some time we have a big classic settings page. Unfortunately the placement and...

Per Nergård (MVP) | Apr 6, 2026

Using Azure Devops Pipelines in Optimizely SAAS (Configured) Commerce

Introduction When working with SAAS Commerce build service v2 your currently need to use a github repo with configured branches to start deployment...

Mark Hall | Apr 4, 2026 |

Forcing Lowercase URLs in Optimizely CMS During Auto-Translation

Learn how to fix uppercase and punctuation issues in Optimizely CMS 12 URL segments caused by LanguageManager auto-translation using a custom...

Stuart | Apr 2, 2026 |

Stott Robots Handler v7 for Optimizely CMS 13

Stott Robots Handler version 7 is now available for  Optimizely PaaS CMS 13 . This is includes updates to support the switch from a Site based...

Mark Stott | Apr 2, 2026