Daniel Ovaska
Feb 14, 2020
  4780
(3 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
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