Error in content deploy in magento 2.2.1












2















I have installed the magento 2.2.1 but on deploying static content it is giving following error



    PHP Fatal error:  Uncaught Error: Call to a member function getPackage() on null in /var/www/html/unicorn-magento/vendor/magento/module-deploy/Package/Processor/PostProcessor/CssUrls.php:215
Stack trace:
#0 /var/www/html/unicorn-magento/vendor/magento/module-deploy/Package/Processor/PostProcessor/CssUrls.php(109): MagentoDeployPackageProcessorPostProcessorCssUrls->getValidExternalUrl('{{base_url_path...', Object(MagentoDeployPackagePackage))
#1 /var/www/html/unicorn-magento/vendor/magento/module-deploy/Package/Processor/PostProcessor/CssUrls.php(80): MagentoDeployPackageProcessorPostProcessorCssUrls->parseCss(Array, 'css/email-inlin...', 'frontend/Custom...', '@import url("{{...', Object(MagentoDeployPackagePackage))
#2 /var/www/html/unicorn-magento/vendor/magento/module-deploy/Service/DeployPackage.php(147): MagentoDeployPackageProcessorPostProcessorCssUrls->process(Object(MagentoDeployPackagePackage), Array)
#3 /var/www/html/unicorn-magento/vendor/magento/module-deploy/Service/DeployPackage.php(103): in /var/www/html/unicorn-magento/vendor/magento/module-deploy/Package/Processor/PostProcessor/CssUrls.php on line 215


I have removed view_processed content, pub/satatic and tried multiple times but this error is showing. Please help to resolve this. Thanks










share|improve this question























  • Magento tried to run getPackage function on some object which is equal null. Try to find out why this object is null using xdebug...

    – Stepan Furman
    Feb 22 '18 at 21:29











  • @Nitin Pawar did you find out the reason?

    – M.Elwan
    May 29 '18 at 11:21
















2















I have installed the magento 2.2.1 but on deploying static content it is giving following error



    PHP Fatal error:  Uncaught Error: Call to a member function getPackage() on null in /var/www/html/unicorn-magento/vendor/magento/module-deploy/Package/Processor/PostProcessor/CssUrls.php:215
Stack trace:
#0 /var/www/html/unicorn-magento/vendor/magento/module-deploy/Package/Processor/PostProcessor/CssUrls.php(109): MagentoDeployPackageProcessorPostProcessorCssUrls->getValidExternalUrl('{{base_url_path...', Object(MagentoDeployPackagePackage))
#1 /var/www/html/unicorn-magento/vendor/magento/module-deploy/Package/Processor/PostProcessor/CssUrls.php(80): MagentoDeployPackageProcessorPostProcessorCssUrls->parseCss(Array, 'css/email-inlin...', 'frontend/Custom...', '@import url("{{...', Object(MagentoDeployPackagePackage))
#2 /var/www/html/unicorn-magento/vendor/magento/module-deploy/Service/DeployPackage.php(147): MagentoDeployPackageProcessorPostProcessorCssUrls->process(Object(MagentoDeployPackagePackage), Array)
#3 /var/www/html/unicorn-magento/vendor/magento/module-deploy/Service/DeployPackage.php(103): in /var/www/html/unicorn-magento/vendor/magento/module-deploy/Package/Processor/PostProcessor/CssUrls.php on line 215


I have removed view_processed content, pub/satatic and tried multiple times but this error is showing. Please help to resolve this. Thanks










share|improve this question























  • Magento tried to run getPackage function on some object which is equal null. Try to find out why this object is null using xdebug...

    – Stepan Furman
    Feb 22 '18 at 21:29











  • @Nitin Pawar did you find out the reason?

    – M.Elwan
    May 29 '18 at 11:21














2












2








2








I have installed the magento 2.2.1 but on deploying static content it is giving following error



    PHP Fatal error:  Uncaught Error: Call to a member function getPackage() on null in /var/www/html/unicorn-magento/vendor/magento/module-deploy/Package/Processor/PostProcessor/CssUrls.php:215
Stack trace:
#0 /var/www/html/unicorn-magento/vendor/magento/module-deploy/Package/Processor/PostProcessor/CssUrls.php(109): MagentoDeployPackageProcessorPostProcessorCssUrls->getValidExternalUrl('{{base_url_path...', Object(MagentoDeployPackagePackage))
#1 /var/www/html/unicorn-magento/vendor/magento/module-deploy/Package/Processor/PostProcessor/CssUrls.php(80): MagentoDeployPackageProcessorPostProcessorCssUrls->parseCss(Array, 'css/email-inlin...', 'frontend/Custom...', '@import url("{{...', Object(MagentoDeployPackagePackage))
#2 /var/www/html/unicorn-magento/vendor/magento/module-deploy/Service/DeployPackage.php(147): MagentoDeployPackageProcessorPostProcessorCssUrls->process(Object(MagentoDeployPackagePackage), Array)
#3 /var/www/html/unicorn-magento/vendor/magento/module-deploy/Service/DeployPackage.php(103): in /var/www/html/unicorn-magento/vendor/magento/module-deploy/Package/Processor/PostProcessor/CssUrls.php on line 215


I have removed view_processed content, pub/satatic and tried multiple times but this error is showing. Please help to resolve this. Thanks










share|improve this question














I have installed the magento 2.2.1 but on deploying static content it is giving following error



    PHP Fatal error:  Uncaught Error: Call to a member function getPackage() on null in /var/www/html/unicorn-magento/vendor/magento/module-deploy/Package/Processor/PostProcessor/CssUrls.php:215
Stack trace:
#0 /var/www/html/unicorn-magento/vendor/magento/module-deploy/Package/Processor/PostProcessor/CssUrls.php(109): MagentoDeployPackageProcessorPostProcessorCssUrls->getValidExternalUrl('{{base_url_path...', Object(MagentoDeployPackagePackage))
#1 /var/www/html/unicorn-magento/vendor/magento/module-deploy/Package/Processor/PostProcessor/CssUrls.php(80): MagentoDeployPackageProcessorPostProcessorCssUrls->parseCss(Array, 'css/email-inlin...', 'frontend/Custom...', '@import url("{{...', Object(MagentoDeployPackagePackage))
#2 /var/www/html/unicorn-magento/vendor/magento/module-deploy/Service/DeployPackage.php(147): MagentoDeployPackageProcessorPostProcessorCssUrls->process(Object(MagentoDeployPackagePackage), Array)
#3 /var/www/html/unicorn-magento/vendor/magento/module-deploy/Service/DeployPackage.php(103): in /var/www/html/unicorn-magento/vendor/magento/module-deploy/Package/Processor/PostProcessor/CssUrls.php on line 215


I have removed view_processed content, pub/satatic and tried multiple times but this error is showing. Please help to resolve this. Thanks







magento2 static-content-deploy






share|improve this question













share|improve this question











share|improve this question




share|improve this question










asked Feb 22 '18 at 19:50









Nitin PawarNitin Pawar

78911438




78911438













  • Magento tried to run getPackage function on some object which is equal null. Try to find out why this object is null using xdebug...

    – Stepan Furman
    Feb 22 '18 at 21:29











  • @Nitin Pawar did you find out the reason?

    – M.Elwan
    May 29 '18 at 11:21



















  • Magento tried to run getPackage function on some object which is equal null. Try to find out why this object is null using xdebug...

    – Stepan Furman
    Feb 22 '18 at 21:29











  • @Nitin Pawar did you find out the reason?

    – M.Elwan
    May 29 '18 at 11:21

















Magento tried to run getPackage function on some object which is equal null. Try to find out why this object is null using xdebug...

– Stepan Furman
Feb 22 '18 at 21:29





Magento tried to run getPackage function on some object which is equal null. Try to find out why this object is null using xdebug...

– Stepan Furman
Feb 22 '18 at 21:29













@Nitin Pawar did you find out the reason?

– M.Elwan
May 29 '18 at 11:21





@Nitin Pawar did you find out the reason?

– M.Elwan
May 29 '18 at 11:21










2 Answers
2






active

oldest

votes


















2














This is already answered here by @MateuszLerczak



I am quoting the relevant part from the answer below:




Workaround for that is remove generated data before deploy. If
var/view_preprocessed exists magento using data from this dir.



rm -rf pub/static/* var/view_preprocessed/pub/*



php bin/magento setup:static-content:deploy -f en_US




Also see this GitHub thread for more details






share|improve this answer































    0














    It seems to be a magento bug :-( . The way to reverse it is the following (I know this is not a solution) but it will help to have the site working again:



    On command line:



    Magento ≥ 2.2
    bin/magento config:set dev/css/minify_files 0
    bin/magento cache:clean



    Magento < 2.2
    On DB (mysql client) execute: UPDATE core_config_data SET value = 0 WHERE 'dev/css/minify_files



    bin/magento cache:clean



    Now, you can compile again.






    share|improve this answer








    New contributor




    Kopernix dotcom is a new contributor to this site. Take care in asking for clarification, commenting, and answering.
    Check out our Code of Conduct.




















      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%2f214696%2ferror-in-content-deploy-in-magento-2-2-1%23new-answer', 'question_page');
      }
      );

      Post as a guest















      Required, but never shown

























      2 Answers
      2






      active

      oldest

      votes








      2 Answers
      2






      active

      oldest

      votes









      active

      oldest

      votes






      active

      oldest

      votes









      2














      This is already answered here by @MateuszLerczak



      I am quoting the relevant part from the answer below:




      Workaround for that is remove generated data before deploy. If
      var/view_preprocessed exists magento using data from this dir.



      rm -rf pub/static/* var/view_preprocessed/pub/*



      php bin/magento setup:static-content:deploy -f en_US




      Also see this GitHub thread for more details






      share|improve this answer




























        2














        This is already answered here by @MateuszLerczak



        I am quoting the relevant part from the answer below:




        Workaround for that is remove generated data before deploy. If
        var/view_preprocessed exists magento using data from this dir.



        rm -rf pub/static/* var/view_preprocessed/pub/*



        php bin/magento setup:static-content:deploy -f en_US




        Also see this GitHub thread for more details






        share|improve this answer


























          2












          2








          2







          This is already answered here by @MateuszLerczak



          I am quoting the relevant part from the answer below:




          Workaround for that is remove generated data before deploy. If
          var/view_preprocessed exists magento using data from this dir.



          rm -rf pub/static/* var/view_preprocessed/pub/*



          php bin/magento setup:static-content:deploy -f en_US




          Also see this GitHub thread for more details






          share|improve this answer













          This is already answered here by @MateuszLerczak



          I am quoting the relevant part from the answer below:




          Workaround for that is remove generated data before deploy. If
          var/view_preprocessed exists magento using data from this dir.



          rm -rf pub/static/* var/view_preprocessed/pub/*



          php bin/magento setup:static-content:deploy -f en_US




          Also see this GitHub thread for more details







          share|improve this answer












          share|improve this answer



          share|improve this answer










          answered Jun 6 '18 at 10:23









          Rajeev K TomyRajeev K Tomy

          14.5k54589




          14.5k54589

























              0














              It seems to be a magento bug :-( . The way to reverse it is the following (I know this is not a solution) but it will help to have the site working again:



              On command line:



              Magento ≥ 2.2
              bin/magento config:set dev/css/minify_files 0
              bin/magento cache:clean



              Magento < 2.2
              On DB (mysql client) execute: UPDATE core_config_data SET value = 0 WHERE 'dev/css/minify_files



              bin/magento cache:clean



              Now, you can compile again.






              share|improve this answer








              New contributor




              Kopernix dotcom is a new contributor to this site. Take care in asking for clarification, commenting, and answering.
              Check out our Code of Conduct.

























                0














                It seems to be a magento bug :-( . The way to reverse it is the following (I know this is not a solution) but it will help to have the site working again:



                On command line:



                Magento ≥ 2.2
                bin/magento config:set dev/css/minify_files 0
                bin/magento cache:clean



                Magento < 2.2
                On DB (mysql client) execute: UPDATE core_config_data SET value = 0 WHERE 'dev/css/minify_files



                bin/magento cache:clean



                Now, you can compile again.






                share|improve this answer








                New contributor




                Kopernix dotcom is a new contributor to this site. Take care in asking for clarification, commenting, and answering.
                Check out our Code of Conduct.























                  0












                  0








                  0







                  It seems to be a magento bug :-( . The way to reverse it is the following (I know this is not a solution) but it will help to have the site working again:



                  On command line:



                  Magento ≥ 2.2
                  bin/magento config:set dev/css/minify_files 0
                  bin/magento cache:clean



                  Magento < 2.2
                  On DB (mysql client) execute: UPDATE core_config_data SET value = 0 WHERE 'dev/css/minify_files



                  bin/magento cache:clean



                  Now, you can compile again.






                  share|improve this answer








                  New contributor




                  Kopernix dotcom is a new contributor to this site. Take care in asking for clarification, commenting, and answering.
                  Check out our Code of Conduct.










                  It seems to be a magento bug :-( . The way to reverse it is the following (I know this is not a solution) but it will help to have the site working again:



                  On command line:



                  Magento ≥ 2.2
                  bin/magento config:set dev/css/minify_files 0
                  bin/magento cache:clean



                  Magento < 2.2
                  On DB (mysql client) execute: UPDATE core_config_data SET value = 0 WHERE 'dev/css/minify_files



                  bin/magento cache:clean



                  Now, you can compile again.







                  share|improve this answer








                  New contributor




                  Kopernix dotcom is a new contributor to this site. Take care in asking for clarification, commenting, and answering.
                  Check out our Code of Conduct.









                  share|improve this answer



                  share|improve this answer






                  New contributor




                  Kopernix dotcom is a new contributor to this site. Take care in asking for clarification, commenting, and answering.
                  Check out our Code of Conduct.









                  answered 1 hour ago









                  Kopernix dotcomKopernix dotcom

                  1




                  1




                  New contributor




                  Kopernix dotcom is a new contributor to this site. Take care in asking for clarification, commenting, and answering.
                  Check out our Code of Conduct.





                  New contributor





                  Kopernix dotcom is a new contributor to this site. Take care in asking for clarification, commenting, and answering.
                  Check out our Code of Conduct.






                  Kopernix dotcom is a new contributor to this site. Take care in asking for clarification, commenting, and answering.
                  Check out our Code of Conduct.






























                      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%2f214696%2ferror-in-content-deploy-in-magento-2-2-1%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