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


Jun 10, 2014
  3933
(0 votes)

EPiImage & EPiImage Gallery dojo-based custom property for EPiServer 7.5 and above

Upon the heavily uses of the popular MakingWaves EPiImage gallery property , I have decided to put some of the effort to upgrade the property from old school jquery based on EPiServer 6 on to EPiServer 7. This was at the same time as a good exercise to help started with Dojo development. Furthermore,  since the VPP is no longer used, and replaced with media content on EPiServer 7.5, with the help from others I have also managed to upgrade the property, so that it is compatible with the latest assets management system. Drag and drop images from assets management is also added on to this new release.

Following the philisopy of contributing back to the community, I hope this could provide back some benefits for other EPiServer developer

Properties values are also stored in the same format as the original values so that they could be easily migrated. Here are the list of items within the project:

Here is the structure view of the project:

EPiImage

From top to bottom:

1. Templates Folder store all the html templates for the controls used for EPiImage and EPiImage Gallery Property controls. EPiImageInfoForm is to allow user to edit image title, description, and image link. Here is how the form will look like:

EPiImageInfoEdit

On most of the project that requires Image Gallery property, it is found that you usually need these information for the images, .i.e. to be used for slideshow.

2. EPiImage.js , EPiIMageGallery.js

These files store the client logic implementation of the editing control for EPiImage & EPiImage Gallery properties. Digging in to the code, you could see that they are based on a lot of diiferent dojo and EPi-dojo controls

3. EPiImageInfoForm

This is to handle the client side logic for the above editing image infor form

4. ModuleInitializer & RequireModule

These files are responsible to initialize the connection to the Rest Store Controller on the server side, so that the client control could send request back to the server side.

5. EPiImageGalleryProperty, EPiIMageProperty, EPiImageEditorDescriptot, EPiIMageGalleryEditorDescriptor.

These files are responsible for custom property declaration, serialize data, and declare the editor template for the properties.

6. ImageFile on Media Folder

Since EPiServer 7.5, all asset must be based on an image content data class, therefore we will need one for our images as well. Please feel free to remove this file from your copy if you already had one on your project.

7. EPiImageStore

This class is responsible for getting the image info from Content Data Store. This is inherited from RestControllerBase , that available from EPiServer 7.

8. Module.config

You will need to copy the bits that needed from within this module.config file on to your project, to get the properties working:

<assemblies>
    <add assembly="EPiImage" />
  </assemblies>
  <clientResources>
    <add name="epiimage.editors.style" path="Styles/imagegallery.css" resourceType="Style" />
  </clientResources>
  <dojo>
    <!-- Add a mapping from alloy to ~/ClientResources/Scripts to the dojo loader configuration -->
    <paths>
      <add name="app" path="Scripts" />
      <add name="epiimage" path="Scripts/EPiImage/" />
    </paths>
  </dojo>
  <clientModule initializer="app.ModuleInitializer">
    <requiredResources>
      <add name="epiimage.editors.style"/>
    </requiredResources>
  </clientModule>

For the above config:

8.1. Fist block,add assembly to generate the url for EpiImageStore, which is declared as a Rest Store, to get the file info from the server back to the client.

8.2. Second block, the client resources are for module initializer, and css that will be used for our properties.

8.3. . Third block, the dojo module is to define the namespace for Scripts folder that will be used for EPI Image/Gallery client editor.

 

Here is how the image gallery property will look like on the back-end :

ImageGalleryProperty

When editing the image collection, user will has the ability drag and drop images from media assets to the add image box as well.

Here is how the properties can be called on the fron-end:

@if (Model.ImageCollection != null)
    {
        foreach (EPiImageGalleryImage image in Model.ImageCollection)
        {
            <a class="image_view" href="@Url.ContentUrl(image.ImageUrl)" rel="lightbox"><img src="@Url.ContentUrl(image.ImageUrl)" /></a>
        }
    }

This could also be used on Webform project without any problems.

A screencast on how the property works could be found here: http://www.screencast.com/t/IPVCO5OmPtPU

The full source code of this project is available at here. If you need the sample project or any help send a request here.

Jun 10, 2014

Comments

Please login to comment.
Latest blogs
Optimizely Configured Commerce and Spire CMS - Figuring out Handlers

I recently entered the world of Optimizely Configured Commerce and Spire CMS. Intriguing, interesting and challenging at the same time, especially...

Ritu Madan | Mar 12, 2025

Another console app for calling the Optimizely CMS REST API

Introducing a Spectre.Console.Cli app for exploring an Optimizely SaaS CMS instance and to source code control definitions.

Johan Kronberg | Mar 11, 2025 |

Extending UrlResolver to Generate Lowercase Links in Optimizely CMS 12

When working with Optimizely CMS 12, URL consistency is crucial for SEO and usability. By default, Optimizely does not enforce lowercase URLs, whic...

Santiago Morla | Mar 7, 2025 |

Optimizing Experiences with Optimizely: Custom Audience Criteria for Mobile Visitors

In today’s mobile-first world, delivering personalized experiences to visitors using mobile devices is crucial for maximizing engagement and...

Nenad Nicevski | Mar 5, 2025 |

Unable to view Optimizely Forms submissions when some values are too long

I discovered a form where the form submissions could not be viewed in the Optimizely UI, only downloaded. Learn how to fix the issue.

Tomas Hensrud Gulla | Mar 4, 2025 |

CMS 12 DXP Migrations - Time Zones

When it comes to migrating a project from CMS 11 and .NET Framework on the DXP to CMS 12 and .NET Core one thing you need to be aware of is the...

Scott Reed | Mar 4, 2025