• Resolved Super Interactive

    (@superinteractive)


    We use a setup where WP has its own directory. The new version of the plugin is displaying a notice to create a file called “w3tc-wp-loader.php” for Minify and support requests to work.

    We use Capistrano for deploys, which creates a new path for every release, and changes the location of the wp-load.php file with each deploy. i.e.:

    /home/example.com/releases/20130301150418/app/www/wp/wp-load.php

    If I put a relative path to wp-load.php file in w3tc-wp-loader.php, it works, but W3TC keeps displaying the notice.

    Hopefully you can fix this in a next release of your excellent plugin.

    https://www.ads-software.com/extend/plugins/w3-total-cache/

Viewing 3 replies - 1 through 3 (of 3 total)
  • Plugin Contributor Frederick Townes

    (@fredericktownes)

    Disable the loader verification by adding define('DONOTVERIFY_WP_LOADER', true); to wp-config.php. The information is in the plugin’s FAQ.

    Thread Starter Super Interactive

    (@superinteractive)

    Doh! Thanks, I wasn’t aware.

    Anthony Scolaro

    (@plmcomputerservices)

    Thanks for asking! I deploy with Capistrano and keep wordpress in it’s own directory and didn’t think to check the FAQ first.

Viewing 3 replies - 1 through 3 (of 3 total)
  • The topic ‘Issue with w3tc-wp-loader.php’ is closed to new replies.