Alexander Haneng
Jan 23, 2013
  5660
(3 votes)

EPiImage for EPiServer 7: Legacy release

If you are upgrading an EPiServer CMS 6 site to EPiServer CMS 7 and you are using EPiImage, you can now download a version of EPiImage that works with EPiServer 7.

 

Word of warning!

Currently this version of EPiImage is strictly a “works on my machine” release! No promises made!

Also there are some small issues that needs to be worked out. See the section “Know issues” later in this blog post for details.

The full source code is available here, so if you run into any issues you can try to fix them yourself. Just remember to commit any fixes back to the community!

 

Legacy

This version is not meant for a new site based on EPiServer 7, but for people upgrading an existing EPiServer CMS 6 site that uses EPiImage. The reason is that this version does not take advantage of all the new UI features, but simply make it work using EPiServer legacy features.

 

The legacy mode in EPiServer 7 new UI

Below you can see how the EPiImage properties behaves in the new edit UI:

image

A page showing an EPiImageProperty and an EPiImageGalleryProperty in the new edit mode.

 

image

If you use the <EPiServer:Property runat="server" PropertyName="EPiImage" /> to show the EPiImageProperty the image will be clickable.

 

image

When you click the EPiImageProperty image you get a dialog box where you can edit the image.

image

EPiImageGallery does not have a EPiServer:Property template, so you will have to go to forms mode to edit it.

 

 

image

Clicking the “…” button will open the property in a dialog box where you can edit the gallery. Note: You can not drag and drop files from the file manager in this mode (you need to use classic mode).

 

 

 

The “classic” edit mode in EPiServer 7

If you run your site in the “classic” edit mode, then the properties works the same as in EPiServer CMS 6.

image

 

 

Known issues

There are a few known issues:

1. You can’t drag and drop files from the file manager into galleries in the new UI.

2. The preview window is not fully displayed in the legacy mode.

image

If you find any more, please leave them in the comments.

 

Thanks to

Steve Celius (EPiServer Norway) has done most of the work to get this version together, so send him some happy thoughts Smile Also Linus Ekström (EPiServer Sweden) provided the key sample code to get the JSON serialization working: Thanks!

 

Download

Get the module from nuget.episerver.com or download it here.

Jan 23, 2013

Comments

ketels
ketels Jul 25, 2013 03:31 PM

Hi.
I'm having some problems with EPiImage on a EPi7 site. When the app pool, recycles the EPiImage Property becomes null.
Is this anything you have seen before?

Mar 24, 2014 02:00 PM

I'm having the same issue after a site upgrade. Any help on resolving?

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