Slow tree

Daniel Sandberg
Member since: 2012
 

The left tree structure in CMS->Edit does not seem to trigger any event when clicking on a page. On our production server it works ok, but on a less powerful server we sometimes need to refresh the browser to get the page to load. Has anyone experience this? Surfing on the site works perfectly fine, and there is no problem with load times.

Please help!

#189609 Mar 21, 2018 12:44
  • Drew Null
    Member since: 2013
     

    In my experience this usually means that I have some server-side code that is taking waaay too long to execute, even if the live site looks okay. 

    What happens when you click blocks or media -- do those load up okay? 

    Have you checked your browser console for any JavaScript errors? I would try it in a fresh incognito window just to rule out any corrupt client side assets. 

    #190600 Apr 12, 2018 15:09
  • Daniel Sandberg
    Member since: 2012
     

    Hi Drew,

    thanks for your input! I will definitly check that out. 

    #190618 Apr 13, 2018 8:49
  • Daniel Sandberg
    Member since: 2012
     

    I do not find any console errors. Strange thing is that sometimes everything loads fast, and sometimes I have to reload the page to be able to navigate.

    #190619 Apr 13, 2018 9:30
  • Drew Null
    Member since: 2013
     

    As a troubleshooting step, I would set up a blank page type, add it to a start page, and see if CMS Edit loads slowly. That way you can start to narrow down whether it is a CMS Edit problem or a problem in your code. 

    I mean completely blank, like this... 

    namespace Example
    {
        using System.Web.Mvc;
        using EPiServer.Core;
        using EPiServer.DataAnnotations;
        using EPiServer.Web.Mvc;
    
        [ContentType(DisplayName = "Blank Page", GUID = "2874DACE-32D4-43CE-B6F2-399BB76C2204")]
        public class BlankPage : PageData
        {
    
        }
    
        public class BlankPageController : PageController<BlankPage>
        {
            public virtual ActionResult Index(BlankPage currentPage)
            {
                return this.View("~/Views/Example/BlankPage/Index.cshtml", currentPage);
            }
        }
    }
    @model Example.BlankPage
    @{
        Layout = null;
    }
    
    <!DOCTYPE html>
    
    <html>
    <head>
        <meta name="viewport" content="width=device-width" />
        <title></title>
    </head>
    <body>
        <div>
            <h1>This is a blank page!</h1>
        </div>
    </body>
    </html>
    
    #190652 Apr 13, 2018 16:24
  • Daniel Sandberg
    Member since: 2012
     

    I will add a blank page, and see if that result in a reduced load time as you prepose Drew.

    #194853 Jul 04, 2018 14:55
  • Daniel Sandberg
    Member since: 2012
     

    Could this perhaps be a cache issue?

    #194854 Jul 04, 2018 14:56
  • Daniel Sandberg
    Member since: 2012
     

    I created a blank page as suggested, and that page loads perfectly every time. Strange thing is that other pages sometimes loads fast, and sometimes not at all. Then if one page fails, others fail to, until I refresh the browser. Then all pages works again. It's like something puts a lock on everything.

    #194870 Jul 05, 2018 9:27
  • Marija Jemuovic
    Member since: 2010
     

    Hey Daniel,

    Perhaps you can install something like Prefix.io on the server and check out what happens when you click. It might give you ideas on what gets stuck. New Relic is a great tool, too, but prefix.io is free and a bit easier to install.

    BR,
    Marija

    #194914 Jul 08, 2018 15:40