Stephan Lonntorp
Dec 7, 2017
  2390
(6 votes)

All I want for christmas is updated addons and an automated approval process.

Today I decided to make a little effort in getting things ready for the inevitable CMS 11 upgrade storm. Eventually, we'll be asked to upgrade our client sites to the latest and greates version of EPiServer. This process usually goeas a little something like this:

  1. Upgrade site
  2. Fix compilation errors
  3. Identify obsoleted methods
  4. Find out how to do it the new way
  5. Do it the new way
  6. Huge sigh of relief for your code not being nearly as broken as you thought it was going to be.
  7. Stop everything because an add-on you're using hasn't been upgraded yet.

This time around, EPiServer has been fast to fix things, but there are still a few things missing.

I have taken the time to ensure that the FocalPoint and URL Transliteration plugins are updated accordingly, beacuse we use them in quite a few projects.

I just submitted a PR to get PowerSlice up to speed, being that PowerSlice is open source.

OK, so why the blog post?

Well, a small part is obviously self promotion, (hi mom!), but mostly it's because I feel that the workflow for submitting updated nuget packages is broken.

I get how PR's will take time to process, but the packages I manage could easily be deployed via the NuGet API, instead of being manually processed. I think that we as a developer community should speak up about what we need, and this is my way of doing just that.

So, as soon as someone at EPiServer has approved the aforementioned packages and PR, I will have done my part in getting us all one step closer to upgrading all our sites.

Also, Alans automated IFTTT script will tweet this, and that will make for a funny tweet.

Merry X-Mas!

Dec 07, 2017

Comments

valdis
valdis Dec 7, 2017 03:12 PM

veri gut ;)

Please login to comment.
Latest blogs
Optimizely CMS 13: Why Search & Navigation Now Means Graph Migration

Optimizely CMS 13 makes Graph a required part of the platform. Here is what that means in practice for teams moving from Search & Navigation, with ...

Wojciech Seweryn | Apr 8, 2026 |

Jhoose Security Module V3.0.0 – Site-Level Security Configuration for Optimizely

Jhoose Security Module updated for Optimizely CMS 13, introducing separate packages for CMS 12 and 13 with ongoing support and enhancements.

Andrew Markham | Apr 6, 2026 |

Searchable settings page

In my current project which has been actively developed for quite some time we have a big classic settings page. Unfortunately the placement and...

Per Nergård (MVP) | Apr 6, 2026

Using Azure Devops Pipelines in Optimizely SAAS (Configured) Commerce

Introduction When working with SAAS Commerce build service v2 your currently need to use a github repo with configured branches to start deployment...

Mark Hall | Apr 4, 2026 |