Purpose of magentogeneratedmetadataglobal.php file and is it safe to delete this file?












0















I encountered the following issue when I was moved Magento 2 module into production with command setup:di:compile




Uncaught Error: Call to a member function setActive() on boolean in /opt/bitnami/apps/magento/htdocs/vendor/magento/module-backend/Model/View/Result/Page.php:27nStack trace:
/opt/bitnami/apps/magento/htdocs/generated/code/Magento/Backend/Model/View/Result/Page/Interceptor.php(24): MagentoBackendModelViewResultPage->setActiveMenu('...')




I found a solution to delete magentogeneratedmetadataglobal.php file which worked.



Does anyone know the purpose of global.php file and is it safe to delete it?



Thanks in advance.










share|improve this question























  • I would look for any errors that occur while Magento is in developer mode, without running di:compile. You'll want to find a root cause of your issue, rather than trying to delete core Magento files.

    – andyjv
    Jan 18 at 15:01
















0















I encountered the following issue when I was moved Magento 2 module into production with command setup:di:compile




Uncaught Error: Call to a member function setActive() on boolean in /opt/bitnami/apps/magento/htdocs/vendor/magento/module-backend/Model/View/Result/Page.php:27nStack trace:
/opt/bitnami/apps/magento/htdocs/generated/code/Magento/Backend/Model/View/Result/Page/Interceptor.php(24): MagentoBackendModelViewResultPage->setActiveMenu('...')




I found a solution to delete magentogeneratedmetadataglobal.php file which worked.



Does anyone know the purpose of global.php file and is it safe to delete it?



Thanks in advance.










share|improve this question























  • I would look for any errors that occur while Magento is in developer mode, without running di:compile. You'll want to find a root cause of your issue, rather than trying to delete core Magento files.

    – andyjv
    Jan 18 at 15:01














0












0








0








I encountered the following issue when I was moved Magento 2 module into production with command setup:di:compile




Uncaught Error: Call to a member function setActive() on boolean in /opt/bitnami/apps/magento/htdocs/vendor/magento/module-backend/Model/View/Result/Page.php:27nStack trace:
/opt/bitnami/apps/magento/htdocs/generated/code/Magento/Backend/Model/View/Result/Page/Interceptor.php(24): MagentoBackendModelViewResultPage->setActiveMenu('...')




I found a solution to delete magentogeneratedmetadataglobal.php file which worked.



Does anyone know the purpose of global.php file and is it safe to delete it?



Thanks in advance.










share|improve this question














I encountered the following issue when I was moved Magento 2 module into production with command setup:di:compile




Uncaught Error: Call to a member function setActive() on boolean in /opt/bitnami/apps/magento/htdocs/vendor/magento/module-backend/Model/View/Result/Page.php:27nStack trace:
/opt/bitnami/apps/magento/htdocs/generated/code/Magento/Backend/Model/View/Result/Page/Interceptor.php(24): MagentoBackendModelViewResultPage->setActiveMenu('...')




I found a solution to delete magentogeneratedmetadataglobal.php file which worked.



Does anyone know the purpose of global.php file and is it safe to delete it?



Thanks in advance.







magento2






share|improve this question













share|improve this question











share|improve this question




share|improve this question










asked Dec 11 '18 at 9:10









KalpeshKalpesh

34




34













  • I would look for any errors that occur while Magento is in developer mode, without running di:compile. You'll want to find a root cause of your issue, rather than trying to delete core Magento files.

    – andyjv
    Jan 18 at 15:01



















  • I would look for any errors that occur while Magento is in developer mode, without running di:compile. You'll want to find a root cause of your issue, rather than trying to delete core Magento files.

    – andyjv
    Jan 18 at 15:01

















I would look for any errors that occur while Magento is in developer mode, without running di:compile. You'll want to find a root cause of your issue, rather than trying to delete core Magento files.

– andyjv
Jan 18 at 15:01





I would look for any errors that occur while Magento is in developer mode, without running di:compile. You'll want to find a root cause of your issue, rather than trying to delete core Magento files.

– andyjv
Jan 18 at 15:01










1 Answer
1






active

oldest

votes


















0














As the documentation says




"The code compiler creates generated/metadata/global.php, which is a
PHP serialized map of all constructor definitions mixed with object
linking configuration defined in di.xml. di.xml is the dependency
injection configuration. There is a global app/etc/di.xml and there
can one defined for every module ."







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%2f253149%2fpurpose-of-magento-generated-metadata-global-php-file-and-is-it-safe-to-delete-t%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














    As the documentation says




    "The code compiler creates generated/metadata/global.php, which is a
    PHP serialized map of all constructor definitions mixed with object
    linking configuration defined in di.xml. di.xml is the dependency
    injection configuration. There is a global app/etc/di.xml and there
    can one defined for every module ."







    share|improve this answer




























      0














      As the documentation says




      "The code compiler creates generated/metadata/global.php, which is a
      PHP serialized map of all constructor definitions mixed with object
      linking configuration defined in di.xml. di.xml is the dependency
      injection configuration. There is a global app/etc/di.xml and there
      can one defined for every module ."







      share|improve this answer


























        0












        0








        0







        As the documentation says




        "The code compiler creates generated/metadata/global.php, which is a
        PHP serialized map of all constructor definitions mixed with object
        linking configuration defined in di.xml. di.xml is the dependency
        injection configuration. There is a global app/etc/di.xml and there
        can one defined for every module ."







        share|improve this answer













        As the documentation says




        "The code compiler creates generated/metadata/global.php, which is a
        PHP serialized map of all constructor definitions mixed with object
        linking configuration defined in di.xml. di.xml is the dependency
        injection configuration. There is a global app/etc/di.xml and there
        can one defined for every module ."








        share|improve this answer












        share|improve this answer



        share|improve this answer










        answered Jan 18 at 14:40









        JohnJohn

        693520




        693520






























            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%2f253149%2fpurpose-of-magento-generated-metadata-global-php-file-and-is-it-safe-to-delete-t%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

            An IMO inspired problem

            Management

            Investment