Preventing automated htaccess additions from taking a site down when using suexec?

[etcio]

I've been working on a Wordpress installation for a client, and have W3 Total Cache installed. I also have the New Relic daemon installed and configured through W3TC.

The problem that I'm having is that it tries to set newrelic.appname using php_value in htaccess. This, of course causes the site to immediate get internal server errors. The proper place to put it is in the .user.ini file of course, and this can be done manually.

However, when you are in W3TC, there is a warning that the newrelic settings aren't configured correctly (because they're commented out, or you've deleted them) and it will immediately revert them back without further action by the client.

Effectively, if they click on that warning, the server goes down.

Is there any way to prevent this behavior?

 

[tvcnet]

Did you ever figure this one out?

I've been working on a Wordpress installation for a client, and have W3 Total Cache installed. I also have the New Relic daemon installed and configured through W3TC.

The problem that I'm having is that it tries to set newrelic.appname using php_value in htaccess. This, of course causes the site to immediate get internal server errors. The proper place to put it is in the .user.ini file of course, and this can be done manually.

However, when you are in W3TC, there is a warning that the newrelic settings aren't configured correctly (because they're commented out, or you've deleted them) and it will immediately revert them back without further action by the client.

Effectively, if they click on that warning, the server goes down.

Is there any way to prevent this behavior?

 

[cPanelMichael]

Hello

It sounds like this is a flaw with the plugin for WordPress. You may want to consult with the developer to alert them of this issue.

Thank you.

 

[quietFinn]

Is there any way to prevent this behavior?

You could try this:

chmod 400 .htaccess