Turning on display_errors in WAMP – Video Tutorial

August 30, 2007

PHP Video Tutorial

Hi,

Within a WAMP installation, I ran into a little issue today when trying to change php.ini’s ‘display_errors’ property.

By default WAMP installs with ‘display_errors’ to ‘Off’:

display_errors = Off

… This is a pain-in-the-ass setting when trying to write new PHP code because errors don’t get displayed in the browser window; you have to go to the log file.

So like any good nerd, I popped open php.ini and made the change:

display_errors = On

Problem is that it didn’t work. I soon discovered that WAMP was using ANOTHER php.ini file on my machine!

Solution:

Run phpinfo() and look for the property: ‘Loaded Configuration File’

This will tell you what php.ini WAMP is using.

I created a video (with more details on WAMP and php.ini) for those who like to watch.

Thanks,

Stefan Mischook

www.killerphp.com

5 Responses

  1. Pingback: PHPDeveloper.org

  2. Pingback: developercast.com » Stefan Mischook’s Blog: Turning on display_errors in WAMP - Video Tutorial

  3. Michael Girouard Author August 31, 2007 at 6:17 pm

    Good cast.

    I think it’s important to mention that display_errors should only be set to ‘on’ under development servers and should always be ‘off’ under production.

    Also, display_errors will not show parse errors by default. If you want PHP to render parse errors on your development server, you’ll need to set the error_reporting directive to an appropriate level.

    I personally find it easier to leave them both set to the default, secure setting as they are shipped with PHP. When in development, I include a ‘development.php’ file which has the following content.

    Cheers,
    Mike G.

  4. Michael Girouard Author August 31, 2007 at 6:18 pm

    I guess you set wordpress to not render anything within brackets… The content for the file is as follows:

    ini_set(‘display_errors’, ‘on’);
    error_reporting(E_ALL);

  5. Stefan Mischook Author August 31, 2007 at 6:28 pm

    “I think it’s important to mention that display_errors should only be set to ‘on’ under development servers and should always be ‘off’ under production.”

    Agreed.

To Top