error on magento 2 after update php 5 to 7, Warning:...












0















Error on Magento 2 after update from PHP 5 to PHP 7:




Warning: require(/var/www/html/vendor/magento/framework/registration.php): failed to open stream: No such file or directory in /var/www/html/vendor/composer/autoload_real.php on line 60



Fatal error: require(): Failed opening required '/var/www/html/vendor/magento/framework/registration.php' (include_path='/var/www/html/vendor/phpseclib/phpseclib/phpseclib:/var/www/html/vendor/magento/zendframework1/library:/var/www/html/vendor/phpunit/php-file-iterator:/var/www/html/vendor/phpunit/phpunit:/var/www/html/vendor/symfony/yaml:.:/usr/share/php') in /var/www/html/vendor/composer/autoload_real.php on line 60




Any help?










share|improve this question
















bumped to the homepage by Community 54 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















    Error on Magento 2 after update from PHP 5 to PHP 7:




    Warning: require(/var/www/html/vendor/magento/framework/registration.php): failed to open stream: No such file or directory in /var/www/html/vendor/composer/autoload_real.php on line 60



    Fatal error: require(): Failed opening required '/var/www/html/vendor/magento/framework/registration.php' (include_path='/var/www/html/vendor/phpseclib/phpseclib/phpseclib:/var/www/html/vendor/magento/zendframework1/library:/var/www/html/vendor/phpunit/php-file-iterator:/var/www/html/vendor/phpunit/phpunit:/var/www/html/vendor/symfony/yaml:.:/usr/share/php') in /var/www/html/vendor/composer/autoload_real.php on line 60




    Any help?










    share|improve this question
















    bumped to the homepage by Community 54 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








      Error on Magento 2 after update from PHP 5 to PHP 7:




      Warning: require(/var/www/html/vendor/magento/framework/registration.php): failed to open stream: No such file or directory in /var/www/html/vendor/composer/autoload_real.php on line 60



      Fatal error: require(): Failed opening required '/var/www/html/vendor/magento/framework/registration.php' (include_path='/var/www/html/vendor/phpseclib/phpseclib/phpseclib:/var/www/html/vendor/magento/zendframework1/library:/var/www/html/vendor/phpunit/php-file-iterator:/var/www/html/vendor/phpunit/phpunit:/var/www/html/vendor/symfony/yaml:.:/usr/share/php') in /var/www/html/vendor/composer/autoload_real.php on line 60




      Any help?










      share|improve this question
















      Error on Magento 2 after update from PHP 5 to PHP 7:




      Warning: require(/var/www/html/vendor/magento/framework/registration.php): failed to open stream: No such file or directory in /var/www/html/vendor/composer/autoload_real.php on line 60



      Fatal error: require(): Failed opening required '/var/www/html/vendor/magento/framework/registration.php' (include_path='/var/www/html/vendor/phpseclib/phpseclib/phpseclib:/var/www/html/vendor/magento/zendframework1/library:/var/www/html/vendor/phpunit/php-file-iterator:/var/www/html/vendor/phpunit/phpunit:/var/www/html/vendor/symfony/yaml:.:/usr/share/php') in /var/www/html/vendor/composer/autoload_real.php on line 60




      Any help?







      magento2 error fatal-error






      share|improve this question















      share|improve this question













      share|improve this question




      share|improve this question








      edited Dec 19 '17 at 13:36









      Matt Antley

      1,057518




      1,057518










      asked Dec 19 '17 at 13:25









      Ganesh Ganesh

      468




      468





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


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
























          2 Answers
          2






          active

          oldest

          votes


















          0














          yes got it, we need to update composer.. i hope it will help some one






          share|improve this answer



















          • 1





            I do not agree that this is not an answer to the question, it is, but it is a bit short... Could you elaborate more? What was the cause and why is this the right solution? What commands did you run?

            – 7ochem
            Dec 19 '17 at 13:51











          • i used rm -rf var/page_cache/* var/cache/* var/session/* var/di* var/view_preprocessed/* pub/static/* var/generation.

            – Ganesh
            Dec 20 '17 at 12:02











          • But you said you had updated composer - now you are saying you deleted the cache folders? @Ganesh

            – MJCoder
            May 4 '18 at 15:59



















          0














          I am facing sem issue I have resolved this by below steps




          1. Remove below folders



          rm -rf var/page_cache/* var/cache/* var/session/* var/di*
          var/view_preprocessed/* pub/static/* var/generation





          1. Update composer



          composer remove [companyname]/[modulename]



          composer update





          1. Setup upgrade



          php bin/magento setup:upgrade





          1. Content Deploy



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







          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%2f206398%2ferror-on-magento-2-after-update-php-5-to-7-warning-require-var-www-html-vendo%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









            0














            yes got it, we need to update composer.. i hope it will help some one






            share|improve this answer



















            • 1





              I do not agree that this is not an answer to the question, it is, but it is a bit short... Could you elaborate more? What was the cause and why is this the right solution? What commands did you run?

              – 7ochem
              Dec 19 '17 at 13:51











            • i used rm -rf var/page_cache/* var/cache/* var/session/* var/di* var/view_preprocessed/* pub/static/* var/generation.

              – Ganesh
              Dec 20 '17 at 12:02











            • But you said you had updated composer - now you are saying you deleted the cache folders? @Ganesh

              – MJCoder
              May 4 '18 at 15:59
















            0














            yes got it, we need to update composer.. i hope it will help some one






            share|improve this answer



















            • 1





              I do not agree that this is not an answer to the question, it is, but it is a bit short... Could you elaborate more? What was the cause and why is this the right solution? What commands did you run?

              – 7ochem
              Dec 19 '17 at 13:51











            • i used rm -rf var/page_cache/* var/cache/* var/session/* var/di* var/view_preprocessed/* pub/static/* var/generation.

              – Ganesh
              Dec 20 '17 at 12:02











            • But you said you had updated composer - now you are saying you deleted the cache folders? @Ganesh

              – MJCoder
              May 4 '18 at 15:59














            0












            0








            0







            yes got it, we need to update composer.. i hope it will help some one






            share|improve this answer













            yes got it, we need to update composer.. i hope it will help some one







            share|improve this answer












            share|improve this answer



            share|improve this answer










            answered Dec 19 '17 at 13:30









            Ganesh Ganesh

            468




            468








            • 1





              I do not agree that this is not an answer to the question, it is, but it is a bit short... Could you elaborate more? What was the cause and why is this the right solution? What commands did you run?

              – 7ochem
              Dec 19 '17 at 13:51











            • i used rm -rf var/page_cache/* var/cache/* var/session/* var/di* var/view_preprocessed/* pub/static/* var/generation.

              – Ganesh
              Dec 20 '17 at 12:02











            • But you said you had updated composer - now you are saying you deleted the cache folders? @Ganesh

              – MJCoder
              May 4 '18 at 15:59














            • 1





              I do not agree that this is not an answer to the question, it is, but it is a bit short... Could you elaborate more? What was the cause and why is this the right solution? What commands did you run?

              – 7ochem
              Dec 19 '17 at 13:51











            • i used rm -rf var/page_cache/* var/cache/* var/session/* var/di* var/view_preprocessed/* pub/static/* var/generation.

              – Ganesh
              Dec 20 '17 at 12:02











            • But you said you had updated composer - now you are saying you deleted the cache folders? @Ganesh

              – MJCoder
              May 4 '18 at 15:59








            1




            1





            I do not agree that this is not an answer to the question, it is, but it is a bit short... Could you elaborate more? What was the cause and why is this the right solution? What commands did you run?

            – 7ochem
            Dec 19 '17 at 13:51





            I do not agree that this is not an answer to the question, it is, but it is a bit short... Could you elaborate more? What was the cause and why is this the right solution? What commands did you run?

            – 7ochem
            Dec 19 '17 at 13:51













            i used rm -rf var/page_cache/* var/cache/* var/session/* var/di* var/view_preprocessed/* pub/static/* var/generation.

            – Ganesh
            Dec 20 '17 at 12:02





            i used rm -rf var/page_cache/* var/cache/* var/session/* var/di* var/view_preprocessed/* pub/static/* var/generation.

            – Ganesh
            Dec 20 '17 at 12:02













            But you said you had updated composer - now you are saying you deleted the cache folders? @Ganesh

            – MJCoder
            May 4 '18 at 15:59





            But you said you had updated composer - now you are saying you deleted the cache folders? @Ganesh

            – MJCoder
            May 4 '18 at 15:59













            0














            I am facing sem issue I have resolved this by below steps




            1. Remove below folders



            rm -rf var/page_cache/* var/cache/* var/session/* var/di*
            var/view_preprocessed/* pub/static/* var/generation





            1. Update composer



            composer remove [companyname]/[modulename]



            composer update





            1. Setup upgrade



            php bin/magento setup:upgrade





            1. Content Deploy



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







            share|improve this answer




























              0














              I am facing sem issue I have resolved this by below steps




              1. Remove below folders



              rm -rf var/page_cache/* var/cache/* var/session/* var/di*
              var/view_preprocessed/* pub/static/* var/generation





              1. Update composer



              composer remove [companyname]/[modulename]



              composer update





              1. Setup upgrade



              php bin/magento setup:upgrade





              1. Content Deploy



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







              share|improve this answer


























                0












                0








                0







                I am facing sem issue I have resolved this by below steps




                1. Remove below folders



                rm -rf var/page_cache/* var/cache/* var/session/* var/di*
                var/view_preprocessed/* pub/static/* var/generation





                1. Update composer



                composer remove [companyname]/[modulename]



                composer update





                1. Setup upgrade



                php bin/magento setup:upgrade





                1. Content Deploy



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







                share|improve this answer













                I am facing sem issue I have resolved this by below steps




                1. Remove below folders



                rm -rf var/page_cache/* var/cache/* var/session/* var/di*
                var/view_preprocessed/* pub/static/* var/generation





                1. Update composer



                composer remove [companyname]/[modulename]



                composer update





                1. Setup upgrade



                php bin/magento setup:upgrade





                1. Content Deploy



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








                share|improve this answer












                share|improve this answer



                share|improve this answer










                answered Aug 29 '18 at 11:41









                Deexit SanghaniDeexit Sanghani

                880422




                880422






























                    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%2f206398%2ferror-on-magento-2-after-update-php-5-to-7-warning-require-var-www-html-vendo%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