Copied to clipboard

Flag this post as spam?

This post will be reported to the moderators as potential spam to be looked at


  • Brett Fullam 119 posts 629 karma points
    Jun 06, 2017 @ 13:50
    Brett Fullam
    0

    HELP! Erros in the back office ...? The CMS interface layout is broken!?

    Wow ... I have a real problem on my hands. For some odd reason the back office is behaving strangely ... after navigating through the back office between a doc type and a partial type the back office layout and styles BREAK?

    Any idea WHY this is happening ...? Looking at the console in Google Chrome there seems to be an error:

    DependencyHandler.axd?s=L3VtYnJhY28vbGliL2pxdWVyeS9qcXVlcnkubWluLmpzOy91bWJyYWNvL2xpYi9hbmd1bGFyLzE…:8 TypeError: element.datetimepicker is not a function
        at DependencyHandler.axd?s=L3VtYnJhY28vbGliL2pxdWVyeS9qcXVlcnkubWluLmpzOy91bWJyYWNvL2xpYi9hbmd1bGFyLzE…:2153
        at i (DependencyHandler.axd?s=L3VtYnJhY28vbGliL2pxdWVyeS9qcXVlcnkubWluLmpzOy91bWJyYWNvL2xpYi9hbmd1bGFyLzE…:10)
        at DependencyHandler.axd?s=L3VtYnJhY28vbGliL2pxdWVyeS9qcXVlcnkubWluLmpzOy91bWJyYWNvL2xpYi9hbmd1bGFyLzE…:10
        at Object.$eval (DependencyHandler.axd?s=L3VtYnJhY28vbGliL2pxdWVyeS9qcXVlcnkubWluLmpzOy91bWJyYWNvL2xpYi9hbmd1bGFyLzE…:10)
        at Object.$digest (DependencyHandler.axd?s=L3VtYnJhY28vbGliL2pxdWVyeS9qcXVlcnkubWluLmpzOy91bWJyYWNvL2xpYi9hbmd1bGFyLzE…:10)
        at a.$apply (DependencyHandler.axd?s=L3VtYnJhY28vbGliL2pxdWVyeS9qcXVlcnkubWluLmpzOy91bWJyYWNvL2xpYi9hbmd1bGFyLzE…:10)
        at Object.safeApply (DependencyHandler.axd?s=L3VtYnJhY28vbGliL2pxdWVyeS9qcXVlcnkubWluLmpzOy91bWJyYWNvL2xpYi9hbmd1bGFyLzE…:798)
        at DependencyHandler.axd?s=L3VtYnJhY28vbGliL2pxdWVyeS9qcXVlcnkubWluLmpzOy91bWJyYWNvL2xpYi9hbmd1bGFyLzE…:819
        at finish (lazyload.js:108)
        at HTMLScriptElement._finish (lazyload.js:162) 
    

    I just tried to reproduce the error again and this appeared in the console (with more specific info):

    TypeError: element.datetimepicker is not a function
        at umbraco/js/umbraco.controllers.js?cdv=71880264:12571
        at i (umbraco/lib/angular/1.1.5/angular.min.js?cdv=71880264:79)
        at umbraco/lib/angular/1.1.5/angular.min.js?cdv=71880264:80
        at Object.$eval (umbraco/lib/angular/1.1.5/angular.min.js?cdv=71880264:92)
        at Object.$digest (umbraco/lib/angular/1.1.5/angular.min.js?cdv=71880264:90)
        at a.$apply (umbraco/lib/angular/1.1.5/angular.min.js?cdv=71880264:92)
        at Object.safeApply (umbraco/js/umbraco.services.js?cdv=71880264:58)
        at umbraco/js/umbraco.services.js?cdv=71880264:714
        at finish (lazyload.js:108)
        at HTMLScriptElement._finish (lazyload.js:162)
    

    Here's a screen shot of the broken back office interface:

    enter image description here

  • Brett Fullam 119 posts 629 karma points
    Jun 06, 2017 @ 15:12
    Brett Fullam
    100

    OK ... I'm marking this as "solved" to take it off of everybody's radar ... I just took the hit and rolled it back a couple of commits to resolve it.

    I have no idea why that happened, but THIS is why you use version control. Luckily there were a couple of commits with light edits that pre-dated the error. I still have no idea as to why that happened though.

    I was working on adding pagination to a news section ... working first with PagedList.Mvc, but later tried x.PagedList.Mvc since the author of the previous package had commented that he was no longer maintaining it.

    I can only imagine that this occured during the installation and/or removal of either of these packages.

    SO ... crisis averted ... I'm back on track thanks to a few reverted commits via git.

Please Sign in or register to post replies

Write your reply to:

Draft