Error 500 after install

  • Resolved crystalfyre

    (@crystalfyre)


    2 years, 11 months ago

    Hello!

    I just wanted to let you know, that upon first install and activation of the Breeze Caching plugin, your plugin attempts to set some variables in the .htaccess of the WordPress directory which causes an internal server Error on some servers.

    The issue seems to be when your plugin automatically adds “SetEnv” variables (SetEnv BREEZE_GZIP_ON 1), when the server in question does not have the “mod_env” Apache Module extension installed on their server.

    There is a high chance that this may be the case in a lot of websites, as is the case with mine, and by not having “mod_env” installed the “SetEnv” causes a HUGE server error, crashing it with an Error 500.

    Perhaps there is something you can do before adding this line to the .htaccess to test to see if “mod_env” is enabled before adding those lines to the .htaccess? Perhaps not assuming that it is installed on every server?

    Thanks. ??

Viewing 2 replies - 1 through 2 (of 2 total)
  • Plugin Author adeelkhan

    (@adeelkhan)

    you may handle it by the following line of code

    <IfModule mod_env.c>
SetEnv BREEZE_GZIP_ON 1
</IfModule>

<IfModule mod_env.c>
SetEnv BREEZE_BROWSER_CACHE_ON 1
</IfModule>
    Thread Starter crystalfyre

    (@crystalfyre)

    Yes, that is the kind of fix I’m talking about. ??

    Put that into the plugin as well, just in case you have other people who download your plugin and don’t have “mod_env” installed on their servers. That way you won’t have people who have their websites suddenly killed after installing a plugin like I did. I guarantee they won’t know what hit them, so I can’t wait to see this fix you made make it into the plugin for the future.

    Have a great day!

Viewing 2 replies - 1 through 2 (of 2 total)
  • The topic ‘Error 500 after install’ is closed to new replies.

Tags