We launched new forums in March 2019—join us there. In a hurry for help with your website? Get Help Now!
    • 26503
    • 620 Posts
    Geting this error on an upgrade & need to fix!!

    Fatal error: Call to a member function log() on a non-object in /home/canad036/public_html/core/cache/includes/elements/modplugin/12.include.cache.php on line 18

    the content of the cache file is:

    <?php
    function elements_modplugin_12($scriptProperties= array()) {
    global $modx;
    if (is_array($scriptProperties)) {
    extract($scriptProperties, EXTR_SKIP);
    }
    //$modx->log(modX::LOG_LEVEL_ERROR, 'email = '.$user->get('email'));
    
    //$modx->setPlaceholder('myPlaceholder', 'this is my placeholder data'.$ext);
    
    $eventname = $modx->event->name;
    
    $modx->log(modX::LOG_LEVEL_ERROR,'System event running = ' . $eventname);
    }



    no errors in the log, any ideas?
      *** Not just websites, we also create signage, banners, print, trade show displays and more! ***

      Sean Kimball CLP, CLS.
      Technical Director / Sr. Developer | BigBlock Studios
      ._______________________________________________.
      Bigblock Studios http://www.bigblockstudios.ca Web site design & development.
      27-1300 King Street East. Box 167 Oshawa, Ontario L1H8J4 Canada.
      phone/fax: 905-426-5525
      • 3749
      • 24,544 Posts
      It means the $modx object is not getting instantiated. It might be a bad path or URL in core/config/config.inc.php or in one of the three config.core.php files (root, manager/includes, connectors).

      I assume you've tried deleting all files and the core/cache directory and clearing you browser cache and cookies.
        Did I help you? Buy me a beer
        Get my Book: MODX:The Official Guide
        MODX info for everyone: http://bobsguides.com/modx.html
        My MODX Extras
        Bob's Guides is now hosted at A2 MODX Hosting
        • 26503
        • 620 Posts
        Quote from: BobRay at Jun 25, 2013, 02:11 AM
        It means the $modx object is not getting instantiated. It might be a bad path or URL in core/config/config.inc.php or in one of the three config.core.php files (root, manager/includes, connectors).

        I assume you've tried deleting all files and the core/cache directory and clearing you browser cache and cookies.

        Yes - been through all that & checked the paths, no dice.

        I'm jumping a couple of versions - so I think I will try an incremental update next.
          *** Not just websites, we also create signage, banners, print, trade show displays and more! ***

          Sean Kimball CLP, CLS.
          Technical Director / Sr. Developer | BigBlock Studios
          ._______________________________________________.
          Bigblock Studios http://www.bigblockstudios.ca Web site design & development.
          27-1300 King Street East. Box 167 Oshawa, Ontario L1H8J4 Canada.
          phone/fax: 905-426-5525
          • 26503
          • 620 Posts
          Still no luck - is there anyway to run the setup in debug mode or something?
            *** Not just websites, we also create signage, banners, print, trade show displays and more! ***

            Sean Kimball CLP, CLS.
            Technical Director / Sr. Developer | BigBlock Studios
            ._______________________________________________.
            Bigblock Studios http://www.bigblockstudios.ca Web site design & development.
            27-1300 King Street East. Box 167 Oshawa, Ontario L1H8J4 Canada.
            phone/fax: 905-426-5525
            • 3749
            • 24,544 Posts
            I'm an idiot. Just disable that plugin in the DB in the modx_site_plugins table, then run setup again.

            Let me know what plugin 12 is in case its one of mine.
              Did I help you? Buy me a beer
              Get my Book: MODX:The Official Guide
              MODX info for everyone: http://bobsguides.com/modx.html
              My MODX Extras
              Bob's Guides is now hosted at A2 MODX Hosting
              • 26503
              • 620 Posts
              Interesting - it looks like maybe a testing plugin or something that just logs the current running event .... definitely not one of yours and obviously not actually doing anything useful.

              *disabled*

              well, the update worked but now I'm getting these:
              Fatal error: Call to a member function getOption() on a non-object in /home/canad036/public_html/core/xpdo/om/xpdoobject.class.php on line 692




              Quote from: BobRay at Jun 25, 2013, 07:18 PM
              I'm an idiot. Just disable that plugin in the DB in the modx_site_plugins table, then run setup again.

              Let me know what plugin 12 is in case its one of mine.
                *** Not just websites, we also create signage, banners, print, trade show displays and more! ***

                Sean Kimball CLP, CLS.
                Technical Director / Sr. Developer | BigBlock Studios
                ._______________________________________________.
                Bigblock Studios http://www.bigblockstudios.ca Web site design & development.
                27-1300 King Street East. Box 167 Oshawa, Ontario L1H8J4 Canada.
                phone/fax: 905-426-5525
                • 3749
                • 24,544 Posts
                That means the xPDO object is not instantiated, but I have no idea how that could happen other than maybe a corrupted or missing file in the update or something stuck in the MODX or browser cache.
                  Did I help you? Buy me a beer
                  Get my Book: MODX:The Official Guide
                  MODX info for everyone: http://bobsguides.com/modx.html
                  My MODX Extras
                  Bob's Guides is now hosted at A2 MODX Hosting
                  • 41574
                  • 14 Posts
                  Hey Sean did you ever figure out why you were getting that fatal error:

                  Fatal error: Call to a member function getOption() on a non-object in /home/canad036/public_html/core/xpdo/om/xpdoobject.class.php on line 692

                  I am having the same problem.
                    • 37210
                    • 131 Posts
                    Quote from: greyskymedia.los at Aug 28, 2013, 06:26 PM
                    Hey Sean did you ever figure out why you were getting that fatal error:

                    Fatal error: Call to a member function getOption() on a non-object in /home/canad036/public_html/core/xpdo/om/xpdoobject.class.php on line 692

                    I am having the same problem.

                    Hi greysky,

                    I think I had the same issue as you and it was a server configuration problem. Get in touch with your host provider.

                    It was quite a stressful time for us when we had this issue! But our server provider created a php.ini file in our root folder with the following:

                    date.timezone = "Australia/Perth"
                    extension=pdo.so
                    extension=pdo_sqlite.so
                    extension=sqlite.so
                    extension=pdo_mysql.so
                    


                    Now obviously, change the info to reflect your timezone. It's not exactly a magic solution so it might not work for you..but in our specific case it seemed to fix everything.
                      • 3749
                      • 24,544 Posts
                      The pdo extensions are enabled on most hosts but the date/timezone think is a common issue. Did you try setting the MODX date_timezone System Setting to Australia/Perth?
                        Did I help you? Buy me a beer
                        Get my Book: MODX:The Official Guide
                        MODX info for everyone: http://bobsguides.com/modx.html
                        My MODX Extras
                        Bob's Guides is now hosted at A2 MODX Hosting