Magento 2.0.7 is not creating certain files in pub/static and pub/media The Next CEO of Stack...

Ising model simulation

How can the PCs determine if an item is a phylactery?

Small nick on power cord from an electric alarm clock, and copper wiring exposed but intact

Is fine stranded wire ok for main supply line?

How can I make proper oatmeal cookies?

Plausibility of squid whales

Which Pokemon have a special animation when running with them out of their pokeball?

how one can write a nice vector parser, something that does pgfvecparse{A=B-C; D=E x F;}

Defamation due to breach of confidentiality

Is it professional to write unrelated content in an almost-empty email?

Audio Conversion With ADS1243

Why is information "lost" when it got into a black hole?

What was Carter Burke's job for "the company" in Aliens?

What happened in Rome, when the western empire "fell"?

What is the difference between "hamstring tendon" and "common hamstring tendon"?

Computationally populating tables with probability data

What day is it again?

What CSS properties can the br tag have?

Won the lottery - how do I keep the money?

What is the process for purifying your home if you believe it may have been previously used for pagan worship?

Is dried pee considered dirt?

What difference does it make using sed with/without whitespaces?

Yu-Gi-Oh cards in Python 3

Physiological effects of huge anime eyes



Magento 2.0.7 is not creating certain files in pub/static and pub/media



The Next CEO of Stack Overflowrequired error in magento2?Magento 2.0.7 After page refresh some js giving error?Adding Custom JS to Magento 2 ThemeMagento 2 require js throw errorMagento 2 Product checkout isnt loadError loading popper.js on Magento 2 Theme (require js)Issue with bootstrap 4 in magento 2Magento 2 checkout page keeps on loading.In console,$.event.props is undefined in jquery.mobile.custom.js:44:2.How to clear that?Multi website Magento store (2.2.6) 404-error on /pub/media on one storeMagento 2 Stuck on Checkout page












0















For some reason mage 2 is not creating files that seems to be needed for a proper working of the shop. For example there is a file http://dev.domain.co.uk/pub/media/catalog/productno_selection requested but a 404 is delivered because it is not there. I guess that might be a file containing the amount of items in basket since my top right corner does not state the products amount and I can't reach the basket without going directly in there via url. The top right basket doesn't let me in, stating that no products are in basket... which is wrong.



Going to that url directly delivers an empty page.



The other files missing are javascript-files that should be created by mage2 in pub/static too, it seems. For example I mapped the right filename (.js is not needed or allowed) to the left handle



'jquery_191':           'js/jquery-1.9.1.min',


Then mage2 requests the filename http://dev.domain.co.uk/pub/static/frontend/company/celo_theme/de_DE/jquery_191.js but this file does not exist.



Going to that file directly gives some mage bugs claiming that the file does not exist.



What's wrong? Why are these files not created? I think it brings certain problems to my installation.



PS: Errors in chrome console after setup:upgrade and setup:static-cache:deploy with the correct language.



Error parsing header X-XSS-Protection: 1; mode=block, 1; mode=block: expected semicolon at character position 14. The default protections will be applied.
(index):366 GET http://dev.domain.co.uk/pub/media/catalog/productno_selection 404 (Not Found)
productno_selection:1 GET http://dev.domain.co.uk/pub/media/catalog/productno_selection 404 (Not Found)
jquery-migrate.js:21 JQMIGRATE: Logging is active
require.js:1895 GET http://dev.domain.co.uk/pub/static/frontend/company/celo_theme/en_GB/jquery_191.js req.load @ require.js:1895load @ require.js:1639load @ require.js:820fetch @ require.js:810check @ require.js:840enable @ require.js:1143enable @ require.js:1511(anonymous function) @ require.js:1128(anonymous function) @ require.js:132each @ require.js:57enable @ require.js:1090init @ require.js:774(anonymous function) @ require.js:1416
require.js:166 Uncaught Error: Script error for: jquery_191
http://requirejs.org/docs/errors.html#scripterrormakeError @ require.js:166onScriptError @ require.js:1681
require.js:1895 GET http://dev.domain.co.uk/pub/static/frontend/company/celo_theme/en_GB/script_code_header.js req.load @ require.js:1895load @ require.js:1639load @ require.js:820fetch @ require.js:810check @ require.js:840enable @ require.js:1143enable @ require.js:1511(anonymous function) @ require.js:1128(anonymous function) @ require.js:132each @ require.js:57enable @ require.js:1090init @ require.js:774(anonymous function) @ require.js:1416
require.js:166 Uncaught Error: Script error for: script_code_header
http://requirejs.org/docs/errors.html#scripterrormakeError @ require.js:166onScriptError @ require.js:1681









share|improve this question
















bumped to the homepage by Community 15 mins ago


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




















    0















    For some reason mage 2 is not creating files that seems to be needed for a proper working of the shop. For example there is a file http://dev.domain.co.uk/pub/media/catalog/productno_selection requested but a 404 is delivered because it is not there. I guess that might be a file containing the amount of items in basket since my top right corner does not state the products amount and I can't reach the basket without going directly in there via url. The top right basket doesn't let me in, stating that no products are in basket... which is wrong.



    Going to that url directly delivers an empty page.



    The other files missing are javascript-files that should be created by mage2 in pub/static too, it seems. For example I mapped the right filename (.js is not needed or allowed) to the left handle



    'jquery_191':           'js/jquery-1.9.1.min',


    Then mage2 requests the filename http://dev.domain.co.uk/pub/static/frontend/company/celo_theme/de_DE/jquery_191.js but this file does not exist.



    Going to that file directly gives some mage bugs claiming that the file does not exist.



    What's wrong? Why are these files not created? I think it brings certain problems to my installation.



    PS: Errors in chrome console after setup:upgrade and setup:static-cache:deploy with the correct language.



    Error parsing header X-XSS-Protection: 1; mode=block, 1; mode=block: expected semicolon at character position 14. The default protections will be applied.
    (index):366 GET http://dev.domain.co.uk/pub/media/catalog/productno_selection 404 (Not Found)
    productno_selection:1 GET http://dev.domain.co.uk/pub/media/catalog/productno_selection 404 (Not Found)
    jquery-migrate.js:21 JQMIGRATE: Logging is active
    require.js:1895 GET http://dev.domain.co.uk/pub/static/frontend/company/celo_theme/en_GB/jquery_191.js req.load @ require.js:1895load @ require.js:1639load @ require.js:820fetch @ require.js:810check @ require.js:840enable @ require.js:1143enable @ require.js:1511(anonymous function) @ require.js:1128(anonymous function) @ require.js:132each @ require.js:57enable @ require.js:1090init @ require.js:774(anonymous function) @ require.js:1416
    require.js:166 Uncaught Error: Script error for: jquery_191
    http://requirejs.org/docs/errors.html#scripterrormakeError @ require.js:166onScriptError @ require.js:1681
    require.js:1895 GET http://dev.domain.co.uk/pub/static/frontend/company/celo_theme/en_GB/script_code_header.js req.load @ require.js:1895load @ require.js:1639load @ require.js:820fetch @ require.js:810check @ require.js:840enable @ require.js:1143enable @ require.js:1511(anonymous function) @ require.js:1128(anonymous function) @ require.js:132each @ require.js:57enable @ require.js:1090init @ require.js:774(anonymous function) @ require.js:1416
    require.js:166 Uncaught Error: Script error for: script_code_header
    http://requirejs.org/docs/errors.html#scripterrormakeError @ require.js:166onScriptError @ require.js:1681









    share|improve this question
















    bumped to the homepage by Community 15 mins ago


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


















      0












      0








      0








      For some reason mage 2 is not creating files that seems to be needed for a proper working of the shop. For example there is a file http://dev.domain.co.uk/pub/media/catalog/productno_selection requested but a 404 is delivered because it is not there. I guess that might be a file containing the amount of items in basket since my top right corner does not state the products amount and I can't reach the basket without going directly in there via url. The top right basket doesn't let me in, stating that no products are in basket... which is wrong.



      Going to that url directly delivers an empty page.



      The other files missing are javascript-files that should be created by mage2 in pub/static too, it seems. For example I mapped the right filename (.js is not needed or allowed) to the left handle



      'jquery_191':           'js/jquery-1.9.1.min',


      Then mage2 requests the filename http://dev.domain.co.uk/pub/static/frontend/company/celo_theme/de_DE/jquery_191.js but this file does not exist.



      Going to that file directly gives some mage bugs claiming that the file does not exist.



      What's wrong? Why are these files not created? I think it brings certain problems to my installation.



      PS: Errors in chrome console after setup:upgrade and setup:static-cache:deploy with the correct language.



      Error parsing header X-XSS-Protection: 1; mode=block, 1; mode=block: expected semicolon at character position 14. The default protections will be applied.
      (index):366 GET http://dev.domain.co.uk/pub/media/catalog/productno_selection 404 (Not Found)
      productno_selection:1 GET http://dev.domain.co.uk/pub/media/catalog/productno_selection 404 (Not Found)
      jquery-migrate.js:21 JQMIGRATE: Logging is active
      require.js:1895 GET http://dev.domain.co.uk/pub/static/frontend/company/celo_theme/en_GB/jquery_191.js req.load @ require.js:1895load @ require.js:1639load @ require.js:820fetch @ require.js:810check @ require.js:840enable @ require.js:1143enable @ require.js:1511(anonymous function) @ require.js:1128(anonymous function) @ require.js:132each @ require.js:57enable @ require.js:1090init @ require.js:774(anonymous function) @ require.js:1416
      require.js:166 Uncaught Error: Script error for: jquery_191
      http://requirejs.org/docs/errors.html#scripterrormakeError @ require.js:166onScriptError @ require.js:1681
      require.js:1895 GET http://dev.domain.co.uk/pub/static/frontend/company/celo_theme/en_GB/script_code_header.js req.load @ require.js:1895load @ require.js:1639load @ require.js:820fetch @ require.js:810check @ require.js:840enable @ require.js:1143enable @ require.js:1511(anonymous function) @ require.js:1128(anonymous function) @ require.js:132each @ require.js:57enable @ require.js:1090init @ require.js:774(anonymous function) @ require.js:1416
      require.js:166 Uncaught Error: Script error for: script_code_header
      http://requirejs.org/docs/errors.html#scripterrormakeError @ require.js:166onScriptError @ require.js:1681









      share|improve this question
















      For some reason mage 2 is not creating files that seems to be needed for a proper working of the shop. For example there is a file http://dev.domain.co.uk/pub/media/catalog/productno_selection requested but a 404 is delivered because it is not there. I guess that might be a file containing the amount of items in basket since my top right corner does not state the products amount and I can't reach the basket without going directly in there via url. The top right basket doesn't let me in, stating that no products are in basket... which is wrong.



      Going to that url directly delivers an empty page.



      The other files missing are javascript-files that should be created by mage2 in pub/static too, it seems. For example I mapped the right filename (.js is not needed or allowed) to the left handle



      'jquery_191':           'js/jquery-1.9.1.min',


      Then mage2 requests the filename http://dev.domain.co.uk/pub/static/frontend/company/celo_theme/de_DE/jquery_191.js but this file does not exist.



      Going to that file directly gives some mage bugs claiming that the file does not exist.



      What's wrong? Why are these files not created? I think it brings certain problems to my installation.



      PS: Errors in chrome console after setup:upgrade and setup:static-cache:deploy with the correct language.



      Error parsing header X-XSS-Protection: 1; mode=block, 1; mode=block: expected semicolon at character position 14. The default protections will be applied.
      (index):366 GET http://dev.domain.co.uk/pub/media/catalog/productno_selection 404 (Not Found)
      productno_selection:1 GET http://dev.domain.co.uk/pub/media/catalog/productno_selection 404 (Not Found)
      jquery-migrate.js:21 JQMIGRATE: Logging is active
      require.js:1895 GET http://dev.domain.co.uk/pub/static/frontend/company/celo_theme/en_GB/jquery_191.js req.load @ require.js:1895load @ require.js:1639load @ require.js:820fetch @ require.js:810check @ require.js:840enable @ require.js:1143enable @ require.js:1511(anonymous function) @ require.js:1128(anonymous function) @ require.js:132each @ require.js:57enable @ require.js:1090init @ require.js:774(anonymous function) @ require.js:1416
      require.js:166 Uncaught Error: Script error for: jquery_191
      http://requirejs.org/docs/errors.html#scripterrormakeError @ require.js:166onScriptError @ require.js:1681
      require.js:1895 GET http://dev.domain.co.uk/pub/static/frontend/company/celo_theme/en_GB/script_code_header.js req.load @ require.js:1895load @ require.js:1639load @ require.js:820fetch @ require.js:810check @ require.js:840enable @ require.js:1143enable @ require.js:1511(anonymous function) @ require.js:1128(anonymous function) @ require.js:132each @ require.js:57enable @ require.js:1090init @ require.js:774(anonymous function) @ require.js:1416
      require.js:166 Uncaught Error: Script error for: script_code_header
      http://requirejs.org/docs/errors.html#scripterrormakeError @ require.js:166onScriptError @ require.js:1681






      magento2 magento-2.0.7






      share|improve this question















      share|improve this question













      share|improve this question




      share|improve this question








      edited Jul 23 '16 at 16:50







      Magento2noob

















      asked Jul 20 '16 at 6:38









      Magento2noobMagento2noob

      12




      12





      bumped to the homepage by Community 15 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 15 mins ago


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
























          1 Answer
          1






          active

          oldest

          votes


















          0














          Try running both the codes below:




          • php bin/magento setup:upgrade


          • php bin/magento setup:static-content:deploy







          share|improve this answer
























          • Thanks for answering... I use the first command relatively regularly. The second command fails for a reason I do not understand. PHP claims having not enough memory. Though phpinfo.php has a memory limit way higher. And the cli-user has another php.ini that has unlimited ram. I wonder what the problem is.

            – Magento2noob
            Jul 22 '16 at 14:25











          • It was an error in chosing the wrong php.ini. Though even when running setup:upgrade and then running deploy with the correct language... it does not change a little bit. Are these files created by a special user that might be missing writing rights or something? I'm not sure what to do. I think about trying to upgrade to mage 2.0.8 or 2.1 but I wonder if it will change the issue. I added the console output in my first post...

            – Magento2noob
            Jul 23 '16 at 16:49













          • Maybe those missing files do not belong to the real static content like the require_js- folder in pub/static? It does not get deleted when deleting static content cache so maybe those files would not be created by deploying and the error lies in the engine that handles code files?

            – Magento2noob
            Jul 25 '16 at 9:08












          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%2f126515%2fmagento-2-0-7-is-not-creating-certain-files-in-pub-static-and-pub-media%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














          Try running both the codes below:




          • php bin/magento setup:upgrade


          • php bin/magento setup:static-content:deploy







          share|improve this answer
























          • Thanks for answering... I use the first command relatively regularly. The second command fails for a reason I do not understand. PHP claims having not enough memory. Though phpinfo.php has a memory limit way higher. And the cli-user has another php.ini that has unlimited ram. I wonder what the problem is.

            – Magento2noob
            Jul 22 '16 at 14:25











          • It was an error in chosing the wrong php.ini. Though even when running setup:upgrade and then running deploy with the correct language... it does not change a little bit. Are these files created by a special user that might be missing writing rights or something? I'm not sure what to do. I think about trying to upgrade to mage 2.0.8 or 2.1 but I wonder if it will change the issue. I added the console output in my first post...

            – Magento2noob
            Jul 23 '16 at 16:49













          • Maybe those missing files do not belong to the real static content like the require_js- folder in pub/static? It does not get deleted when deleting static content cache so maybe those files would not be created by deploying and the error lies in the engine that handles code files?

            – Magento2noob
            Jul 25 '16 at 9:08
















          0














          Try running both the codes below:




          • php bin/magento setup:upgrade


          • php bin/magento setup:static-content:deploy







          share|improve this answer
























          • Thanks for answering... I use the first command relatively regularly. The second command fails for a reason I do not understand. PHP claims having not enough memory. Though phpinfo.php has a memory limit way higher. And the cli-user has another php.ini that has unlimited ram. I wonder what the problem is.

            – Magento2noob
            Jul 22 '16 at 14:25











          • It was an error in chosing the wrong php.ini. Though even when running setup:upgrade and then running deploy with the correct language... it does not change a little bit. Are these files created by a special user that might be missing writing rights or something? I'm not sure what to do. I think about trying to upgrade to mage 2.0.8 or 2.1 but I wonder if it will change the issue. I added the console output in my first post...

            – Magento2noob
            Jul 23 '16 at 16:49













          • Maybe those missing files do not belong to the real static content like the require_js- folder in pub/static? It does not get deleted when deleting static content cache so maybe those files would not be created by deploying and the error lies in the engine that handles code files?

            – Magento2noob
            Jul 25 '16 at 9:08














          0












          0








          0







          Try running both the codes below:




          • php bin/magento setup:upgrade


          • php bin/magento setup:static-content:deploy







          share|improve this answer













          Try running both the codes below:




          • php bin/magento setup:upgrade


          • php bin/magento setup:static-content:deploy








          share|improve this answer












          share|improve this answer



          share|improve this answer










          answered Jul 22 '16 at 9:31







          user41152




















          • Thanks for answering... I use the first command relatively regularly. The second command fails for a reason I do not understand. PHP claims having not enough memory. Though phpinfo.php has a memory limit way higher. And the cli-user has another php.ini that has unlimited ram. I wonder what the problem is.

            – Magento2noob
            Jul 22 '16 at 14:25











          • It was an error in chosing the wrong php.ini. Though even when running setup:upgrade and then running deploy with the correct language... it does not change a little bit. Are these files created by a special user that might be missing writing rights or something? I'm not sure what to do. I think about trying to upgrade to mage 2.0.8 or 2.1 but I wonder if it will change the issue. I added the console output in my first post...

            – Magento2noob
            Jul 23 '16 at 16:49













          • Maybe those missing files do not belong to the real static content like the require_js- folder in pub/static? It does not get deleted when deleting static content cache so maybe those files would not be created by deploying and the error lies in the engine that handles code files?

            – Magento2noob
            Jul 25 '16 at 9:08



















          • Thanks for answering... I use the first command relatively regularly. The second command fails for a reason I do not understand. PHP claims having not enough memory. Though phpinfo.php has a memory limit way higher. And the cli-user has another php.ini that has unlimited ram. I wonder what the problem is.

            – Magento2noob
            Jul 22 '16 at 14:25











          • It was an error in chosing the wrong php.ini. Though even when running setup:upgrade and then running deploy with the correct language... it does not change a little bit. Are these files created by a special user that might be missing writing rights or something? I'm not sure what to do. I think about trying to upgrade to mage 2.0.8 or 2.1 but I wonder if it will change the issue. I added the console output in my first post...

            – Magento2noob
            Jul 23 '16 at 16:49













          • Maybe those missing files do not belong to the real static content like the require_js- folder in pub/static? It does not get deleted when deleting static content cache so maybe those files would not be created by deploying and the error lies in the engine that handles code files?

            – Magento2noob
            Jul 25 '16 at 9:08

















          Thanks for answering... I use the first command relatively regularly. The second command fails for a reason I do not understand. PHP claims having not enough memory. Though phpinfo.php has a memory limit way higher. And the cli-user has another php.ini that has unlimited ram. I wonder what the problem is.

          – Magento2noob
          Jul 22 '16 at 14:25





          Thanks for answering... I use the first command relatively regularly. The second command fails for a reason I do not understand. PHP claims having not enough memory. Though phpinfo.php has a memory limit way higher. And the cli-user has another php.ini that has unlimited ram. I wonder what the problem is.

          – Magento2noob
          Jul 22 '16 at 14:25













          It was an error in chosing the wrong php.ini. Though even when running setup:upgrade and then running deploy with the correct language... it does not change a little bit. Are these files created by a special user that might be missing writing rights or something? I'm not sure what to do. I think about trying to upgrade to mage 2.0.8 or 2.1 but I wonder if it will change the issue. I added the console output in my first post...

          – Magento2noob
          Jul 23 '16 at 16:49







          It was an error in chosing the wrong php.ini. Though even when running setup:upgrade and then running deploy with the correct language... it does not change a little bit. Are these files created by a special user that might be missing writing rights or something? I'm not sure what to do. I think about trying to upgrade to mage 2.0.8 or 2.1 but I wonder if it will change the issue. I added the console output in my first post...

          – Magento2noob
          Jul 23 '16 at 16:49















          Maybe those missing files do not belong to the real static content like the require_js- folder in pub/static? It does not get deleted when deleting static content cache so maybe those files would not be created by deploying and the error lies in the engine that handles code files?

          – Magento2noob
          Jul 25 '16 at 9:08





          Maybe those missing files do not belong to the real static content like the require_js- folder in pub/static? It does not get deleted when deleting static content cache so maybe those files would not be created by deploying and the error lies in the engine that handles code files?

          – Magento2noob
          Jul 25 '16 at 9:08


















          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%2f126515%2fmagento-2-0-7-is-not-creating-certain-files-in-pub-static-and-pub-media%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

          “%fieldName is a required field.”, in Magento2 REST API Call for GET Method Type The Next...

          How to change City field to a dropdown in Checkout step Magento 2Magento 2 : How to change UI field(s)...

          變成蝙蝠會怎樣? 參考資料 外部連結 导航菜单Thomas Nagel, "What is it like to be a...