Take the community feedback survey now.

Daniel Ovaska
Feb 14, 2020
  59
(0 votes)

Fix problems with edit mode

Episerver edit mode normally works great. But sometimes a developer manages to crash it.  I'll go through the most common issues you can check for to make it work again

  1. WebSockets not enabled on IIS
    Easy to fix by adding the feature to IIS. If you forget this you will get a warning in edit mode and some newer functionality like support for projects won't work. 


  2. Parts of the nuget package for edit mode was lost along the way
    Double check that you have the relevant zip files below modules on the server. Sometimes that get lost in the deploy process somewhere.

    If they don't exist on your development environment, reinstall the relevant nuget packages.
  3. Make sure edit mode hasn't been removed
    Sometimes you do this if you have a separate editor server. It can look similar to this in webconfig. Notice that the allow tag has been removed. Common symphoms are that you get a 404 or 403 after logging in. 
  4. Custom properties
    If edit mode doesn't work properly or goes blank for some content types, check in admin mode if there are some custom properties on them. Try removing them in development environment to see if that is what causes the issue. Remove old properties that isn't used anymore on that content type.

  5. Check edit mode for js errors
    Use Chrome developer tools or similar and check console. This can give you a good hint what isn't working. Often custom properties like above.

  6. PropertyList and Url properties can't be saved
    A common problem if you add a Url property to a property list is that you forget to handle the json transformation properly. Add some attributes to handle the Url property correctly. If you don't, saving the property list won't work correctly. 
    [JsonProperty]
    [JsonConverter(typeof(UrlConverter))]
    [Display(Name = "Link1", Order = 200)]
    public virtual Url UrlLink { get; set; }
    ​

    Hope that helps someone with troubleshooting if edit mode gives you a hard time. 

    Happy coding!

    PS If you blog and use web[dot]config somewhere in your blog, cloudflare will block you from creating that blog. DS

Feb 14, 2020

Comments

Please login to comment.
Latest blogs
A day in the life of an Optimizely OMVP - Opticon London 2025

This installment of a day in the life of an Optimizely OMVP gives an in-depth coverage of my trip down to London to attend Opticon London 2025 held...

Graham Carr | Oct 2, 2025

Optimizely Web Experimentation Using Real-Time Segments: A Step-by-Step Guide

  Introduction Personalization has become de facto standard for any digital channel to improve the user's engagement KPI’s.  Personalization uses...

Ratish | Oct 1, 2025 |

Trigger DXP Warmup Locally to Catch Bugs & Performance Issues Early

Here’s our documentation on warmup in DXP : 🔗 https://docs.developers.optimizely.com/digital-experience-platform/docs/warming-up-sites What I didn...

dada | Sep 29, 2025

Creating Opal Tools for Stott Robots Handler

This summer, the Netcel Development team and I took part in Optimizely’s Opal Hackathon. The challenge from Optimizely was to extend Opal’s abiliti...

Mark Stott | Sep 28, 2025

Integrating Commerce Search v3 (Vertex AI) with Optimizely Configured Commerce

Introduction This blog provides a technical guide for integrating Commerce Search v3, which leverages Google Cloud's Vertex AI Search, into an...

Vaibhav | Sep 27, 2025

A day in the life of an Optimizely MVP - Opti Graph Extensions add-on v1.0.0 released

I am pleased to announce that the official v1.0.0 of the Opti Graph Extensions add-on has now been released and is generally available. Refer to my...

Graham Carr | Sep 25, 2025