Alexander Haneng
Sep 20, 2010
(2 votes)

EPiImage Part 2: EPiImage Property

This is the second part of a four part series that started with EPiImage Part 1: EPiImageResizer


Point of confusion: EPiImageResizer is NOT EPiImage Property

Most people get this point wrong, so I thought I start this blog post by clearing this up: EPiImage Property is NOT EPiImageResizer. In other words: you can use the EPiImageResizer to resize any image, not only EPiImage Property images.The opposite is also true: You don’t need to use EPiImageResizer to display a EPiImage Property. You  get an image URL just like you would from the built in “URL to image” property.

That being said: EPiImage Property and EPiImageResizer works really well together :-)


EPiImage Property

The EPiImage Property is very similar to the built in “URL to image” property, but adds the following features:

  1. Thumbnail preview of the selected image, not just a meaningless url
  2. Click the “i” button to preview the image and add an image description



This is what the EPiImage Property looks like in edit mode if no image is selected. If clicked the normal file selection dialog box is opened.


Once an image is selected a small thumbnail is shown.


If you click the “i” button you will see a bigger preview of the image and you have the possibility to add a description.


How do I start using it?

Simply download the module from EPiCode and install it using EPiServer Deployment Center. (It just copies in a few files, it doesn’t touch your web.config or require a rebuild)

You will now get a new property type called “EPiImage”:



How do I access the property value?

The easiest is just using the string value:

<%= CurrentPage["MyEPiImageProperty"] %>

If you have added an image description it will be added as a query string: /globals/MyImage.jpg?alt=mydescription

To get access to the image url and description separately, cast the property to  a EPiImageProperty. You can then access the variables ImageUrl and ImageDescription.

<%= (CurrentPage.Property["MyEPiImageProperty"] as 
MakingWaves.EPiImage.EPiImageProperty).ImageUrl %> <%= (CurrentPage.Property["MyEPiImageProperty"] as
MakingWaves.EPiImage.EPiImageProperty).ImageDescription %>

You can also use it as a normal EPiServer property.

<EPiServer:Property PropertyName="MyEPiImageProperty" runat="server" />

This will render a img tag with an alt text if you have added a image description.

You can also get an automatically resized version of the image by specifying width, height and transformation:

<EPiServer:Property PropertyName="MyEPiImageProperty" 
runat="server" />


EPiImage Property and EPiImageResizer

To use an EPiImage Property with the EPiImageResizer user control simply specify the PropertyName of a EPiImage Property.

<EPiImage:EPiImageResizer PropertyName="MyEPiImageProperty"
                          runat="server" />


Can I convert my existing “URL to image” properties to EPiImage Property?

You certainly can. Simply change their property type to EPiImage. The existing image urls will be preserved.


Have feedback? Want to help out?

Feel free to email or twitter me with your feedback: @ahaneng :-) Also if you like to help out with debugging/testing let me know.

Thank you to Making Waves for donating it to EpiCode!


Next post: EPiImageGallery Property.

Sep 20, 2010


Andreas Thente
Andreas Thente Sep 21, 2010 10:33 AM

Look verys good Alexander.

One thing me and my customers often miss is the possibility to add language specific descriptions to an image. To work with this module on a globalized site would be a great step forward for a lot of us out here :)
I guess it wouldn´t be to difficult to wrap it in a custom property with this functionality though. Dec 6, 2010 02:38 PM

Agree, I like this one a lot! Globalization support is the tricky part though, you want the image to be common for all languages, but the alt text to differ. Guess you could store them in the image property as ?alt-en=xxx&alt-sv=yyy and render edit fields according to the active languages. But maybe then it's becoming a bit cluttry.

Rodolphe Toots
Rodolphe Toots Jan 12, 2011 10:16 AM

thank you for a very nice control!
But there is a problem with using it when the folder name and/or filename contains swedish chars like å, ä or ö.
Server.UrlDecode seems to solve that for me...

Jan 12, 2011 03:19 PM

Rodolphe: Is that for a EPiImageProperty or EPiImageGalleryProperty?
Working on 2.0 of EPiImage that will include bugfixes.

Rodolphe Toots
Rodolphe Toots Mar 28, 2011 01:44 PM

sorry for late answer, but it is for EPiImageProperty

jon pye
jon pye Mar 1, 2012 12:10 AM

Hi Alexander,

thank you for a comprehensive image gallery control by the way! Is there any way I can amend the EPiImageGalleryPropertyEditMode.js to include additional fields? (so that I have description, a url, and text to display for the url)


Please login to comment.
Latest blogs
Vulnerability in EPiServer.GoogleAnalytics v3 and v4

Introduction A potential security vulnerability was detected for Optimizely Google Analytics addon (including EPiServer.GoogleAnalytics and...

Bien Nguyen | Sep 20, 2023

Overriding Optimizely’s Content Recommendations Block to Implement Custom Recommendations

Introduction The Content Recommendations add-on for Optimizely CMS dynamically recommends content from your site tailored to the interests of each...

abritt | Sep 13, 2023 | Syndicated blog

Developer contest! Install the AI Assistant and Win Bose QC45 Headphones!

We are thrilled to announce a developer contest where you have the chance to win a pair of Bose Headphones. The goal is to be the first developer t...

Luc Gosso (MVP) | Sep 7, 2023 | Syndicated blog

Send Optimizely notifications with SendGrid API, not SMTP

If your Optimizely site already sends transaction emails through an email platform API, why not do the same with Optimizely notification emails?

Stefan Holm Olsen | Sep 6, 2023 | Syndicated blog