World is now on Opti ID! Learn more

Stephan Lonntorp
Dec 7, 2017
  771
(0 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

Please login to comment.
Latest blogs
Make Global Assets Site- and Language-Aware at Indexing Time

I had a support case the other day with a question around search on global assets on a multisite. This is the result of that investigation. This co...

dada | Jun 26, 2025

The remote server returned an error: (400) Bad Request – when configuring Azure Storage for an older Optimizely CMS site

How to fix a strange issue that occurred when I moved editor-uploaded files for some old Optimizely CMS 11 solutions to Azure Storage.

Tomas Hensrud Gulla | Jun 26, 2025 |

Enable Opal AI for your Optimizely products

Learn how to enable Opal AI, and meet your infinite workforce.

Tomas Hensrud Gulla | Jun 25, 2025 |

Deploying to Optimizely Frontend Hosting: A Practical Guide

Optimizely Frontend Hosting is a cloud-based solution for deploying headless frontend applications - currently supporting only Next.js projects. It...

Szymon Uryga | Jun 25, 2025

World on Opti ID

We're excited to announce that world.optimizely.com is now integrated with Opti ID! What does this mean for you? New Users:  You can now log in wit...

Patrick Lam | Jun 22, 2025

Avoid Scandinavian Letters in File Names in Optimizely CMS

Discover how Scandinavian letters in file names can break media in Optimizely CMS—and learn a simple code fix to automatically sanitize uploads for...

Henning Sjørbotten | Jun 19, 2025 |