Stephan Lonntorp
Dec 7, 2017
  2433
(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
Accelerating Optimizely CMS and Commerce upgrades with agentic AI (Part 1 of 2)

How Niteco's Upgrade Machine   uses orchestrated AI coding agents to deliver a buildable baseline and a running CMS, then hands over for...

Hung Le Hoang | May 11, 2026

Commerce 15 and CMS 13: Optimizely’s Next Step Toward AI-Powered, Graph-First Commerce

Optimizely is preparing to release Commerce 15 in mid-May 2026 , positioning this as a foundational shift—not just an upgrade. The direction is...

Augusto Davalos | May 7, 2026

The future of Content: Introducing Optimizely CMS 13

Optimizely In the rapidly evolving landscape of digital experience, the "monolithic vs. headless" debate is being replaced by a more sophisticated...

Aniket | May 6, 2026

Hide built in scheduled job from the admin UI

Ok so this probably goes into the not so useful section but late last night I got a veery strong feeling that all projects I am  involved with have...

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

Optimizely CMS 11 Is Out of Support — and the Hard Part of the Upgrade Isn't the CMS

On 10 April 2026, Optimizely formally announced that CMS 11 was out of support — CMS 13 had reached GA on 31 March, and by policy only the two most...

Allan Thraen | May 6, 2026 |

Optimizely SaaS CMS Developer Certification Exam

The Optimizely SaaS CMS Developer Certification is an industry-recognized credential for developers and architects who build scalable, composable...

Megha Rathore | May 5, 2026