We launched new forums in March 2019—join us there. In a hurry for help with your website? Get Help Now!
MODX Community Forums Archive

event log stopped working

    • 14883 ☆ A M B ☆
    • 450 Posts
    jrotering Reply #1, 15 years, 10 months ago
    I was debugging a plugin, and was referring back to the event log - clearing and refreshing it after each change. Did this about 8 or 10 times, and then... my event log suddenly stopped logging. Nothing in the database table. Is there some setting I could have inadvertently triggered, or anything I should look for that would turn logging back on?
      • 14883 ☆ A M B ☆
      • 450 Posts
      jrotering Reply #2, 15 years, 10 months ago
      I still haven’t figured this out. I copied my plugin to another Revo installation (both are 2.0.4pl2) and I managed to trigger the same problem. Nothing whatsoever is being logged to the error log now. I was looking at my php error logs on the server, and there were some syntax errors in my plugin that were causing heap dumps and other errors. I’ve fixed those now, and the plugin isn’t generating any errors... but there still isn’t ANYTHING being written to the MODx error log.

      Are there any settings anywhere, or any conditions that could be present that would stop the error log table from accepting entries?
        • 22303 MODX Staff
        • 10,725 Posts
        opengeek Reply #3, 15 years, 10 months ago
        Some configurations can trap errors and send them to the Apache error log by default, but MODx can usually override this behavior. Worth a check again, just in case.

        Otherwise, it may just be that the logic of the code is simply not generating an error, nor doing what you expect.
          Jason Coward
          Chief Architect @ MODX
          http://www.jasoncoward.com | http://twitter.com/drumshaman | https://github.com/opengeek
          • 14883 ☆ A M B ☆
          • 450 Posts
          jrotering Reply #4, 15 years, 10 months ago
          Quote from: OpenGeek at Nov 24, 2010, 11:59 AM

          Some configurations can trap errors and send them to the Apache error log by default, but MODx can usually override this behavior. Worth a check again, just in case.

          Otherwise, it may just be that the logic of the code is simply not generating an error, nor doing what you expect.

          I have several snippets that used to write to the error log regularly... and also I’m used to seeing lots of lines with some sort of JSON warning/error that I can’t quite recall at the moment but I think maybe is TinyMCE-related... anyway, none of that has been showing up at all. Not a single thing in the MODx error logs of two different instances on this server for well over a week.

          My php.ini file is set as follows:
          error_reporting  =  E_ALL & ~E_NOTICE
display_errors = Off
display_startup_errors = Off
log_errors = On


          and my index.php file(s) (which I haven’t modified) have the default:
          $modx->setLogLevel(modX::LOG_LEVEL_ERROR);
$modx->setLogTarget('FILE');

/* Set debugging mode (i.e. error_reporting): */
$modx->setDebug(E_ALL & ~E_NOTICE);


          I finally tried reinstalling 2.0.4pl-2 over the top on one of the instances. Still no logging going on. I really don’t know what could be causing this. My regular php error log on the server is logging ok.


            • 9674
            • 170 Posts
            Fildefer57 Reply #5, 15 years, 10 months ago
            What happened to you looks like what happemend to me with "no more quip and redirector’s contents (bug ?)" I filled today on http://modxcms.com/forums/index.php/topic,57977.0.html

            Philippe
              twitter : https://twitter.com/ComAmazili
              Facebook Page : https://www.facebook.com/Amazili
              Website : https://amazili-communication.com