w3tc new relic = htaccess 500 internal server error

  • jwf1776

    (@jwf1776)


    10 years, 11 months ago

    i tried to setup new relic but it keeps killing my site.

    i found the new relic api key and pasted that into w3tc, i put my domain name in for the application name: http://www.korucomputing.com and then i can’t access wordpress (500 error).

    i figured out the if i remove the lines below from the htaccess then wordpress works again.
    # BEGIN W3TC New Relic core
    php_value newrelic.appname ‘www.korucomputing.com’
    # END W3TC New Relic core

    once my site is accessible, if i return to any w3tc plugin config page, i get the 500 error again (it’s like it instantly sticks the new relic lines into the htaccess again, even if i was trying to edit a different w3tc setting)

    the other thing i found weird was that if i uninstall w3tc and even delete the files, and then re-install w3tc, the new relic settings like the api key re-appear without any interaction… shouldn’t it forget the old settings

    http://wordpress.org/extend/plugins/w3-total-cache/

Viewing 1 replies (of 1 total)
  • Thread Starter jwf1776

    (@jwf1776)

    10 years, 11 months ago

    update, this was partly me being a n00b and not realizing that the new relic integration requires several pieces of configuration outside w3tc… as opposed to the cloudflare setup which only requires an account and api key.

    having said that, the w3tc/rew relic integration logic might be improved by refusing to “enable” the new relic features if the prerequisites aren’t in place.

    also enhance the w3tc config page to draw attention to the fact that new relic integration requires several pieces of configuration outside w3tc

Viewing 1 replies (of 1 total)
  • The topic ‘w3tc new relic = htaccess 500 internal server error’ is closed to new replies.