mg
mg
Nov 24, 2008
  12834
(1 votes)

Tweaking the Image Editor

Now that we've been running the CMS 5 R2 for a while, I would like to hint about a small configuration option available for the Image Editor which comes with R2.

With the new image editor we've included functions to crop and resize images. By using preset formats it will be easier for editors to resize and crop to most commonly used sizes on the web site. A little nice thing you can do is to configure the preset sizes very easily by modifying the imageEditor section in web.config.

Example of preset sizes in web.config. Note: Each preset can have a name as well. If name is left out the preset name will be "width x height".

<sizePresets>
       <preset name="4:3 320 * 240" width="320" height="240" />
       <preset name="4:3 800 * 600" width="800" height="600" />
       <preset name="4:3 1280 * 960" width="1280" height="960" />
       <preset name="16:9 320 * 180" width="320" height="180" />
       <preset name="16:9 800 * 450" width="800" height="450" />
       <preset name="16:9 1280 * 720" width="1280" height="720" />
</sizePresets>

Oh, you can also set (web.config) the size of the window that is hosting the Image editor, have a look at these settings: windowWidth="900" windowHeight="600" in the ImageEditor section.

Another good thing with the Image Editor is that you can separate it to another server in in scenarios where you don't want image operations to burden the live site. But that is another story. Read more about that in this Tech note....

Nov 24, 2008

Comments

Sep 21, 2010 10:32 AM

Or you could just go ahead and buy ImageVault! :) ... but nice tweaks anyway, could come in handy, for projects without ImageVault!

Apr 17, 2017 03:34 PM

Please login to comment.
Latest blogs
Resource Editor - A localization management tool for Optimizely CMS

If you have worked with Optimizely CMS for any amount of time you know that managing localization through XML files can be tedious. Content type...

Per Nergård (MVP) | Feb 23, 2026

Storing JSON in a property the efficient way

Here is a little-known trick to store and retrieve JSON property data more efficiently.

Stefan Holm Olsen | Feb 23, 2026 |

Upgrade RSS Feed Integration to Optimizely CMS 13 – v3.0.0 Beta

I’ve upgraded my  RSS Feed Integration library for Optimizely CMS to support Optimizely CMS 13. Version 3.0.0 is currently released as a beta to...

David Drouin-Prince | Feb 21, 2026 |

Multi Site NuGet v2 for Optimizely CMS 13 – Breaking Changes & Migration

The beta version 2 of DavidHome.Optimizely.MultiSite is now available on NuGet: https://www.nuget.org/packages?q=DavidHome.Optimizely.MultiSite Thi...

David Drouin-Prince | Feb 21, 2026 |

Automate Your OCP Opal Tool Development with PowerShell

Creating an OCP (Optimizely Connect Platform) Opal Tool app from scratch can be time consuming and error prone. You need to set up the project...

Sanjay Kumar | Feb 21, 2026

Using HeadlessKit to build a head for an Optimizely SaaS CMS in .NET 10

Headless has a tendency to promise freedom and deliver alignment meetings. Two codebases. Two sets of models. Two teams trying very hard not to dri...

Allan Thraen | Feb 19, 2026 |