Per Nergård (MVP)
+1
Nov 29, 2015
visibility 3868
star star star star star
(1 votes)

Validation of media file attributes

As all of you know media files in EPiServer are IContent which lets us add properties to handle for example meta data. This is great but how do we make the editors fill in those fields...

I guess that it depends a lot of what type of target audience you have as well as what fits the site editors. 

The below could be alternatives to consider:

  • You don't do anything at all
    Obviously not recommended.

  • You add fallbacks in the code so atleast some is used.
    Could be ok, but "real" meta data is better.

  • You make the field required and disable auto publishing of mediafiles.
    I don't like this because it seems a bit to hard on the editors. It should be easy to add a bunch of images without needing to process them all at once.

  • You try to add som other validation before publishing pages or blocks that use media files.
    If you block publishing I guess this is basically as hard on the editors as the previous option but to me it still feels as a better way.

To solve the last option I did a small validation class that checks all ContentReference and ContentArea properties on a page, checks if it's an image and then checks if the Copyright attribute is empty or not (Did this in the Alloy demo site). If youn're using Url properties with a media file UIHint it's easy to add.

You can get the code over at Gist. You can see the result below where I added a image with no Copyright info into the Teaser Image property.

Image ValidateImageFileExample.jpg

Nov 29, 2015

Comments

error Please login to comment.
Latest blogs
You’re not headless. You’re hybrid — and that’s the CMS 12 default.

For CMS 12 / Commerce teams with a React (or similar) storefront who keep hearing “just go headless” or “just move to Graph.” This is Part 1 of Fin...

Hanskumar Tripathi | Aug 13, 2026

Stott Security for Optimizely SaaS CMS

Introduction Stott Security  has been helping developers and editors manage Content Security Policies and security headers on  Optimizely PaaS CMS...

Mark Stott | Aug 13, 2026

Optimizely XML Resource Builder: A Visual Studio Extension for Language Resource Files

Anyone who has worked on a larger Optimizely solution will know the feeling. You add or update a page type, block type, or shared base class,

Adnan Zameer | Aug 13, 2026 |

Optimizely SaaS CMS Management API: The Write Side of Headless

Everything I’ve written in this series so far has been about reading content — Optimizely Graph, webhooks, ISR, caching layers. But at some point y...

Kiran Patil | Aug 12, 2026 |