+- GetSimple Support Forum (http://get-simple.info/forums)
+-- Forum: GetSimple (http://get-simple.info/forums/forumdisplay.php?fid=3)
+--- Forum: General Questions and Problems (http://get-simple.info/forums/forumdisplay.php?fid=16)
+--- Thread: A note on PHP errors and warnings (/showthread.php?tid=6826)
A note on PHP errors and warnings - shawn_a - 2014-10-14
If you are seeing php warnings or errors on a production(live) site, this means your host has php error_reporting enabled. You should NEVER have php reporting enabled on a production site, as it can leak sensitive information to hackers testing your sites security.
You should properly disable php errors in your hosts configuration. If you cannot control this or figure out how, you can attempt to have GetSimple disable them for you by enabling the GSSUPRESSERRORS directive in your gsconfig.php file. (as of 3.3x)
You can still enable errors with GS debug mode, and find them in your error.log file in data/other/logs/
A quick note about php errors.
There are typically 3 types.
php warnings
php notify
php error
warnings and notifications are to tell you something is not right or missing somewhere, and could potentially be a problem or will be in the future. Neither of these are fatal errors, they are mostly harmless, however if you have them enabled they can interfere with the layout of your pages, and prevent cookie headers from working properly, preventing logins and all kinds of other issues. But all in all, they are NOT errors and are typically no reason for concern.
php errors, are fatal and will stop all processing in your files. These identify a bug or fatal configuration issue, or incompatibility with a plugin for example.
it is typically useful to indicate all these errors when reporting issues, but the fatal errors are the most important ones and likely the cause of empty page results or things not saving or behaving as expected.
One other side effect of having errors enabled, is that they can cause excessive logging to error logs on a production site and cause your site to stop responding.
In these cases check your error.log and delete it if too large, it should be recreated.