Per Nergård (MVP)
OMVPSaaS CMS Developer CertificationCommerce Connect 13 Developer Certification +2
Jun 5, 2026
visibility 577
star star star star star
(0 votes)

Automatic assign of content reference properties on content creation

A long time ago I was tired of configuring setting properties on a settings page when deploying new functionality that needed global settings, so I did a way of accomplishaing that with attributes from the settings page.

Earlier this week I got tired of it again and did another version for CMS 13 but this time I did it from the other way around with an attribute on the content type. 

Old blog post here: 2019

So the idea is that when building a new function and we need to configure a settings property to point to a new content type for some shared functionality you could configure that via an attribute on the content type so after deploy you just create your new page and it automatically wires up the setting for you.  Done in an Alloy site so thats why I use StartPage.

Maybe not a super big problem if you just delploying a new features but if setting up a boilerplate solution of some sort from scratch it will make your life much easier.

// Auto-match: the settings property whose [AllowedTypes] most specifically accepts ContactPage is used.
[RegisterIn(typeof(StartPage))]
public class ContactPage : SitePageData { }

// Explicit property: recommended when the settings property allows a broad base type (e.g. PageData).
[RegisterIn(typeof(StartPage), nameof(StartPage.ContactsPageLink))]
public class ContactPage : SitePageData { }

// React on creation instead of publish.
[RegisterIn(typeof(StartPage), Trigger = RegisterTrigger.Created)]
public class ContactPage : SitePageData { }


Code over at my GitHub. Pnergard AutoRegister

Jun 05, 2026

Comments

error Please login to comment.
Latest blogs
Lessons From the Optimizely Web Experimentation Compromise

Introduction On 16th November 2026, Scott Helme and the team at Report URI published a detailed investigation into malicious JavaScript being serve...

Mark Stott | Nov 17, 2026

From Review to Release: Publishing My First Optimizely OCP App

Building an OCP app is only half the story. This post follows Publish Child Items from its first submission to a live App Directory release: what...

Chirag Khanna | Nov 16, 2026 |

Brilliant and Ignorant: Building an Optimizely Knowledge Base for AI Agents

Claude is a brilliant developer who has never seen Optimizely. How we gave our agents the framework experience a human needs half a year to earn:...

Allan Thraen | Nov 16, 2026 |

Budgeting for Agent Platform credits in 2027

How to budget for Optimizely Agent Platform (formerly Opal) credits in 2027: what a credit buys, how to size use cases, and what to agree with...

Matthew Dunn | Nov 15, 2026 |

Integrating Siteimprove with Optimizely: From Accessibility Compliance to Content Excellence

Over the last few months, I’ve worked on several Optimizely solution designs involving accessibility, SEO, analytics, governance, and content...

Madhu | Nov 14, 2026 |

Fallback images that fit: handling broken images with a service worker

A broken image is never the right shape On a content-heavy commerce site, some images will fail. Editors delete assets that are still referenced, C...

Allyn Thomas | Nov 14, 2026