How to Add Valid Elements (like iframes) to TinyMCE version 2 for Episerver

on in Episerver, TinyMCE with 0 Comments

With the breaking change release of Episerver CMS 11, the underlying functionality for TinyMCE has been moved into a separate NuGet package and updated to the next major version. One of the biggest changes with TinyMCE version 2 for Episerver, aside from the new editor based on TinyMCE v4, is that you can no longer customize the TinyMCE editor from the CMS Admin area. Now, all changes are done through code. and the way that you make these customizations have changed dramatically. So let’s look at the new way to add valid elements into TinyMCE version 2 for Episerver.

More ››

How to Add Valid Elements (like iframes) to TinyMCE in Episerver (Updated)

on in Episerver, TinyMCE with 0 Comments

A couple of years ago, I wrote a post about how to add valid elements to the TinyMCE WYSIWYG editor in Episerver 7. While the same process generally remains for newer version of Episerver, there are some small updates to my previous post that makes it much easier and quicker. In this post, I’ll show you the updated way to add valid elements to TinyMCE.

More ››

Integrating EPiServer 7 MVC and Commerce 1 R3 - Part 3: Creating an Entry Action Filter

on in Episerver, Episerver 7, Episerver MVC, Commerce 1 R3 with 0 Comments

When developing out our EPiServer 7 MVC and Commerce site, we needed to have some way to ensure that the requested Entry is valid and exists in our catalog. In our solution, since we have multiple actions in our ProductDetailPageController, we created an action filter to validate {entry} parameter in our route, instead of repeating the code for every action.

This is part of a multi-post series regarding integrating EPiServer Commerce 1 R3 with an EPiServer 7 MVC site. In this post, I’ll discuss the action filter we created to validate the requested Entry.

More ››

Integrating EPiServer 7 MVC and Commerce 1 R3 - Part 2: Routing to the Product Detail Page

on in Episerver, Episerver 7, Episerver MVC, Commerce 1 R3 with 0 Comments

Routing to the Product Detail Page is one of the most important components of our EPiServer 7 MVC and Commerce integration. The routing we create will define the primary path to the product’s information. Since we are not going to be creating page instances for each product, we need to have some way to determine which Entry should be displayed.

This is part of a multi-post series regarding integrating EPiServer Commerce 1 R3 with an EPiServer 7 MVC site. In this post, I’ll discuss the different routing methods to the Product Detail Page.

More ››

Integrating EPiServer 7 MVC and Commerce 1 R3 - Part 1: Developing the Basics

on in Episerver, Episerver 7, Episerver MVC, Commerce 1 R3 with 0 Comments

Over the last couple of months, we’ve been working on integrating EPiServer Commerce 1 R3 with an EPiServer 7 MVC site. Unfortunately, this is not the most straightforward process, as Commerce 1 R3 is not fully supported with EPiServer 7 sites using MVC. After a lot of trial and error, we’ve developed a workable solution to getting both to play nicely with each other.

This is part of a multi-post series. In this post, I’ll briefly discuss setting up the solution, then cover the basic components needed for our EPiServer 7 MVC and Commerce 1 R3 site.

More ››