Ah ha, think I found what happened after perusing some of the godaddy help topics:
Troubleshooting Deprecated PHP Functions
Date Submitted: 8-3-2012 by Go Daddy
This was helpful!
Not what you’re looking for?
We want your feedback!
Topic: Web Hosting
As we announced in in June, we are discontinuing support for PHP 4.
As a constantly developing language, PHP versions include functions that become deprecated (cease to exist or change the expected result of the function). These changes can result in warnings and error messages when you update your version of PHP.
Modifying the error reporting helps treat symptoms of deprecated functions, but it’s not the same as updating the code. Keeping your code updated is the preferred solution.
Common issues can arise when using deprecated functions:
Functions just flat-out stop working — Very few functions get completely removed from PHP. But sometimes it happens. Applications or scripts might rely on functions that are simply no longer supported. PHP.net has a page for each function describing its use, and includes information about when or if a function was deprecated or removed. In these cases it suggests which functions could be used instead, or which functions were meant to replace the deprecated version.
Warning messages display about deprecation — These warning messages don’t normally interfere with site functionality. However, in some cases they might disrupt the process of the server sending headers. This can cause login issues (cookies/sessions don’t get set properly) or forwarding issues (301/302/303 redirects use headers to instruct the browser).
If you receive errors regarding function deprecation, the following two methods can tell PHP to simply stop mentioning deprecated functions or coding:
You can add the following line to your php5.ini file:
error_reporting = E_ALL & ~E_DEPRECATED & ~E_NOTICE
Or you may add the following line to a PHP file itself, inside existing or new <?php ?> tags:
error_reporting(E_ALL & ~E_DEPRECATED & ~E_NOTICE);
This leaves on important PHP error reporting such as Fatal Errors or Parser Errors. These errors flat-out prevent a file from working correctly, so it’s best you leave them on. Fatal Errors are things such as “I tried to perform that command but I’m not sure what that command is” or “I ran out of time to work on running these instructions”. Parser Errors are things such as “I was not expecting this comma in the middle of the line” or “Why is there a variable here, I was already done with this line.”
If somehow all else fails and you need to turn off all error messages, you can add the following line to your php5.ini file:
display_errors = Off
or you may add the following line to a PHP file itself, inside existing or new <?php ?> tags:
error_reporting(0);
This means you’ll get no indication of why a file failed to perform its expected function, so typically this is not the solution you’re looking for.
Finally, if you are interested in suppressing a specific error message, you can do so for even a single time that a function is used. For instance, running this in PHP 5.3:
split(‘l’,‘hello’);
gives you the error message
Deprecated: Function split() is deprecated in /test.php on line 1
This error message conveniently tells you exactly what line uses the offending function.
So if you update the line to say:
@split(‘l’,‘hello’);
There is no more error message. The @ symbol instructs the function to try, and not report if it fails.
For more information, see:
Setting the levels in-code
Setting error reporting levels in php.ini
Suppressing individual errors with @
I will try the above.
