Menu
Community /Pin to ProfileBookmark
@NogDogNov 17.2009 — #What did you change it to?
Did you restart the web server after you changed it?
PS: Have you considered fixing your code so that it doesn't generate those errors/notices? @NogDogNov 17.2009 — #But what is the exact value assigned to error_reporting. For example is it something like:
If so, to not report notices you'd need:
And of course you could set display_errors to off so that no error messages get displayed and instead only get logged to the error log.@NogDogNov 18.2009 — #And I'll still reiterate: the best solution is to fix your code so that no notices or warnings are generated. While the code may "work", any such notices indicate that it is not optimal.
When you get to the production environment, I recommend turning display_errors off, as it can be a security hole to have any system-generated error message displayed to the user, which may give them an insight as to what your script is doing.
Lastly, for any line of code that you expect to possibly throw an error message and you are willing to live with it as is, you can use the "@" operator to suppress errors for the rest of that line, though most of the time that's probably just lazy programming. (Of course, most programmers are lazy. ? )
How to off Notices in windows vista
Hi,
I have new version of wamp and it keeps on showing on Notices how can i get rid of them. Please help i guess they can be put off from php.ini file but how can anyone help me on this thanks.
Sign in
to post a comment8 Comments(s) ↴
0
@NogDogNov 17.2009 — #Did you restart the web server after you changed it?
PS: Have you considered fixing your code so that it doesn't generate those errors/notices?
0
@NogDogNov 17.2009 — #But what is the exact value assigned to error_reporting. For example is it something like:<i>
</i>error_reporting [color=red]E_ALL[/color]
If so, to not report notices you'd need:
<i>
</i>error_reporting E_ALL & ~E_NOTICE
And of course you could set display_errors to off so that no error messages get displayed and instead only get logged to the error log.
0
@NogDogNov 18.2009 — #And I'll still reiterate: the best solution is to fix your code so that no notices or warnings are generated. While the code may "work", any such notices indicate that it is not optimal. When you get to the production environment, I recommend turning display_errors off, as it can be a security hole to have any system-generated error message displayed to the user, which may give them an insight as to what your script is doing.
Lastly, for any line of code that you expect to possibly throw an error message and you are willing to live with it as is, you can use the "@" operator to suppress errors for the rest of that line, though most of the time that's probably just lazy programming. (Of course, most programmers are lazy. ? )