• Fastest Cache has been working great for a couple weeks until I disabled it for a bit and then when I enabled it again my site immediately showed a 500 Error message.

    I contacted my hosting and they fixed it. They said the issue was that Fastest Cache caused a config issue in the .htaccess file.

    Here is a transcript from the chat:

    01:46:49 PM [Tom M.] This line:
    “suphp_configpath /home/bucksa7/public_html# BEGIN LBCWpFastestCache”

    Should, and now does look like:
    suphp_configpath /home/bucksa7/public_html
    # BEGIN LBCWpFastestCache

    01:47:05 PM [Myself] Ok so the problem happened as soon as I enabled the Fastest Cache plugin
    01:47:52 PM [Myself] I see its enabled now, so it must not be breaking the site
    01:48:49 PM [Tom M.] That makes sense. For what ever reason it didn’t put the carriage return in when it modified the .htaccess file to add it’s code in there.

    The page I need help with: [log in to see the link]

Viewing 5 replies - 1 through 5 (of 5 total)
  • Plugin Author Emre Vona

    (@emrevona)

    is the problem solved when you disable the “Browser Caching” option and save the settings?

    Thread Starter clarkag

    (@clarkag)

    Well the problem seems to be solved after the tech support fixed the PHP code. Since then I am able to disable and enable as normal.

    I just want to make you aware of the issue in case it happens again or to someone else.

    Plugin Author Emre Vona

    (@emrevona)

    ok. please do not enable the “browser caching” option.

    Thread Starter clarkag

    (@clarkag)

    Ok I can disable that option.

    However, doesn’t that defeat the purpose of a caching plugin? I understood it’s job was to cache the page files on a user’s browser after the page loads for the first time.

    Plugin Author Emre Vona

    (@emrevona)

    you can add the rule manually later.

Viewing 5 replies - 1 through 5 (of 5 total)
  • The topic ‘Fastest Cache caused a config issue in the .htaccess file.’ is closed to new replies.