Five New Optimizely Certifications are Here! Validate your expertise and advance your career with our latest certification exams. Click here to find out more


Jan 8, 2019
  3319
(3 votes)

Image Cropper Property Editors (using ImageResizing.NET)

Happy New Year All!

There are many ways an image crop can be defined. As we know, editors do like as much flexibility as possible :) Having discussed various approaches with multiple content teams, we have decided to enable cropping at the page or block level.  

We made 2 editors available:

  • Image Reference
  • Image Reference List

The aspect ratio can be defined for each instance of the property editor individually

Usage

Image can be assigned by drag and dropping it into the drop zone:

Once the image is dropped, Image Cropper dialog is displayed:

Of course, any image can be edited or deleted at any point. Moreover images in Image Reference List editor can be reordered:

Implementation

The NuGet package is available in the EPiServer Nuget Feed. The source code and the implemenation guide can be found on GitHub.

Jan 08, 2019

Comments

Jan 8, 2019 03:26 PM

What I'd like it to be able to fix the ratio. If a shared image is being used in a block/page that's a fixed 16/9 area it would be good that the editor only supported that ratio and would mean large images could be reused across the board. Else users can still crop an image out that then when rendering through might be displayed in a different ratio

Jan 8, 2019 06:46 PM

Hi Scott,

This is something that is supported out of the box. Please have a look at the code snippet below:

[ImageReference(CropRatio = (double)16/9)]
public virtual ImageReference SingleImage { get; set; }

Thanks, M

valdis
valdis Jan 9, 2019 06:31 PM

hey, this is nais that you finally packed it up as nugget :) would be cool if you could add syntax sugars for rendering picture tag as well (https://github.com/valdisiljuconoks/ImageResizer.Plugins.EPiServerBlobReader#render-picture-element).

also would be awesome to jump to StructureMap v4.x

don't take it like critisism :), I just don't have naything else to do as reviewing foreign code.. i added coupe github issues. just my old man 2 cents :)

Please login to comment.
Latest blogs
Transitioning to Application Insights Connection Strings: Essential Insights for Optimizely CMS

Transitioning to Application Insights Connection Strings: Essential Insights for Optimizely CMS As part of Microsoft's ongoing modernization effort...

Stefan Johansson | Mar 27, 2025

Save The Date - London 2025 Summer Meetup

Following last years very succesful meetup in London July 2024 https://world.optimizely.com/blogs/scott-reed/dates/2024/7/optimizely-london-dev-mee...

Scott Reed | Mar 25, 2025

Revalidate Page in Next.js after Publishing Content in Headless Optimizely PaaS CMS.

Headless CMS implementations are becoming increasingly popular. In this approach, the CMS and the front-end application are decoupled and can use...

Tomek Juranek | Mar 25, 2025

Getting 404 when expecting 401

A short story about the mysterious behavior of an API in headless architecture.

Damian Smutek | Mar 25, 2025 |