We launched new forums in March 2019—join us there. In a hurry for help with your website? Get Help Now!
    • 28042 ☆ A M B ☆
    • 24,524 Posts
    I'm getting a stupid warning about the MySQL client mismatch, and the hosting tech support isn't going to do anything about it. I've got this in index.php as well as in the config.inc.php file
    error_reporting(E_ALL & ~E_NOTICE);

    I can't seem to find the right way to add E_WARNING to the exclusion. I can do
    error_reporting(0);

    but I don't want to disable all error reporting, just get rid of the client mismatch error.
      Studying MODX in the desert - http://sottwell.com
      Tips and Tricks from the MODX Forums and Slack Channels - http://modxcookbook.com
      Join the Slack Community - http://modx.org
      • 3749
      • 24,544 Posts
      Try something like this:


      error_reporting(E_ALL & ~(E_STRICT|E_NOTICE|E_WARNING|E_DEPRECATED));
        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
        • 28042 ☆ A M B ☆
        • 24,524 Posts
        Seems to work for the Manager, no error there with that. But the front-end still throws the big, ugly error. I was able to stop that by adding @ to the line making the actual connection (this is with Evo 1.0.12) in the dbapi.mysql.class.inc.php file but I really don't like hacking into the core like that.
                  if($persist!=0) $this->conn = @mysql_pconnect($host, $uid, $pwd);
                  else            $this->conn = @mysql_connect($host, $uid, $pwd, true);
         
          Studying MODX in the desert - http://sottwell.com
          Tips and Tricks from the MODX Forums and Slack Channels - http://modxcookbook.com
          Join the Slack Community - http://modx.org