Magento 2.1 js errors break backend - wrong paths in magento-ui?












2

















// EDIT:




This error was caused by the Firebug extension in Firefox.



I would recommend anyone that uses this ext to disable and remove it
immediately!






From a fresh composer setup, I receive a lot of js errors in both the backend and frontend. In the backend this actually breaks the navigation, does not load the products or order grid, so pretty much completely breaks the backend.



I tried 2.1.0 and 2.1.1, both seem to have the exact same issues. 2.0.7 did not have these issues. No extra modules installed, just a clean, fresh composer setup. I tried deleting cache dirs and re-deploying the static-content, making sure the user and file permissions are correct, but the missing files are never generated. The browser cache was flushed and pages force reloaded:



BE errors:



404 Not Found:



/pub/static/adminhtml/Magento/backend/en_US/Magento_Ui/js/lib/registry/bindings.js
/pub/static/adminhtml/Magento/backend/en_US/Magento_Ui/js/lib/registry/dom-observer.js


and sometimes:



/pub/static/adminhtml/Magento/backend/template/renderer.js


JS:



TypeError: ko is undefined (knockout-es5.js (line 428, col 5))
ko.track = track;

TypeError: utils.extend is not a function (class.js (line 129, col 30))
child.defaults = utils.extend({}, parent.defaults || {});


These .js files are never even created in the above path in the magento-ui.



enter image description here



instead I think the files now reside in js/lib/view/utils/ instead of js/lib/registry/. So the error may be in the Magento magento/module-ui version 100.1.0.



enter image description here



FrontEnd:



404 errors:



/pub/static/frontend/Magento/luma/en_US/Magento_Ui/js/lib/registry/bindings.js
/pub/static/frontend/Magento/luma/en_US/Magento_Ui/js/lib/registry/dom-observer.js


However, the FE errors dissapear after a few reloads, sometimes at least?



other error is the same as in the BE:



TypeError: utils.extend is not a function ( class.js (line 129, col 30) )
child.defaults = utils.extend({}, parent.defaults || {});


I have not been able to find any bug reports on this and no fixes.



Test System:




  • Docker container Debian 8

  • Server version: Apache/2.4.10 (Debian)

  • PHP 5.6.24

  • MySQL Community Server 5.6.32










share|improve this question
















bumped to the homepage by Community 11 mins ago


This question has answers that may be good or bad; the system has marked it active so that they can be reviewed.
















  • Did you try to deploy the static content?

    – Muk
    Sep 6 '16 at 9:47











  • Yes, as mentioned above: " I tried deleting cache dirs and re-deploying the static-content, making sure the user and file permissions are correct"

    – tecjam
    Sep 6 '16 at 9:52











  • Please try once to redepoly static content after removing everything, except .htaccess file from pub/static folder.

    – Muk
    Sep 6 '16 at 10:01











  • Did that, checked the file owner (all still the same as the rest of the files) and the missing files are not generated in the folder. Backend grids still do not load. Version 2.0.7 has no such issues.

    – tecjam
    Sep 6 '16 at 12:13













  • @tecjam put your comment as an answer this is the firebug issue if you are running firefox version > 50 then you have to disable the firebug same thing causing me issue

    – Murtuza Zabuawala
    Nov 3 '17 at 5:36
















2

















// EDIT:




This error was caused by the Firebug extension in Firefox.



I would recommend anyone that uses this ext to disable and remove it
immediately!






From a fresh composer setup, I receive a lot of js errors in both the backend and frontend. In the backend this actually breaks the navigation, does not load the products or order grid, so pretty much completely breaks the backend.



I tried 2.1.0 and 2.1.1, both seem to have the exact same issues. 2.0.7 did not have these issues. No extra modules installed, just a clean, fresh composer setup. I tried deleting cache dirs and re-deploying the static-content, making sure the user and file permissions are correct, but the missing files are never generated. The browser cache was flushed and pages force reloaded:



BE errors:



404 Not Found:



/pub/static/adminhtml/Magento/backend/en_US/Magento_Ui/js/lib/registry/bindings.js
/pub/static/adminhtml/Magento/backend/en_US/Magento_Ui/js/lib/registry/dom-observer.js


and sometimes:



/pub/static/adminhtml/Magento/backend/template/renderer.js


JS:



TypeError: ko is undefined (knockout-es5.js (line 428, col 5))
ko.track = track;

TypeError: utils.extend is not a function (class.js (line 129, col 30))
child.defaults = utils.extend({}, parent.defaults || {});


These .js files are never even created in the above path in the magento-ui.



enter image description here



instead I think the files now reside in js/lib/view/utils/ instead of js/lib/registry/. So the error may be in the Magento magento/module-ui version 100.1.0.



enter image description here



FrontEnd:



404 errors:



/pub/static/frontend/Magento/luma/en_US/Magento_Ui/js/lib/registry/bindings.js
/pub/static/frontend/Magento/luma/en_US/Magento_Ui/js/lib/registry/dom-observer.js


However, the FE errors dissapear after a few reloads, sometimes at least?



other error is the same as in the BE:



TypeError: utils.extend is not a function ( class.js (line 129, col 30) )
child.defaults = utils.extend({}, parent.defaults || {});


I have not been able to find any bug reports on this and no fixes.



Test System:




  • Docker container Debian 8

  • Server version: Apache/2.4.10 (Debian)

  • PHP 5.6.24

  • MySQL Community Server 5.6.32










share|improve this question
















bumped to the homepage by Community 11 mins ago


This question has answers that may be good or bad; the system has marked it active so that they can be reviewed.
















  • Did you try to deploy the static content?

    – Muk
    Sep 6 '16 at 9:47











  • Yes, as mentioned above: " I tried deleting cache dirs and re-deploying the static-content, making sure the user and file permissions are correct"

    – tecjam
    Sep 6 '16 at 9:52











  • Please try once to redepoly static content after removing everything, except .htaccess file from pub/static folder.

    – Muk
    Sep 6 '16 at 10:01











  • Did that, checked the file owner (all still the same as the rest of the files) and the missing files are not generated in the folder. Backend grids still do not load. Version 2.0.7 has no such issues.

    – tecjam
    Sep 6 '16 at 12:13













  • @tecjam put your comment as an answer this is the firebug issue if you are running firefox version > 50 then you have to disable the firebug same thing causing me issue

    – Murtuza Zabuawala
    Nov 3 '17 at 5:36














2












2








2










// EDIT:




This error was caused by the Firebug extension in Firefox.



I would recommend anyone that uses this ext to disable and remove it
immediately!






From a fresh composer setup, I receive a lot of js errors in both the backend and frontend. In the backend this actually breaks the navigation, does not load the products or order grid, so pretty much completely breaks the backend.



I tried 2.1.0 and 2.1.1, both seem to have the exact same issues. 2.0.7 did not have these issues. No extra modules installed, just a clean, fresh composer setup. I tried deleting cache dirs and re-deploying the static-content, making sure the user and file permissions are correct, but the missing files are never generated. The browser cache was flushed and pages force reloaded:



BE errors:



404 Not Found:



/pub/static/adminhtml/Magento/backend/en_US/Magento_Ui/js/lib/registry/bindings.js
/pub/static/adminhtml/Magento/backend/en_US/Magento_Ui/js/lib/registry/dom-observer.js


and sometimes:



/pub/static/adminhtml/Magento/backend/template/renderer.js


JS:



TypeError: ko is undefined (knockout-es5.js (line 428, col 5))
ko.track = track;

TypeError: utils.extend is not a function (class.js (line 129, col 30))
child.defaults = utils.extend({}, parent.defaults || {});


These .js files are never even created in the above path in the magento-ui.



enter image description here



instead I think the files now reside in js/lib/view/utils/ instead of js/lib/registry/. So the error may be in the Magento magento/module-ui version 100.1.0.



enter image description here



FrontEnd:



404 errors:



/pub/static/frontend/Magento/luma/en_US/Magento_Ui/js/lib/registry/bindings.js
/pub/static/frontend/Magento/luma/en_US/Magento_Ui/js/lib/registry/dom-observer.js


However, the FE errors dissapear after a few reloads, sometimes at least?



other error is the same as in the BE:



TypeError: utils.extend is not a function ( class.js (line 129, col 30) )
child.defaults = utils.extend({}, parent.defaults || {});


I have not been able to find any bug reports on this and no fixes.



Test System:




  • Docker container Debian 8

  • Server version: Apache/2.4.10 (Debian)

  • PHP 5.6.24

  • MySQL Community Server 5.6.32










share|improve this question


















// EDIT:




This error was caused by the Firebug extension in Firefox.



I would recommend anyone that uses this ext to disable and remove it
immediately!






From a fresh composer setup, I receive a lot of js errors in both the backend and frontend. In the backend this actually breaks the navigation, does not load the products or order grid, so pretty much completely breaks the backend.



I tried 2.1.0 and 2.1.1, both seem to have the exact same issues. 2.0.7 did not have these issues. No extra modules installed, just a clean, fresh composer setup. I tried deleting cache dirs and re-deploying the static-content, making sure the user and file permissions are correct, but the missing files are never generated. The browser cache was flushed and pages force reloaded:



BE errors:



404 Not Found:



/pub/static/adminhtml/Magento/backend/en_US/Magento_Ui/js/lib/registry/bindings.js
/pub/static/adminhtml/Magento/backend/en_US/Magento_Ui/js/lib/registry/dom-observer.js


and sometimes:



/pub/static/adminhtml/Magento/backend/template/renderer.js


JS:



TypeError: ko is undefined (knockout-es5.js (line 428, col 5))
ko.track = track;

TypeError: utils.extend is not a function (class.js (line 129, col 30))
child.defaults = utils.extend({}, parent.defaults || {});


These .js files are never even created in the above path in the magento-ui.



enter image description here



instead I think the files now reside in js/lib/view/utils/ instead of js/lib/registry/. So the error may be in the Magento magento/module-ui version 100.1.0.



enter image description here



FrontEnd:



404 errors:



/pub/static/frontend/Magento/luma/en_US/Magento_Ui/js/lib/registry/bindings.js
/pub/static/frontend/Magento/luma/en_US/Magento_Ui/js/lib/registry/dom-observer.js


However, the FE errors dissapear after a few reloads, sometimes at least?



other error is the same as in the BE:



TypeError: utils.extend is not a function ( class.js (line 129, col 30) )
child.defaults = utils.extend({}, parent.defaults || {});


I have not been able to find any bug reports on this and no fixes.



Test System:




  • Docker container Debian 8

  • Server version: Apache/2.4.10 (Debian)

  • PHP 5.6.24

  • MySQL Community Server 5.6.32







magento2






share|improve this question















share|improve this question













share|improve this question




share|improve this question








edited Nov 3 '17 at 6:30









Teja Bhagavan Kollepara

3,01141949




3,01141949










asked Sep 6 '16 at 9:27









tecjamtecjam

2,75221540




2,75221540





bumped to the homepage by Community 11 mins ago


This question has answers that may be good or bad; the system has marked it active so that they can be reviewed.







bumped to the homepage by Community 11 mins ago


This question has answers that may be good or bad; the system has marked it active so that they can be reviewed.















  • Did you try to deploy the static content?

    – Muk
    Sep 6 '16 at 9:47











  • Yes, as mentioned above: " I tried deleting cache dirs and re-deploying the static-content, making sure the user and file permissions are correct"

    – tecjam
    Sep 6 '16 at 9:52











  • Please try once to redepoly static content after removing everything, except .htaccess file from pub/static folder.

    – Muk
    Sep 6 '16 at 10:01











  • Did that, checked the file owner (all still the same as the rest of the files) and the missing files are not generated in the folder. Backend grids still do not load. Version 2.0.7 has no such issues.

    – tecjam
    Sep 6 '16 at 12:13













  • @tecjam put your comment as an answer this is the firebug issue if you are running firefox version > 50 then you have to disable the firebug same thing causing me issue

    – Murtuza Zabuawala
    Nov 3 '17 at 5:36



















  • Did you try to deploy the static content?

    – Muk
    Sep 6 '16 at 9:47











  • Yes, as mentioned above: " I tried deleting cache dirs and re-deploying the static-content, making sure the user and file permissions are correct"

    – tecjam
    Sep 6 '16 at 9:52











  • Please try once to redepoly static content after removing everything, except .htaccess file from pub/static folder.

    – Muk
    Sep 6 '16 at 10:01











  • Did that, checked the file owner (all still the same as the rest of the files) and the missing files are not generated in the folder. Backend grids still do not load. Version 2.0.7 has no such issues.

    – tecjam
    Sep 6 '16 at 12:13













  • @tecjam put your comment as an answer this is the firebug issue if you are running firefox version > 50 then you have to disable the firebug same thing causing me issue

    – Murtuza Zabuawala
    Nov 3 '17 at 5:36

















Did you try to deploy the static content?

– Muk
Sep 6 '16 at 9:47





Did you try to deploy the static content?

– Muk
Sep 6 '16 at 9:47













Yes, as mentioned above: " I tried deleting cache dirs and re-deploying the static-content, making sure the user and file permissions are correct"

– tecjam
Sep 6 '16 at 9:52





Yes, as mentioned above: " I tried deleting cache dirs and re-deploying the static-content, making sure the user and file permissions are correct"

– tecjam
Sep 6 '16 at 9:52













Please try once to redepoly static content after removing everything, except .htaccess file from pub/static folder.

– Muk
Sep 6 '16 at 10:01





Please try once to redepoly static content after removing everything, except .htaccess file from pub/static folder.

– Muk
Sep 6 '16 at 10:01













Did that, checked the file owner (all still the same as the rest of the files) and the missing files are not generated in the folder. Backend grids still do not load. Version 2.0.7 has no such issues.

– tecjam
Sep 6 '16 at 12:13







Did that, checked the file owner (all still the same as the rest of the files) and the missing files are not generated in the folder. Backend grids still do not load. Version 2.0.7 has no such issues.

– tecjam
Sep 6 '16 at 12:13















@tecjam put your comment as an answer this is the firebug issue if you are running firefox version > 50 then you have to disable the firebug same thing causing me issue

– Murtuza Zabuawala
Nov 3 '17 at 5:36





@tecjam put your comment as an answer this is the firebug issue if you are running firefox version > 50 then you have to disable the firebug same thing causing me issue

– Murtuza Zabuawala
Nov 3 '17 at 5:36










1 Answer
1






active

oldest

votes


















0














The issue is a problem with the Firefox Firebug add-on.
If you still use it, you should disable it and use the Firefox devtools.



Firebug has officially been deprecated.



Please see: https://getfirebug.com/






share|improve this answer























    Your Answer








    StackExchange.ready(function() {
    var channelOptions = {
    tags: "".split(" "),
    id: "479"
    };
    initTagRenderer("".split(" "), "".split(" "), channelOptions);

    StackExchange.using("externalEditor", function() {
    // Have to fire editor after snippets, if snippets enabled
    if (StackExchange.settings.snippets.snippetsEnabled) {
    StackExchange.using("snippets", function() {
    createEditor();
    });
    }
    else {
    createEditor();
    }
    });

    function createEditor() {
    StackExchange.prepareEditor({
    heartbeatType: 'answer',
    autoActivateHeartbeat: false,
    convertImagesToLinks: false,
    noModals: true,
    showLowRepImageUploadWarning: true,
    reputationToPostImages: null,
    bindNavPrevention: true,
    postfix: "",
    imageUploader: {
    brandingHtml: "Powered by u003ca class="icon-imgur-white" href="https://imgur.com/"u003eu003c/au003e",
    contentPolicyHtml: "User contributions licensed under u003ca href="https://creativecommons.org/licenses/by-sa/3.0/"u003ecc by-sa 3.0 with attribution requiredu003c/au003e u003ca href="https://stackoverflow.com/legal/content-policy"u003e(content policy)u003c/au003e",
    allowUrls: true
    },
    onDemand: true,
    discardSelector: ".discard-answer"
    ,immediatelyShowMarkdownHelp:true
    });


    }
    });














    draft saved

    draft discarded


















    StackExchange.ready(
    function () {
    StackExchange.openid.initPostLogin('.new-post-login', 'https%3a%2f%2fmagento.stackexchange.com%2fquestions%2f134908%2fmagento-2-1-js-errors-break-backend-wrong-paths-in-magento-ui%23new-answer', 'question_page');
    }
    );

    Post as a guest















    Required, but never shown

























    1 Answer
    1






    active

    oldest

    votes








    1 Answer
    1






    active

    oldest

    votes









    active

    oldest

    votes






    active

    oldest

    votes









    0














    The issue is a problem with the Firefox Firebug add-on.
    If you still use it, you should disable it and use the Firefox devtools.



    Firebug has officially been deprecated.



    Please see: https://getfirebug.com/






    share|improve this answer




























      0














      The issue is a problem with the Firefox Firebug add-on.
      If you still use it, you should disable it and use the Firefox devtools.



      Firebug has officially been deprecated.



      Please see: https://getfirebug.com/






      share|improve this answer


























        0












        0








        0







        The issue is a problem with the Firefox Firebug add-on.
        If you still use it, you should disable it and use the Firefox devtools.



        Firebug has officially been deprecated.



        Please see: https://getfirebug.com/






        share|improve this answer













        The issue is a problem with the Firefox Firebug add-on.
        If you still use it, you should disable it and use the Firefox devtools.



        Firebug has officially been deprecated.



        Please see: https://getfirebug.com/







        share|improve this answer












        share|improve this answer



        share|improve this answer










        answered Nov 21 '17 at 12:51









        tecjamtecjam

        2,75221540




        2,75221540






























            draft saved

            draft discarded




















































            Thanks for contributing an answer to Magento Stack Exchange!


            • Please be sure to answer the question. Provide details and share your research!

            But avoid



            • Asking for help, clarification, or responding to other answers.

            • Making statements based on opinion; back them up with references or personal experience.


            To learn more, see our tips on writing great answers.




            draft saved


            draft discarded














            StackExchange.ready(
            function () {
            StackExchange.openid.initPostLogin('.new-post-login', 'https%3a%2f%2fmagento.stackexchange.com%2fquestions%2f134908%2fmagento-2-1-js-errors-break-backend-wrong-paths-in-magento-ui%23new-answer', 'question_page');
            }
            );

            Post as a guest















            Required, but never shown





















































            Required, but never shown














            Required, but never shown












            Required, but never shown







            Required, but never shown

































            Required, but never shown














            Required, but never shown












            Required, but never shown







            Required, but never shown







            Popular posts from this blog

            What other Star Trek series did the main TNG cast show up in?

            Berlina muro

            Berlina aerponto