How to enable display_errors with .htaccess

Question

I have the following environment on one server:

dev.domain.com for the development
test.domain.com for the tests
www.domain.com is the working production

For the development environment I would like to see all PHP errors (including parse errors). Unfortunately the PHP configuration is quite strict. It does not allow to set the display_errors within the PHP file. It means that

ini_set("display_errors", 1);

and all variants of it are not working. The following works fine within the .htassess file:

php_flag display_errors "1"

Thus, my idea was to do something like this:

if(HOST==dev.domain.com) {
    php_flag display_errors "1"
}

I tried SetEnvIf, RewriteCond, IfDefine and other variants, but without success.

Is there somehow a way to do it?

You should always be able to change display_errors via ini_set() — Phil
– Phil, Commented Mar 24, 2011 at 3:56
Do you have access to httpd.conf or at least to configuration of virtual hosts? — zerkms
– zerkms, Commented Mar 24, 2011 at 3:57

Peter Mortensen · Accepted Answer · 2020-04-22 03:09:01Z

1

As I mentioned in my comment, you can set display_errors using ini_set(). However, it won't help with parse errors as noted in the manual

Can you make changes to the VirtualHost sections for each site? If so, add the php_flag in there.

If not, why not just have a different .htaccess file per site?

edited Apr 22, 2020 at 3:09

Peter Mortensen

31.4k22 gold badges110 silver badges134 bronze badges

answered Mar 24, 2011 at 4:01

Phil

166k25 gold badges265 silver badges269 bronze badges

Sign up to request clarification or add additional context in comments.

6 Comments

Dennis Over a year ago

I am able to set the display_errors using ini_set(). You're right, It just don't show the parse errors. If I am doing it in the .htaccess, I can see them.

Dennis Over a year ago

I am managing i with a git,with three (dev/test/production) branches. I even want to handle the .htaccess file with it.

Phil Over a year ago

@Dennis If you have three branches, why not have the different .htaccess files in each branch?

Dennis Over a year ago

To avoid mistakes during the merging. if I change something in the .htaccess of the dev, it must pass thought all branches.,,

Phil Over a year ago

@Dennis It shouldn't if you change and commit it in dev, then merge the other branches and change and commit.

|

Matt Campbell · Accepted Answer · 2013-03-15 04:09:32Z

0

Just ignore the .htaccess file within your version control system and create a separate file for each set of settings on each server.

answered Mar 15, 2013 at 4:09

Matt Campbell

3192 silver badges10 bronze badges

Collectives™ on Stack Overflow

How to enable display_errors with .htaccess

2 Answers 2

6 Comments

Comments

Your Answer

Linked

Hot Network Questions

Collectives™ on Stack Overflow

2 Answers 2

6 Comments

Comments

Your Answer

Sign up or log in

Post as a guest

Linked

Related