In this blog post I'll show you one way of extending Episerver's On Page Editing view, by automatically setting image caption and alt text properties on a page based on the image content that the editor selects.

Just wanted to share a custom Epi Commerce hierarchical router that I'm using in a project where we have a Product -> Variant structure. All variants in the catalog belong to a product and a product can have one or multiple variants.

Have you ever wanted to index a content item in Find without having to publish a meaningless change to it? Or index an entire content tree from a specific starting point? Maybe you want to force an item into the index even though it's excluded by conventions? Just install Geta.Epi.IndexContentInFind package and it will be easy to do just that.

By default, Episerver supports only WebForms views for its modules. We have created a package which adds support for Razor views too.

For quite a long time I've been wondering if Episerver is going to do anything about the built-in category functionality. I feel it's pretty outdated and it's not so convenient to edit and localize categories. I guess the teams at Episerver are busy with other, more important stuff, so I decided to create a module. Say hello to Geta.EpiCategories.

You might already know about our Episerver extensions package, Geta.Epi.Extensions. We have now added a set of extensions and HTML helpers to help improve user experience for content editors. The goal with the helpers is to reduce the need for "All properties view" in the Episerver edit interface.

I don't know about you, but at least for me, I rarely create image thumbnails for the different content types in the solutions I am working on. If you are like me, then this package will hopefully give your editors a somewhat more pleasant user experience when creating content.

When you are working on several inRiver PIM projects simultaneously, you find yourself in need of switching between them from time to time. One option is to change the configuration files and restart inRiver services and website. A better option is have multiple instances of inRiver PIM running on the same system. This way you can easily access the desired instance for configurations, developing and demos. This is a walk-through on how to set up multiple instances of inRiver PIM on the same system.

Let's say you have developed a site framework that you use on many different sites that contains some content types spread over various assemblies. Sooner or later, on at least one of the sites, you will want to add, hide or modify a property on a specific content type. You could create a new content type that inherits the original and then hide the original. No thanks. Let's do it better than that.

This data feed will allow you to easily share your e-commerce sites product data with Google Shopping and other channels. At Geta we've used it for quite a few 3rd party integrations.

Recently I helped out investigating an issue where the search result from Find contained non-published and deleted pages. The site in question had a search page that fetched results from two separate Find indexes.

The popular Episerver Languages addon has added supported for exporting and importing content using the widely supported XLIFF format.

Extending the Episerver global menu is easy. You can add menu sections and sub-menu items such as menu sections, drop-downs, URLs and pop-up menu items. In this short blog post I will demonstrate how you can keep your menu context while navigating between several MVC actions.

Sometimes when developing Episerver solutions you find the need to extend the behaviour of already existing property editors. In this blog post I will briefly describe how I extended the built-in content selector with direct upload functionality using drag and drop. This way you don’t have to create your "Media"-items before being able to select them. You can just upload them directly to the property editor and they will be added to the assets folder of the content you are working on and selected automatically.

The other day I had to deal with a mysterious error with the Episerver Shell search function. You know the little search icon to the right in the dashboard drop-down menu. When I clicked it nothing happened. I looked at the request in developer toolbar, discovered the exception and this is how I fixed it.

From time to time I get asked; 'How can I retrieve all parent catalog nodes for a product in Episerver Commerce?' Achieving this using the current version of Episerver commerce API is a bit cumbersome. Luckily Episerver is working on a relation overhaul for the next major version of Commerce, but until then I'll provide some sample code that does the trick.

EPiServer released Service API some time ago but it was missing an API for Customers, Carts and Order. We have now released additional Service API endpoints for this Commerce functionality.

This is an example of a custom content area renderer that automatically wraps blocks in container and row <div> tags and also has support for non wrapped hero blocks.

When working with advanced e-commerce solutions as a developer or consultant you quickly get introduced to the acronym PIM: Product Information Management. What is it and why would you want one as part of your Episerver e-commerce project?