Magento 1.x site gives me an error message about Fatal error





.everyoneloves__top-leaderboard:empty,.everyoneloves__mid-leaderboard:empty,.everyoneloves__bot-mid-leaderboard:empty{ margin-bottom:0;
}







0















I get this when I go to my site:



Fatal error: Call to a member function children() on a non-object in app/code/core/Mage/Core/Model/Config.php on line 946



I have done anything on it today.



May I ask for direction?










share|improve this question
















bumped to the homepage by Community 4 mins ago


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
















  • tak the backup of this file and replace original file and check

    – Baby in Magento
    May 4 '16 at 18:29











  • For those magically appearing errors that weren't there yesterday and aren't the result of making code changes, or module installations, have you tried clearing the cache? Sounds like a config cache corruption issue.

    – Fiasco Labs
    May 5 '16 at 4:35




















0















I get this when I go to my site:



Fatal error: Call to a member function children() on a non-object in app/code/core/Mage/Core/Model/Config.php on line 946



I have done anything on it today.



May I ask for direction?










share|improve this question
















bumped to the homepage by Community 4 mins ago


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
















  • tak the backup of this file and replace original file and check

    – Baby in Magento
    May 4 '16 at 18:29











  • For those magically appearing errors that weren't there yesterday and aren't the result of making code changes, or module installations, have you tried clearing the cache? Sounds like a config cache corruption issue.

    – Fiasco Labs
    May 5 '16 at 4:35
















0












0








0








I get this when I go to my site:



Fatal error: Call to a member function children() on a non-object in app/code/core/Mage/Core/Model/Config.php on line 946



I have done anything on it today.



May I ask for direction?










share|improve this question
















I get this when I go to my site:



Fatal error: Call to a member function children() on a non-object in app/code/core/Mage/Core/Model/Config.php on line 946



I have done anything on it today.



May I ask for direction?







magento-1 fatal-error






share|improve this question















share|improve this question













share|improve this question




share|improve this question








edited May 4 '16 at 20:04









Prashant Valanda

10k12356




10k12356










asked May 4 '16 at 17:07









Matthew McLennanMatthew McLennan

81531128




81531128





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


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















  • tak the backup of this file and replace original file and check

    – Baby in Magento
    May 4 '16 at 18:29











  • For those magically appearing errors that weren't there yesterday and aren't the result of making code changes, or module installations, have you tried clearing the cache? Sounds like a config cache corruption issue.

    – Fiasco Labs
    May 5 '16 at 4:35





















  • tak the backup of this file and replace original file and check

    – Baby in Magento
    May 4 '16 at 18:29











  • For those magically appearing errors that weren't there yesterday and aren't the result of making code changes, or module installations, have you tried clearing the cache? Sounds like a config cache corruption issue.

    – Fiasco Labs
    May 5 '16 at 4:35



















tak the backup of this file and replace original file and check

– Baby in Magento
May 4 '16 at 18:29





tak the backup of this file and replace original file and check

– Baby in Magento
May 4 '16 at 18:29













For those magically appearing errors that weren't there yesterday and aren't the result of making code changes, or module installations, have you tried clearing the cache? Sounds like a config cache corruption issue.

– Fiasco Labs
May 5 '16 at 4:35







For those magically appearing errors that weren't there yesterday and aren't the result of making code changes, or module installations, have you tried clearing the cache? Sounds like a config cache corruption issue.

– Fiasco Labs
May 5 '16 at 4:35












2 Answers
2






active

oldest

votes


















0














Go to code app/code/core/Mage/Core/Model/Config.php on line 946



$modules = $this->getNode('modules')->children();


In your one of module have missing modules node.



go to app/etc/modules and locate the module declaration file. It'll follow the naming convention [Package]_[Modulename].xml



In that xml file,For disable module find the <active>true</active> node and change it to <active>false</active>



Disable module one by one and check which module have error.






share|improve this answer































    0














    change following in app/Mage.php



    public static function getRoot()
    {
    return self::$_appRoot;
    }


    to



    public static function getRoot()
    {
    if(empty(self::$_appRoot))
    self::setRoot();
    return self::$_appRoot;
    }


    this is working fine in almost all upgrade issues






    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%2f113982%2fmagento-1-x-site-gives-me-an-error-message-about-fatal-error%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














      Go to code app/code/core/Mage/Core/Model/Config.php on line 946



      $modules = $this->getNode('modules')->children();


      In your one of module have missing modules node.



      go to app/etc/modules and locate the module declaration file. It'll follow the naming convention [Package]_[Modulename].xml



      In that xml file,For disable module find the <active>true</active> node and change it to <active>false</active>



      Disable module one by one and check which module have error.






      share|improve this answer




























        0














        Go to code app/code/core/Mage/Core/Model/Config.php on line 946



        $modules = $this->getNode('modules')->children();


        In your one of module have missing modules node.



        go to app/etc/modules and locate the module declaration file. It'll follow the naming convention [Package]_[Modulename].xml



        In that xml file,For disable module find the <active>true</active> node and change it to <active>false</active>



        Disable module one by one and check which module have error.






        share|improve this answer


























          0












          0








          0







          Go to code app/code/core/Mage/Core/Model/Config.php on line 946



          $modules = $this->getNode('modules')->children();


          In your one of module have missing modules node.



          go to app/etc/modules and locate the module declaration file. It'll follow the naming convention [Package]_[Modulename].xml



          In that xml file,For disable module find the <active>true</active> node and change it to <active>false</active>



          Disable module one by one and check which module have error.






          share|improve this answer













          Go to code app/code/core/Mage/Core/Model/Config.php on line 946



          $modules = $this->getNode('modules')->children();


          In your one of module have missing modules node.



          go to app/etc/modules and locate the module declaration file. It'll follow the naming convention [Package]_[Modulename].xml



          In that xml file,For disable module find the <active>true</active> node and change it to <active>false</active>



          Disable module one by one and check which module have error.







          share|improve this answer












          share|improve this answer



          share|improve this answer










          answered May 4 '16 at 20:12









          Prashant ValandaPrashant Valanda

          10k12356




          10k12356

























              0














              change following in app/Mage.php



              public static function getRoot()
              {
              return self::$_appRoot;
              }


              to



              public static function getRoot()
              {
              if(empty(self::$_appRoot))
              self::setRoot();
              return self::$_appRoot;
              }


              this is working fine in almost all upgrade issues






              share|improve this answer




























                0














                change following in app/Mage.php



                public static function getRoot()
                {
                return self::$_appRoot;
                }


                to



                public static function getRoot()
                {
                if(empty(self::$_appRoot))
                self::setRoot();
                return self::$_appRoot;
                }


                this is working fine in almost all upgrade issues






                share|improve this answer


























                  0












                  0








                  0







                  change following in app/Mage.php



                  public static function getRoot()
                  {
                  return self::$_appRoot;
                  }


                  to



                  public static function getRoot()
                  {
                  if(empty(self::$_appRoot))
                  self::setRoot();
                  return self::$_appRoot;
                  }


                  this is working fine in almost all upgrade issues






                  share|improve this answer













                  change following in app/Mage.php



                  public static function getRoot()
                  {
                  return self::$_appRoot;
                  }


                  to



                  public static function getRoot()
                  {
                  if(empty(self::$_appRoot))
                  self::setRoot();
                  return self::$_appRoot;
                  }


                  this is working fine in almost all upgrade issues







                  share|improve this answer












                  share|improve this answer



                  share|improve this answer










                  answered Mar 6 '17 at 10:32









                  Emizen TechEmizen Tech

                  1866




                  1866






























                      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%2f113982%2fmagento-1-x-site-gives-me-an-error-message-about-fatal-error%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