A critical vulnerability was discovered in React Server Components (Next.js). Our systems remain protected but we advise to update packages to newest version. Learn More

Alexander Haneng
Jan 15, 2013
  3308
(0 votes)

EPiImage and EPiServer 7

Can I use EPiImage with EPiServer 7? What is happening with EPiImage going forward?

 

I get a lot of questions regarding EPiImage, so I thought I answer you all with a blog post.

 

Why have you been so quiet lately?

Since last fall my current project has eaten up all my time, and I haven’t had much time to blog and work on open source projects like EPiImage. Soon I will go into 3 months of paternity leave and will try to keep my days EPiServer free for a change. (Brain: EPiServer out, diapers in).

I will however be back to normal speed in May, so expect to hear more from me then.

 

Does EPiImage work with EPiServer 7?

Currently the answer is no yes. Steve Celius at EPiServer Norway has started work on making the current code working with EPiServer 7, but it is still a way from doing so.

Read more here: EPiImage for EPiServer 7: Legacy release

The goal is to create a Nuget package that will make the current version of EPiImage work in a legacy way with EPiServer 7. Primarily for sites migrating from earlier versions of EPiServer.

 

Does EPiImageResizer work with EPiServer 7?

It actually does. Joel Abrahamsson asked me that question back in July 2012 and I recompiled the EPiImageResizer for EPiServer 7 Preview back then and it worked like a charm.

 

So if anyone has some spare time:

Please download the source and compile it against EPiServer 7 and create a Nuget package. The files you need are: EPiImageResizer.asx, EPiImageConfiguration.cs and EPiImageEngine.cs-

 

What is the future of EPiImage and EPiServer 7?

I have some ideas how we could totally rebuild EPiImage to use the cool new UI in EPiServer 7, but I haven’t gotten as far as building anything yet. EPiImage is open source and a collaborative undertaking, so any ideas or code is much appreciated. Unfortunately I won’t contribute anything solid until May 2013.

 

Status

So that is the status. I would really have liked to have something more positive to tell you (like that the next version of EPiImage is just around the corner), but such is life with a demanding project and small kids.

Jan 15, 2013

Comments

Please login to comment.
Latest blogs
A day in the life of an Optimizely OMVP: Learning Optimizely Just Got Easier: Introducing the Optimizely Learning Centre

On the back of my last post about the Opti Graph Learning Centre, I am now happy to announce a revamped interactive learning platform that makes...

Graham Carr | Jan 31, 2026

Scheduled job for deleting content types and all related content

In my previous blog post which was about getting an overview of your sites content https://world.optimizely.com/blogs/Per-Nergard/Dates/2026/1/sche...

Per Nergård (MVP) | Jan 30, 2026

Working With Applications in Optimizely CMS 13

💡 Note:  The following content has been written based on Optimizely CMS 13 Preview 2 and may not accurately reflect the final release version. As...

Mark Stott | Jan 30, 2026

Experimentation at Speed Using Optimizely Opal and Web Experimentation

If you are working in experimentation, you will know that speed matters. The quicker you can go from idea to implementation, the faster you can...

Minesh Shah (Netcel) | Jan 30, 2026

How to run Optimizely CMS on VS Code Dev Containers

VS Code Dev Containers is an extension that allows you to use a Docker container as a full-featured development environment. Instead of installing...

Daniel Halse | Jan 30, 2026

A day in the life of an Optimizely OMVP: Introducing Optimizely Graph Learning Centre Beta: Master GraphQL for Content Delivery

GraphQL is transforming how developers query and deliver content from Optimizely CMS. But let's be honest—there's a learning curve. Between...

Graham Carr | Jan 30, 2026