Which error_reporting levels do you use, if at all?

**Cups** · Nov 13, 2008 11:31

Following on from something i just read in another thread, one way of dealing with irksome error messages (E_WARNING) is to simply turn them off.

It is a surprisingly simple way of simplifying some of your code I suppose.

I have been running display_errors, and E_ALL for a few years now and never really give it a second thought.

Now I am only talking about on your development environment, and I am not particularly concerned about how you log Live server errors.

So, as you are working away do you display errors or not?
To what level?
Do you log them as well?

Let me know either way, and why you do that.

**spikeZ** · Nov 13, 2008 11:35

2 for development
0 for production

**Raju Gautam** · Nov 13, 2008 11:41

error_reporting(E_ALL);
display_error = ON;

**Cups** · Nov 13, 2008 11:43

Too quick, hadn't got my poll together...

I run on E_ALL and display the errors. I recently started using an Ajax framework on a CMS so the errors ruin my headers, so on that I am just logging errors, not notices, but generally I work with errors displaying.

Are Notices a bad thing?

Edit:

Doh, that's two of you ...

**Mittineague** · Nov 13, 2008 12:11

Usually I just use the default to start with. Then once things are cleaned up and if I'm feeling adventurous I'll run it with STRICT to

ensure the best interoperability and forward compatibility of your code.

which is usually a very enlightening and humbling experience. I am blessed/cursed with a tendency towards perfectionism, and I guess at times maybe I have a bit of masochism in me as well.

I usually don't log errors during development. Except after things are fairly cleaned up and then usually only in "behind the scenes" files. i.e. scripts that don't get rendered.

**Mark Baker** · Nov 13, 2008 12:15

error_reporting(E_ALL) for development, but logged with a full stack trace by a custom error handler;
error_reporting(E_ERROR) in production environments

**RDFrame** · Nov 13, 2008 16:17

E_ALL. I display the errors, and log the warnings and notices.

**Jake Arkinstall** · Nov 13, 2008 16:24

I display strict errors, warnings and notices in development and log them in production.

No excuse for hiding them under the rug

**spikeZ** · Nov 13, 2008 16:34

Originally Posted by arkinstall

I display strict errors, warnings and notices in development and log them in production.

No excuse for hiding them under the rug

Absolutely, fix em - dont hide em!

**Mounty** · Nov 13, 2008 17:05

Originally Posted by arkinstall

I display strict errors, warnings and notices in development and log them in production.

No excuse for hiding them under the rug

That's my preference too!

Here's the code I generally use:

Code:

error_reporting(E_ALL);        //report all errors, warnings
ini_set('display_errors','0');    //prevent errors displaying to browser
ini_set('log_errors','on');       //set error logging to on
ini_set("ignore_repeated_errors","1");       //ignore repeated errors in loops
ini_set('error_log',"../logs/errors.txt");  //set an error logging file path

**crmalibu** · Nov 13, 2008 23:09

During development I run E_ALL, and usually display them in addition to logging.

**tdolsen** · Nov 14, 2008 03:05

Display errors during developement. I log them in production, and at the same time output a custom error message if the page fail to load as expected.

Allways E_ALL.

**Cups** · Nov 14, 2008 03:47

Originally Posted by Mounty

Here's the code I generally use:

Code:

error_reporting(E_ALL);        //report all errors, warnings
ini_set('display_errors','0');    //prevent errors displaying to browser
ini_set('log_errors','on');       //set error logging to on
ini_set("ignore_repeated_errors","1");       //ignore repeated errors in loops
ini_set('error_log',"../logs/errors.txt");  //set an error logging file path

Is there a reason why you don't just set these in your development machine's php.ini file?

**tdolsen** · Nov 14, 2008 06:12

Could be that he don't have access to the ini. I have had that problem in some projects.

**Cups** · Nov 14, 2008 06:45

No access to php.ini on a development machine? That seems hard to believe.

Then again, maybe Mounty needs to override the ini settings on the live server.

**SpacePhoenix** · Nov 14, 2008 12:45

At the moment I'm using: E_ALL, E_STRICT, E_NOTICE, E_ERROR, E_WARNING, E_PARSE, E_CORE_ERROR, E_CORE_WARNING, E_COMPILE_ERROR, E_COMPILE_WARNING, E_USER_ERROR, E_USER_WARNING, E_USER_NOTICE, E_RECOVERABLE_ERROR, E_DEPRECATED as I want to be 100% sure that absolutely all errors, notices, strict and anything else is displayed so i can fix them all and make sure I have less bugs and more secure code.