Known issues after EPiServer Commerce 7.5 upgrade

After upgrading an EPiServer Commerce solution from version 6 R3 to 7.5, we came across some issues that quickly becomes time consuming if you are not aware of them.

Read about the issues and learn how to get around them by visiting the blog post on our company blog: http://geta.no/blogg/known-issues-after-episerver-commerce-7.5-upgrade/

Jun 25, 2014

Comments

error Please login to comment.

You’re not headless. You’re hybrid — and that’s the CMS 12 default.

For CMS 12 / Commerce teams with a React (or similar) storefront who keep hearing “just go headless” or “just move to Graph.” This is Part 1 of Fin...

Hanskumar Tripathi | Aug 13, 2026

Stott Security for Optimizely SaaS CMS

Introduction Stott Security has been helping developers and editors manage Content Security Policies and security headers on Optimizely PaaS CMS...

Mark Stott | Aug 13, 2026

Optimizely XML Resource Builder: A Visual Studio Extension for Language Resource Files

Anyone who has worked on a larger Optimizely solution will know the feeling. You add or update a page type, block type, or shared base class,

Adnan Zameer | Aug 13, 2026 |

Optimizely SaaS CMS Management API: The Write Side of Headless

Everything I’ve written in this series so far has been about reading content — Optimizely Graph, webhooks, ISR, caching layers. But at some point y...

Kiran Patil | Aug 12, 2026 |

See all blogs