The output buffer with gz handler is a good idea.
I don't feel there is anything wrong with using @ for stopping errors. PHP would not have included this feature if they did not want us to use it.
I only use it for vaiables that and might not be set.
error reporting full on is good because it shows you coding mistakes and can stop hackers exploiting open variables.
I don't feel there is anything wrong with using @ for stopping errors. PHP would not have included this feature if they did not want us to use it.
I only use it for vaiables that and might not be set.
error reporting full on is good because it shows you coding mistakes and can stop hackers exploiting open variables.
OpenCart®
Project Owner & Developer.
well, that's what i don't understand, why not turn error reporting off (in the admin config) for a live site? I'm talking about php's function to display errors or to silently log them. the only good time to use @ is when you want to be lazy and allow an error rather than trap it. for example, instead of doing something like if (!$var) { do or don't do something } you'd prefer @$var.
I would recommened that the error_reporting is E_ALL and have an optional option that when site is live that it is turned off.
The reason is so you can address any issues and not be a lazy programmer.. @ works but it not a good habbit.. I suggest the following as a suggestion maybe. It's rough but it shows the point
or if you doing if statements if(is_defined('content',$value)){
Just have the function look after the error checking isset and comparasion etc.
The reason is so you can address any issues and not be a lazy programmer.. @ works but it not a good habbit.. I suggest the following as a suggestion maybe. It's rough but it shows the point
or if you doing if statements if(is_defined('content',$value)){
Just have the function look after the error checking isset and comparasion etc.
Who is online
Users browsing this forum: No registered users and 2 guests